[JBossWS] - wsconsume ant task
by kj_newbie
Hello,
I am getting the following error when using the wsconsume ant task:
| taskdef class org.jboss.wsf.spi.tools.ant.WSConsumeTask cannot be found
|
This is my build.xml
| <path id="class.path">
| <pathelement path="C:\Program Files\Java\jdk1.5.0_19\lib\tools.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\streambuffer.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\stax-ex.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\saaj-api.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\saaj-impl.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\jbossws-common.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\jaxws-api.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\jaxws-tools.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\jaxws-rt.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\xmlsec.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\client\*.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\lib\*.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\lib\endorsed\jaxb-api.jar"/>
| <pathelement path="E:\jboss\jboss-5.0.0.GA\lib\endorsed\activation.jar"/>
| </path>
|
| <taskdef name="wsconsume"
| classname="org.jboss.wsf.spi.tools.ant.WSConsumeTask">
| <classpath path="class.path"/>
| </taskdef>
|
|
|
| <target name="generate-from-wsdl">
|
| <wsconsume
| fork="true"
| binding="wsdl/stock.xsd"
| keep="true"
| destdir="generated"
| sourcedestdir="gen-src"
| package="com.sun.samples"
| wsdlLocation="/WEB-INF/wsdl/stockservice.wsdl"
| wsdl="wsdl/stockservice.wsdl">
| </wsconsume>
|
|
| </target>
|
Can anyone point out..what ma I missing ?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237158#4237158
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237158
15 years
[JBossWS] - Re: NotSerializableException: org.jboss.ws.core.soap.SOAPFau
by lafr
I downloaded jbossws-3.0.1-native-2.0.4.GA-src
and modified src/main/java/org/jboss/ws/core/soap/SOAPFaultElementImpl.java
and
src/main/java/org/jboss/ws/core/soap/SOAPFaultImpl.java
adding an "implements java.io.Serializable" to their class definition.
This helped me to avoid the NotSerializableException.
In the scenario the problem problem occurred, there are three apps involved.
The MS Axapta system as the WS-provider.
An EAR / EJB3 app as the WS-consumer.
And an standalone java app as the driver of this (unit test) calling the EJB3 session beans via their remote interface.
The WS provider gets an exception and send this to WS consumer using a SOAPFault.
The WS consumer does not catch the exception, so it has to be transferred to the client.
And as this is a remote client the SOAPFault has to serialized.
And there the Exception occurred while trying to send the SOAPFault from JBoss-Server to the standalone client app using serialization.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237086#4237086
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237086
15 years
[JBossWS] - About WS client security (obfuscation required ?)
by agomese
Hello all,
I'm developing a client (Swing-based) software which allows to send/receive files from a JBoss AS central repository, using the JBossWS web service implementation. The JBossWS version we use is the one that is bundled within the JBoss AS version, in order to ensure compatibility.
To allow this communication, our swing-based client software is going to be released with the required JBossWS client jars (taken from the JBossAS distribution). For now, we plan to put those JBossWS jars in a "lib" folder, placed directly under the client software's root folder. The rest of the client's code (the "proprietary" part) will be obfuscated.
My question is : in your opinion, should the JBossWS client jars be protected through the same obfuscation mecanism, in order to ensure maximum security ? And BTW, does JBoss authorize such mecanism for the jars/sources they deliver ?
I tried to found related questions on this forum and on the web, but found none. Actually, we are affraid one could override the endpoint's adress by switching the original JBossWS client jars placed in the "lib" folder, in order to obtain the sent/received files from the remote AS.
We are already securing the communication through HTTPS transport, signature and encryption. However, the client keystore providing the security configuration is not going to be part of the obfuscation process, as it has to be specific per customer (please note that the JBoss AS install is specific per customer too, and so each client specific keystore is associated to a server specific keystore). We believe one could change this client keystore, create a fake endpoint with a new server keystore, and redirect traffic to this fake endpoint by changing the JBossWS client jars. But maybe are we being a bit paranoiac ?
Our configuration :
- JDK 5
- JBoss AS 4.2.3 with JBossWS native 3.0.1
Any opinion about this point would be appreciated.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236956#4236956
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236956
15 years