You should be able to use command line svn (make sure u set the as described in http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.1)
"svn co https://svn.apache.org/repos/asf/webservices/axis2/trunk/java/ axis2" Then once u get the code, you can add entries in etc/project.properties (documented here - http://maven.apache.org/maven-1.x/reference/properties.html) maven.proxy.host=xxx maven.proxy.port=yyy thanks, dims On 1/6/06, Liu, Tao <[EMAIL PROTECTED]> wrote: > 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/ > -- Davanum Srinivas : http://wso2.com/blogs/
