Please see my answers below...
-------- Original-Nachricht -------- Datum: Wed, 21 Mar 2007 17:32:26 +0530 Von: "Amila Suriarachchi" <[EMAIL PROTECTED]> An: [email protected] Betreff: Re: Data binding questions > On 3/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Thanks for fast response. Unfortunately I cannot post the WSDL due to > > legal reasons. Sorry! > > > Are you testing with the Axis2 1.1.1 or with nightly builds? > 1.1.1 > Is there a way, to integrate a generated XML beans jar (and skip the > > generation error)? > > > You should be able to interage the XML beans jar seperately. > > Does it generates the Skelton and stub classes correctly? > No, generation stops immediately and no classes are generated. > If not try some thing like this to generate stub and skelton correctly. > Remove all the elements except the elements which are directly call by the > wsdl messages. > then remove the inner parts of the elements and complex types of the > remaining elements as well. > basically you keep minimal set of elements to comple the wsdl. > > So if you generate the code now it should generate the stub and skelton > classes correctly. since there only simple complex and elements (I hope > you > got my point). I will try to remove all parts from WSDL, which are not directly part of the service interface. After that I will use the already generated XMLBeans jar, containg the "real" beans. I wonder, if this will work reliantly. Would you recommend to use Axis2 (1.1.1) in production? > then integrate the correct classes by generating them seperately. > > One other question in Xfier case what it generates when you data bind with > xmlbeans? With XFire I have to generate XMLbeans before and add them to their ANT generation-task classpath. As result, a service interface using XMLBeans is generated (and other stub stuff). > > -------- Original-Nachricht -------- > > Datum: Wed, 21 Mar 2007 10:09:42 +0000 > > Von: "Paul Fremantle" <[EMAIL PROTECTED]> > > An: [email protected] > > Betreff: Re: Data binding questions > > > > > Hi > > > > > > A couple of suggestions. Firstly - we would really like it if you > > > could post the WSDL as a JIRA (bug report) so that we can fix the ADB > > > and XMLBeans issues. > > > > > > The other option you could try is either JAXB or JIBX which are other > > > databinding frameworks that work with Axis2. > > > > > > Paul > > > > > > On 3/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > > > > update: > > > > > > > > Our given WSDL seems to be really challenging. With ADB, attributes > > are > > > missing in the generated classes. With XMLBeans, everything is > generated > > > fine. Therefore I must use XMLBeans. Is there any way to use an > existing > > > xmlbeans jar with axis2 (due to generation problem mentioned in my > > previous > > > post). > > > > > > > > -------- Original-Nachricht -------- > > > > Datum: Wed, 21 Mar 2007 09:57:00 +0100 > > > > Von: [EMAIL PROTECTED] > > > > An: [email protected] > > > > Betreff: Data binding questions > > > > > > > > > Hi, > > > > > > > > > > I have some questions about data binding: > > > > > > > > > > We have a rather complex wsdl, which does not work with axis 1.x > > > > > WSDL2Java. Therefore we are planning to move to a newer SOAP > engine. > > > > > > > > > > Our partner recommends to use XFire with XMLbeans, but I want to > > give > > > Axis > > > > > 2 a try, too. If I use XMLbeans binding, WSDL2Java crashes with > some > > > > > unresolved references in WSDL during generation. XMLBeans single > Ant > > > task > > > > > (org.apache.xmlbeans.impl.tool.XMLBean) works without any > problems! > > > There seems > > > > > to be a problem with XMLBeans integration into WSDL2Java. > > > > > > > > > > - Can I use custom generated XMLBeans-jar (by own XMLBeans ant > task) > > > for > > > > > axis2 (like XFire does)? > > > > > > > > > > - Generally speaking, would you recommend to use ADB or XMLBeans? > We > > > do > > > > > not need XMLBeans in out other application layers. So the decision > > > would only > > > > > depend on Axis2. > > > > > > > > > > Thanks for answers! > > > > > -- > > > > > "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... > > > > > Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > > > > "Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ... > > > > Jetzt GMX TopMail testen: www.gmx.net/de/go/mailfooter/topmail-out > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > Paul Fremantle > > > VP/Technology, WSO2 and OASIS WS-RX TC Co-chair > > > > > > http://bloglines.com/blog/paulfremantle > > > [EMAIL PROTECTED] > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > > "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... > > Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Amila Suriarachchi, > WSO2 Inc. -- "Feel free" - 5 GB Mailbox, 50 FreeSMS/Monat ... Jetzt GMX ProMail testen: www.gmx.net/de/go/mailfooter/promail-out --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
