From do-not-reply at jboss.com Sun Apr 1 21:58:48 2007
From: do-not-reply at jboss.com (michea)
Date: Sun, 1 Apr 2007 21:58:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot get port meta data
Message-ID: <2501455.1175479128284.JavaMail.jboss@colo-br-02.atl.jboss.com>
On jboss4.0.5+ws1.2SP1
I try to consume a webservice were artifacts and Service comes from a local wsdl packed in the war (I use wsconsume).
Well try to obtain the port I get
| javax.xml.ws.WebServiceException: Cannot get port meta data for: {http://service.workflow.mvno.manaty.org/}ConsoServiceCRMBeanPort
| at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:143)
|
Any idea ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033569#4033569
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033569
From do-not-reply at jboss.com Mon Apr 2 04:07:28 2007
From: do-not-reply at jboss.com (magnus.ahlander)
Date: Mon, 2 Apr 2007 04:07:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Activating xjc plugin
Message-ID: <28625254.1175501248476.JavaMail.jboss@colo-br-02.atl.jboss.com>
What is the suggested way for activating an xjc plugin when generating bean artifacts though wsconsume?
Specifically I would like to use the commons-lang-plugin which generates equals(), hashcode() and toString() methods.
Looking at https://jaxb2-commons.dev.java.net/commons-lang-plugin/ I understand that I need to :
i) include a jar in the classpath
ii) pass the argument 'Xcommons-lang' to the xjc task.
How can I achieve the latter using wsconsume?
Regards,
Magnus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033597#4033597
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033597
From do-not-reply at jboss.com Mon Apr 2 04:08:16 2007
From: do-not-reply at jboss.com (michea)
Date: Mon, 2 Apr 2007 04:08:16 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot get port meta data
Message-ID: <29780148.1175501296790.JavaMail.jboss@colo-br-02.atl.jboss.com>
solved: the wsdllocation was null
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033598#4033598
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033598
From do-not-reply at jboss.com Mon Apr 2 09:06:01 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Mon, 2 Apr 2007 09:06:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Mapping problem
Message-ID: <33500359.1175519161347.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have a problem with my web service client :
| try {
| //urn:bsa.ws.test
| ServiceFactory factory = ServiceFactory.newInstance();
| URL wsdlLocation = new URL("http://localhost:8080/DmexWs" + "?wsdl");
| QName serviceName = new QName("urn:bsa.ws.test", "DmexWs");
| Service service = (Service)factory.createService(wsdlLocation, serviceName);
| Call call = service.createCall();
|
| QName operationName = new QName("urn:bsa.ws.test", "getDmex");
| call.setOperationName(operationName);
|
| Integer id = new Integer(274);
| Object retObj = call.invoke(new Object[]{id});
|
| System.out.println(retObj);
| } catch (Exception e) {
| e.printStackTrace();
| }
|
The return type is "Dmex" and when I run my client I have this error:
| org.jboss.ws.WSException: Cannot obtain java type mapping for: {urn:bsa.ws.test.types}Dmex
|
I generated the jaxrpc-mapping.xml but it seems that my client doesn't use it.
What could I do for this problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033677#4033677
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033677
From do-not-reply at jboss.com Mon Apr 2 10:00:12 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Mon, 2 Apr 2007 10:00:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JbossWs and hibernate
Message-ID: <27558790.1175522412812.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have another problem.
My webservice is a methode that takes an object of type "Dmex" in the mysql data base (with Hibernate).
| public class DmexWs implements IDmexWs {
|
| SessionFactory sessionFactory = new Configuration().configure ().buildSessionFactory();
|
| public String getDmex(int id) throws RemoteException {
| CommonManager cm = HibernateEnviron.getCommonManager();
|
| Dmex dmex = (Dmex)cm.findOneId(Dmex.class, 792);
|
| return dmex.getDescription();
|
| }
|
| }
|
And when I run the client, I have this error:
| java.rmi.RemoteException: Call invocation failed with code [Client] because of: JDBC Driver class not found: com.mysql.jdbc.Driver; nested exception is:
|
Must I put the mysqlConnector jar with my class DmexWs in the .war deployed on the server?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033697#4033697
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033697
From do-not-reply at jboss.com Mon Apr 2 12:48:18 2007
From: do-not-reply at jboss.com (danielmesser)
Date: Mon, 2 Apr 2007 12:48:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - how to run the jbossws samples?
Message-ID: <13460204.1175532498419.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi,
I am running JBoss-4.0.5.GA on linux Suse 10.0.
I installed jbossws-1.2.0-SP1 using the instructions in the user guide.
To build the samples I dis the following:
- unziped the jbossws-samples-1.2.0.SP1.zip file
- cd jbossws-samples-1.2.0.SP1
- cp ant.properties.example ant.properties
- in the ant.properties file:
- set jboss40.home
- set jbossws.integration.target=jboss40
I then ran ant.
It got most of the third party libraries but failed to compile because the junit library was missing.
I downloaded junit4.1 and installed it in the thirdparty directory.
I was then able to build the samples.
Now, my general question is:
what do I do to run the tests?
I am most interested in running the jaxws/webresult sample.
I tried to run:
- ant tests
but I don't see any web services deployed in my $JBOSS_HOME/server/default/deploy directory and I don't see any services in
http://localhost:8080/jbossws/services
I also get the following exceptions:
tests-main:
[mkdir] Created dir: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/reports
[junit] Running org.jboss.test.ws.jaxrpc.samples.docstyle.bare.TrivialServiceDocBareTestCase
[junit] java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
[junit] at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
[junit] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
[junit] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
[junit] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
[junit] at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
[junit] at sun.reflect.GeneratedMethodAccessor1189.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:585)
[junit] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
[junit] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
[junit] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
[junit] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
[junit] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
[junit] at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
[junit] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
[junit] at sun.reflect.GeneratedMethodAccessor1188.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:585)
[junit] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
[junit] at sun.rmi.transport.Transport$1.run(Transport.java:153)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
[junit] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
[junit] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
[junit] at java.lang.Thread.run(Thread.java:595)
[junit] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
[junit] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
[junit] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
[junit] at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
[junit] at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
[junit] at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
[junit] at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
[junit] at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
[junit] at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
[junit] at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
[junit] at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
[junit] at $Proxy0.invoke(Unknown Source)
[junit] at org.jboss.test.ws.TestDeployerJBoss.deploy(TestDeployerJBoss.java:48)
[junit] at org.jboss.test.ws.JBossWSTestHelper.deploy(JBossWSTestHelper.java:55)
[junit] at org.jboss.test.ws.JBossWSTestSetup.setUp(JBossWSTestSetup.java:90)
[junit] at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:128)
[junit] at junit.extensions.TestSetup.run(TestSetup.java:27)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766)
[junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 0.921 sec
[junit] Test org.jboss.test.ws.jaxrpc.samples.docstyle.bare.TrivialServiceDocBareTestCase FAILED
[junit] Running org.jboss.test.ws.jaxrpc.samples.docstyle.wrapped.TrivialServiceDocWrappedTestCase
[junit] java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console
[junit] at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:97)
[junit] at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
[junit] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
[junit] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
[junit] at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
[junit] at sun.reflect.GeneratedMethodAccessor1189.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:585)
[junit] at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
[junit] at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
[junit] at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
[junit] at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
[junit] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
[junit] at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:819)
[junit] at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
[junit] at sun.reflect.GeneratedMethodAccessor1188.invoke(Unknown Source)
[junit] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[junit] at java.lang.reflect.Method.invoke(Method.java:585)
[junit] at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
[junit] at sun.rmi.transport.Transport$1.run(Transport.java:153)
[junit] at java.security.AccessController.doPrivileged(Native Method)
[junit] at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
[junit] at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
[junit] at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
[junit] at java.lang.Thread.run(Thread.java:595)
[junit] at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
[junit] at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
[junit] at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126)
[junit] at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source)
[junit] at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133)
[junit] at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365)
[junit] at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197)
[junit] at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66)
[junit] at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70)
[junit] at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74)
[junit] at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100)
[junit] at $Proxy0.invoke(Unknown Source)
[junit] at org.jboss.test.ws.TestDeployerJBoss.deploy(TestDeployerJBoss.java:48)
[junit] at org.jboss.test.ws.JBossWSTestHelper.deploy(JBossWSTestHelper.java:55)
[junit] at org.jboss.test.ws.JBossWSTestSetup.setUp(JBossWSTestSetup.java:90)
[junit] at junit.extensions.TestSetup$1.protect(TestSetup.java:22)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:128)
[junit] at junit.extensions.TestSetup.run(TestSetup.java:27)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:421)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:912)
[junit] at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:766)
[junit] Tests run: 0, Failures: 0, Errors: 1, Time elapsed: 0.688 sec
[junit] Test org.jboss.test.ws.jaxrpc.samples.docstyle.wrapped.TrivialServiceDocWrappedTestCase FAILED
Just FYI, here is the output of the build process:
Buildfile: build.xml
prepare:
[mkdir] Created dir: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/log
[touch] Creating /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/log/test.log
[echo]
[echo] -----------------------------------------------
[echo] jboss.home = /opt/jboss/jboss-4.0.5.GA
[echo] tomcat.home = /usr/java/tomcat
[echo] java.home = /usr/java/jdk1.5.0_11/jre
[echo] endorsed = /opt/jboss/jboss-4.0.5.GA/lib/endorsed
[echo] excludesfile = tests-jboss40-excludes.txt
[echo] -----------------------------------------------
thirdparty-get:
thirdparty-classpath:
thirdparty:
common-classpath:
jboss-classpath:
tomcat-classpath:
init:
wsconsume:
compile14:
compile15:
[mkdir] Created dir: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/classes
[javac] Compiling 230 source files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/classes
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
compile:
copy-resources:
[copy] Copying 1 file to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/classes
[copy] Copying 1 file to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/classes
[copy] Copying 169 files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/resources
[copy] Copying 28 files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/resources
[copy] Copied 24 empty directories to 11 empty directories under /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/resources
servicegen:
[mkdir] Created dir: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs
[zip] Building zip: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wsbpel-hello-process.zip
[copy] Copying 1 file to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs
[servicegen] Apr 2, 2007 11:44:44 AM org.jbpm.JbpmConfiguration getInstance
[servicegen] INFO: using jbpm configuration resource 'jbpm.cfg.xml'
[servicegen] Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
[servicegen] Apr 2, 2007 11:44:46 AM org.jbpm.bpel.xml.BpelReader readWsdlDocument
[servicegen] INFO: read wsdl definitions: hello.wsdl
[servicegen] Warning: Running an XSLT 1.0 stylesheet with an XSLT 2.0 processor
[servicegen] Apr 2, 2007 11:44:47 AM org.jbpm.bpel.xml.BpelReader read
[servicegen] INFO: read bpel process: hello.bpel
[servicegen] Apr 2, 2007 11:44:47 AM org.jbpm.bpel.wsdl.util.ServiceGenerator writeImportedDefinition
[servicegen] INFO: wrote interface definition: locationURI=hello.wsdl, basePath=/home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/wstools/resources/jaxrpc/samples/wsbpel/hello/WEB-INF/wsdl
[servicegen] Apr 2, 2007 11:44:47 AM org.jbpm.bpel.wsdl.util.ServiceGenerator generatePortComponents
[servicegen] INFO: wrote binding definition: hello-binding-1.wsdl
[servicegen] Apr 2, 2007 11:44:47 AM org.jbpm.bpel.wsdl.util.ServiceGenerator generatePortComponents
[servicegen] INFO: wrote service definition: hello-service.wsdl
wstools:
[mkdir] Created dir: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/wstools/java
[move] Moving 2 files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/wstools/java
[copy] Copying 51 files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/resources
[copy] Copying 10 files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/resources/jaxrpc/samples
[copy] Copied 18 empty directories to 1 empty directory under /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/resources/jaxrpc/samples
wsprovide:
generate-resources:
[javac] Compiling 2 source files to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/classes
main:
build-samples-jaxrpc:
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-docstyle-bare.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-docstyle-bare-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-docstyle-wrapped.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-docstyle-wrapped-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-dynamichandler.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-dynamichandler-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-exception.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-exception-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-handler.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-handler-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-holder.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-holder-client.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jmstransport.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jmstransport.sar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109ejb-rpc.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109ejb-rpc-client.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109ejb-doc.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109ejb-doc-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109pojo-rpc.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109pojo-rpc-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109pojo-doc.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-jsr109pojo-doc-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-message.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-message-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-mtom.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-mtom-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-oneway.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-oneway-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-rpcstyle.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-rpcstyle-client.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-secureejb.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-secureejb-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-swa.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-swa-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-store-pass-encrypt.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-store-pass-encrypt-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wsbpel-hello.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wsbpel-hello-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wssecurity-sign.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wssecurity-sign-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wssecurity-encrypt.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxrpc-samples-wssecurity-encrypt-client.jar
build-samples-jaxws:
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-asynchronous.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-context.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-context.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-context-jboss4x.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-exception.war
[copy] Copying 1 file to /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/classes/org/jboss/test/ws/jaxws/samples/handlerchain
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-handlerchain.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-handlerchain-client.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-jsr181ejb.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-jsr181pojo.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-jsr181pojo-docwrapped.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-jsr181pojo-docwrapped-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-logicalhandler-source.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-logicalhandler-jaxb.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-oneway.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-provider-jaxb.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-provider-message.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-provider-payload.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-retail.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-retail-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-soapbinding.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webmethod.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webparam.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webresult.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webservice01-jse.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webservice02-jse.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webservice03-jse.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webservice01-ejb3.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webservice02-ejb3.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webservice03-ejb3.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-servlet-client.war
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-ejb3-client.jar
[jar] Warning: skipping jar archive /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-secure.jar because no files were included.
[jar] Building MANIFEST-only jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-secure.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-secure-client.jar
[jar] Building jar: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-webserviceref-override-client.jar
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-wsaddressing.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-wseventing.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-wssecurity-encrypt.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-wssecurity-sign.war
[war] Building war: /home/dmesser/jbossws/jbossws-samples-1.2.0.SP1/output/libs/jaxws-samples-xop-doclit.war
BUILD SUCCESSFUL
Total time: 21 seconds
Thanks,
Daniel Messer
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033759#4033759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033759
From do-not-reply at jboss.com Mon Apr 2 16:49:13 2007
From: do-not-reply at jboss.com (grego122)
Date: Mon, 2 Apr 2007 16:49:13 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - XJC error: PhotoMessage.xsd ' 'is not a
part of this compil
Message-ID: <4566065.1175546953278.JavaMail.jboss@colo-br-02.atl.jboss.com>
I'm getting a 'nota part of this compilation' error using JBossWS 1.2 and Jaxb2.0 environment libraries. This works fine if I use the jaxb-ri-20070125 libraries. If I compile w/o a bindings file, it works and I'm thinking I'm having a problem with my schemaLocation in the bindings file. Here's a simplified view of my bindings file. I'd be grateful for any suggestions. Do you know if I could just ust the jaxb-ri-20070125 libaries with JBossWS 1.2?
--------------------------------------------------------------------------------------
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033825#4033825
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033825
From do-not-reply at jboss.com Mon Apr 2 18:39:45 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 2 Apr 2007 18:39:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Pooling pojos
Message-ID: <12573955.1175553585346.JavaMail.jboss@colo-br-02.atl.jboss.com>
I guess I really didn't mean pooling, but rather what is done with servlets, with only one being instantiated. Of course, you would also want to provide for init() and destroy() methods, just like servlets have, though probably identified via annotation.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033857#4033857
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033857
From do-not-reply at jboss.com Mon Apr 2 18:57:31 2007
From: do-not-reply at jboss.com (noclueu2)
Date: Mon, 2 Apr 2007 18:57:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Unable to create a WSClient that uses
jboss-wsse-client.xml
Message-ID: <19076452.1175554651596.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello All,
I am trying to do a simple WS that requires a user/password and has encryption. I have the user/password working and the server (i think) is doing encryption but I cannot get my client to use the jboss-wsse-client.xml file. Here is all my code, step by step.
SERVER:
jboss-wsse-server.xml
|
|
|
| META-INF/wsse.keystore
| jbossws
| META-INF/wsse.truststore
| jbossws
|
|
|
|
|
|
|
|
ServerHandler.xml
|
|
|
|
| SecureHandlerChain
|
| WSSecurityHandlerInbound
| org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer
|
|
|
|
Server Source:
TestMagicRemoteInterface.java
| import javax.ejb.Local;
| import javax.ejb.Remote;
|
| @Local
| @Remote
| public interface TestMagicRemoteInterface {
| String pullFromHat(String input);
| }
|
TestMagicBean.java
| import javax.annotation.PostConstruct;
| import javax.annotation.security.RolesAllowed;
| import javax.ejb.Local;
| import javax.ejb.Remote;
| import javax.ejb.Stateless;
| import javax.jws.WebMethod;
| import javax.jws.WebResult;
| import javax.jws.WebService;
| import javax.jws.HandlerChain;
| import javax.jws.soap.SOAPBinding;
|
| import org.jboss.annotation.ejb.RemoteBinding;
| import org.jboss.annotation.security.SecurityDomain;
| import org.jboss.ws.annotation.WebContext;
|
| @WebService(name = "EndpointInterface",
| targetNamespace = "http://com.test.www/test/jsr181ejb",
| serviceName = "MagicService")
| @SOAPBinding(style = SOAPBinding.Style.RPC)
| @Local(TestMagicRemoteInterface.class)
| @Remote(TestMagicRemoteInterface.class)
| @RolesAllowed("internal")
| @Stateless
| @RemoteBinding(jndiBinding = "/ejb3/TestMagician")
| @WebContext(authMethod="BASIC", transportGuarantee="NONE", secureWSDLAccess=false)
| @SecurityDomain(value="JBossWS")
| @HandlerChain(file="resource://config/ServerHandler.xml", name="SecureHandlerChain")
| public class TestMagicBean implements TestMagicRemoteInterface {
|
| @WebMethod(operationName="PullFromHat")
| @WebResult(name = "hat")
| public String pullFromHat(String input) {
| return "White Rabbit--"+input;
| }
| }
|
build.xml
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Everything above builds and deploys and expects the client to use wsse:Security
Client Code:
jboss-wsse-client.jar
|
|
|
| c:/work/workspace/TestWebServicesClient/keystore/wsse.keystore
| jbossws
| c:/work/workspace/TestWebServicesClient/keystore/wsse.truststore
| jbossws
|
|
|
|
|
|
|
|
wstools-config.xml
|
|
|
|
|
|
|
|
ClientTest.java
| import java.net.URL;
| import java.util.Map;
|
| import javax.xml.namespace.QName;
| import javax.xml.ws.BindingProvider;
|
| import com.client.MagicService;
| import com.client.EndpointInterface;
|
| public class ClientTest {
|
| public static void main(String[] args) {
| System.setProperty("org.jboss.wsse.keyStore", "c:/work/workspace/TestWebServicesClient/keystore/wsse.keystore");
| System.setProperty("org.jboss.wsse.keyStorePassword", "jbossws");
| System.setProperty("org.jboss.wsse.keyStoreType", "x509v3");
| System.setProperty("org.jboss.wsse.trustStore", "c:/work/workspace/TestWebServicesClient/keystore/wsse.truststore");
| System.setProperty("org.jboss.wsse.trustStorePassword", "jbossws");
| System.setProperty("org.jboss.wsse.trustStoreType", "x509v3");
|
|
| try {
| System.out.println("Hello World, I'm about to do magic");
| MagicService service = new MagicService();
| EndpointInterface port = service.getEndpointInterfacePort();
| BindingProvider bindingProvider = (BindingProvider) port;
| Map reqContext = bindingProvider.getRequestContext();
| reqContext.put(BindingProvider.USERNAME_PROPERTY, "myuser");
| reqContext.put(BindingProvider.PASSWORD_PROPERTY, "mypassword");
|
| System.out.println(port.pullFromHat("Java Client Test"));
|
| } catch (Exception e) {
| e.printStackTrace();
| }
|
| }
|
| }
|
build.xml
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jar File structure:
| META-INF
| jboss-wsse-client.xml
| Manifest.mf
| ClientTest.class
| com
| client
| MagicService.class
| EndpointInterface.class
|
My above code works if I do not include the jboss-wsse-server.xml but once I add it, the client fails. I do know that I had to add the HandlerChain to the server class for things to work, is there something similar that I have to do to the client?
Thanks,
Richard K
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033861#4033861
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033861
From do-not-reply at jboss.com Mon Apr 2 21:50:18 2007
From: do-not-reply at jboss.com (arekatla@gmail.com)
Date: Mon, 2 Apr 2007 21:50:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - WS Clinet working as a standalone but
not when I deployed on
Message-ID: <31536834.1175565018733.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi
I've written a SOAP client using AXIS, Its working as a standalone but not when I deployed on JBOSS APP server.
I'm getting the following error.
can anyone help me out to fix this?
ERROR [org.jboss.ws.binding.soap.SOAPMessageUnMarshaller] Cannot unmarshall SOAPMessage
javax.xml.soap.SOAPException: Unsupported content type: text/html; charset=ISO-8859-1
at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:206)
at org.jboss.ws.binding.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:76)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
at org.jboss.remoting.Client.invoke(Client.java:525)
at org.jboss.remoting.Client.invoke(Client.java:488)
at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:189)
at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:99)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
2007-04-02 21:11:06,140 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Error invoking http client invoker.
java.io.IOException: javax.xml.soap.SOAPException: Unsupported content type: text/html; charset=ISO-8859-1
at org.jboss.ws.binding.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:82)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81)
at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
at org.jboss.remoting.Client.invoke(Client.java:525)
at org.jboss.remoting.Client.invoke(Client.java:488)
at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:189)
at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:99)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:595)
2007-04-02 21:11:06,140 INFO [STDOUT] javax.xml.soap.SOAPException: Could not transmit message
2007-04-02 21:11:06,156 ERROR [STDERR] javax.xml.soap.SOAPException: Could not transmit message
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:204)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:99)
2007-04-02 21:11:06,156 ERROR [STDERR] at com.dnb.linkage.testharness.action.LinkageReport.getReport(LinkageReport.java:42)
2007-04-02 21:11:06,156 ERROR [STDERR] at com.dnb.linkage.testharness.action.WSLinkageAction.execute(WSLinkageAction.java:28)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
2007-04-02 21:11:06,156 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
2007-04-02 21:11:06,156 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
2007-04-02 21:11:06,156 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
2007-04-02 21:11:06,156 ERROR [STDERR] Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:201)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:81)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:143)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.remoting.Client.invoke(Client.java:525)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.remoting.Client.invoke(Client.java:488)
2007-04-02 21:11:06,156 ERROR [STDERR] at org.jboss.ws.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:189)
2007-04-02 21:11:06,156 ERROR [STDERR] ... 28 more
2007-04-02 21:11:06,156 ERROR [STDERR] Caused by: java.io.IOException: javax.xml.soap.SOAPException: Unsupported content type: text/html; charset=ISO-8859-1
2007-04-02 21:11:06,171 ERROR [STDERR] at org.jboss.ws.binding.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:82)
2007-04-02 21:11:06,171 ERROR [STDERR] at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:175)
2007-04-02 21:11:06,171 ERROR [STDERR] ... 33 more
2007-04-02 21:41:18,343
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033872#4033872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033872
From do-not-reply at jboss.com Tue Apr 3 05:41:06 2007
From: do-not-reply at jboss.com (magnus.ahlander)
Date: Tue, 3 Apr 2007 05:41:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Name of generated exception class
Message-ID: <5472726.1175593266897.JavaMail.jboss@colo-br-02.atl.jboss.com>
Thanks for the reply.
It seems like in the wsconsume task, the package name specified in the 'package' attribute takes precedence over any custom jaxws or jaxb bindings.
Wouldn't it be more appropriate to initially apply any custom bindings and then fall back to the value of the 'package' attribute only if no appropriate bindings are available?
Lp, Magnus
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033936#4033936
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033936
From do-not-reply at jboss.com Tue Apr 3 05:47:04 2007
From: do-not-reply at jboss.com (xiaozhang51)
Date: Tue, 3 Apr 2007 05:47:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Deploying JDeveloper/Oracle
webservices on JBossWS
Message-ID: <12048973.1175593624532.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have the same problem.help me.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033939#4033939
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033939
From do-not-reply at jboss.com Tue Apr 3 06:04:46 2007
From: do-not-reply at jboss.com (valjjou)
Date: Tue, 3 Apr 2007 06:04:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot obtain java type mapping for
String.Array
Message-ID: <8823136.1175594686995.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have my WS and my client, JBOSS 4.0.5, ws1.2.0.
With simple type like int, no pb. But I try to have a String[] and when i run my client i have this error :
INFO [STDOUT] org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://service/types}String.Array
I don't understand because when i test my client on a static java project, no pb... I have this exception with my jsp...
Can you help me please.
Thank for attention.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4033946#4033946
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4033946
From do-not-reply at jboss.com Tue Apr 3 10:24:32 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 3 Apr 2007 10:24:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <10234751.1175610272360.JavaMail.jboss@colo-br-02.atl.jboss.com>
First, I think the client is neither signing nor encrypting the messages. The jboss-wsse-client.xml file is confused, it indicates that encryption is required but never states how to encrypt the message, but it does indicate how to sign the message. To encrypt the message, the < config > section should read:
|
|
|
|
|
Similarly, according to the jboss-wsse-server.xml file, the response messages is being signed but not encrypted.
What error are you seeing? Is there an error on both the client and server? If so, the error is happening at the server and the client error is typically a reflection of that error.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034101#4034101
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034101
From do-not-reply at jboss.com Tue Apr 3 10:39:41 2007
From: do-not-reply at jboss.com (noclueu2)
Date: Tue, 3 Apr 2007 10:39:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <3429067.1175611181321.JavaMail.jboss@colo-br-02.atl.jboss.com>
I tried changing the config files to have encrypt in them with no succes. The serve continues to work but my client does not.
Here is the error message:
| javax.xml.ws.soap.SOAPFaultException: javax.xml.rpc.soap.SOAPFaultException: This service requires , which is missing.
| at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:56)
| at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:111)
| at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:460)
| at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:333)
| at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:185)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:163)
| at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:149)
| at $Proxy8.pullFromHat(Unknown Source)
| at com.partminer.test.client.ClientTest.main(Unknown Source)
|
Here is the client request (Notice how there is no signing or encryption):
| POST /MagicService/TestMagicBean?datatype=SOAPMessage HTTP/1.1
| Authorization: Basic Y29ubmVjdGVzOnNlY3JldA==
| SOAPAction: ""
| Content-Type: text/xml; charset=UTF-8
| User-Agent: Java/1.5.0_11
| Host: localhost:8080
| Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
| Connection: keep-alive
| Content-Length: 245
|
| Java Client Test
|
And the server response:
| HTTP/1.1 500 Internal Server Error
| Server: Apache-Coyote/1.1
| X-Powered-By: Servlet 2.4; JBoss-4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)/Tomcat-5.5
| Content-Type: text/xml;charset=UTF-8
| Transfer-Encoding: chunked
| Date: Tue, 03 Apr 2007 14:31:45 GMT
| Connection: close
|
| bd
| env:Server
| c
|
| 72
| javax.xml.rpc.soap.SOAPFaultException: This service requires , which is missing.
| e
|
| c
|
| 1a
|
| 0
|
|
|
It seems the server is doing what is expected but the client is not.
Thanks,
Richard K
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034108#4034108
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034108
From do-not-reply at jboss.com Tue Apr 3 10:52:03 2007
From: do-not-reply at jboss.com (noclueu2)
Date: Tue, 3 Apr 2007 10:52:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <8996023.1175611923296.JavaMail.jboss@colo-br-02.atl.jboss.com>
One more question that might answer my problem.
In the service code for user/password I add annotation:
@RolesAllowed("internal")
| and
| @SecurityDomain(value="JBossWS")
|
In the client to pass the user password, I had to add:
| BindingProvider bindingProvider = (BindingProvider) port;
| Map reqContext = bindingProvider.getRequestContext();
| reqContext.put(BindingProvider.USERNAME_PROPERTY, "myuser");
| reqContext.put(BindingProvider.PASSWORD_PROPERTY, "mypassword");
|
For signing/encryption I added this annotation to the service:
@HandlerChain(file="resource://config/ServerHandler.xml", name="SecureHandlerChain")
and added the the ServerHandler.xml and jboss-wsse-server.xml
To the client, I did nothing special to the code, just added the jboss-wsse-client.xml. Is there a bit of code I am not doing, that I should? If so, what is it?
Thanks Again,
Richard K
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034114#4034114
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034114
From do-not-reply at jboss.com Tue Apr 3 10:54:45 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 3 Apr 2007 10:54:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <23161565.1175612085057.JavaMail.jboss@colo-br-02.atl.jboss.com>
You never said if you made the suggested jboss-wsse-client.xml changes.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034118#4034118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034118
From do-not-reply at jboss.com Tue Apr 3 11:03:41 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 3 Apr 2007 11:03:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <23372902.1175612621810.JavaMail.jboss@colo-br-02.atl.jboss.com>
I also see that the handler chain is missing for the client. Without that, the client doesn't know to apply the jboss-wsse-client.xml.
I was going to refer you to the documentation on how to do this, but noticed that there is nothing about it in the documentation. Perhaps I got it from the older documentation? No matter, add to your client a META-INF/standard-jaxws-client-config.xml file with these contents:
|
|
|
|
|
|
|
| Standard WSSecurity Client
|
|
| ##SOAP11_HTTP
|
| WSSecurityHandlerOutbound
| org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient
|
|
|
|
|
|
The name is unimportant, the client code for JBossWS will pick up the first client-config in this file.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034127#4034127
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034127
From do-not-reply at jboss.com Tue Apr 3 12:35:34 2007
From: do-not-reply at jboss.com (noclueu2)
Date: Tue, 3 Apr 2007 12:35:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <8286977.1175618134648.JavaMail.jboss@colo-br-02.atl.jboss.com>
Yes I did update jboss-wsee-***.xml on both the client and server. The issue was the missing META-INF/standard-jaxws-client-config.xml on the client. Once I added that I now get a new error:
javax.xml.ws.soap.SOAPFaultException: Endpoint {http://com.test.www/test/jsr181ejb}EndpointInterfacePort does not contain operation meta data for: {http://www.w3.org/2001/04/xmlenc#}EncryptedData
But the important part is that the client is sending encrypted data and the server is expecting encrypted data. I just now need to sort out why the data I'm sending is incorrect.
Thanks for the help,
Richard K
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034189#4034189
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034189
From do-not-reply at jboss.com Tue Apr 3 12:56:04 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 3 Apr 2007 12:56:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <3483544.1175619364057.JavaMail.jboss@colo-br-02.atl.jboss.com>
I think this error comes about because the method name used on the client does not exactly match the method name on the server. Looking at your code, the method is exported as PullFromHat but in the client you use pullFromHat. Seems like you used a different WSDL to generate the client than what you actually are using on the server.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034201#4034201
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034201
From do-not-reply at jboss.com Tue Apr 3 13:11:27 2007
From: do-not-reply at jboss.com (noclueu2)
Date: Tue, 3 Apr 2007 13:11:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <2372447.1175620287501.JavaMail.jboss@colo-br-02.atl.jboss.com>
I recreated the service removing anotation:
@WebMethod(operationName="PullFromHat")
Then rebuilt the client classes using the new WSDL. I still get the same error.
If I just do signing and not encryption everything works great. I use the same file contents for both the jboss-wsse-server.xml and jboss-wsse-client.xml which is:
|
|
|
| META-INF/wsse.keystore
| jbossws
| META-INF/wsse.truststore
| jbossws
|
|
|
|
|
|
|
|
|
|
If I change them to:
|
|
|
| META-INF/wsse.keystore
| jbossws
| META-INF/wsse.truststore
| jbossws
|
|
|
|
|
|
|
|
The above works. I also tried it without the signature and just encryption which gives me the same error.
Thanks,
Richard k
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034211#4034211
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034211
From do-not-reply at jboss.com Tue Apr 3 14:04:32 2007
From: do-not-reply at jboss.com (jimhenderson)
Date: Tue, 3 Apr 2007 14:04:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: I get an
Message-ID: <3190865.1175623472804.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi Keiko,
That was the problem.
Thanks for your help.
Jim
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034233#4034233
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034233
From do-not-reply at jboss.com Tue Apr 3 14:05:47 2007
From: do-not-reply at jboss.com (jimhenderson)
Date: Tue, 3 Apr 2007 14:05:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: I get an
Message-ID: <6917905.1175623547764.JavaMail.jboss@colo-br-02.atl.jboss.com>
Sorry for the typo - thanks Heiko.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034234#4034234
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034234
From do-not-reply at jboss.com Wed Apr 4 05:07:32 2007
From: do-not-reply at jboss.com (kot)
Date: Wed, 4 Apr 2007 05:07:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot annotate minOccurs with JAXB
Message-ID: <8934841.1175677652633.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello everybody
Using JBossWS 1.2.0GA, I want to generate XSD-Schema out of Java using JAXB2.0 annotations.
There is i.e. an @XmlElement providing attribute 'nillable' but no 'minOccurs' or 'maxOccurs'.
Does anybody have an idea how to use annotations to define these two attributes? Are JAXB 2.0 annotations complete at all?
By default, JBoss WS generates minOccurs='0' and maxOccurs='unbound' for all elements of the XSD. This is not what I need.
thanks in advance
ng
Harald
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034442#4034442
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034442
From do-not-reply at jboss.com Wed Apr 4 06:02:50 2007
From: do-not-reply at jboss.com (TonyCruickshank)
Date: Wed, 4 Apr 2007 06:02:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Accessing a .NET web service from JBoss
4.0.4
Message-ID: <2004837.1175680970644.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi all,
I hope someone here help me with a problem I have accessing a
.NET web service from a JBoss J2EE application. Everything seems
to be okay up to the point where I try to access the first method
when I get the following exception...
java.rmi.RemoteException: Call invocation failed: Target endpoint address not set; nested exception is:
org.jboss.ws.WSException: Target endpoint address not set
at org.jboss.ws.jaxrpc.CallImpl.invokeInternal(CallImpl.java:719)
at org.jboss.ws.jaxrpc.CallImpl.invoke(CallImpl.java:398)
at org.jboss.ws.jaxrpc.CallProxy.invoke(CallProxy.java:164)
Any advice on where I need to look to correct this problem
gratefully received.
Thanks,
TonyC
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034460#4034460
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034460
From do-not-reply at jboss.com Wed Apr 4 07:14:25 2007
From: do-not-reply at jboss.com (valjjou)
Date: Wed, 4 Apr 2007 07:14:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain java type mapping for
String.Array
Message-ID: <31333753.1175685265803.JavaMail.jboss@colo-br-02.atl.jboss.com>
This was juste a pb of librairies... sorry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034487#4034487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034487
From do-not-reply at jboss.com Wed Apr 4 09:17:04 2007
From: do-not-reply at jboss.com (KoniKoni)
Date: Wed, 4 Apr 2007 09:17:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Handlers
Message-ID: <15390883.1175692624441.JavaMail.jboss@colo-br-02.atl.jboss.com>
I want to use Statefull Webservice for that i saw a example. If i add follo code:
@SOAPMessageHandlers( {
| @SOAPMessageHandler(className = "org.jboss.ws.addressing.soap.SOAPServerHandler"),
| @SOAPMessageHandler(className = "org.jboss.test.ws.samples.wsaddr.ServerHandler")
Neatbeans 5.5 ist depricated, is it right? If yes, what i have to use instead?
Thera are examples for this stuff?
Waht is the difference beetwin Client and Server handles?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034546#4034546
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034546
From do-not-reply at jboss.com Wed Apr 4 13:03:41 2007
From: do-not-reply at jboss.com (KoniKoni)
Date: Wed, 4 Apr 2007 13:03:41 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Handle
Message-ID: <27189673.1175706221199.JavaMail.jboss@colo-br-02.atl.jboss.com>
I use Netbeans 5.5, where i have to be save jaxws-handlers.xml im netbeans projekt struktur?
org.jboss.ws.WSException: Cannot resolve URL to handler file: WEB-INF/jaxws-handlers.xml
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034693#4034693
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034693
From do-not-reply at jboss.com Wed Apr 4 16:17:09 2007
From: do-not-reply at jboss.com (KoniKoni)
Date: Wed, 4 Apr 2007 16:17:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - I got follow exception
Message-ID: <18923565.1175717829365.JavaMail.jboss@colo-br-02.atl.jboss.com>
22:12:26,755 INFO [EARDeployer] Init J2EE application: file:/home/kostja/IT/jboss-4.0.5.GA/server/default/deploy/laolaWS.ear
| 22:12:29,197 INFO [Ejb3Deployment] EJB3 deployment time took: 26
| 22:12:29,992 INFO [TomcatDeployer] deploy, ctxPath=/laolaWS-laolaWS-ejb, warUrl=.../tmp/deploy/laolaWS.ear-laolaWS-ejb.jar-ws64404.war/
| 22:12:30,095 INFO [JmxKernelAbstraction] installing MBean: persistence.units:ear=laolaWS.ear,jar=laolaWS-ejb.jar,unitName=laolaWS-ejbPU with dependencies:
| 22:12:30,095 INFO [JmxKernelAbstraction] jboss.jca:name=mysqllaola,service=DataSourceBinding
| 22:12:30,104 WARN [ServiceController] Problem starting service persistence.units:ear=laolaWS.ear,jar=laolaWS-ejb.jar,unitName=laolaWS-ejbPU
| javax.naming.NameNotFoundException: mysqllaola not bound
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
| at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
| at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
| at org.jnp.server.NamingServer.lookup(NamingServer.java:296)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625)
| at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
| at javax.naming.InitialContext.lookup(InitialContext.java:351)
| at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:240)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:102)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy101.start(Unknown Source)
| at org.jboss.ejb3.JmxKernelAbstraction.install(JmxKernelAbstraction.java:96)
| at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.java:467)
| at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:317)
| at org.jboss.ejb3.Ejb3Module.startService(Ejb3Module.java:91)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
| at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
| at $Proxy0.start(Unknown Source)
| at org.jboss.system.ServiceController.start(ServiceController.java:417)
| at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy28.start(Unknown Source)
| at org.jboss.ejb3.EJB3Deployer.start(EJB3Deployer.java:449)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
| at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238)
| at org.jboss.ws.integration.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:93)
| at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188)
| at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy29.start(Unknown Source)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
| at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
| at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
| at sun.reflect.GeneratedMethodAccessor19.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:585)
| at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
| at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy8.deploy(Unknown Source)
| at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
| at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
| at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
| 22:12:30,106 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=laolaWS.ear,jar=laolaWS-ejb.jar,name=laolaWS,service=EJB3 with dependencies:
| 22:12:30,120 INFO [EJBContainer] STARTED EJB: kk.laola.sw.gen.laolaWS ejbName: laolaWS
| 22:12:30,128 INFO [EJB3Deployer] Deployed: file:/home/kostja/IT/jboss-4.0.5.GA/server/default/tmp/deploy/tmp64401laolaWS.ear-contents/laolaWS-ejb.jar
| 22:12:30,130 INFO [WSDLFilePublisher] WSDL published to: file:/home/kostja/IT/jboss-4.0.5.GA/server/default/data/wsdl/laolaWS.ear/laolaWS-ejb.jar/LaolaWSService64402.wsdl
| 22:12:30,136 INFO [ServiceEndpointManager] WebService started: http://kostja-mobil:8080/laolaWS-laolaWS-ejb/laolaWS
| 22:12:30,142 INFO [EARDeployer] Started J2EE application: file:/home/kostja/IT/jboss-4.0.5.GA/server/default/deploy/laolaWS.ear
| 22:12:30,144 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
|
| --- MBeans waiting for other MBeans ---
| ObjectName: persistence.units:ear=laolaWS.ear,jar=laolaWS-ejb.jar,unitName=laolaWS-ejbPU
| State: FAILED
| Reason: javax.naming.NameNotFoundException: mysqllaola not bound
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=mysqllaola
|
| --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
| ObjectName: persistence.units:ear=laolaWS.ear,jar=laolaWS-ejb.jar,unitName=laolaWS-ejbPU
| State: FAILED
| Reason: javax.naming.NameNotFoundException: mysqllaola not bound
| I Depend On:
| jboss.jca:service=DataSourceBinding,name=mysqllaola
|
|
I used the latest jboss ws package with installer.
Can it be that the server got dirty, because I pressed several times one behind the other deploy without to undeploy? How can one actually undeploy?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034772#4034772
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034772
From do-not-reply at jboss.com Thu Apr 5 09:17:31 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Thu, 5 Apr 2007 09:17:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Mapping problem
Message-ID: <20984122.1175779051543.JavaMail.jboss@colo-br-02.atl.jboss.com>
With a String return type, it runs
So, it's a mapping problem but I don't know it exactly is
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4034997#4034997
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4034997
From do-not-reply at jboss.com Thu Apr 5 09:24:37 2007
From: do-not-reply at jboss.com (artd)
Date: Thu, 5 Apr 2007 09:24:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Salesforce client stub generation fails
Message-ID: <1754810.1175779477072.JavaMail.jboss@colo-br-02.atl.jboss.com>
I'm trying to move away from Axis due to what appear to be classloading issues when Axis is included in a deployed webapp, and exposing portions of the webapp are exposed using JBOSSWS. So I figured I would just convert the Axis stubs to JBOSSWS stubs using wsconsume.
I've tried JBOSS AS 4.0.5, 4.2.0 with the native JBOSSWS and upgrades to 1.2.0SP1 to no avail.
With the latest, 1.2.0SP1 I get the following exception
| [wsconsume] Command invoked: org.jboss.ws.tools.jaxws.command.wsconsume -k -o "C:\Documents and Settings\adalessandro\Workspace\AxaptaSOAPClient" -s "C:\Documents and Settings\adalessandro\Workspace\AxaptaSOAPClient\src" -t enterprise.wsdl
| [wsconsume] warning: src-resolve: Cannot resolve the name 'ens:sObject' to a(n) 'type definition' component.
| [wsconsume] line ? of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema2
| [wsconsume] error: A class/interface with the same name "com.sforce.soap.enterprise.DescribeLayout" is already in use. Use a class customization to resolve this conflict.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema2
| [wsconsume] error: (Relevant to above error) another "DescribeLayout" is generated from here.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema2
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema2
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema2
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: Two declarations cause a collision in the ObjectFactory class.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] error: (Related to above error) This is the other declaration.
| [wsconsume] line 0 of file:/C:/Documents%20and%20Settings/adalessandro/Workspace/AxaptaSOAPClient/enterprise.wsdl#types?schema1
| [wsconsume] com.sun.istack.SAXParseException2: (Related to above error) This is the other declaration.
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:213)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.config.ModelInfo.buildModel(ModelInfo.java:88)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.Processor.runModeler(Processor.java:82)
| [wsconsume] at org.jboss.com.sun.tools.ws.wscompile.CompileTool.run(CompileTool.java:543)
| [wsconsume] at org.jboss.com.sun.tools.ws.util.ToolBase.run(ToolBase.java:57)
| [wsconsume] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl$1.run(WSContractConsumerImpl.java:163)
| [wsconsume] at org.jboss.ws.tools.jaxws.impl.WSContractConsumerImpl.consume(WSContractConsumerImpl.java:166)
| [wsconsume] at org.jboss.ws.tools.jaxws.command.wsconsume.importServices(wsconsume.java:194)
| [wsconsume] at org.jboss.ws.tools.jaxws.command.wsconsume.main(wsconsume.java:77)
| [wsconsume] Caused by: com.sun.istack.SAXParseException2: (Related to above error) This is the other declaration.
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:128)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildJAXBModel(WSDLModeler.java:2207)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.internalBuildModel(WSDLModeler.java:224)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:181)
| [wsconsume] ... 8 more
| [wsconsume] Caused by: com.sun.istack.SAXParseException2: (Related to above error) This is the other declaration.
| [wsconsume] at com.sun.tools.xjc.ErrorReceiver.error(ErrorReceiver.java:66)
| [wsconsume] at com.sun.tools.xjc.generator.bean.ObjectFactoryGeneratorImpl.populate(ObjectFactoryGeneratorImpl.java:152)
| [wsconsume] at com.sun.tools.xjc.generator.bean.PublicObjectFactoryGenerator.populate(PublicObjectFactoryGenerator.java:19)
| [wsconsume] at com.sun.tools.xjc.generator.bean.BeanGenerator.(BeanGenerator.java:210)
| [wsconsume] at com.sun.tools.xjc.generator.bean.BeanGenerator.generate(BeanGenerator.java:151)
| [wsconsume] at com.sun.tools.xjc.model.Model.generateCode(Model.java:230)
| [wsconsume] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:217)
| [wsconsume] at com.sun.tools.xjc.api.impl.s2j.SchemaCompilerImpl.bind(SchemaCompilerImpl.java:67)
| [wsconsume] at org.jboss.com.sun.tools.ws.processor.modeler.wsdl.JAXBModelBuilder.bind(JAXBModelBuilder.java:126)
| [wsconsume] ... 11 more
| [wsconsume] error: com.sun.istack.SAXParseException2: (Related to above error) This is the other declaration.
|
Any suggestions on how to resolve? I couldn't find any exact JIRA issues on this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035002#4035002
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035002
From do-not-reply at jboss.com Thu Apr 5 09:34:57 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Thu, 5 Apr 2007 09:34:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Mapping problem
Message-ID: <14095665.1175780097872.JavaMail.jboss@colo-br-02.atl.jboss.com>
I tried to use the methode
| Service service = (Service)factory.createService(wsdlLocation, serviceName,mappingURL);
|
as I saw in an example but this method doesn't seem exist...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035006#4035006
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035006
From do-not-reply at jboss.com Thu Apr 5 10:41:09 2007
From: do-not-reply at jboss.com (KoniKoni)
Date: Thu, 5 Apr 2007 10:41:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: I got follow exception
Message-ID: <10523888.1175784069152.JavaMail.jboss@colo-br-02.atl.jboss.com>
after two days looking for:
false
is needed.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035043#4035043
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035043
From do-not-reply at jboss.com Thu Apr 5 11:10:15 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Thu, 5 Apr 2007 11:10:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Mapping problem
Message-ID: <24558533.1175785815928.JavaMail.jboss@colo-br-02.atl.jboss.com>
I solved this problem by using ServiceFactoryImpl instead of ServiceFactory
But now I have some errors to parse my jaxrpc-mapping.xml file at the line
| Service service = (Service)factory.createService(wsdlLocation, serviceName,mappingUrl);
|
| org.jboss.xb.binding.JBossXBRuntimeException: Failed to create a new SAX parser
| at org.jboss.xb.binding.UnmarshallerFactory$UnmarshallerFactoryImpl.newUnmarshaller(UnmarshallerFactory.java:100)
| at org.jboss.ws.metadata.jaxrpcmapping.JavaWsdlMappingFactory.parse(JavaWsdlMappingFactory.java:79)
| at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:77)
| at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:111)
| at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:157)
| at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:142)
| at jbosstest.HelloClient.testDmex(HelloClient.java:95)
|
Any ideas?
I need answers quickly plz
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035054#4035054
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035054
From do-not-reply at jboss.com Thu Apr 5 12:39:39 2007
From: do-not-reply at jboss.com (TonyCruickshank)
Date: Thu, 5 Apr 2007 12:39:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Accessing a .NET web service from
JBoss 4.0.4
Message-ID: <14346571.1175791179075.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi All,
Resolved. The WSDL file I was generating from contained soap12
artefacts. Though the JBoss wstools generated the mapping and
java successfully, at run time the server log contained the
warning
WARN [org.jboss.ws.metada?ta.wsdl.WSDLDefiniti?ons] Multiple WSDL bindings referrence the same interface:
Removing all the soap12 information from the WSDL and starting
again with wstools fixed the problem.
TonyC
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035088#4035088
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035088
From do-not-reply at jboss.com Fri Apr 6 10:50:59 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Fri, 6 Apr 2007 10:50:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - [Fatal Error] :-1:-1: Premature end of
file.
Message-ID: <7144817.1175871059102.JavaMail.jboss@colo-br-02.atl.jboss.com>
I work on an application to test JBossWS
I have a web service which turns on a JBoss AS 4.0.5 server, which returns a complex type object, "Dmex"
I have this client:
| try {
|
| ServiceFactoryImpl factory=new ServiceFactoryImpl();
| URL wsdlLocation = new URL("http://localhost:8080/DmexWs" + "?wsdl");
| URL mappingUrl=new File("src/java/jaxrpc-mapping.xml").toURL();
| QName serviceName = new QName("urn:bsa.ws.test", "DmexWs");
| Service service = (Service)factory.createService(wsdlLocation, serviceName,mappingUrl);
| Call call = service.createCall();
|
| QName operationName = new QName("urn:bsa.ws.test", "getDmex");
| call.setOperationName(operationName);
|
| Integer id = new Integer(274);
| Object retObj = call.invoke(new Object[]{id});
|
| System.out.println(retObj);
| } catch (Exception e) {
| e.printStackTrace();
| }
|
and when I run the client, I have this error:
| [Fatal Error] :-1:-1: Premature end of file.
|
Any idea?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035346#4035346
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035346
From do-not-reply at jboss.com Fri Apr 6 12:24:48 2007
From: do-not-reply at jboss.com (flindet)
Date: Fri, 6 Apr 2007 12:24:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How Do I See the XML?
Message-ID: <13965503.1175876689000.JavaMail.jboss@colo-br-02.atl.jboss.com>
rmartony, here's what I ended up doing to log my full SOAP message. It's based heavily on the example handlers included with JBossWS.
| public class ProtocolHandler extends GenericSOAPHandler
| {
| /**
| * The {@link Logger} used for writing logging messages.
| */
| private static Logger log = Logger.getLogger(ProtocolHandler.class);
|
| /* (non-Javadoc)
| * @see org.jboss.ws.core.jaxws.handler.GenericSOAPHandler#handleOutbound(javax.xml.ws.handler.MessageContext)
| */
| @Override
| public boolean handleOutbound(final MessageContext msgContext)
| {
| if (log.isInfoEnabled())
| {
| return logMessage(msgContext);
| }
| return true;
| }
|
| /* (non-Javadoc)
| * @see org.jboss.ws.core.jaxws.handler.GenericSOAPHandler#handleInbound(javax.xml.ws.handler.MessageContext)
| */
| @Override
| public boolean handleInbound(final MessageContext msgContext)
| {
| if (log.isInfoEnabled())
| {
| return logMessage(msgContext);
| }
| return true;
| }
|
| /**
| * Logs the full SOAP message.
| *
| * @param messageContext The message context containing the SOAP message to be handled.
| * @return True if handler processing should continue, false otherwise.
| * @throws WebServiceException If the SOAP message is malformed.
| */
| private boolean logMessage(final MessageContext messageContext)
| {
| try
| {
| SOAPMessage soapMessage = ((SOAPMessageContext) messageContext).getMessage();
| if (soapMessage.getSOAPBody().getChildElements().hasNext())
| {
| SOAPElement soapElement = (SOAPElement) soapMessage.getSOAPBody().getChildElements().next();
| if (soapElement.getChildElements().hasNext())
| {
| soapElement = (SOAPElement) soapElement.getChildElements().next();
|
| ByteArrayOutputStream xmlStream = new ByteArrayOutputStream();
| soapMessage.writeTo(xmlStream);
| log.info(new String(xmlStream.toByteArray()));
| }
| }
|
| return true;
| }
| catch (SOAPException ex)
| {
| throw new WebServiceException(ex);
| }
| catch (IOException ex)
| {
| throw new WebServiceException(ex);
| }
| }
| }
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035389#4035389
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035389
From do-not-reply at jboss.com Fri Apr 6 16:05:27 2007
From: do-not-reply at jboss.com (artd)
Date: Fri, 6 Apr 2007 16:05:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - PortComponent Annotation - Jar
Requirements
Message-ID: <28046148.1175889927370.JavaMail.jboss@colo-br-02.atl.jboss.com>
I've loaded just about all jars from the JBOSS server, client and jbossws.sar and ejb3deployer.sar, to no avail.
Can someone shed some light on which jar the PortComponent annotation is located.
Running 4.05GA and 4.2CR1
Thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035451#4035451
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035451
From do-not-reply at jboss.com Fri Apr 6 16:13:25 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 6 Apr 2007 16:13:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: PortComponent Annotation - Jar
Requirements
Message-ID: <21309674.1175890405175.JavaMail.jboss@colo-br-02.atl.jboss.com>
I found it in server/[all|default]/deploy/jbossws.sar/jbossws-core.jar in 4.0.5.GA. I could not find it in 4.2.0.CR1.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035453#4035453
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035453
From do-not-reply at jboss.com Fri Apr 6 16:26:12 2007
From: do-not-reply at jboss.com (artd)
Date: Fri, 6 Apr 2007 16:26:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: PortComponent Annotation - Jar
Requirements
Message-ID: <25982589.1175891172850.JavaMail.jboss@colo-br-02.atl.jboss.com>
Yup, must have had too many jars in my classpatch, Eclipse wasn't finding it, reordered, and sure enough; autocomplete worked for portcomponent.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035456#4035456
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035456
From do-not-reply at jboss.com Fri Apr 6 16:29:48 2007
From: do-not-reply at jboss.com (artd)
Date: Fri, 6 Apr 2007 16:29:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: PortComponent Annotation - Jar
Requirements
Message-ID: <26391440.1175891388543.JavaMail.jboss@colo-br-02.atl.jboss.com>
Ok, clarrification, the PortComponent is found in the jbossws.sar jbossws14-core.jar, which I've upgraded on 4.0.5 to JBossWS 1.2.0SP1 and using whatever shipped with the JBOSSAS 4.2.0
Does anyone know if this is a known issue or is the @PortComponent deprecated?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035458#4035458
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035458
From do-not-reply at jboss.com Fri Apr 6 18:30:34 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 6 Apr 2007 18:30:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: PortComponent Annotation - Jar
Requirements
Message-ID: <5975227.1175898634810.JavaMail.jboss@colo-br-02.atl.jboss.com>
I found it in the jboss-ejb3.jar file in a recent svn get of trunk (5.0 beta2).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035467#4035467
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035467
From do-not-reply at jboss.com Mon Apr 9 11:20:33 2007
From: do-not-reply at jboss.com (zauberlehrling)
Date: Mon, 9 Apr 2007 11:20:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Strange java code generated by wsprovide
Message-ID: <15359418.1176132033440.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi,
I build a webservice with the following simple pojo endpoint:
package beispiel_1;
|
| import javax.jws.WebService;
| import javax.xml.ws.RequestWrapper;
| import javax.xml.ws.ResponseWrapper;
|
| @WebService
| public class PojoEndpoint {
|
| @RequestWrapper(className="beispiel_1.Request")
| @ResponseWrapper(className="beispiel_1.Response")
| public String sayHello(String name)
| {
| return "Hallo "+name+"!";
| }
| }
and I generate the wsdl file with wsprovide:
|
|
|
|
I need the wsdl file for a workflow. The wsprovide task above also generates two classes Request and Response. But these java classes are not correct:
package beispiel_1;
|
| import javax.xml.bind.annotation.XmlAccessType;
| import javax.xml.bind.annotation.XmlAccessorType;
| import javax.xml.bind.annotation.XmlElement;
| import javax.xml.bind.annotation.XmlRootElement;
| import javax.xml.bind.annotation.XmlType;
|
| @XmlRootElement(namespace = "http://beispiel_1", name = "sayHello")
| @XmlType(namespace = "http://beispiel_1", name = "sayHello")
| @XmlAccessorType(XmlAccessType.FIELD)
| public class Request {
|
| @XmlElement(namespace = "", name = "arg0")
| private String arg0;
|
| public String getArg0() {
| return this.arg0;
| }
|
| public String setArg0(String arg0) {
| this.arg0 = arg0;
| }
|
| }
|
and
package beispiel_1;
|
| import javax.xml.bind.annotation.XmlAccessType;
| import javax.xml.bind.annotation.XmlAccessorType;
| import javax.xml.bind.annotation.XmlElement;
| import javax.xml.bind.annotation.XmlRootElement;
| import javax.xml.bind.annotation.XmlType;
|
| @XmlRootElement(namespace = "http://beispiel_1", name = "sayHelloResponse")
| @XmlType(namespace = "http://beispiel_1", name = "sayHelloResponse")
| @XmlAccessorType(XmlAccessType.FIELD)
| public class Response {
|
| @XmlElement(namespace = "", name = "return")
| private String return;
|
| public String getReturn() {
| return this.return;
| }
|
| public String setReturn(String return) {
| this.return = return;
| }
| }
To be more precise the return type of the set methods should be void and not String and I have problems with the variable name return.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035737#4035737
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035737
From do-not-reply at jboss.com Mon Apr 9 13:27:36 2007
From: do-not-reply at jboss.com (alexboyer)
Date: Mon, 9 Apr 2007 13:27:36 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - parser exception when deploying
webservice
Message-ID: <1772608.1176139656809.JavaMail.jboss@colo-br-02.atl.jboss.com>
I am using 4.0.5.GA and 1.2.0.SP1. I used wsconsume to create a top-down web service. When I deploy I get an error as follows. As this error seems to be from trying to parse a jboss generated .xsd file I am unclear what to do. I assume this schema is generated from the wsdl. I cannot see any non-UTF8 characters in the wsdl or the xsd file generated.
I would appreciate any pointers on how to debug this problem.
2007-04-09 12:14:15,222 ERROR [org.jboss.ws.core.server.ServiceEndpointDeployer] Cannot create service endpoint
org.apache.xerces.xni.XNIException: Parser should stop: JBossWS__ws_ship7329.xsd[domain:http://www.w3.org/TR/1998/REC-xml-19980210]::[key=InvalidByte]::Message=Invalid byte 1 of 1-byte UTF-8 sequence.
at org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler.fatalError(JBossXSErrorHandler.java:78)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source)
at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(Unknown Source)
at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(Unknown Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(Unknown Source)
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(Unknown Source)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(Unknown Source)
at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:181)
at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:278)
at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:165)
at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:131)
at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:313)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:139)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:49)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:68)
at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:90)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035770#4035770
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035770
From do-not-reply at jboss.com Mon Apr 9 15:45:18 2007
From: do-not-reply at jboss.com (alexboyer)
Date: Mon, 9 Apr 2007 15:45:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: parser exception when deploying
webservice
Message-ID: <388239.1176147918016.JavaMail.jboss@colo-br-02.atl.jboss.com>
Somehow and apostrophe in an annotation in the already existing wsdl was being changed to a non-utf8 character in the generated schema. Have another problem when the apostrophe was removed but got past this issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035799#4035799
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035799
From do-not-reply at jboss.com Mon Apr 9 17:32:27 2007
From: do-not-reply at jboss.com (alexboyer)
Date: Mon, 9 Apr 2007 17:32:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - provide your own wsdl - cannot seem to
get this to work
Message-ID: <27991584.1176154347228.JavaMail.jboss@colo-br-02.atl.jboss.com>
I followed http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104843 quite carefully.
I used wsconsume to generate my classes, created an impl class and followed all the pointers in the mentioned forum thread.
I get a wsdl now but it is not the one I defined in my wsdlLocation value in the endpoint interface in the wsdlLocation javax.jws.WebService annotation. I get datetime types set to anySimpleType and all my enumerations have camel case now like this - dropOffType - rather than DropOffType like in the wsdl. I believe a wsdl is being generated still.
How do I generate and deploy a web service and have jboss use the wsdl I supply in the war?
Thank you
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035816#4035816
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035816
From do-not-reply at jboss.com Mon Apr 9 23:14:32 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 9 Apr 2007 23:14:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security and certificate password
Message-ID: <6065135.1176174872342.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have a patch. It works. I could simply apply the patch in Subversion, but I would prefer to place the patch into JIRA and have someone on the JBossWS team apply the patch (especially since I changed the xsd file, not sure if that requires a new version number or what). But JIRA doesn't like me, no matter whether I use Firefox or IE. When I log in, I can see the list of projects in the left column, but in the right column, where I should see things such as my assigned JIRA tasks, I instead see this exception:
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug. Details: ------- java.lang.NullPointerException at com.atlassian.jira.issue.search.providers.LuceneSearchProvider.searchCount(LuceneSearchProvider.java:87) at com.atlassian.jira.portal.portlets.SavedFiltersPortlet.getCountsForFilter(SavedFiltersPortlet.java:52) at sun.reflect.GeneratedMethodAccessor832.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:267) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:197) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:166) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:114) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:55) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:70) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230) at org.apache.velocity.Template.merge(Template.java:256) at org.apache.velocity.app.VelocityEngine.mergeTemplate(VelocityEngine.java:450) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:76) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:60) at com.atlassian.velocity.DefaultVelocityManager.getEncodedBody(DefaultVelocityManager.java:55) at com.atlassian.jira.plugin.JiraResourcedModuleDescriptor.getHtml(JiraResourcedModuleDescriptor.java:97) at com.atlassian.jira.portal.PortletImpl.getViewHtml(PortletImpl.java:67) at com.atlassian.jira.portal.portlets.AbstractRequiresUserPortlet.getViewHtml(AbstractRequiresUserPortlet.java:25) at org.apache.jsp.secure.views.dashboard_jsp._jspService(dashboard_jsp.java:1035) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:672) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:463) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:398) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:301) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:253) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:35) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:182) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.seraph.filter.LoginFilter.doFilter(LoginFilter.java:181) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.util.profiling.filters.ProfilingFilter.doFilter(ProfilingFilter.java:132) at com.atlassian.jira.web.filters.ProfilingAndErrorFilter.doFilter(ProfilingAndErrorFilter.java:35) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.ActionCleanupDelayFilter.doFilter(ActionCleanupDelayFilter.java:39) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.johnson.filters.JohnsonFilter.doFilter(JohnsonFilter.java:91) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.gzip.GzipFilter.doFilter(GzipFilter.java:72) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.core.filters.AbstractEncodingFilter.doFilter(AbstractEncodingFilter.java:37) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(FastCommonAccessLogValve.java:495) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595)
And if I go straight to this particular JIRA issue I am informed that I would have more options available if I first logged in.
Help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035849#4035849
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035849
From do-not-reply at jboss.com Tue Apr 10 04:12:32 2007
From: do-not-reply at jboss.com (nicolemans72)
Date: Tue, 10 Apr 2007 04:12:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: [Fatal Error] :-1:-1: Premature end
of file.
Message-ID: <21762669.1176192752734.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have no other error log.
Is anyone know what could be the cause of the problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035882#4035882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035882
From do-not-reply at jboss.com Tue Apr 10 05:10:40 2007
From: do-not-reply at jboss.com (sgof)
Date: Tue, 10 Apr 2007 05:10:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBoss 4.0.5--JAX-RPC has Issues?
Message-ID: <11428737.1176196240178.JavaMail.jboss@colo-br-02.atl.jboss.com>
I resolved using a jboss prevous version
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035891#4035891
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035891
From do-not-reply at jboss.com Tue Apr 10 05:48:22 2007
From: do-not-reply at jboss.com (thomas.diesler@jboss.com)
Date: Tue, 10 Apr 2007 05:48:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Pooling pojos
Message-ID: <11215248.1176198502286.JavaMail.jboss@colo-br-02.atl.jboss.com>
This has been a long outstanding feature request.
http://jira.jboss.org/jira/browse/JBWS-1603
BTW, this is a nice little task for a community contribution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4035903#4035903
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4035903
From do-not-reply at jboss.com Tue Apr 10 11:03:23 2007
From: do-not-reply at jboss.com (rmartony)
Date: Tue, 10 Apr 2007 11:03:23 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: How Do I See the XML?
Message-ID: <7363693.1176217403716.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi flindet and joshlam, thank you very much for your help.
Regards,
Rafael.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036023#4036023
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036023
From do-not-reply at jboss.com Tue Apr 10 12:40:47 2007
From: do-not-reply at jboss.com (stattit)
Date: Tue, 10 Apr 2007 12:40:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Getting Error
Message-ID: <19125709.1176223247419.JavaMail.jboss@colo-br-02.atl.jboss.com>
We want the web service to publish the user created WSDL instead of the JBOssWS generated WSDL. I followed the instructions as in this post viz.
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031124#4031124
However, I am now getting the following error when I try to deploy the war.
12:19:13,139 ERROR [MainDeployer] Could not create deployment: file:/C:/sofadev/dev-env/jboss-4.0.5.GA/server/flagstar/deploy/fsb-MortgageService.war
org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (java.lang.IllegalArgumentException: Illegal schema location map)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:83)
at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy39.create(Unknown Source)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
at sun.reflect.GeneratedMethodAccessor55.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:610)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225)
Caused by: java.lang.IllegalArgumentException: Illegal schema location map
at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:155)
at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:278)
at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:165)
at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:131)
at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:313)
at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:139)
at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:49)
at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:68)
at org.jboss.ws.core.server.ServiceEndpointDeployer.create(ServiceEndpointDeployer.java:90)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.createServiceEndpoint(DeployerInterceptor.java:127)
at org.jboss.ws.integration.jboss42.DeployerInterceptorJSE.createServiceEndpoint(DeployerInterceptorJSE.java:132)
at org.jboss.ws.integration.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:78)
... 28 more
The WSDL file does some imports of external schemas which in turn can import other schemas. The .wsdl file has been placed in WEB-INF/wsdl and the schema files have been copied to the same spot too. The relevant section in the .wsdl file is
|
|
|
|
|
|
|
|
|
|
|
My question is this: Is this the proper way to refer to external schemas when you want to publish your own WSDL or would you have to refer to them as
schemaLocation="WEB-INF/wsdl/MortgageResponse.xsd"
The example MortgageResponse.xsd file is (note the import)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Any help in this matter is appreciated. If you need any additional information, I will be glad to provide it.
JBossWS 1.2.0.SP1
JBoss 4.0.5.GA
Regards
Sandesh
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036058#4036058
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036058
From do-not-reply at jboss.com Tue Apr 10 15:40:28 2007
From: do-not-reply at jboss.com (stattit)
Date: Tue, 10 Apr 2007 15:40:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Getting Error
Message-ID: <7820204.1176234028848.JavaMail.jboss@colo-br-02.atl.jboss.com>
Weird....started the deploy from scratch, ensuring that the schemas were
copied to the same location as the wsdl viz. to WEB-INF/wsdl and made
sure that the imports had just a reference to the schemas, without any
reference to any relative directories and now things are working fine.
Note sure what caused the previous issues.
Regards
Sandesh
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036105#4036105
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036105
From do-not-reply at jboss.com Tue Apr 10 18:36:33 2007
From: do-not-reply at jboss.com (estrnod)
Date: Tue, 10 Apr 2007 18:36:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <19650125.1176244593803.JavaMail.jboss@colo-br-02.atl.jboss.com>
Did you ever get an answer to how to get the client to use ? I have been following this thread closely because it reflects my own experience and even my own suspicion that the client needed something similar to the HandlerChain on the server side, before I read your post. I incorporated standard-jaxws-client-config.xml in my own build but with both signature & encryption required, am also still getting javax.xml.rpc.soap.SOAPFaultException: This service requires , which is missing.
Thanks,
Ellen Strnod
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036167#4036167
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036167
From do-not-reply at jboss.com Tue Apr 10 18:57:29 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 10 Apr 2007 18:57:29 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to create a WSClient that
uses jboss-wsse-client.
Message-ID: <31851492.1176245849439.JavaMail.jboss@colo-br-02.atl.jboss.com>
Make sure the standard-jaxws-client-config.xml contains only the "Standard WSSecurity Client" configuration, you have to delete the other two configurations. Seems like only the first one is used, and I have not found out how to indicate which one to use if there are multiple.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036170#4036170
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036170
From do-not-reply at jboss.com Tue Apr 10 19:27:58 2007
From: do-not-reply at jboss.com (alexboyer)
Date: Tue, 10 Apr 2007 19:27:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: provide your own wsdl - cannot seem
to get this to work
Message-ID: <21593401.1176247678982.JavaMail.jboss@colo-br-02.atl.jboss.com>
The problem here was that I needed to add a target namespace to the endpoint implementation that was the same as the endpoint interface. That seemed to fix the problem.
Now my wsdl that I provided is served.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036174#4036174
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036174
From do-not-reply at jboss.com Tue Apr 10 19:36:57 2007
From: do-not-reply at jboss.com (alexboyer)
Date: Tue, 10 Apr 2007 19:36:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Losing soap request after it gets to
server
Message-ID: <1637565.1176248217920.JavaMail.jboss@colo-br-02.atl.jboss.com>
I can see my soap request getting to the server in the log file. But by the time that sei impl has the method invoked on it the request java object is null. One thing I noted is that the log notes that when the xml type is deserialized to the java type the java type does not have the package name of the request wrapper. It has a jaxws on the end of it. So if my request wrapper that was generated from wsconsume has fully qualified name of com.company.ws.RequestWrapper the log file notes:
2007-04-10 18:15:53,705 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue [xmlType={http://company.com/ws}request,javaType=class com.company.ws.jaxws.RequestWrapper]
I don't see this class com.company.ws.jaxws.RequestWrapper in my war so I guess it must be generated on the server side. Can this be why my soap request is getting lost? Any suggestions?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036176#4036176
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036176
From do-not-reply at jboss.com Tue Apr 10 20:34:03 2007
From: do-not-reply at jboss.com (d_pavel)
Date: Tue, 10 Apr 2007 20:34:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem using wstools
Message-ID: <13946843.1176251643764.JavaMail.jboss@colo-br-02.atl.jboss.com>
I should have posted these answers sooner then one month but time flies so here you go (in case somebody will stumble upon same things):
-I solved relatively fast the wstools problem which turned out to be the result of using the full path for the SEI class in the command which I described in point 4 in my first post (as was mentioned in the user guide...). So using a path just to WEB-INF/classes directory solved the problem and the related artifacts are generated correct.
-jbossws14-client.jar is needed for J2EE 1.4, whereas jbossws-client.jar is needed for Java EE; if you keep both jar files order of loading is important depending what you need to use.
-yes I had to get an updated "jboss-xml-binding.jar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036182#4036182
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036182
From do-not-reply at jboss.com Tue Apr 10 22:24:19 2007
From: do-not-reply at jboss.com (d_pavel)
Date: Tue, 10 Apr 2007 22:24:19 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JSR-109Client,
Mapping problem and trying to connect to a .N
Message-ID: <3443355.1176258259126.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi All,
I developed a JAX-RPC web service client in order to connect to a .NET webservice. I am using jdk1.5.0_09, JBoss AS 4.0.5.GA and jbossws-1.2.0.GA. I set properly the java.endorsed.dirs.
Here is the config file:
|
|
|
|
|
|
|
|
|
|
|
Using wstools I was able to generate the related artifacts (the jaxrpc-mapping.xml file and all the related stubs and the required Service Endpoint Interface (SEI).
The target namespace it will be similar with: "https://www.acompany.com/VaxHttp/Vax"
The important code in my client looks like this:
| String feedback = "";
| try
| {
| URL url = null;
| //wsdl location
| try
| {
| url = new URL(urlstr);
| }
| catch (MalformedURLException e)
| {
| e.printStackTrace();
| }
|
| QName qName = new QName("https://www.acompany.com/VaxHttp/Vax.asmx?wsdl", "Vax");
|
| System.out.println("############ local part = "+qName.getLocalPart());
| System.out.println("############ namespace URI = "+qName.getNamespaceURI());
|
| //set jboss ServiceFactory
| System.setProperty( "javax.xml.rpc.ServiceFactory",
| "org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl" );
|
| //have to have only one instance of the ServiceFactory
| ServiceFactoryImpl serviceFactory = (ServiceFactoryImpl)ServiceFactory.newInstance();
| File mapping = new File("WebRoot/WEB-INF/jaxrpc-mapping.xml");
| URL mappingURL = null;
| try
| {
| mappingURL = mapping.toURL();
| }
| catch (MalformedURLException e)
| {
| e.printStackTrace();
| }
|
| ServiceImpl service = (ServiceImpl)serviceFactory.createService(url, qName, mappingURL);
|
| //get stub or dynamic proxy that supports the specified service endpoint interface
| VaxSoap port = (VaxSoap) service.getPort(VaxSoap.class);
|
| //create PutOrder object
| PutOrder po = new PutOrder(...);
|
| //using SOAP 1.1 and calling the related method on the service endpoint interface
| PutOrderResponse status = port.putOrder(po);
|
| feedback = status.getPutOrderResult();
| //check the PurchaseOrder status
| System.out.println("output order response:" + feedback);
|
| }
| catch(ServiceException se)
| {
| System.out.println("Service Exception from executePutPurchaseOrder() = "+se.getMessage());
| }
|
| return feedback;
|
Now when I try to run the client passing the valid parameters, I get the following mapping exception from the Client:
anonymous wrote :
| Could not update IN parameter to be INOUT, as indicated in the mapping: parameters
|
In the generated jaxrpc-mapping.xml (after the wsdl available) all the ~SoapIn wsdl-message from within the related wsdl-message-mapping have this
anonymous wrote :
| INOUT
|
parameter mode defined.
I want to metion that is no denial of traffic and the network is good.
Now this param can be IN, OUT, or INOUT. I should not have to modify this generated xml file! However if I modify it and put "IN" instead of "INOUT" I am able to go further (but this in fact is not correct because the called method has to return a PutOrderResponse object so we need the INOUT isn't it ?). Anyway using a modified jaxrpc-mapping.xml as I said before I am able to make the invokation to the remote web service but it barfs here:
anonymous wrote :
| org.jboss.remoting.CannotConnectException: Can not connect http client invoker.
|
This exception is generated when the remoting layer cannot connect to
the remote server . It means that the client cannot send the request to
the server. Well it's normal I think when the remote side is on .NET and the JBoss TransporterClient(InvokerLocator locator, String targetSubsystem) it's trying to use a org.jboss.remoting.InvokerLocator which will work as it is only between JBOSS application servers (correct me if I'm wrong please). The JBossWS fails to create properly the org.jboss.remoting.Client remoteClient instance.
How can one explicitly set the transport protocol to be "http" (and not "socket" as for the JBoss AS) ?
I mean the InvokerLocator has to take that into consideration when trying to connect to .NET webservices right ?
There is some documentation or useful links related to how to connect to .NET webservices ? I will have also my own JBoss webservices which will have to be accessible from any endpoint (well .NET is the one I'm afraid off and it's causing me grief).
Did I missed something ? I mean the client description is pretty straight forward in the user guide...
Aside: when the "JBoss Remoting" comes in to play ? For what is recommended especially ?If one doesn't use transports and data marshallers or push and pull callbacks, then doesn't need "JBoss Remoting" either right?
I hope to get an answer to this post because this is not trivial to debug and fix. Please help.
I would really appreciate an/any answer as soon as possible.
Thank you in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036197#4036197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036197
From do-not-reply at jboss.com Wed Apr 11 06:43:45 2007
From: do-not-reply at jboss.com (Schludi)
Date: Wed, 11 Apr 2007 06:43:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Maven2,
XDoclet and JBossWS (no webservices shown)
Message-ID: <9218685.1176288225694.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello I have a question. I only want to deploy an EJB written in XDoclet (i know about annotations, but need to publish webservices of an existing project written with XDoclet) which is displayed under http://localhost:8080/jbossws/services
I am using Maven2 and XDoclet.
I will post the POM.XML of the EJB-Project an the EJB's Java-Code.
First the EJB-Code with XDoclet:
| package com.bbraun.bbmag.test;
|
| import java.rmi.RemoteException;
|
| import java.math.*;
| import javax.ejb.SessionBean;
| import javax.ejb.SessionContext;
| import java.math.*;
|
| /**
| * Trade Session EJB manages all Trading services
| *
| * @ejb.bean name="FirstEJBBean"
| * display-name="FirstEJBBean"
| * description="A simple hello world bean."
| * jndi-name="FirstEJBBean"
| * type=stateless
| * view-type="service-endpoint"
| *
| * @ejb.interface
| * service-endpoint-class="com.bbraun.bbmag.test.StatlessEJBEndpoint"
| *
| * @wsee.port-component
| * name="StatlessEJBEndpointPort"
| */
| public class StatlessEjbBean implements SessionBean
| {
|
| BigDecimal yenRate = new BigDecimal("121.6000");
|
| BigDecimal euroRate = new BigDecimal("0.0077");
|
| /**
| * @ejb.interface-method view-type="service-endpoint"
| */
| public BigDecimal dollarToYen(BigDecimal dollars) {
| BigDecimal result = dollars.multiply(yenRate);
| return result.setScale(2, BigDecimal.ROUND_UP);
| }
|
| /**
| * @ejb.interface-method view-type="service-endpoint"
| */
| public BigDecimal yenToEuro(BigDecimal yen) {
| BigDecimal result = yen.multiply(euroRate);
| return result.setScale(2, BigDecimal.ROUND_UP);
| }
|
| public StatlessEjbBean() {
| }
|
| public void ejbCreate() {
| }
|
| public void ejbRemove() {
| }
|
| public void ejbActivate() {
| }
|
| public void ejbPassivate() {
| }
|
| public void setSessionContext(SessionContext sc) {
| }
| }
|
Here is the POM.XML of the EJB-Project:
|
| 4.0.0
|
| com.bbraun.bbmag.test
| FirstEJB
| 0.1
|
| FirstEJB-ejb
| ejb
| FirstEJBejb
| Eine EJB
|
|
|
|
| org.apache.geronimo.specs
| geronimo-j2ee_1.4_spec
| 1.0
| provided
|
|
| commons-logging
| commons-logging
| 1.0.3
| provided
|
|
| axis
| axis
| 1.2
| provided
|
|
| axis
| axis-jaxrpc
| 1.2
| provided
|
|
|
| src/test
|
|
| org.codehaus.mojo
| xdoclet-maven-plugin
|
|
| ejb
| generate-sources
|
| xdoclet
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| org.apache.maven.plugins
| maven-ejb-plugin
|
| true
|
|
| **/ejb/*Bean.class
|
|
|
|
|
|
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036310#4036310
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036310
From do-not-reply at jboss.com Wed Apr 11 08:54:24 2007
From: do-not-reply at jboss.com (openyourmind)
Date: Wed, 11 Apr 2007 08:54:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - It works now
Message-ID: <17731209.1176296064940.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi all,
It works now!!! Thanks for your answers.
This is what we did to correct our issue:
BEFORE we used the following command to generate the keys
| keytool -genkey -alias procedure_key -keystore wsse_procedure.keystore
|
NOW, we use the following command where we explicitly set RSA as the key algorithm
| keytool -genkey -alias procedure_key -keystore wsse_procedure.keystore -keyalg RSA
|
I have to say that the exception message or logs didn't help us much to find our issue. So I guess we were pretty lucky.
Thanks again for your suggestions and see you soon
OYM
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036339#4036339
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036339
From do-not-reply at jboss.com Wed Apr 11 09:02:09 2007
From: do-not-reply at jboss.com (openyourmind)
Date: Wed, 11 Apr 2007 09:02:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WS-Security - Invalid timestamp,
message claimed to be c
Message-ID: <25012138.1176296529795.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi,
We have the same problem and we would be happy to use the future feature Jason asked.
http://jira.jboss.com/jira/browse/JBWS-1316
Bye
OYM
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036341#4036341
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036341
From do-not-reply at jboss.com Wed Apr 11 09:40:37 2007
From: do-not-reply at jboss.com (anescu)
Date: Wed, 11 Apr 2007 09:40:37 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Generated WSDL has default port 8080
even if server runs on
Message-ID: <16708585.1176298837628.JavaMail.jboss@colo-br-02.atl.jboss.com>
I'm trying to run the trailblazer from the JBoss ESB, on JBossAS 4.0.5. (the one shipped with ESB 4.0) I have changed the port on the server to 8090, instead of the default one.
And I have stumbled over a bug related to the WS:
I have changed everywhere in the code & config the port from 8080 to 8090, but when i deploy to JBoss i get this message:
2007-04-11 16:16:32,325 INFO [org.jboss.ws.server.ServiceEndpointManager] WebService started: http://ts541:8080/trailblazer/LoanBrokerWS
Here is a snapshot from the debug section (you can see that every other message reffers to port localhost:8090):
2007-04-11 16:16:31,309 DEBUG [org.jboss.ws.metadata.wsdl.WSDLDefinitionsFactory] parse: file:/D:/Work/jboss-4.0.5/server/default/tmp/jbossws/LoanBrokerWSService64691.wsdl
| 2007-04-11 16:16:31,622 DEBUG [org.jboss.ws.tools.JavaToXSD] load schema: http://localhost:8090/trailblazer=file:/D:/Work/jboss-4.0.5/server/default/tmp/jbossws/JBossWS_localhost_8090_trailblazer64692.xsd
| 2007-04-11 16:16:31,622 DEBUG [org.jboss.ws.utils.JBossWSEntityResolver] resolveEntity: [pub=http://schemas.xmlsoap.org/soap/encoding/,sysid=null]
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLInterface] new WSDLInterface
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLInterface] setName: LoanBrokerWS
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLInterface] setQName: {http://localhost:8090/trailblazer}LoanBrokerWS
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLBinding] new WSDLBinding
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLBinding] setQName: {http://localhost:8090/trailblazer}LoanBrokerWSBinding
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLBinding] setName: LoanBrokerWSBinding
| 2007-04-11 16:16:31,669 DEBUG [org.jboss.ws.metadata.wsdl.WSDLBinding] setInterfaceName: LoanBrokerWSBinding
| 2007-04-11 16:16:31,684 DEBUG [org.jboss.ws.deployment.AbstractMetaDataBuilder] Replace service endpoint address 'REPLACE_WITH_ACTUAL_URL' with 'http://ts541:8080/trailblazer/LoanBrokerWS'
If you haven't fixed this issue maybe you can investigate the problem?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036352#4036352
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036352
From do-not-reply at jboss.com Wed Apr 11 09:56:52 2007
From: do-not-reply at jboss.com (xslava)
Date: Wed, 11 Apr 2007 09:56:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: @Interceptor call failure on
@WebMethod
Message-ID: <21997789.1176299812499.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi,
I have the same problem. Enviroment:
jboss-4.0.5.GA
jboss-EJB-3.0_RC9_Patch_1
jbossws-1.2.0.SP1
Interceptor don't work until bean implements interface marked with @Remote or @Local annotation.
Slava
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036369#4036369
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036369
From do-not-reply at jboss.com Wed Apr 11 12:39:18 2007
From: do-not-reply at jboss.com (d_pavel)
Date: Wed, 11 Apr 2007 12:39:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JSR-109Client,
Mapping problem and trying to connect to
Message-ID: <25133548.1176309558116.JavaMail.jboss@colo-br-02.atl.jboss.com>
OK this is what I discovered:
The "Could not update IN parameter to be INOUT..." error comes from processOutputDocElement method inside JAXRPCMetaDataBuilder class. The processOutputDocElement is called from
anonymous wrote :
| buildParameterMetaDataDoc(OperationMetaData opMetaData, WSDLInterfaceOperation wsdlOperation, ServiceEndpointMethodMapping seiMethodMapping,TypeMappingImpl typeMapping)
|
Now the description of this class is mentioning: "A meta data builder that is based on webservices.xml." So I supposed that this error occurs due to issues related to my webservices.xml.
Here is my webservices.xml :
|
|
| Vax
| WebRoot/WEB-INF/wsdl/Vax.wsdl
| WebRoot/WEB-INF/jaxrpc-mapping.xml
|
| VaxSoapPort
|
| anonymous wrote : portNS:VaxSoapPort
| ca.agenthttp.vax.VaxSoap
|
| VaxSoap
|
|
|
|
|
Now from the docs we know:
anonymous wrote :
| The port-component-name element specifies a port component's name. This name is assigned by the module producer to name the service implementation bean in the module's deployment descriptor. The name must be unique among the port component names defined in the same module.
| Used in: port-component
| Example:
| EmployeeService
|
|
So according to this the wsdl-port tag line should be like this:
anonymous wrote :
| portNS:VaxSoapPort
|
I tried also to provide the target namespace like in the commented line:
anonymous wrote :
|
|
(even if I know the correct use is like in the previous uncommented line) but with same error results:
anonymous wrote :
| Could not update IN parameter to be INOUT, as indicated in the mapping: parameters
|
Is it possible that this occurs because the wsdl location URL points to
anonymous wrote :
| https://www.acompany.com/VaxHttp/Vax?wsdl
|
but the real SEI is in fact "VaxSoap" class ???
Let me explain: "Vax" referenced in URL is just a simple javax.xml.rpc.Service and looks like this:
| /*
| * JBoss, the OpenSource EJB server
| * Distributable under LGPL license. See terms of license at gnu.org.
| */
|
| //Auto Generated by jbossws - Please do not edit!!!
|
| package ca.agenthttp.vax;
|
|
| import javax.xml.rpc.*;
|
|
| public interface Vax extends javax.xml.rpc.Service
| {
|
| public ca.agenthttp.vax.VaxSoap getVaxSoap() throws ServiceException;
|
| }
|
Now the ca.agenthttp.vax.VaxSoap is my real SEI which contains references to all the published methods which are web servable.
Please confirm to me if this webservices.xml is properly configured or if I have to reconfigure some other .xml files.
Last but not least this is my jboss-client.xml file:
|
|
|
| jbossws-client
|
| Vax
|
| https://www.acompany.com/VaxHttpTest/Vax.asmx?wsdl
|
|
|
|
The service defined in Wax.wsdl looks like this:
|
|
|
|
|
|
Any suggestions ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036444#4036444
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036444
From do-not-reply at jboss.com Thu Apr 12 05:38:06 2007
From: do-not-reply at jboss.com (shiransf)
Date: Thu, 12 Apr 2007 05:38:06 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Disableing MTOM
Message-ID: <23913315.1176370686726.JavaMail.jboss@colo-br-02.atl.jboss.com>
I wanted to do the same in jboss 4.0.5 but found that jbossws-core.jar doesn't contain required handler class org.jboss.ws.xop.DisableMTOMHandler.
Is there a equivalent handler class for this?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036650#4036650
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036650
From do-not-reply at jboss.com Thu Apr 12 10:16:46 2007
From: do-not-reply at jboss.com (ltenmatay)
Date: Thu, 12 Apr 2007 10:16:46 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SOAP Message with Body of any type
Message-ID: <12018050.1176387406203.JavaMail.jboss@colo-br-02.atl.jboss.com>
Is it possible to create a wsdl that accepts a soap:body of any/anyType? And just let JAXB 2.0 convert it to an element list. I have been trying, but only successful in creating an element of complexType that accepts any element as body. Seems wsconsume does not allow a message part that does not correspond to any element in wsdl. Is it possible to be able to use a dynamic first child element of the SOAP:BODY element?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036735#4036735
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036735
From do-not-reply at jboss.com Thu Apr 12 11:01:30 2007
From: do-not-reply at jboss.com (oskar.carlstedt)
Date: Thu, 12 Apr 2007 11:01:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SOAP Message with Body of any type
Message-ID: <16567683.1176390090688.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello!!
I'm not sure if I understand you right here. Take a look at writing you own endpoint provider http://jbws.dyndns.org/mediawiki/index.php/JAX-WS_User_Guide#Endpoint_Provider. It may help you.
Best
Oskar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036759#4036759
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036759
From do-not-reply at jboss.com Thu Apr 12 14:16:54 2007
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 12 Apr 2007 14:16:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Pooling pojos
Message-ID: <1254296.1176401814618.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hmm, I would have to research how this is done in Tomcat (or now, JBoss Web Server) for servlets. And even provide some kind of init() and destroy() capability. Sounds like a challenge. If no-one else picks it up soon I just might work on this (I am a little swamped for the next week or so).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036831#4036831
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036831
From do-not-reply at jboss.com Thu Apr 12 16:40:03 2007
From: do-not-reply at jboss.com (alexboyer)
Date: Thu, 12 Apr 2007 16:40:03 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Losing soap request after it gets
to server
Message-ID: <23554865.1176410403123.JavaMail.jboss@colo-br-02.atl.jboss.com>
I needed all these entries in my service endpoint implementation:
@javax.jws.WebService(endpointInterface="com.company.ws.service.ServicePortType",
name="ServicePortType",
portName="ServicePort",
wsdlLocation="META-INF/wsdl/Service.wsdl",
targetNamespace = "http://company.com/ws/service",
serviceName="Service")
This is just an example, not the real values. Without all these entries jboss tried to generate things instead of using what I supplied. For instance the reason I was losing my soap request was that a new request wrapper was being generated with a different package. So when my impl method was called it was called with a null request object. My soap message had been bound to the generated request wrapper, not the type of object my impl method required.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036859#4036859
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036859
From do-not-reply at jboss.com Fri Apr 13 09:41:49 2007
From: do-not-reply at jboss.com (wilth)
Date: Fri, 13 Apr 2007 09:41:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SoapBodyImpl, JDK5 and JDom
Message-ID: <25742046.1176471709326.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello,
I recently tried to upgrade from JDK 1.4 to JDK 5 (we are talking Jboss 4.0.5) but I'm having trouble with the following piece of code:
| org.jdom.Document doc = new org.jdom.Document();
| org.jdom.Element root = new org.jdom.Element("inputData");
| doc.setRootElement(root);
|
| MessageFactory messageFactory = MessageFactory.newInstance();
|
| // Create the SOAP Message
| SOAPMessage requestSoapMessage = messageFactory.createMessage();
|
| DOMOutputter converter = new DOMOutputter();
| org.w3c.dom.Document iDoc = converter.output(doc);
| requestSoapMessage.getSOAPBody().addDocument(iDoc);
|
As you can see, I'm creating an XML Document programmatically with JDom, then I'm converting it into a "standard" DOM and then I'm putting it into a SOAP envelope. The addDocument method throws:
org.w3c.dom.DOMException: NAMESPACE_ERR: An attempt is made to create or change an object in a way which is incorrect with regard to namespaces.
Now this error should be raised when a prefix is used, but no namespace or the qualified name is malformed. However, I'm not using namespaces in my document (other than the empty default NS).
I have tried to add a namespace to the Dom4j Document - that solves the problem. The document (when outputted through a transformer) is well-formed. The problem also does not occur with JDK 1.4 or JDK 6 u1. I'm not sure the problem is with the Jboss WS package either, so please let me know if this is not related to the jboss ws implementation.
Any ideas on why I'm facing this? Thanks for any pointers.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037071#4037071
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037071
From do-not-reply at jboss.com Fri Apr 13 17:17:26 2007
From: do-not-reply at jboss.com (TTHUNT)
Date: Fri, 13 Apr 2007 17:17:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Issues with JBoss5 Beta 1 and
WebService Annotations
Message-ID: <22275345.1176499046327.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi,
I'm trying to run a simple test in which I'd like to deploy an EJB in JBoss 5 Beta 1 (with Java 6). I've created an interface and implementation class (see below), put them in a JAR file and deploy the JAR. I can see on the console output that it is reading in the JAR file and creating an EJB, but there is nothing for the WebService. When I got to http://localhost:8080/jbossws/services there are no services listed. There are no errors reported either. I would expect something to come back. Is there a setting that needs to be changed for WebServices to auto deploy in JBoss 5? Is this a bug?
Thanks,
TTH
INTERFACE
package com.simple;
|
| import javax.jws.WebService;
| import javax.jws.WebMethod;
| import java.rmi.Remote;
|
| @WebService
| public interface Hello extends Remote {
| @WebMethod
| void speak();
|
| }
IMPLEMENTATION
package com.simple;
|
| import javax.jws.WebService;
| import javax.ejb.Remote;
| import javax.ejb.Stateless;
|
| @WebService
| @Remote(Hello.class)
| @Stateless
| public class HelloBean implements Hello{
| public void speak(){
| System.out.println("Hello");
| }
| }
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037235#4037235
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037235
From do-not-reply at jboss.com Fri Apr 13 18:21:20 2007
From: do-not-reply at jboss.com (jposnersails)
Date: Fri, 13 Apr 2007 18:21:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Generated WSDL has default port
8080 even if server runs
Message-ID: <20062037.1176502880329.JavaMail.jboss@colo-br-02.atl.jboss.com>
I have the same problem deploying the Duke's Bank (sample app) following the Getting Started Guide. I searched through every source, xml, property, etc. file and found nothing.
Please xpost if you get a solution. I'm stumped!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037258#4037258
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037258
From do-not-reply at jboss.com Sat Apr 14 10:46:59 2007
From: do-not-reply at jboss.com (chui)
Date: Sat, 14 Apr 2007 10:46:59 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - String[] with SOAP... Please help me!
Message-ID: <4616412.1176562019063.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello there! I'm trying to develop a HelloWorld with JBossWS1.0.4, JBossAS4.0.5 and EJB3, but instead of returning a string "Hello World", I'd like to receive a String[]...
If I don't create a wsdl, JBossAS autocreate a default file, where the String[] is mapped as a NMTOKENS type. I don't want that because my array [Hello World, Hello World] becomes [Hello, World, Hello, World]... So I used WStools for creating a wsdl. That's my wstools-config.xml:
anonymous wrote :
| -
|
|
|
|
|
|
I found something similar on the userguide and I used interfaces/jaws because JBoss complained if I didn't. WStools generated the wsdl and the mapping xml. Here is the wsdl: http://www.linux.ime.usp.br/~chui/HelloService.wsdl
However, isn't accepted when deploying the EJB, so I have to change that to HelloServicePort. And I don't know what I should write as =/ Yeah, I'm newbie.
This is the generated jaxrpc-mapping.xml:
anonymous wrote :
| -
| -
| interfaces
| http://org.jboss.ws/samples/rpcstyle/types
|
| -
| interfaces.HelloService
| serviceNS:HelloService
| -
| HelloSEIPort
| HelloSEIPort
|
|
| -
| interfaces.HelloSEI
| portTypeNS:HelloSEI
| bindingNS:HelloSEIBinding
| -
| hello
| hello
| -
| 0
| java.lang.String
| -
| wsdlMsgNS:HelloSEI_hello
| String_1
| IN
|
|
| -
| java.lang.String[]
| wsdlMsgNS:HelloSEI_helloResponse
| result
|
|
|
|
Finally I could deploy the bean. But, when I call it using a client application, I receive this error:
anonymous wrote : java.rmi.RemoteException: Call invocation failed; nested exception is:
| org.jboss.ws.WSException: org.jboss.ws.binding.BindingException: org.jboss.ws.jbossxb.UnmarshalException: Failed to parse source: Not supported xsdType: anyType, hashCode=-842881210
As you can see, I never used anyType. So I tried to find where's this term... And I found it here: http://www.w3.org/2001/XMLSchema.xsd
Now I ask you:
1-) Why do I need to use http://interfaces/jaws ??
2-) How can I receive the String[]??? The bean is being called, but the client can't receive the result =(
Please help me! I REALLY NEED this to function so I can apply it to my real (and also EJB3+WS) project...
Thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037307#4037307
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037307
From do-not-reply at jboss.com Sun Apr 15 12:01:00 2007
From: do-not-reply at jboss.com (ltenmatay)
Date: Sun, 15 Apr 2007 12:01:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SOAP Message with Body of any type
Message-ID: <61728.1176652860619.JavaMail.jboss@colo-br-02.atl.jboss.com>
Thanks! got it to work cause of your suggestion.
Btw, my previous wasn't really clear. I wanted to create a soap service in which the body is dynamic. I have no choice since the wsdl I got defined it that way. Problem is that the classes i generated using wsconsume expected the first child element of the soap body to be always the same. Same as the element name used in wsdl.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037376#4037376
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037376
From do-not-reply at jboss.com Sun Apr 15 12:07:02 2007
From: do-not-reply at jboss.com (ltenmatay)
Date: Sun, 15 Apr 2007 12:07:02 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Soap with attachments
Message-ID: <22319626.1176653222225.JavaMail.jboss@colo-br-02.atl.jboss.com>
Would like to know how to support soap message with attachments in jbossws 1.2.0 SP1. Do I need to define multipart section in my wsdl? The wsdl i got didn't specify any mime sections. I created my own provider. Whenever I send a soap with attachment, the jboss will throw a timeout error and it does not reach the provider.
I am using saaj and the message is something like this
------=_Part_0_22691179.1176653070718
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: binary
Content-Id:
soap xml
------=_Part_0_22691179.1176653070718
Content-Type: application/octet-stream
Content-Transfer-Encoding: binary
Content-Id:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037378#4037378
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037378
From do-not-reply at jboss.com Mon Apr 16 00:37:32 2007
From: do-not-reply at jboss.com (bittu.arvind)
Date: Mon, 16 Apr 2007 00:37:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - java.sql.SQLException: File
input/output error: Unexpected
Message-ID: <32033829.1176698252874.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi all,
i am new in this area. i have installed netbeans ide 5.5 daily bundled with jboss-4.0.4, when i am strting the jboss server using netbeans "run time tab", i am geeting following error.
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\jboss-4.0.4.GA\bin\\..
.
JAVA: C:\Program Files\Java\jdk1.5.0_11\bin\java
.
JAVA_OPTS: -Dhttp.proxyHost=199.63.1.0 -Dhttp.proxyPort=80 -Dhttp.nonProxyHosts="*.honeywell.com|*|localhost|127.0.0.1|ie10dtxp6b3zl1s|ie10dtxp6b3zl1s.global.ds.honeywell.com" -Dhttps.proxyHost=199.63.1.0 -Dhttps.proxyPort=80 -Dprogram.name=run.bat -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
.
CLASSPATH: C:\Program Files\Java\jdk1.5.0_11\lib\tools.jar;C:\jboss-4.0.4.GA\bin\\run.jar
.
===============================================================================
.
09:49:38,578 INFO [Server] Starting JBoss (MX MicroKernel)...
09:49:38,578 INFO [Server] Release ID: JBoss [Zion] 4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)
09:49:38,593 INFO [Server] Home Dir: C:\jboss-4.0.4.GA
09:49:38,593 INFO [Server] Home URL: file:/C:/jboss-4.0.4.GA/
09:49:38,593 INFO [Server] Patch URL: null
09:49:38,593 INFO [Server] Server Name: default
09:49:38,593 INFO [Server] Server Home Dir: C:\jboss-4.0.4.GA\server\default
09:49:38,593 INFO [Server] Server Home URL: file:/C:/jboss-4.0.4.GA/server/default/
09:49:38,703 INFO [Server] Server Log Dir: C:\jboss-4.0.4.GA\server\default\log
09:49:38,703 INFO [Server] Server Temp Dir: C:\jboss-4.0.4.GA\server\default\tmp
09:49:38,703 INFO [Server] Root Deployment Filename: jboss-service.xml
09:49:39,046 INFO [ServerInfo] Java version: 1.5.0_11,Sun Microsystems Inc.
09:49:39,046 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_11-b03,Sun Microsystems Inc.
09:49:39,046 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
09:49:39,703 INFO [Server] Core system initialized
09:49:41,000 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
09:49:46,453 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://199.63.66.250:3873/]
09:49:47,765 INFO [AspectDeployer] Deployed AOP: file:/C:/jboss-4.0.4.GA/server/default/deploy/ejb3-interceptors-aop.xml
09:50:00,609 INFO [WebService] Using RMI server codebase: http://ie10dtxp6b3zl1s:8083/
09:50:02,609 INFO [MailService] Mail Service bound to java:/Mail
09:50:02,937 INFO [NamingService] JNDI bootstrap JNP=/0.0.0.0:1099, RMI=/0.0.0.0:1098, backlog=50, no client SocketFactory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
09:50:02,937 WARN [NamingService] Context.PROVIDER_URL in server jndi.properties, url=localhost:1099
09:50:03,015 INFO [SubscriptionManager] Bound event dispatcher to java:/EventDispatcher
09:50:03,796 INFO [Embedded] Catalina naming disabled
09:50:03,859 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
09:50:03,859 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set.
09:50:04,203 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080
09:50:04,203 INFO [Catalina] Initialization processed in 344 ms
09:50:04,203 INFO [StandardService] Starting service jboss.web
09:50:04,203 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.17
09:50:04,250 INFO [StandardHost] XML validation disabled
09:50:04,265 INFO [Catalina] Server startup in 62 ms
09:50:04,406 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/
09:50:04,890 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined
09:50:05,484 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp17170jbossws-exp.war/
09:50:05,656 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
09:50:06,781 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
09:50:07,203 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
09:50:07,312 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
09:50:07,328 INFO [QuartzResourceAdapter] start quartz!!!
09:50:07,406 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
09:50:07,437 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
09:50:07,437 INFO [RAMJobStore] RAMJobStore initialized.
09:50:07,546 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
09:50:07,546 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
09:50:07,546 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
09:50:08,218 WARN [ServiceController] Problem starting service jboss:service=Hypersonic,database=localDB
java.sql.SQLException: File input/output error: Unexpected token:
why this error is coming?? and how i can solve this???
please give reply as soon as possible.
thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037424#4037424
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037424
From wolfgang.moser at src-gmbh.de Mon Apr 16 04:05:34 2007
From: wolfgang.moser at src-gmbh.de (Wolfgang Moser)
Date: Mon, 16 Apr 2007 10:05:34 +0200
Subject: [jbossws-users] How to disable weak ciphersuites for a SSL secured
webservice
In-Reply-To: <460A4F69.6000908@src-gmbh.de>
References: <460A4F69.6000908@src-gmbh.de>
Message-ID: <46232E4E.6090002@src-gmbh.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
I got my requirements solved. According to:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=75091
configuring the Tomcat connector to (via
deploy/jbossweb-tomcat55.sar/server.xml):
restricts the available server-side SSL/TLS
ciphersuites to the ones given.
- --
Mit freundlichen Gr??en,
Wolfgang Moser
_______________________________________________________________
SRC Security Research & Consulting GmbH
Graurheindorfer Str. 149 a Tel: +49(0)228-2806-149
53117 Bonn Fax: +49(0)228-2806-199
http://www.src-gmbh.de Mob: +49(0)
Handelsregister Bonn: HRB 9414 Gesch?ftsf?hrer: Gerd Cimiotti
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
iQEVAwUBRiMuTV351eL5alt0AQipGgf+MR0ZU9SNnRSa9GjgmoEDvvl7rj5BZJlK
T+dF81yY06UPYR9tQ4GSpEApi9kTFzDbTx8+Ig4/2HyGSMDV7ajqKpI2Mf115x/2
9m9GzrC5RWHQkcYP7nduqLzHIGPuuqpc6SzM3SjfyanMkyp55+BpUDoKt0AOMDoy
u7qv3FAlW4CxJ3gHyQHvW+GubeU1KvEyK5ywj98JCTwokL4puLQ2mft/HJAO5FUH
NeCWNgsWnBflh9shObCGc/AMrD0m8ykmZ5y66zomGqgTmeKDRejNttEtJqi457Dk
pgT/7fS8UunVzDwEnbcUZW2CIsEHI1YHr2mS/4OZqAJJ4ba0cv6fbA==
=pq/2
-----END PGP SIGNATURE-----
From do-not-reply at jboss.com Mon Apr 16 04:16:00 2007
From: do-not-reply at jboss.com (anescu)
Date: Mon, 16 Apr 2007 04:16:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Generated WSDL has default port
8080 even if server runs
Message-ID: <33287467.1176711360512.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hi,
I found no solution for this. I finally found out what was keeping the port 8080 occupied (the firewall client, off course), so I changed Tomcat's port to 8080 and it worked. I guess nobody from WS project is looking over this topic??? Can we post a JIRA issue about this bug?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037450#4037450
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037450
From do-not-reply at jboss.com Mon Apr 16 05:12:33 2007
From: do-not-reply at jboss.com (oskar.carlstedt)
Date: Mon, 16 Apr 2007 05:12:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Element or attribute do not match QName
production: QName::=
Message-ID: <12686597.1176714753414.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello!!
I'm getting a strange exception when invoking a simple client inside a stateless session bean. Everything has to do with the javax.xml.namespace.QName. I'm using xml beans which I had to modify because of an extra include of the javax.xml.namespace.QName, i.e. I have removed the javax.xml.namespace from the xbean.jar.
I have the following code:
| XmlOptions xmlOptions = new XmlOptions();
| xmlOptions.setSavePrettyPrint();
|
| // create target namespace
| String targetNamespace = "http://test/test-service";
|
| QName serviceQName = new QName(targetNamespace, "Test");
| QName portTypeQname = new QName(targetNamespace, "TestSoap11Port");
| URL wsdlURL = new URL("http://lpt-osca:8080/service-test-jaxws-web?wsdl");
|
| Service service = Service.create(wsdlURL, serviceQName);
| Dispatch dispatch = service.createDispatch(portTypeQname, DOMSource.class, Mode.PAYLOAD);
|
| // creating xml beans request ...
| TestRequestDocument testRequestDocument = TestRequestDocument.Factory.newInstance();
| ...
|
| System.out.println("REQUEST");
| testRequestDocument.save(System.out, xmlOptions);
| System.out.println();
|
| DOMSource requestSource = new DOMSource(testRequestDocument.newDomNode());
| DOMSource responseSource = dispatch.invoke(requestSource);
| XmlObject xmlObject = XmlObject.Factory.parse(responseSource.getNode());
|
| System.out.println("RESPONSE");
| xmlObject.save(System.out, xmlOptions);
|
|
And I'm getting the following error:
| 2007-04-16 10:31:51,636 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml; charset=UTF-8]
| 2007-04-16 10:31:51,665 ERROR [STDERR] [Fatal Error] :1:331: Element or attribute do not match QName production: QName::=(NCName':')?NCName.
| 2007-04-16 10:31:51,691 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure SOAPBinding
| 2007-04-16 10:31:51,691 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception
| java.io.IOException: org.xml.sax.SAXParseException: Element or attribute do not match QName production: QName::=(NCName':')?NCName.
| at org.jboss.ws.core.utils.DOMUtils.parse(DOMUtils.java:125)
| at org.jboss.ws.core.soap.EnvelopeBuilderPayload.build(EnvelopeBuilderPayload.java:56)
| at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:253)
| at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
| at org.jboss.ws.core.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:185)
| at org.jboss.ws.core.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:440)
| at org.jboss.ws.core.server.AbstractServiceEndpointServlet.doPost(AbstractServiceEndpointServlet.java:114)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.ws.core.server.AbstractServiceEndpointServlet.service(AbstractServiceEndpointServlet.java:75)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
Can anyone explain this to me. I found the same error for someone using axis thread about using a different constructor when instantiating the QName (http://forums.crmsuccess.com/sforce/board/message?board.id=JAVA_development&message.id=962), but can it be that? Sounds strange to me. Is there a conflict between my jvm/jee (using std sun when compiling) and the JBoss environment.
I have JBoss 4.0.5.GA with EJB3 RC9 and JBossWS 1.2.0SP1. I'm running everything on a Windows Vista E.Ed. with JDK 1.5.11.
Best Regardsd
Oskar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037472#4037472
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037472
From do-not-reply at jboss.com Mon Apr 16 05:16:28 2007
From: do-not-reply at jboss.com (oskar.carlstedt)
Date: Mon, 16 Apr 2007 05:16:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Element or attribute do not match
QName production: QNam
Message-ID: <10330086.1176714988226.JavaMail.jboss@colo-br-02.atl.jboss.com>
... one more thing ...
I'm running JBoss in isolated mode. All xmlbeans jar file are bundled in the EAR file.
//Oskar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037474#4037474
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037474
From do-not-reply at jboss.com Mon Apr 16 10:17:58 2007
From: do-not-reply at jboss.com (RomeuFigueira)
Date: Mon, 16 Apr 2007 10:17:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Generated WSDL has default port
8080 even if server runs
Message-ID: <2644006.1176733078576.JavaMail.jboss@colo-br-02.atl.jboss.com>
Until 1.0.4 you need to change also this line:
8080
which is located in deploy\jbossws.sar\jbossws.beans\META-INF\jboss-beans.xml
You will need to expload jbossws.sar and jbossws.beans to get access to that particular xml file.
Once changed, both your tomcat an jbossws ports to the same one, you should have no problem regarding this issue.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037565#4037565
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037565
From do-not-reply at jboss.com Mon Apr 16 10:57:45 2007
From: do-not-reply at jboss.com (anescu)
Date: Mon, 16 Apr 2007 10:57:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Generated WSDL has default port
8080 even if server runs
Message-ID: <19331147.1176735465360.JavaMail.jboss@colo-br-02.atl.jboss.com>
Great,
Thanks for the info. I searched everywhere for the 8080 string, but I guess the search treated jbossws.beans as a binary file, not as an archive.
Why is it jboss-beans.xml pachaged inside a jbossws.beans archive? Why not put directly the file under the META-INF dir as the other 3 XML files?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4037590#4037590
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4037590
From do-not-reply at jboss.com Mon Apr 16 11:44:12 2007
From: do-not-reply at jboss.com (oskar.carlstedt)
Date: Mon, 16 Apr 2007 11:44:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to provide soapAction from dispatch
call?
Message-ID: <27504912.1176738252709.JavaMail.jboss@colo-br-02.atl.jboss.com>
Hello!
I've tried a to fix this for some hours know. Maybe I'm doing something completely wrong here.
I have a web service client that that is using the dispatch technique. I will use the dispatch because I'm using xmlbeans to bind my data. Here is a little code snippet of what I'm trying to do:
| // names
| String targetNamespace = "http://test/test-service";
| QName serviceQName = new QName(targetNamespace, "TestService");
| QName portQName = new QName(targetNamespace, "TestServiceSoap11Port");
| URL wsdlURL = new URL("http://lpt-osca:8080/service-testservice-jaxws-web?wsdl");
|
| // create service
| Service service = Service.create(serviceQName);
| service.addPort(portQName, SOAPBinding.SOAP11HTTP_BINDING, wsdlURL.toExternalForm());
| Dispatch dispatch = service.createDispatch(portQName, StreamSource.class, Mode.PAYLOAD);
|
| // set SOAPAction
| dispatch.getRequestContext().put(BindingProvider.SOAPACTION_USE_PROPERTY, true);
| dispatch.getRequestContext().put(BindingProvider.SOAPACTION_URI_PROPERTY, "uri:placeBuyOrder");
|
| // create xml options for pretty print
| XmlOptions xmlOptions = new XmlOptions();
| xmlOptions.setSavePrettyPrint();
|
| // create request
| TestRequestDocument testRequestDocument = TestRequestDocument.Factory.newInstance();
| ...
|
|
| // print request
| System.out.println("REQUEST");
| testRequestDocument.save(System.out, xmlOptions);
| System.out.println();
|
| // save request in a stream
| ByteArrayOutputStream requestByteArrayOutputStream = new ByteArrayOutputStream();
| testRequestDocument.save(requestByteArrayOutputStream);
|
| // create a new stream source
| StreamSource requestStreamSource = new StreamSource(new ByteArrayInputStream(requestByteArrayOutputStream.toByteArray()));
|
| // invoke
| StreamSource responseSource = dispatch.invoke(requestStreamSource);
|
| // parse result
| XmlObject xmlObject = XmlObject.Factory.parse(responseSource.getInputStream());
|
| // print response
| System.out.println("RESPONSE");
| xmlObject.save(System.out, xmlOptions);
|
When doing this. it seems like the soap action attribute is not sent to the server, at least not in the http headers. So, my question is: Is the soapAction sent to the sever? If so, where can I find it in the messageContext?
My service is a web service endpoint provider implementation like
| @Stateless
| @WebServiceProvider(
| serviceName = "TestService",
| portName = "TestServiceSoap11Port",
| targetNamespace = "http://test/test-service",
| wsdlLocation = "WEB-INF/wsdl/test-service.wsdl")
| @ServiceMode(value = Service.Mode.PAYLOAD)
| public class FundOrderEndpointProvider implements Provider