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

Reply via email to