As a follow-up, I was on track with my original thoughts. The error
in the ActionScript code was registering CalendarVO to
java.util.Calendar. It should have been
java.util.GregorianCalendar. java.util.Calendar is an abstract class
and doesn't have a public constructor.
Would've been nice i
It would be more like replacing the Date objects in your WorkGroupVO
with vars of type Number, set to calendar.getTime().getTime() on the
Java side. This may or may not be an option in your case, but it
would completely avoid object conversion issues between Java and AS.
--- In flexcoders@yaho
Doug,
Our java objects need to have dates set to type Calendar. So are you
suggesting that my ActionScript value objects have a setter/getter?
Something like:
class com.beans.WorkGroupVO {
public var workGroupID:String;
public var startDate:Date;
public var endDate:Date;;
static var r
Geoffrey, you may or may not find this to be helpful but I've found
it much easier to deal with times as longs than as instances of
various date classes (java.util.Date, java.sql.Date,
java.util.Calendar, etc). The timelong can be easily retrieved with
date.getTime() or calendar.getTime().getT
Could someone voice an opinion on this? Please.
--- In flexcoders@yahoogroups.com, "Geoffrey" wrote:
ENV: Flex 1.5 served from WebSphere6.1
All of our Java objects used to use java.util.Date for date
properties, but we had to convert them to java.util.Calendar. Since
Flex 1.5 doesn't suppor
No ideas? Is this something no one has tried before?
--- In flexcoders@yahoogroups.com, "Geoffrey" <[EMAIL PROTECTED]> wrote:
>
> ENV: Flex 1.5 served from WebSphere6.1
>
> All of our Java objects used to use java.util.Date for date
> properties, but we had to convert them to java.util.Calendar
6 matches
Mail list logo
