Thanks for your help, Joe.
I have run the following command against my WSDL:
D:\agile\repository\wsdl>d:\javatools\axis2-1.5.1\bin\wsdl2java -d jibx
-s -uri .\ValidationCodeService.wsdl
Using AXIS2_HOME: D:\javatools\axis2-1.5.1
Using JAVA_HOME: d:\java\jdk
Retrieving document at '.\ValidationCodeService.wsdl'.
Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException
: java.lang.RuntimeException: JiBX wrapped support requires a binding
definition
to be provided using the -Ebindingfile {file-path} parameter
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:271)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: java.lang.RuntimeException: JiBX wrapped support requires a
binding d
efinition to be provided using the -Ebindingfile {file-path} parameter
at
org.apache.axis2.jibx.CodeGenerationUtility.engage(CodeGenerationUtil
ity.java:233)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.axis2.wsdl.codegen.extension.JiBXExtension.engage(JiBXExte
nsion.java:77)
at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.generate(CodeGener
ationEngine.java:224)
... 2 more
It appears to want a binding document. I read the article that you sent
me and the section of the Axis manual and found references to binding
document, but no examples of how one looks. Can you help?
Thanks!
________________________________
From: Caristi, Joe [mailto:[email protected]]
Sent: Wednesday, May 05, 2010 11:05 AM
To: [email protected]
Subject: RE: I don't get it
The missing piece is that somehow Axis2 needs to be able to translate
between XML (the Soap or Rest message on the wire) and Java classes (in
your application). This is known as data binding, and consists of code
to marshall and unmarshall the XML data. This code usually gets
generated (in one way or another) and needs to be incorporated into your
application.
Look at this article, which explains the three available choices in
detail: http://www.ibm.com/developerworks/webservices/library/ws-java3/.
The summary at the end of the article is a good starting point for
making a choice between the frameworks. We have had great success with
JiBX. We originally used ADB, but switched to JiBX for performance and
flexibility.
________________________________
From: Hehl, Thomas [mailto:[email protected]]
Sent: Wednesday, May 05, 2010 10:27 AM
To: [email protected]
Subject: I don't get it
OK, I've used Axis once before briefly and now I'm trying to use Axis2.
The problem I'm having is that the documents don't appear to be written
for me. I need some advice on how to proceed.
My situation is that after building a web application, it turns out that
we need to have heterogeneous clients accessing our application. No
problem, I thought, because I created a services layer behind the
controller. I can use axis2 to generate a WSDL for my services layer and
expose the API that way to the other clients that need to access it and
our controllers as well.
My intent had been simply to run java2wsdl on the classes in my services
jar, then wsdl2java on the resulting wsdl to build the client. Then I'd
patch these pieces together and let the web services do the
communication.
As I'm reading through the documentation, though, it talks a lot about
ADB and JiBX and AXIOM and XML beans, but doesn't appear to explain any
of them. Evidently, I'm supposed to know which of these I'm using before
selecting Axis2 as a tool.
So now I'm sort of stuck. Will someone kindly take a moment and shine a
little light, please?
Thom Hehl
Senior Development Specialist
Public Safety & Justice
Affiliated Computer Services, Inc.
A Xerox Company
1733 Harrodsburg Road
Lexington, KY 40504-3617
Tel 859.277.8800 x 144
Fax 859.277.2300
________________________________
STATEMENT OF CONFIDENTIALITY:
The information contained in this electronic message and any attachments
to
this message are intended for the exclusive use of the addressee(s) and
may
contain confidential or privileged information. If you are not the
intended
recipient, please notify WHI Solutions immediately at
[email protected],
and destroy all copies of this message and any attachments.
