You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by vikas kumar <pv...@gmail.com> on 2005/09/28 07:38:15 UTC

[AXIS2]Usind CodeGen eclipse plugin and the commandLine tool

These might sound too naive!!!
 I tried generation server-side codes for the Axis2SampleDocLit.wsdl.
 I used both the eclipse plugin and the command line tool.
 The doubts arises on using the business logic part given in the UserGuide:
 1)It tells us to
 public org.soapinterop.xsd.EchoStringArrayReturnDocument echoStringArray
 org.soapinterop.xsd.EchoStringArrayParamDocument param2)
 {
 // the business logic
 }
whereas the generated code has the signature: *public*
org.apache.axis2.om.OMElement echoStringArray
 (org.apache.axis2.om.OMElement omElement )
 2)The schemas folder that is generated on using the command line tool was
not generated when i tried the same things using the plugin??
 This folder contains the Echo..Documents... hence i have compile time
errors..
 But can someone tell me what am i doing wrong/ what options have i left
uncheked!
 *

*

Re: [AXIS2]Usind CodeGen eclipse plugin and the commandLine tool

Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi Vikas,
It should be mentioned in the documentation (!) but the code generator
plugin does not have the databinding capability. The reason is that XMLBeans
has a classpath/parser problem when inside Eclipse so we opted not to
include the XMLBeans with the Eclipse plugin.
So please try the samples in the user guide with the command line tool only.


On 9/28/05, vikas kumar <pv...@gmail.com> wrote:
>
> These might sound too naive!!!
>  I tried generation server-side codes for the Axis2SampleDocLit.wsdl.
>  I used both the eclipse plugin and the command line tool.
>  The doubts arises on using the business logic part given in the
> UserGuide:
>  1)It tells us to
>  public org.soapinterop.xsd.EchoStringArrayReturnDocument echoStringArray
>  org.soapinterop.xsd.EchoStringArrayParamDocument param2)
>  {
>  // the business logic
>  }
> whereas the generated code has the signature: *public*
> org.apache.axis2.om.OMElement echoStringArray
>  (org.apache.axis2.om.OMElement omElement )
>  2)The schemas folder that is generated on using the command line tool was
> not generated when i tried the same things using the plugin??
>  This folder contains the Echo..Documents... hence i have compile time
> errors..
>  But can someone tell me what am i doing wrong/ what options have i left
> uncheked!
>  * *
>
>


--
Ajith Ranabahu