[ebxmlms-develop] Using Sun's JAXM implementation: bugs?

[Mayne, P. <Pet...@ap...>]

I have Hermes configured so incoming messages are sent to a back-end HTTP
server. These messages appear to be ebXML messages. So I'm using Sun's JAXM
classes to read them in a JAXMServlet.

However, although the SOAP message can be read successfully, the ebXML
within the SOAP message cannot.

After wondering through the JAXM source code, I found two possible problems.

<problem item="1">
In the com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl class, the
namespace

	NS_URI = "http://www.ebxml.org/namespaces/messageHeader";

is being used, and therefore none of the ebXML tags are found, because the
namespaces don't match. If I change this to

	NS_URI =
"http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd";

in Sun's EbXMLMessageImpl.java, the ebXML tags are found and parsed. Why
would Sun's code be using the www.ebxml.org namespace? Is it from an older
version of the specification?
</problem>

<problem item="2">
Also in the com.sun.xml.messaging.jaxm.ebxml.EbXMLMessageImpl class, the
private timeStamp field is declared as long, and the timestamp is parsed as

	this.timeStamp = Long.parseLong(elem.getValue());

Since the timestamp in the msh-header-2_0.xsd schema is an ISO8601 string
(<element name="Timestamp" type="dateTime"/>), rather than a long, this
throws an exception. This code must be changed to parse an ISO8601 string.
</problem>

Is my understanding of these problems correct, or am I missing something?

Should these problems be reported to Sun as bugs?

Thanks.

PJDM
-- 
Peter Mayne
Technology Consultant
Spherion Technology Solutions
Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
T: 61 2 62689727  F: 61 2 62689777

The information contained in this email and any attachments to it:

(a) may be confidential and if you are not the intended recipient, any interference with, 
use, disclosure or copying of this material is unauthorised and prohibited; and

(b) may contain personal information of the recipient and/or the sender as defined 
under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to 
collect, hold and use such information and any personal information contained in a 
response to this email, for any reasonable purpose in the ordinary course of 
Spherion's 
business, including forwarding this email internally or disclosing it to a third party. All 
personal information collected by Spherion will be handled in accordance with 
Spherion's Privacy Policy. If you have received this email in error, please notify the 
sender and delete it.

(c) you agree not to employ or arrange employment for any candidate(s) supplied in 
this email and any attachments without first entering into a contractual agreement with 
Spherion. You further agree not to divulge any information contained in this document 
to any person(s) or entities without the express permission of Spherion.