The business task is to clean up the root package from
all abstract (and for an user unnecessary) classes to
provide a clean API.
I can't change the schema and I don't won't to write
customizations in an external binding file
(except of writing an customization in the binding file
like this pseudo-code:
<jaxb:schemaBindings node=".//xs:isAbstract">
<jaxb:package name="de.mypackage.abstract" />
</jaxb:schemaBindings><!--
).
Am 06.03.2009 um 11:57 schrieb Aleksei Valikov:
> Hi.
>
>> is it possible to move a class into an other package inside a JAXB-
>> Plugin?
>
> You can't move classes into a different package. You can generate them
> in a different package.
>
> What is the business task you are trying to solve?
>
> Bye.
> /lexi
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>