Hi Werner,
Sorry for not getting back to you sooner but I was home sick for a few
days and had to play "catch up" for a bit. I can certainly check out
the source code and apply any patches necessary to help. Please point me
in the right direction.
Thanks!
-- Marko
Werner Guttmann wrote:
Marko,
I will need to provide you with a custom build. Please allow for at
least a day, and I will be back with you.
If you are happy to checkout the sources, apply a patch and build
the binaries yourself, please let me know.
Werner
Marko Srdanovic wrote:
Hi,
Thank you both for your help. If there is a new build I can help to
test I would be happy to do so. Let me know what I need to do.
-- Marko
Werner Guttmann wrote:
Marko, Ralf,
there's a Jira issue that covers exactly your requirement. As far as
I remember, it includes a (working) patch that should cover
everything. Having said that, it has not been applied to the codebase
for a few reasons.
Would you be willing to test-drive a custom build with the patch
aplpied and report back your findings ? I think that this patch could
make it into the current code base within a few days, given some help
on the testing side.
Werner
Ralf Joachim wrote:
Hi Marko,
somewhere between releases 1.0 and 1.2 we had to change the java type
used for xsd:integer according to the requirements of xml schema
specification. As far as I recall we tried to implement a backward
compatibility patch after the first complaints, but I can not tell you
if that covers all releases or made it into the codebase at all. You
may
want to consult the release notes for more details on that. Let's
see if
Werner, who worked on that, can jump in and explain things in details.
The suggestion I can give you is, to use 1.0.5 release to unmarshal to
classes generated with 1.0.5.
Regards
Ralf
Marko Srdanovic schrieb:
Hi,
I have a project that is using a library which includes code generated
using castor 1.0.5. I have some xml that validates properly (in
xmlspy)
against the same version of the schema. When I try to unmarshal
the xml
using the castor 1.2 libraries, I see the an error saying
"Expecting an
Long, received instead: java.lang.Integer" (see below). From what
I can
tell, the code generated using 1.0.5 has a typeValidator = new
org.exolab.castor.xml.validators.IntegerValidator(), however the
IntegerValidator in 1.2 is really for java long types and the
IntValidator should be used.
At this point, I can't change the old libraries. Is there any simple
way of getting around this?
Thanks!
-- Marko
org.exolab.castor.xml.MarshalException: The following exception
occured
while validating field: _diagramLayout of class:
edu.mssm.crover.domain2d.rbdg.xml.RbdeDiagram: The following exception
occured while validating field: _subunitList of class:
edu.mssm.crover.domain2d.rbdg.xml.DiagramLayout: The following
exception
occured while validating field: _spacer of class:
edu.mssm.crover.domain2d.rbdg.xml.Subunit: The following exception
occured while validating field: _x of class:
edu.mssm.crover.domain2d.rbdg.xml.Spacer: Expecting an Long, received
instead: java.lang.Integer{File: [not available]; line: 65; column:
16}
at
org.exolab.castor.xml.Unmarshaller.convertSAXExceptionToMarshalException(Unmarshaller.java:761)
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Marko Srdanovic
Software Engineer, Institute for Computational Biomedicine
Weill Medical College of Cornell University
1305 York Avenue (Box 140)
New York, NY 10021
http://icb.med.cornell.edu/
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
