hi dims, thanks, i'll try in that direction.
grtz -wil- Op donderdag 12-07-2007 om 11:47 uur [tijdzone -0400], schreef Davanum Srinivas: > Wim, > > Please download a nightly and use WSDL2Java from ant or command line, > you can add "-Etypesystemname my_type_system" as mentioned here. > > https://issues.apache.org/jira/browse/AXIS2-926#action_12508868 > > Just run wsdl2java through each of the wsdl's and make sure it > generates the same type system name using the above mentioned switch. > After that you can package it up in a separate jar and share it > between your stubs. > > thanks, > dims > > On 7/12/07, Wim Lambrecht <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I have a bunch of WSDL files which all use (/share) the same xml-element > > definities (XSD's) for their payloads. > > I use the "axis2-wsdl2code-maven-plugin" to generate the necessary > > clientside code, which includes xmlbeans bindings for everything. > > That works fine (*) but it is a per-wsdl approach. > > > > Is it possible to give the "axis2-wsdl2code-maven-plugin" a LIST of wsdl > > files so that the xmlbeans bindings get only generated ones ? > > > > Or if not, is there some way to share the xmlbeans generated code amongst > > all generated axis client stubs ? > > > > This is really a blocker for me (and i don't want to abandone the axis2 > > approach). > > > > thx > > -wil- > > > > (*) except for the '"axis2-wsdl2code-maven-plugin" which don't get wrapped > > the jars, along with the xmlbeans XmlObject classes. And since they belong > > together they should be together in the resulting artifact IMHO (or at least > > in a separate JAR). > > > > **** DISCLAIMER **** > > http://www.schaubroeck.be/maildisclaimer.htm > > **** DISCLAIMER **** http://www.schaubroeck.be/maildisclaimer.htm --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
