Hi all,
By taking latest available SNAPSHOT versions of jars and adding a few
more additional jars I have managed to generate the client artefacts. I
am a much relieved man now :).
But I do have a few questions.
jsr173_api or stax-api ?. pom is in the name stax-api but jar name has
jsr173_api !!!. Some pom files have dependency to stax-api and others
to jsr173_api. Both are same, but how come this discrepancies?
I had to add jsr181-api.jar to my decencies. Otherwise I got
java.lang.NoClassDefFoundError: javax/jws/WebParam$Mode. It doesn't seem
to be available in maven repository, or is it known in another name?
See for more info.
http://forums.java.net/jive/thread.jspa?threadID=19646&tstart=0
________________________________
From: Vijesh A.V. [mailto:vijesh.av_at_emirates.com]
Sent: 02 November 2006 18:07
To: users_at_jax-ws.dev.java.net
Subject: RE: Jars required for JAX-WS Client
Last errors are gone when replaced the jars (took latest) in these two
cases
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.1EA1</version>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>2.1EA1</version>
</dependency>
But now I am getting the following error
[wsimport] Consider using <depends>/<produces> so that wsimport won't
do unnecessary compilation
[wsimport] command line: wsimport -d
D:\CALOGI\WebServices\cls-export-wsclient\target -keep -verbose
D:\CALOGI\WebServi
ces\cls-export-wsclient/src/main/wsdl/GuideLineService.wsdl -b
D:\CALOGI\WebServices\cls-export-wsclient\src\main\resour
ces\custom-client.xml
[wsimport] error: SCD "x-schema::wsa" didnt match any schema component
[wsimport] line 6 of
http://dummy.pseudo-schema#schema2
com.sun.istack.SAXParseException2: SCD "x-schema::wsa" didnt match any
schema component
at
com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModel
er.java:211)
at
com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:87
)
at
com.sun.tools.ws.processor.Processor.runModeler(Processor.java:81)
at
com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:557)
Any idea please?
________________________________
From: Vijesh A.V. [mailto:vijesh.av_at_emirates.com]
Sent: 02 November 2006 15:15
To: users_at_jax-ws.dev.java.net
Subject: RE: Jars required for JAX-WS Client
I have started off with the jars available from java.net repository
(changed to maven2 structure locally).
<dependency>
<groupId>javax.xml.bind</groupId>
<artifactId>jaxb-api</artifactId>
<version>2.1EA1</version>
</dependency>
<dependency>
<groupId>javax.xml.soap</groupId>
<artifactId>saaj-api</artifactId>
<version>1.3</version>
</dependency>
<dependency>
<groupId>javax.xml.stream</groupId>
<artifactId>jsr173_api</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>javax.xml.ws</groupId>
<artifactId>jaxws-api</artifactId>
<version>2.1</version>
</dependency>
<dependency>
<groupId>com.sun.xml.stream</groupId>
<artifactId>sjsxp</artifactId>
<version>1.0</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>com.sun.xml.stream.buffer</groupId>
<artifactId>streambuffer</artifactId>
<version>0.2</version>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-impl</artifactId>
<version>2.0.3</version>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-libs</artifactId>
<version>1.0.5</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>com.sun.xml.bind</groupId>
<artifactId>jaxb-xjc</artifactId>
<version>2.0.3</version>
</dependency>
<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-tools</artifactId>
<version>2.1EA1</version>
</dependency>
<dependency>
<groupId>com.sun.xml.ws</groupId>
<artifactId>jaxws-rt</artifactId>
<version>2.1EA1</version>
</dependency>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0_09</version>
<scope>system</scope>
<systemPath>${java.home}/../lib/tools.jar</systemPath>
</dependency>
Now I have almost all jars that found in the lib directory of jax-ws ri.
I have added an ant task in my pom.xml. This is what I gets
-------
[wsimport] command line: wsimport -d
D:\CALOGI\WebServices\cls-export-wsclient\target -keep -verbose
D:\CALOGI\WebServi
ces\cls-export-wsclient/src/main/wsdl/GuideLineService.wsdl -b
D:\CALOGI\WebServices\cls-export-wsclient\src\main\resour
ces\custom-client.xml
[wsimport] error: JAXB version attribute must be "1.0"
[wsimport] line 4 of
http://dummy.pseudo-schema#schema2
[wsimport] error: The "schemaBindings" customization is not associated
with any schema element.
[wsimport] line 7 of
http://dummy.pseudo-schema#schema2
com.sun.istack.SAXParseException2: The "schemaBindings" customization is
not associated with any schema element.
at
com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModel
er.java:211)
at
com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:87
)
at
com.sun.tools.ws.processor.Processor.runModeler(Processor.java:81)
--------
The error is same without custom binding......
What is it about dummy.pseudo-schema ???
Am I using wrong set/version of jars?......
The wsdl file and custom binding file I have used working fine with
jax-ws ri and glassfish.......
________________________________
From: Vijesh A.V. [mailto:vijesh.av_at_emirates.com]
Sent: 31 October 2006 17:27
To: users_at_jax-ws.dev.java.net
Subject: Jars required for JAX-WS Client
Hi all,
I am planning to use JAX-WS 2.0 based web services client to communicate
with services (which are part of another application and will be
implemented in Axis2, JAX-RPC because of the legacy nature of it).
Though I had experimented with both JAX-WS RI and Glassfish, but I am
bit confused about two things
1) What all jars are required for JAX-WS client code generation as well
as for running it.
2) From where should I take it? from JAX-WS RI 2.1 distribution or from
Glassfish distribution?
From where should I take wsimport, wsgen, xjc tools? (We are using
jdk1.5)
Are the jars available in java.net maven repository. (I am using
maven2).
Our application runs in Weblogic9.1. And the application we are
communicating with runs in Weblogic8.1 (that's why we needs web services
in the first place)
Regards,
Vijesh