|
Hello,
I have a problem using Castor classes generated with an older Castor version using the latest Castor release. The problem is that I use a scheme which imports elements from another scheme. When marshalling with the older Castor version no namespace prefix is used in these imported elements. When using the latest Castor release all elements are tagged with a generated namespace prefix : "ns[1..x]:".
My problem is that we use a report tool which transforms xml into Pdf or Word docs and this tool must be trained on the xml elements it can expect. When namespace prefixes appear in the xml the report tool can't handle them and I can't train the the tool to handle "ns[1..x]:". Making it even worse : since we're just a couple of weeks away from a major release and I run into problems trying to generate Castor objects using the latest Castor version (naming problems : use a binding file) the only option left is to drop the latest Castor release from the build and use the older version. (someone on the development team commited the latest Castor version not knowing that the Report compont is very dependent on the specific xml format) Part of the problem is a lack of knowlegde of Xml schemes and namespaces on my part. Does anyone have a suggestion ?
Part of the scheme xsd : declaration of the scheme namespaces and imports : <xs:schema targetNamespace="http://www.leanapps.com/schemas/laa" xmlns="http://www.leanapps.com/schemas/laa" xmlns:xsr="http://www.leanapps.com/schemas/lifereportparameters" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified"> <xs:import namespace="http://www.leanapps.com/schemas/lifereportparameters" schemaLocation="../parameters/LifeReportParameters.xsd"/>
Greetings Arie Roy
|
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-user
