|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Werner Guttmann - 29/Mar/06 01:33 PM
Just wondering whether there's a particular reason why you are executing this against 0.9.6 ?
If I were you, I'd have a look at the release notes (available at http://castor.org/release-notes.html
 ). While it's quite obvious that in the recent past (e.g. all 1.0M? builds) not many XML issues have been fixed, the same is not true for e.g. 0.9.6 and 0.9.7. In other words, I'd consider 0.9.5 a bit outdated ... ;-(. > When I create the java classes using source generator, it creates classes for the included xsd each time.
As far as I know (and my knowledge is quite limited wrt Castor XML ... ;-( ), changing your include statements to be an import statement should do the trick. I honestly don't see the problem with your second question. If you are using a bindings file, everything is fine, correct ? If you do not use a bindings file, you are getting ..what exactly ? Warnings from the source generator ? Compilation errors ? Can you please be a bit more specific ?
Just another short comment, as I have amended the JIRA notification scheme in use for Castor.
Vinaya, can you please attach the missing FDXShared.xsd ?
Downgrading from critical to major. When you have a complex type and an element with the same name you'll get that cyclic inheritence complaint unless you use a mapping file.
Eddie, how do we go about this now that ...
a) we have automatic class name conflict resolution. Assuming we have a true solution for this problem, we point the user to the docs and ask if this resolves their problem.
Sound reasonable? Eddie, is there anything we should do to e.g improve the docs ?
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Test
Open
Major
Binding file for xsd:enumeration not generating expected classes
