I have difficulty in downloading/building axis2 source from SVN due to proxy setting.
Can I use the jar in this nightly build? http://cvs.apache.org/dist/axis2/nightly/axis2-0.94-SNAPSHOT.zip Thanks, Tao -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 04, 2006 2:32 PM To: [email protected] Subject: Re: [Axis2 0.93] Namespace to Java source package names Already fixed in latest SVN :) thanks, dims On 1/4/06, Nathaniel Auvil <[EMAIL PROTECTED]> wrote: > i am using the: org.apache.axis2.wsdl.WSDL2Java, Class to generate the > XMLBeans, Service skeleton, and descriptors from my WSDL file. I do > not understand the use of namespaces here. When it generates my code, > it does not use the namespaces defined in my WSDL for the package names. > > For example, if the targetnamespace of my wsdl file is: > "http://xml.mycompany.com/foo/services";, i would expect the service > skeletons to be at: "com.mycompany.xml.foo.services ". This is how > Axis 1.2 functions. However, the service code was put in a package named: > "codegen". > > I saw there was a "-p" option to specify the package name directly, > which i did and was able to get the desired behavior. Is Axis2 > intended to have this behavior? My vote would be for the default > behavior to use the namespace of the wsdl for the service files as it > does in Axis 1.2 > > Another thing i saw was the package naming of the generated XMLBeans. > This also does not follow the targetnamespace to package naming. For > example if my xml type is defined in a targetnamespace of: " > http://xml.mycompany.com/foo/types/intf";, the axis2 build generates it > in a package named: > "codegen.databinding.com.mycompany.foo". My vote would be to have it > in a package: "com.mycompany.xml.foo.types.intf " -- Davanum Srinivas : http://wso2.com/blogs/
