From: Johnson, Larry D (LJOHNSON) [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 22, 2007 11:50 AM
To: axis-user@ws.apache.org
Subject: RE: TimeZone Not Handled Properly In java.util.Date Conversions
Amiila,
We are deploying our service via POJOs. I copied a version of saaj
:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 10:54 PM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions
On 2/21/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
I downloaded the axis2-SNAPSHOT.zip
:50 AM
To: axis-user@ws.apache.org
Subject: RE: TimeZone Not Handled Properly In java.util.Date Conversions
Amiila,
We are deploying our service via POJOs. I copied a version of saaj into the
axis2 lib directory and the problem was corrected. I just wanted to let you
know
I think deepal may help you on this.
Please attache your java class as well to that jira.
--
Amila Suriarachchi,
WSO2 Inc.
@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions
On 2/21/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the
test. When the server tries to return the SOAP message, I
?
Regards,
Larry Johnson
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 20, 2007 12:32 AM
To: axis-user@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions
On 2/20/07, Johnson, Larry D (LJOHNSON
On 2/21/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
I downloaded the axis2-SNAPSHOT.zip distribution and tried to rerun the
test. When the server tries to return the SOAP message, I now receive the
following exception:
Caused by: java.lang.NoClassDefFoundError:
Amila,
He's just missing axis2-saaj-api jar in this war and is complaining
that the default build script is not copying that jar
thanks,
dims
On 2/21/07, Amila Suriarachchi [EMAIL PROTECTED] wrote:
On 2/21/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
I downloaded
: TimeZone Not Handled Properly In java.util.Date Conversions
On 2/16/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
I did not specify what platform we are using. We are currently using
Axis2 v1.1, Java v1.5 and Tomcat 5.5.20.
I have also run a similar test using the .NET framework
@ws.apache.org
Subject: Re: TimeZone Not Handled Properly In java.util.Date Conversions
I recently fix this issue with adb. please check with a nightly build.
there i used the SimpleDateFormatter to pares the date values correctly
with the time zones.
On 2/16/07, Dennis Sosnoski [EMAIL PROTECTED
On 2/20/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
I have just downloaded the Axis2 v1.1.1-SNAPSHOT version and installed it.
This version has the same issue.
use http://people.apache.org/dist/axis2/nightly/axis2-SNAPSHOT.zip . I think
you have got the previous
On 2/20/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
Amila,
How do I set the nillable true on automatically generated WSDL from a
deployed POJO?
this should be automatically set. try with the latest nightly build.
Regards,
Larry Johnson
--
On 2/18/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Ah, that's because you're using an invalid format for the offset. The
schema specification says the offset has to be in the form hh:mm (where
the ':', as far as I know, is always required), such as:
2002-10-10T12:00:00-05:00. Sorry I didn't
On 2/17/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Did you actually try passing 2007-02-16T18:41:41.296+0530 to the
Utility.parseDateTime() method?
yes I tried this
System.out.println(date value 1171631501296 == + Utility.parseDateTime
(2007-02-16T18:41:41.296+0530));
and gave me the
Ah, that's because you're using an invalid format for the offset. The
schema specification says the offset has to be in the form hh:mm (where
the ':', as far as I know, is always required), such as:
2002-10-10T12:00:00-05:00. Sorry I didn't notice this before.
Is ADB currently generating
hi dennis,
I checked your parseDateTime method.
It seems that it does not works for the values like 2007-02-16T18:41:
41.296+0530. But as I understood the spec allow this type of date formates
as well. As I understood your method only supports GMT time zone values.
Lets take this piece of code.
Did you actually try passing 2007-02-16T18:41:41.296+0530 to the
Utility.parseDateTime() method? I don't know of any problems in this
area, though it's always possible you've discovered something new.
If you're able to make SimpleDateFormat work for you that's great. I
didn't say it couldn't
I did not specify what platform we are using. We are currently using
Axis2 v1.1, Java v1.5 and Tomcat 5.5.20.
I have also run a similar test using the .NET framework. The client
receives a DateTime object from the stubs. On .NET, the value returned
to the client is correct for the current
Hi Larry,
You're correct on your assumptions, that if a Calendar is being returned
it should have a consistent time value and time zone. In this case the
time zone of the Calendar should be set to UTC. That said, there are
some seriously warped issues involved - Calendar *always* works with
I recently fix this issue with adb. please check with a nightly build. there
i used the SimpleDateFormatter to pares the date values correctly with the
time zones.
On 2/16/07, Dennis Sosnoski [EMAIL PROTECTED] wrote:
Hi Larry,
You're correct on your assumptions, that if a Calendar is being
On 2/16/07, Johnson, Larry D (LJOHNSON) [EMAIL PROTECTED] wrote:
I did not specify what platform we are using. We are currently using
Axis2 v1.1, Java v1.5 and Tomcat 5.5.20.
I have also run a similar test using the .NET framework. The client
receives a DateTime object from the stubs. On
Amila Suriarachchi wrote:
...
On 2/16/07, * Dennis Sosnoski* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Hi Larry,
You're correct on your assumptions, that if a Calendar is being
returned
it should have a consistent time value and time zone. In this case the
time
22 matches
Mail list logo
