Hi, Ajith, Thank you for your answers. By your answer for the first question, I guess that the command line wsdl2java is the only choice if we want to generate XMLBeans code.
Maybe I am not clear in the second question. When I generated services.xml with the Axis2SampleDocLit.wsdl in the samples\wsdl, I found that the service name in wsdl file is Axis2SampleDocLitService and that in services.xml is Axis2SampleDocLitPortType that is, as you said, the porttype name in the wsdl file. So the services.xml and the original wsdl file do not describe the *same* *service*. The developer still need another wsdl file to describe the services in the generated services.xml file, and put it in the .aar package for deployment. Cheers, Don On 11/25/05, Ajith Ranabahu <[EMAIL PROTECTED]> wrote: > Hi Don, > Please find the answers inline > > > > 1. why are the codes generated by WSDL2JAVA in command line and the > > eclipes plug in different? The former generate very complex hirarchies > > of codes and the schema, and the latter uses the OMElement class. > > This is due to a long running unresolved problem with respect to XMLBeans > and Eclipse. We've run into a weird problem where XMLBeans fails to run > inside Eclipse so XMLBeans support is removed in the Eclipse plugin. Hence > the Eclipse plugin generates only non-databound code where as the command > line tool has the flexibility to do either. > > > 2. why are the service name in the generated services.xml and that in > > the original wsdl the different? Does that imply that the developers > > have to change them to be the same if they want to include the wsdl in > > the .aar package? > > I'm not sure what this means.The name in the service.xml is taken from the > name of the porttype in the WSDL. AFAIK you don't have to change anything in > the generated code to include the WSDL. > > > Thanks, > > > > Don > > > > > > -- > Ajith Ranabahu
