On 12/12/06, Thilo Frotscher <[EMAIL PROTECTED]> wrote:
> Think of it as this. The skeleton is not dependant on any Axis2 > Specific libraries (unless you use either ADB or no databinding - even > in the ADB case the helper mode will cause plain java beans to be > generated with no traces of Axis2 specifics). How can you use the Helper Mode with WSDL2Java? The relevant section in the documentation is empty (or white characters on white background :-)) -> http://ws.apache.org/axis2/1_1/adb/adb-advanced.html#helper
use -Eh option
If you do have a Axis1 > skeleton already written then you can actually just place that class > and make it work in this case (perhaps with minor modifications but no > big changes that span the whole set of generated classes) If I don't use ADB or AXIOM,
AXIOM is not a data binding framwork. the remaining options would be XML Beans,
JiBX, JaxMe or JAXB-RI. However these were not exactly the most popular options for XML data binding with Axis 1.x :-)
you can't use the xml beans. but you can use the JAXB-RI. I am not sure about the jibx and JaxMe. the idea here is to generate a java file with the same name and method signatures as in axis 1.x. I will describe this later. Sorry, I still don't see how I could easily re-use an Axis 1.x skeleton.
If I use the normal RPCProvider or MsgProvider with Axis 1.x, these would pass either POJOs into my service methods or DOM objects. So this is how my method signatures would look like in an Axis 1.x skeleton. I don't understandhow I should use/configure the WSDL2Java that comes with Axis2, so that it generates a MessageReceiver which either passes POJOs or DOM objects into a skeleton.
the backword compatibility feature is not complete in 1.1. please take a build from the trunk. Here axis 1.x skelton means the generated skelton with the Axis 1.x code generation tool ( with a wsdl). This generated skelton is similar to normal axis2 generated code but have two differences. 1. have a different file name 2. Lets say we have an element as follows as an input element for an axis operation <xs:element name="AddDisputeRequest" type="ns:AddDisputeRequestType"/> the axis2 method signature is some thing like this methodName(AddDisputeRequest addDisputeRequest); and for axis 1.x methodName(AddDisputeRequestType addDisputeRequestType); As you can see axis1.x parameters are always unwraped. So when you enable the -b (backword compatibility) option it generates a same code as axis 1.x for axis 2 skelton class. So you can replace this generated file with your existing axis 1.x skelton (since they have same method signature and the file name) without doing any change to generated axis2 code. Amila -- Amila Suriarachchi, Software Engineer, WSO2 Inc.
