Generally, I modularize all of mine into specific functionality. I put the
jaxb bindings in the schema itself, giving them their own package. As such,
they each will have their own ObjectFactory as well (though I never use that
class anymore). I find that I like this 'OOP' approach much better than a
long convoluted schema.
On 4/11/06, Jorge M. <ccsdev_at_gmail.com> wrote:
>
> Hi,
> We currently use JAXB with about 5 different types of documents.
> We have defined 5 schemas. All of them are "small" schemas.
>
> a) Does anybody has pros/cons regarding the use of multiple schemas
> vs using a single schema with multiple roots allowed? I decided to use
> multiple schemas to keep them maintainable. (I don't have control over
> some of the schemas and they use the same element names but with
> different set of attributes and subelements. Creating a single schema
> may become difficult to maintain).
>
> b) I am calling xjc.bat 5 different times, therefore I get 5
> different ObjectFactory classes, each under a different java package.
> Is there a way to keep my 5 different schemas but get only a single
> ObjectFactory ?
>
>
> Thanks in advance
>
> -Jorge
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>