Thomas Bielagk wrote:
1) As the xsd is using class as a type name, it complains that it's a reserved
token in java. So I inserted something like
<jaxb:class name="Clazz"/>
and (at other locations)
<jaxb:property name="clazz"/>
in the appinfo section of the element declaration which eliminates the error.
But after compiling Eclipse shows up 5 errors saying that the Class.class could
not be found (I changed them to Clazz and everything works), but shouldn't this
be done automatically?
If you got these errors after introducing the jaxb:class, then an old
class file might still be in the Eclipse cache. Can you reproduce this
behaviour after doing a "project clean" in Eclipse? If so, please file a
bug report in Jira with a schema that demonstrates the problem.
2) Two elements end with 'Type' which does not work because I've elements of
the same name without the 'Type' ending because of JaxME generating classes
adding the Type suffix in same package. So dito, I did
<jaxb:class name="MediumTyp">
(just deleted 'e' from 'Type').
Everything goes fine then up to the point when I'm trying to use the Typ-classes. Compiler tells me
A Manager for test.MediumType is not declared.
Why?
Might be an Eclipse problem again. Is this reproducable after a project
clean? If so, same answer than above: Please file a bug report in Jira
with the sample schema.
I tried to solve such naming problems by inserting something like
<jaxb:schemaBindings>
<jaxb:nameXmlTransform>
<jaxb:elementName suffix="Element"/>
</jaxb:nameXmlTransform>
</jaxb:schemaBindings>
but this doesn't seem do do anything (all Elements keep their names without the
suffix).
That's clearly a bug. Please file a bug report in Jira with a small
sample schema.
Thanks,
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
