[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
It worked. I made changes in sample web service as in addressing sample. Changed Clienthandler,java IQDN instance Now the request and response of web services are linked through a reference parameter in ws-addressing Thanks for the support View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4222851#4222851 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4222851 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
I downloaded src distribution of jbossws 3.1.0 and is working on sample from native-tests. org.jboss.test.ws.jaxws.samples.ws=addressing package. It is written as test case, which files are at server side and which files are to be at client end. the Clienthandler.java is reference to statefulendpointImpl.IQDN variable and should it be at server side? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4222495#4222495 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4222495 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Yes, now I need to set the Addressing attributes in the soap message. In the user guide, http://jbossws.jboss.org/mediawiki/index.php/JAX-WS_User_Guide#WS-Addressing code snippets are provided. Where is the sample available? How can i set the id View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4221163#4221163 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221163 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Download JBossWS source distribution. There are many tests and samples about WS-Addressing. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4221169#4221169 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4221169 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
How does your WSDL looks like? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220807#4220807 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220807 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
definitions name=SampleWebService targetNamespace=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xs:schema targetNamespace=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; version=1.0 xmlns:tns=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; xmlns:xs=http://www.w3.org/2001/XMLSchema; xs:element name=helloWorld type=tns:helloWorld/ xs:element name=helloWorldResponse type=tns:helloWorldResponse/ xs:complexType name=helloWorld xs:sequence xs:element minOccurs=0 name=inputString type=xs:string/ /xs:sequence /xs:complexType xs:complexType name=helloWorldResponse xs:sequence xs:element minOccurs=0 name=return type=xs:string/ /xs:sequence /xs:complexType /xs:schema soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ soap:operation soapAction=/ soap:body use=literal/ soap:body use=literal/ soap:address location=http://200.201.202.159:8080/SampleWebService/SampleWebService/ View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220808#4220808 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220808 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
sorry, i missed the quotes tag. anonymous wrote : | definitions name=SampleWebService targetNamespace=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; xmlns=http://schemas.xmlsoap.org/wsdl/; xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/; xmlns:tns=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; xmlns:xsd=http://www.w3.org/2001/XMLSchema; | | xs:schema targetNamespace=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; version=1.0 xmlns:tns=http://www.jboss.org/jbossws/ws-extensions/wsaddressing; xmlns:xs=http://www.w3.org/2001/XMLSchema; |xs:element name=helloWorld type=tns:helloWorld/ |xs:element name=helloWorldResponse type=tns:helloWorldResponse/ |xs:complexType name=helloWorld | xs:sequence | xs:element minOccurs=0 name=inputString type=xs:string/ | /xs:sequence |/xs:complexType | |xs:complexType name=helloWorldResponse | xs:sequence | xs:element minOccurs=0 name=return type=xs:string/ | /xs:sequence |/xs:complexType | /xs:schema | | | | | | | | | | | | | | | | | soap:binding style=document transport=http://schemas.xmlsoap.org/soap/http/ | |soap:operation soapAction=/ | | soap:body use=literal/ | | | | soap:body use=literal/ | | | | | |soap:address location=http://200.201.202.159:8080/SampleWebService/SampleWebService/ | | | | | | View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220809#4220809 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220809 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Sorry, but I can't reproduce your problem :( I executed the following command: $JBOSS_HOME/bin./wsconsume.sh -k -v a.wsdl | tee test.log and all passes without problems. Here's my test.log output: parsing WSDL... generating code... org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorld.java org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorldResponse.java org/jboss/jbossws/ws_extensions/wsaddressing/ObjectFactory.java org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebService.java org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebServiceInterface.java org/jboss/jbossws/ws_extensions/wsaddressing/package-info.java compiling code... javac -d /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output -classpath :/opt/java/jdk/sun/jdk1.5.0_17/lib/tools.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/activation.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/getopt.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/wstx.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossall-client.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/log4j.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/mail.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-spi.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-common.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-framework.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/clie! nt/jaxws-tools.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxws-rt.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/stax-api.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-api.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-impl.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-xjc.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/streambuffer.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/stax-ex.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/javassist.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jboss-xml-binding.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-client.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-core.! jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/c lient/jbossws-native-jaxws.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxws-ext.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxrpc.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-saaj.jar -Xbootclasspath/p:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxws.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-api.jar /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorld.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorldResponse.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/ObjectFactory.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/buil! d/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebService.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebServiceInterface.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/package-info.java How did you install JBossWS 3.1.0 to JBossAS 4.2.3? Can you describe me your installation process? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220810#4220810 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220810 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Thanks for trying out. The following are the steps I installed JBOSSWS 3.1.0 GA 1. Downloaded and extracted zip file. 2. renamed ant.properties 3. set target container - jboss423 4. ant deploy-jboss423 - completed successfully. 5. ant tests - all tests failed. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220836#4220836 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220836 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Also, I have both jdk 1.5.0.17 and jdk 1.6.0, I tried with both jdks same error, View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220837#4220837 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220837 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
This is my jbossws 3.1.0 GA Install.log, i run it again Buildfile: build.xml target-jboss423: prepare: init: [echo] integration.target=jboss423 undeploy-jboss423: [delete] Deleting directory /root/jboss-4.2.3.GA/server/default/deploy/jbossws.sar [delete] Deleting directory /root/jboss-4.2.3.GA/server/default/deploy/juddi-service.sar prepare-deploy: deploy-structure-jboss42: [delete] Deleting directory /root/jbossws-native-bin-dist/output/deploy-jboss423 check-parameters: deploy-jbossws-endorsed: deploy-jbossws-native42: [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/bin [copy] Copying 8 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/bin [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/client [copy] Copying 23 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/client [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/lib [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/lib [copy] Copying 8 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/lib [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar [copy] Copying 11 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar [unzip] Expanding: /root/jbossws-native-bin-dist/deploy/lib/jbossws-native-management.war into /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar/jbossws-management.war [copy] Copying 1 file to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar/jbossws.beans [copy] Copying 5 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar/META-INF [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/juddi-service.sar [unzip] Expanding: /root/jbossws-native-bin-dist/deploy/lib/juddi-service.sar into /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/juddi-service.sar [copy] Copying 2 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/juddi-service.sar deploy-jboss423: [copy] Copying 79 files to /root/jboss-4.2.3.GA [copy] Copied 30 empty directories to 2 empty directories under /root/jboss-4.2.3.GA BUILD SUCCESSFUL Total time: 3 seconds View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220838#4220838 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220838 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
In ant.properties, i changed jbossws.integration.target=jboss423 # The JBoss settings jboss.server.instance=default jboss.bind.address=200.201.202.159 and run the tests below is portion of log 2009-03-25 15:10:34,174 DEBUG [sun.rmi.loader:65] main: name = org.jnp.server.NamingServer_Stub, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,183 DEBUG [sun.rmi.loader:65] main: name = java.rmi.server.RemoteStub, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,191 DEBUG [sun.rmi.loader:65] main: name = java.rmi.server.RemoteObject, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,219 DEBUG [sun.rmi.transport.tcp:65] main: localHostKnown = false, localHost = 127.0.0.1 2009-03-25 15:10:34,274 DEBUG [sun.rmi.client.ref:65] main: get connection 2009-03-25 15:10:34,275 DEBUG [sun.rmi.transport.tcp:65] main: Version = 2, ep = [127.0.0.1:0] 2009-03-25 15:10:34,277 DEBUG [sun.rmi.transport.tcp:65] main: created local endpoint for socket factory null on port 0 2009-03-25 15:10:34,279 DEBUG [sun.rmi.transport.tcp:65] main: create connection 2009-03-25 15:10:34,280 DEBUG [sun.rmi.transport.tcp.proxy:65] main: host: 200.201.202.159, port: 1098 2009-03-25 15:10:34,285 DEBUG [sun.rmi.transport.tcp:65] main: local host set to 200.201.202.159 2009-03-25 15:10:34,308 DEBUG [sun.rmi.loader:65] main: name = java.rmi.dgc.Lease, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,310 DEBUG [sun.rmi.loader:65] main: name = java.rmi.dgc.VMID, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,312 DEBUG [sun.rmi.loader:65] main: name = [B, codebase = , defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,314 DEBUG [sun.rmi.loader:65] main: name = java.rmi.server.UID, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,316 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:34,320 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,322 DEBUG [sun.rmi.transport.tcp:65] main: create reaper 2009-03-25 15:10:34,326 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,340 DEBUG [sun.rmi.loader:65] main: name = org.jnp.interfaces.MarshalledValuePair, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,344 DEBUG [sun.rmi.loader:65] main: name = java.rmi.MarshalledObject, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,348 DEBUG [sun.rmi.loader:65] main: name = [B, codebase = , defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,349 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:34,350 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,351 DEBUG [sun.rmi.loader:65] main: interfaces = [org.jboss.jmx.adaptor.rmi.RMIAdaptor, org.jboss.jmx.adaptor.rmi.RMIAdaptorExt], codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,401 DEBUG [sun.rmi.loader:65] main: name = java.lang.reflect.Proxy, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,416 DEBUG [sun.rmi.loader:65] main: name = org.jboss.proxy.ClientContainer, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,423 DEBUG [sun.rmi.loader:65] main: name = org.jboss.proxy.ClientMethodInterceptor, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,426 DEBUG [sun.rmi.loader:65] main: name = org.jboss.proxy.Interceptor, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,434 DEBUG [sun.rmi.loader:65] main: name = org.jboss.proxy.SecurityInterceptor, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,437 DEBUG [sun.rmi.loader:65] main: name = org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,464 DEBUG [sun.rmi.loader:65] main: name = org.jboss.invocation.InvokerInterceptor, codebase = http://200.201.202.159:8083/;, defaultLoader = sun.misc.launcher$appclassloa...@17943a4 2009-03-25 15:10:34,520 DEBUG [sun.rmi.loader:65] main: name = org.jboss.util.id.GUID, codebase =
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
And when you leave jboss.bind.address=localhost? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220892#4220892 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220892 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Thank God. It worked.. 1. Used wsconsume.sh from another version of jboss mobicents-all-1.2.0.CR3-jboss-4.2.3.GA-0812022325 2. Included all jars that you referred in the compile command. 3. Added wsdl4j.jar, xercesImpl.jar The sample worked!! With web service trace enabled, i get the log 2009-03-25 18:15:17,684 TRACE [org.jboss.ws.core.MessageTrace] Incoming Request Message env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/' env:Header xmlns:wsa='http://www.w3.org/2005/08/addressing' wsa:ActionhelloWorld/wsa:Action /env:Header env:Body ns1:helloWorld xmlns:ns1='http://www.jboss.org/jbossws/ws-extensions/wsaddressing' KRS, Great Job /ns1:helloWorld /env:Body /env:Envelope 2009-03-25 18:15:17,694 TRACE [org.jboss.ws.core.MessageTrace] Outgoing Response Message env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/' env:Header xmlns:wsa='http://www.w3.org/2005/08/addressing' wsa:Tohttp://www.w3.org/2005/08/addressing/anonymous/wsa:To wsa:Actionhttp://www.jboss.org/jbossws/ws-extensions/wsaddressing/SampleWebServicePort/helloWorldResponse/wsa:Action /env:Header env:Body ns2:helloWorldResponse xmlns:ns2='http://www.jboss.org/jbossws/ws-extensions/wsaddressing' Hello Welcome, KRS, Great Job /ns2:helloWorldResponse /env:Body /env:Envelope Thanks a lot.. Richard Now, next step is provide an id to identify the request and get the id in response. Also, if i could work out a POC for Records Management Framework, that would be great. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220901#4220901 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220901 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Finally success ;) View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220931#4220931 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220931 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
First of all always use up2date JBossWS version (3.1.0.GA currently) Your problem can be caused by the fact that you are running the client code from your IDE and you're using different SOAP stack and not JBossWS as you think. To verify my claim use JBOSS_HOME/bin/wsrunclient to run your client code. If it will work, you're using different SOAP stack and you need to configure your IDE properly. View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220479#4220479 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220479 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
Thanks for the response I upgraded jbossWS 3.1.0 GA I tried to use wsconsume.sh to generate the stub classes, also wsrunclient.sh to check. Now i get a different error. anonymous wrote : | r...@mobax0159:~/jboss-4.2.3.GA/bin# ./wsconsume.sh -k -v http://200.201.202.159:8080/SampleWebService/SampleWebService?wsdl | parsing WSDL... | | | Error: Could not import. (use --verbose to see full traces) | java.lang.NoSuchMethodError: org.w3c.dom.Document.setDocumentURI(Ljava/lang/String;)V | at com.sun.tools.ws.wsdl.parser.DOMForest.parse(DOMForest.java:197) | at com.sun.tools.ws.wsdl.parser.DOMForest.parse(DOMForest.java:147) | at com.sun.tools.ws.wsdl.parser.MetadataFinder.parseWSDL(MetadataFinder.java:102) | at com.sun.tools.ws.wsdl.parser.WSDLParser.parse(WSDLParser.java:141) | at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:126) | at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:182) | at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:230) | at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222) | at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80) | oh God. Will i complete this? View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220800#4220800 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220800 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBossWS] - Re: WS-Addressing in native stack
any body there to help out View the original post : http://www.jboss.org/index.html?module=bbop=viewtopicp=4220122#4220122 Reply to the post : http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4220122 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
