| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| DateTime Validation Problem |
« View previous topic :: View next topic » |
| Author |
Message
|
| PGoodhart |
 Posted: Wed Jul 28, 2004 4:26 am Post subject: DateTime Validation Problem |
 |
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Has anyone else noticed that with dateTime validation using the 'I' physical representation doesn't work properly?
We have formatted our dateTime attribute and node values in our MRM XML wireframe to accept a physical representation of "I" that is a single uppercase i. This is supposed to allow acceptance of ISO-8601 Date Time values. It does this partially and allows the following examples date times:
2004-01-01T12:12:12.12Z
2004-01-01T12:12:12
2004-01-01T12:12:12.12
2004-01-01T12:12:12.12-1:00
2004-01-01T12:12:12.12-1
It fails validation on the following:
2004-01-01T12:12:12Z
2004-01-01T12:12:12-1:00
2004-01-01T12:12:12-1
According to what we know these are valid ISO-8601 date time values. (Fractional seconds are not required.)
We are running Broker Version 5 CSD03 on AIX.
I have opened a ticket with IBM, has anyone else run into this?
I know sometimes things just get lost in the documentation and I was wondering if someone else has a solution?
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
 |
| shanson |
| Posted: Thu Jul 29, 2004 9:33 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
Patrick, you have correctly observed that 'I' processing has some limitations. In particular, the use of the Z character to specify GMT/UT is not handled properly. You will also find that on output a full ISO 8601 datetime string is output, whereas it should be dependent on the schema logical type (eg, an xsd:gYear should only output 'YYYY', and so on). We are aware of these issues and are planning to address them.
However, not all your examples are valid ISO 8601 datetimes. The standard states that only +hh:mm, -hh:mm and Z are valid timezones. Check out http://www.w3.org/TR/NOTE-datetime.
May I suggest you raise an official customer requirement for Z support. This will help expedite the fix. |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Thu Jul 29, 2004 10:56 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Thanks ever so much for the reply. I will be happy to raise an official customer requirement for Z support. I have put in the ticket and I expect the MQ development team will soon see it. Once again, thank you.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
