Rajika, I am going off of this email from a week and a half ago, please see my question below:
On Wed, Apr 22, 2009 at 11:45 PM, Manjula Peiris <[email protected]> wrote: > > On Wed, 2009-04-22 at 11:48 -0400, Bennett, Robert P wrote: > > > > > > > > Major Changes Since Last Release > > > ================================ > > > > > > 1. XPath support for Axiom XML object model > > > 2. CGI support > > > 3. Improvements to MTOM to send, receive very large attachments > > > 4. Improvements to AMQP transport > > > 5. Improvements to WSDL2C codegen tool > > > > How are Improvements to WSDL2C codegen tool a major change to Axis2/C > > version 1.6.0? > > Isn't WSDL2C part of the Axis2, which is still 1.4.1? > > The WSDL2C tool is maintained by Axis2/C community. After releasing > 1.5.0 there are some bug fixes and improvements done to the WSDL2C tool. > Further Axis2/C code also fixed for these changes. You can get these > latest modifications from an Axis2 nightly build. > > Thanks, > -Manjula. Q1: So if I wanted the latest WSDL2C, I need to get from the nightly build of the project Axis2/Java? (I have gotten the latest subversion code from the project, installed mvn, and run mvn install successfully on the Axis2/Java code) Q2: After running the mvn install, what must I do to use the newly compiled WSDL2C? What I don't see is a bin folder in the root of the Axis2/Java project, what I have is this: <DIR> etc <DIR> legal <DIR> modules <DIR> release-docs 4,506 build.xml 11,359 LICENSE.txt 1,236 NOTICE.txt 11,091 pom.xml 2,504 README.txt 39,552 release-notes.html I did read the README.TXT, which is how I knew the correct way to get mvn to build everything, but it does not talk about what I need to do to actually use any of the java code. I am assuming I need to set a class path or something, but I don't know where I should be setting the class path, not being a java expert. Sam
