Really? Using xjc with a list of several schamas that all import a
common schema I haven't had any issues, I'm assuming this is because
I'm doing the xjc build in one hit.
I am a bit disappointed that I can't compile more than one WSDL at a
time - does anyone know the reasons behind that? Is it just that the
code hasn't been written to do it, or is there a technical limitation?
The way I look at it, if you can take multiple schemas, you should be
able to take multiple schemas out of WSDLs.
cheers
dim
On 6/1/05, Vallamshettla, Anand <Anand.Vallamshettla_at_tgslc.org> wrote:
> >>>> A second, and more general question, is has anyone migrated this
> direction previously, and if so did they have any reports on any
> gotchas? We use includes and imports in our schemas, but I've done a
> schema build that seems to have worked ok so far on the early access
> version of jaxb 2.
>
> Yeah. We do have bit of schema imports too - 4 schemas importing one
> common secondary schema and the secondary importing the core schema. We
> faced some of the name collisions at first; it might be the reason that
> same names were used elsewhere. We don't know the reason and can't rule
> out the import problem. But using nameXmlTransform in binding file fixed
> all those problems.
>
>
> Anand Vallamshettla
> Texas Guatanteed Student Loan
> Ph: 512 219 5700 x4481
>
>
>
> -----Original Message-----
> From: Dmitri Colebatch [mailto:colebatchd_at_gmail.com]
> Sent: Tuesday, May 31, 2005 1:09 AM
> To: users_at_jaxb.dev.java.net
> Subject: migration from xmlbeans to jaxb?
>
> Hi list,
>
> I'm doing some initial investigation into the possibility of migrating
> from xmlbeans to jaxb. Our situation is this: we have a desktop app
> that has a lot of relatively static data that we get from the server
> as the response to a doc-centric soap call. Because we have so many
> of these calls, coupled with the relatively heavy memory use of
> xmlbeans, we're looking to retain the responses in a lighter object
> model. We don't modify these responses, but make heavy use of the
> interfaces that xmlbeans generates.
>
> So, I have one real question for now, being is there a straightforward
> way to change the generated packages (for namespace
> http://foo.com/2005/05/31) from com.foo._2005._05._31 to
> com.foo.x2005.x05.x31 (ie to match xmlbeans so we don't have to change
> a whole bunch of code)? If this isn't possible, obviously we can
> change our code, but if its easily avoidable we may as well. I've
> looked
>
> A second, and more general question, is has anyone migrated this
> direction previously, and if so did they have any reports on any
> gotchas? We use includes and imports in our schemas, but I've done a
> schema build that seems to have worked ok so far on the early access
> version of jaxb 2.
>
> cheers
> dim
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
>