From do-not-reply at jboss.com  Tue Dec  1 06:17:10 2009
From: do-not-reply at jboss.com (pvenkatesh)
Date: Tue, 1 Dec 2009 06:17:10 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - How to enable SSL
	security for my webservice?
Message-ID: <22976591.1259666230373.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

Can some one tell me how to enable SSL security for my simple POJO webservice?

Please let me know the exact steps to be followed

Waiting for your response

Thanks

Venkatesh

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268261#4268261

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268261


From do-not-reply at jboss.com  Tue Dec  1 07:49:05 2009
From: do-not-reply at jboss.com (pvenkatesh)
Date: Tue, 1 Dec 2009 07:49:05 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - PKIX path building
	failed: sun.security.provider.certpath.Su
Message-ID: <12585127.1259671745965.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi All

I need your help in enabling security for my webservice

I have tried to enable SSL and encryption for my service, but i failed in both. 

Here i tried to enable SSL security for my service, please find below the steps i have followed

1.I have created keystore and trust store using following commands
keytool -genkey -alias serverkeys -keyalg RSA -keystore server.keystore -storepass 123456 -keypass 123456 -dname "CN=localhost, OU=MYOU, O=MYORG, L=MYCITY, ST=MYSTATE, C=MY"
  | keytool -export -alias serverkeys -keystore server.keystore -storepass 123456 -file server.cer
  | keytool -genkey -alias clientkeys  -keyalg RSA -keystore client.keystore -storepass 123456 -keypass 123456 -dname "CN=localhost, OU=MYOU, O=MYORG, L=MYCITY, S=MYSTATE, C=MY" 
  | keytool -export -alias clientkeys -keystore client.keystore -storepass 123456 -file client.cer
  | keytool -import -v -keystore client.truststore  -storepass 123456 -file server.cer
  | keytool -import -v -keystore server.truststore  -storepass 123456 -file client.cer
  | 

2.I have placed my server.keystore, server.truststore at servers home directory

3.I have updated my server.xml as follows


  | <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
  |                                maxThreads="150" scheme="https" secure="true"
  |                                clientAuth="false" sslProtocol="TLS" 
  |                                keystoreFile="${jboss.server.home.dir}/conf/server.keystore" keystorePass="password"
  |                truststoreFile="${jboss.server.home.dir}/conf/server.truststore" truststorePass="password"/>
  | 
4.My web.xml is as follows
anonymous wrote : 
  |                 
  |                                                 <servlet-name>Hello</servlet-name>
  |                                                 <servlet-class>org.jbia.ws.Hello</servlet-class>
  |                                 
  |                                 <servlet-mapping>
  |                                                 <servlet-name>Hello</servlet-name>
  |                                                 <url-pattern>/hello</url-pattern>
  |                                 </servlet-mapping>
  |                                 
  |                                 <security-constraint> 
  |                     <web-resource-collection> 
  |                       <web-resource-name>All resources</web-resource-name> 
  |                       <url-pattern>/*</url-pattern> 
  |                     </web-resource-collection> 
  |                     <user-data-constraint> 
  |                       <transport-guarantee>CONFIDENTIAL</transport-guarantee> 
  |                     </user-data-constraint> 
  |                 </security-constraint> 
  | 
My service class is as follows
anonymous wrote : 
  |                 package org.jbia.ws;
  |                 import javax.jws.*;
  |                 import javax.jws.soap.SOAPBinding;
  |                 @SOAPBinding(style=SOAPBinding.Style.RPC)
  |                 @WebService
  |                 public class Hello {
  |                    @WebMethod
  |                    public String sayHello(String name){
  |                    return "Hello " + name;
  |                    }
  |                 }
  | 
I have deployed my webservice as .war file in my server then I got the wsdl(generated), using that wsdl I generated my Stub. 

My Client is as follows
anonymous wrote : 
  | package org.jbia.ws;
  |                 public class Client
  |                  {
  |                                 public static void main(String args[]) {
  |                                                 if (args.length != 1) {
  |                                                                 System.err.println("usage: HelloClient ");
  |                                                                 System.exit(1);
  |                                                 }
  |                                                 System
  |                                                                                 .setProperty("org.jboss.wsse.keyStore",
  |                                                                                                                 "D:\\EclipseWorkspace\\Latest\\WebService\\META-INF\\client.keystore");
  |                                                 System.setProperty("org.jboss.wsse.keyStorePassword", "password");
  |                                                 System
  |                                                                                 .setProperty("org.jboss.wsse.trustStore",
  |                                                                                                                 "D:\\EclipseWorkspace\\Latest\\WebService\\META-INF\\client.truststore");
  |                                                 System.setProperty("org.jboss.wsse.trustStorePassword", "password");
  |                                                 try {
  |                 
  |                                                                 HelloProxy proxy = new HelloProxy();
  |                                                                 proxy.setEndpoint("https://127.0.0.1:8443/JBossWS/hello?wsdl");
  |                                                                 proxy.sayHello("Venkat");
  |                                                                 System.out.println("Result = ");
  |                                                 } catch (Exception ex) {
  |                                                                 ex.printStackTrace();
  |                                                                 System.out.println("Exception occurs in web services : " + ex);
  |                                                 }
  |                 
  |                                 }
  |                 }
  | 

Here I am not at all using my certificates i have generated(I am not srue weather this is the issue or not). Please someone correct me if i am wrong.

When i try to acess my service i am getting the following exception

anonymous wrote : 
  | AxisFault
  |  faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
  |  faultSubcode: 
  |  faultString: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |  faultActor: 
  |  faultNode: 
  |  faultDetail: 
  |       {http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1520)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:182)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:176)
  |       at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:975)
  |       at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:123)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:511)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:449)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:817)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1029)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1056)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1040)
  |       at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
  |       at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
  |       at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
  |       at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
  |       at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
  |       at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
  |       at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
  |       at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
  |       at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
  |       at org.apache.axis.client.Call.invoke(Call.java:2767)
  |       at org.apache.axis.client.Call.invoke(Call.java:2443)
  |       at org.apache.axis.client.Call.invoke(Call.java:2366)
  |       at org.apache.axis.client.Call.invoke(Call.java:1812)
  |       at org.jbia.ws.HelloBindingStub.sayHello(HelloBindingStub.java:106)
  |       at org.jbia.ws.HelloProxy.sayHello(HelloProxy.java:50)
  |       at org.jbia.ws.Client.main(Client.java:24)
  | Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285)
  |       at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
  |       at sun.security.validator.Validator.validate(Validator.java:218)
  |       at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
  |       at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
  |       at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
  |       at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:954)
  |       ... 23 more
  | Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
  |       at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
  |       at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
  |       ... 29 more
  | 
  |       {http://xml.apache.org/axis/}hostname:pvenkatesh
  | 
  | javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
  |       at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:154)
  |       at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
  |       at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118), SEND TLSv1 ALERT:  fatal, description = certificate_unknown
  | main, WRITE: TLSv1 Alert, length = 2
  | main, called closeSocket()
  | main, handling exception: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  | 
  |       at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
  |       at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
  |       at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
  |       at org.apache.axis.client.Call.invoke(Call.java:2767)
  |       at org.apache.axis.client.Call.invoke(Call.java:2443)
  |       at org.apache.axis.client.Call.invoke(Call.java:2366)
  |       at org.apache.axis.client.Call.invoke(Call.java:1812)
  |       at org.jbia.ws.HelloBindingStub.sayHello(HelloBindingStub.java:106)
  |       at org.jbia.ws.HelloProxy.sayHello(HelloProxy.java:50)
  |       at org.jbia.ws.Client.main(Client.java:24)
  | Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1520)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:182)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:176)
  |       at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:975)
  |       at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:123)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:511)
  |       at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:449)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:817)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1029)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1056)
  |       at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1040)
  |       at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
  |       at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
  |       at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
  |       at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
  |       ... 12 more
  | Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:285)
  |       at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:191)
  |       at sun.security.validator.Validator.validate(Validator.java:218)
  |       at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)Exception occurs in web services : javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  | HI2
  | 
  |       at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
  |       at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
  |       at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:954)
  |       ... 23 more
  | Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
  |       at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:174)
  |       at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:238)
  |       at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:280)
  |       ... 29 more
  | 
  | 

your inputs are appriciated

Thanks

With Regards
Venkatesh

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268280#4268280

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268280


From do-not-reply at jboss.com  Tue Dec  1 08:07:04 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Tue, 1 Dec 2009 08:07:04 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBossWS is Java EE
	5 compliant?
Message-ID: <29731170.1259672824841.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Peter,

Thanks for your response.  While JBoss AS 5 is JEE5 compliant, do you happen to know if the same is true for JBossWS?  

My main concern is portability for any web services I create in JBossWS should my company decide to change application servers in the future.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268287#4268287

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268287


From do-not-reply at jboss.com  Tue Dec  1 08:25:55 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 1 Dec 2009 08:25:55 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBossWS is Java EE
	5 compliant?
Message-ID: <16947074.1259673955268.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

JBossWS provides the webservice features of JBossAS, which in turn is Java EE 5 compliant. So as long as you use the specs included in Java EE (jaxws for instance) you should not be concerned about portability.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268292#4268292

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268292


From do-not-reply at jboss.com  Tue Dec  1 09:06:58 2009
From: do-not-reply at jboss.com (Minjaman)
Date: Tue, 1 Dec 2009 09:06:58 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Allow HttpSession
	timeout to be set of EJB endpoints
Message-ID: <11118237.1259676418767.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

I have the same question as in JIRA issue JBWS-1202.

I can't find any answer of this question. Is the issue resolved or not? If yes, how can i set the timeout?

Regards
Alexander Kunkel

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268308#4268308

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268308


From do-not-reply at jboss.com  Tue Dec  1 10:02:55 2009
From: do-not-reply at jboss.com (gwzoller)
Date: Tue, 1 Dec 2009 10:02:55 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Newbie: Empty
	ArrayList Passed on WS Call
Message-ID: <3431341.1259679775045.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Here's the rest of the story.  I finally stumbled on the right recipe, and here 'tis.  I was over-complicating things.  Removing almost all the annotations fixed both the list-passing and the WSDL.

Interface:
import java.util.ArrayList;
  | import javax.ejb.Remote;  // for the EJB
  | import javax.jws.WebService;  // for the web service
  | import com.kepler.ecom.domain.OrderLine;
  | 
  | @Remote
  | @WebService
  | public interface OrderTakerRemote {
  | 	public String msg(ArrayList<String> say);
  | }

Implementation:
import javax.ejb.Stateless;
  | import javax.jws.WebService;
  | import com.aviall.kepler.ecom.domain.OrderLine;
  | import com.aviall.kepler.ecom.services.OrderTakerRemote;
  | import java.util.ArrayList;
  | 
  | @WebService
  | @Stateless 
  | public class OrderTaker implements OrderTakerRemote {
  |     public OrderTaker() {
  |     }
  |     
  |     public String msg(ArrayList<String> say) {
  |     	// Use the list here
  |     }
  | }


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268317#4268317

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268317


From do-not-reply at jboss.com  Tue Dec  1 10:57:27 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Tue, 1 Dec 2009 10:57:27 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBossWS is Java EE
	5 compliant?
Message-ID: <4370244.1259683047706.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Great, thanks Alessio.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268325#4268325

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268325


From do-not-reply at jboss.com  Tue Dec  1 11:01:42 2009
From: do-not-reply at jboss.com (pvenkatesh)
Date: Tue, 1 Dec 2009 11:01:42 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JAX-WS Basic
	authorization?
Message-ID: <8721964.1259683302118.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi alessio

I exactly have followed this topic (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=123643) to implement BASIC (authentication) security for my web service, but I am getting the following exeception

Exception in thread "main" java.lang.NoSuchMethodError: org.jboss.wsf.common.DOMUtils.clearThreadLocals()V
      at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:64)
      at javax.xml.ws.Service.(Service.java:57)
      at javax.xml.ws.Service.create(Service.java:302)
      at org.jbia.ws.TestClient.main(TestClient.java:22)
Waiting for your response

Thanks

With regards
Venkat


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268326#4268326

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268326


From do-not-reply at jboss.com  Tue Dec  1 11:01:51 2009
From: do-not-reply at jboss.com (pa12399)
Date: Tue, 1 Dec 2009 11:01:51 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Installing and
	Configuing jbossws for JBOSS App server -
Message-ID: <2557913.1259683311720.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

I am having some errors while deploying webservices.
I am using JBoss 4.2.2.

So, I tried to update the native webservice stack on JBoss 4.2.2 and I found out that the latest stack that is compatible with JBoss 4.2.2 is jbossws-native-3.0.5.

But I could not find jbossws-native-3.0.5 under the download site.

Were you able to successfully upgrade the native stack in JBoss 4.2.2?

Any pointers would be greatly appreciated.

Thank you


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268327#4268327

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268327


From do-not-reply at jboss.com  Tue Dec  1 11:24:45 2009
From: do-not-reply at jboss.com (pa12399)
Date: Tue, 1 Dec 2009 11:24:45 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Reg Installation
Message-ID: <25779873.1259684685613.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am having a similar issue. I am using JBoss AS 4.2.2GA. I am trying to upgrade to the latest WS native stack - i.e. 3.0.5 that is compatible with JBoss AS 4.2.2. But I am unable to find a link from where I can download 3.0.5 stack. Can someone please help me with this issue?

Thank you

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268334#4268334

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268334


From do-not-reply at jboss.com  Tue Dec  1 12:41:28 2009
From: do-not-reply at jboss.com (jbosssupport)
Date: Tue, 1 Dec 2009 12:41:28 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - JBoss 5.1.0:
	jbossws-native-saaj.jar conflicting with saaj-i
Message-ID: <7205995.1259689288593.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello forum,

Situation:
Using a third party application (Appl1) which can be integrated into custom software. 

Appl1 uses saaj-impl.jar and saaj-api.jar (SUN original) in it's program logic. Both jars(saaj-impl.jar and saaj-api.jar) are located in server/serverDir/lib folder. Using Appl1 directly does not cause any problem!

Requirement:
Implement a WebService Application (WSAppl) using Jboss native WS-Security.

...
@EndpointConfig(configName = "Standard WSSecurity Endpoint")
@SecurityDomain("WSAppl")

WS-Sec Method is UsernameToken.
...

As you can see all WSMethods in WSAppl are secured with jbossws-native-saaj.jar, each of these method requests gets passed to Appl1.

Calling any WSMedod in WSAppl, the following Exception occurs:


  | 2009-12-01 18:03:53,794 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] (http-127.0.0.1-8280-1) SOAP request exception
  | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
  | 	at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:215)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
  | 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Thread.java:595)


Assumption:
JBoss can not use 'jbossws-native-saaj.jar' for WS-Security in WSAppl and 'saaj-impl.jar' afterwards in Appl1 programm logic. 

'jbossws-native-saaj.jar' is located in JBossDir/client folder as standard (no changes to Jboss libs). 


Question:
As I can not change Appl1 Implementation to use jbossws-native-saaj.jar, is there any way to use both different implementations (JBoss native saaj for WS Security and SUN saaj in third party program logic) at the same time in the same Jboss instance?!

Thank you very much!

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268354#4268354

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268354


From do-not-reply at jboss.com  Tue Dec  1 23:32:13 2009
From: do-not-reply at jboss.com (GajananM)
Date: Tue, 1 Dec 2009 23:32:13 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re:
	java.lang.LinkageError: loader constraint violation:(In
Message-ID: <11487772.1259728333501.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

jbossws-cxf-3.2.0.GA download this file

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268413#4268413

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268413


From do-not-reply at jboss.com  Wed Dec  2 02:44:37 2009
From: do-not-reply at jboss.com (rkettelerij)
Date: Wed, 2 Dec 2009 02:44:37 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: jax-ws-catalog.xml
Message-ID: <21184552.1259739877777.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

* bump *

Has anyone figured this out yet. I'm also using a jax-ws-catalog.xml file in my webservice client to translate the WSDL location to a locally packaged WSDL file but JBoss seems to ignore this.

I'm running JBoss 4.2.2 with jbossws-native-2.0.1.SP2. 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268423#4268423

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268423


From do-not-reply at jboss.com  Wed Dec  2 04:50:57 2009
From: do-not-reply at jboss.com (bigriver1973)
Date: Wed, 2 Dec 2009 04:50:57 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Trying to use
	jboss.xml instead of @WebContext
Message-ID: <10558598.1259747457621.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

alessio.soldano, I did a test as your jboss.xml in http://fisheye.jboss.org/changelog/JBossWS/?cs=9609, the tag "auth-method" does work, but if I set it as null(<auth-method></auth-method>), JBoss prompts "Cannot configure an authenticator for method", my web services jar can not be deployed successfully. And since I want to secure the web services transport by HTTPS/SSL, I set the tag "transport-guarantee" to "CONFIDENTIAL" in the file jboss.xml, but it does not work, the WSDL published still has the soap adrress with "http" leading. I use jboss-5.1.0.GA.
This is the jboss.xml file I used:
<?xml version="1.0"?>
<!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 4.2//EN" "http://www.jboss.org/j2ee/dtd/jboss_4_2.dtd">

   <security-domain>java:/jaas/JBossWS</security-domain>
   
 	    <context-root>/myservice</context-root>       
   
   <enterprise-beans>
       
          <ejb-name>SendUpCommandBean</ejb-name>
          <port-component>
              <port-component-name>SendUpCommandBeanPort</port-component-name>
              <port-component-uri>/*</port-component-uri>
              <auth-method>BASIC</auth-method>
              <transport-guarantee>CONFIDENTIAL</transport-guarantee>
              <secure-wsdl-access>false</secure-wsdl-access>
          </port-component>
       
   </enterprise-beans>



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268451#4268451

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268451


From do-not-reply at jboss.com  Wed Dec  2 12:05:16 2009
From: do-not-reply at jboss.com (suryasahu)
Date: Wed, 2 Dec 2009 12:05:16 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Invalid HTTP server
	response [400] - Bad Request
Message-ID: <28901472.1259773516339.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi 

I have a web application running on JBoss 4.2.2 on a Windows Xp machine. It has a Web Service client that was built using JBossWS Native 3.0.4. This client is sending a SOAP packet to a .NET WebService. I get a very high failure rate with the following error. 

>From the exception, it looks like there is something wrong with the Request that is being created. How can find out what exactly is wrong with it? Is there a way to influence the way the request is generated? Any documentation, any pointer would help. 

Thanks.

2009-12-02 10:38:03,234 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] --------------------------
  | ---------
  | 2009-12-02 10:38:03,234 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Error invoking h
  | ttp client invoker.
  | org.jboss.ws.WSException: Invalid HTTP server response [400] - Bad Request ( The HTTP request includ
  | es a non-supported header. Contact your ISA Server administrator.  )
  | 	at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:75)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:473)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:
  | 305)
  | 	at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135)
  | 	at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122)
  | 	at org.jboss.remoting.Client.invoke(Client.java:1634)
  | 	at org.jboss.remoting.Client.invoke(Client.java:548)
  | 	at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:242)
  | 	at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
  | 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  | 	at $Proxy80.sendNotification(Unknown Source)
  | 	at gov.pacts.vccaNotification.queue.QueueProcessor.run(QueueProcessor.java:211)
  | 	at java.lang.Thread.run(Thread.java:619)

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268591#4268591

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268591


From do-not-reply at jboss.com  Wed Dec  2 13:59:08 2009
From: do-not-reply at jboss.com (pa12399)
Date: Wed, 2 Dec 2009 13:59:08 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Problem installing
	jbossws-native-3.1.1.GA onto jboss-4.
Message-ID: <15627211.1259780348610.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

I am having the exact same issue. Were you able to resolve the issue? Any pointers would be greatly appreciated.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268616#4268616

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268616


From do-not-reply at jboss.com  Wed Dec  2 14:03:33 2009
From: do-not-reply at jboss.com (pa12399)
Date: Wed, 2 Dec 2009 14:03:33 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Failed to load
	org.jboss.wsf.spi.invocation.WebServiceContex
Message-ID: <20025768.1259780613734.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

I updated the WS native stack on JBoss 4.2.3 with jbossws-native-3.1.1GA. I am trying to deploy my webservices and I am getting all exceptions in server.log

2009-12-02 13:33:40,372 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.management.ServerConfigFactory'
2009-12-02 13:33:40,373 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] class org.jboss.wsf.spi.management.ServerConfigFactory Implementation: org.jboss.wsf.framework.management.ServerConfigFactoryImpl at 4d4d5e
2009-12-02 13:33:40,373 DEBUG [org.jboss.wsf.stack.jbws.WSDLFilePublisher] Publish WSDL file: file:/opt/vzw/webserver/jboss-4.2.3.GA/server/provapi-ws/tmp/jbossws/OnstarServiceRequestsService403.wsdl
2009-12-02 13:33:40,431 INFO  [org.jboss.wsf.stack.jbws.WSDLFilePublisher] WSDL published to: file:/opt/vzw/webserver/jboss-4.2.3.GA/server/provapi-ws/data/wsdl/OnstarWebService.war/OnstarServiceRequestsService403.wsdl
2009-12-02 13:33:40,448 DEBUG [org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl] ServiceEndpointInvokerDeploymentAspect:Create
2009-12-02 13:33:40,467 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider] provide SPI 'class org.jboss.wsf.spi.invocation.WebServiceContextFactory'
2009-12-02 13:33:40,472 ERROR [org.jboss.deployment.MainDeployer] Could not start deployment: file:/opt/vzw/webserver/jboss-4.2.3.GA/server/provapi-ws/deploy/OnstarWebService.war
java.lang.IllegalStateException: Failed to load org.jboss.wsf.spi.invocation.WebServiceContextFactory: org.jboss.wsf.container.jboss42.WebServiceContextFactoryImpl
        at org.jboss.wsf.spi.util.ServiceLoader.loadFromServices(ServiceLoader.java:97)
        at org.jboss.wsf.spi.util.ServiceLoader.loadService(ServiceLoader.java:59)
        at org.jboss.wsf.framework.DefaultSPIProvider.loadService(DefaultSPIProvider.java:155)
        at org.jboss.wsf.framework.DefaultSPIProvider.getSPI(DefaultSPIProvider.java:140)
        at org.jboss.ws.core.server.ServiceEndpointInvoker.(ServiceEndpointInvoker.java:101)
        at org.jboss.wsf.stack.jbws.ServiceEndpointInvokerDeploymentAspect.create(ServiceEndpointInvokerDeploymentAspect.java:56)
        at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115)
        at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97)
        at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90)
        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 $Proxy41.start(Unknown Source)
        at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
        at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
        at sun.reflect.GeneratedMethodAccessor50.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 $Proxy9.deploy(Unknown Source)
        at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421)
        at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634)
        at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263)



View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268617#4268617

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268617


From do-not-reply at jboss.com  Thu Dec  3 07:37:25 2009
From: do-not-reply at jboss.com (tipsico)
Date: Thu, 3 Dec 2009 07:37:25 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: does not contain
	port: null
Message-ID: <12829247.1259843845062.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

i know this is quite an old topic but i'm having exactly the same problem

did you get this to work?

the wird thing is... at the development envirolment it works... 

but find what's wrong

tks

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268752#4268752

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268752


From do-not-reply at jboss.com  Thu Dec  3 11:17:41 2009
From: do-not-reply at jboss.com (pa12399)
Date: Thu, 3 Dec 2009 11:17:41 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBoss 4.2.2 JDK1.5
	Webservice user-defined Exception han
Message-ID: <24661234.1259857061351.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I finally got this to work. I followed this excellent article on how to handle user-defined exceptions in webservices.

http://io.typepad.com/eben_hewitt_on_java/2009/07/using-soap-faults-and-exceptions-in-java-jaxws-web-services.html

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268830#4268830

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268830


From do-not-reply at jboss.com  Thu Dec  3 12:13:01 2009
From: do-not-reply at jboss.com (anteo)
Date: Thu, 3 Dec 2009 12:13:01 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - web service called
	from a portlet
Message-ID: <786968.1259860381571.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

i have writen a simple webservice with axis2 under eclipse that calculates a random number and have deployed it on jboss.I can also see the wsdl description of the web service in the browser.
I have also written a normal portlet that has a text field and a tree. when a node in the tree is clicked the method nodeSelected in the treeBean is called which calls the webservice and saves the value in a variable that is used from the textfield.so the new value should be shown in the text field. but this doesn't happen

The portlet is beeing deployed so i can create an instance of it and also shown in the portal but when i click on any node of the tree a lot of errors shows up. I tried it on tomcat(just the webservice and the webapplication not as portlet) and everything works fine, with no errors and the response of the webservice is beeing showed in the text field. I have jboss-portal-2.7.2 installed.

the portlet works fine if i don't have webservices

The errors i get when deploying are:

  | 17:22:26,968 INFO  [TomcatDeployer] deploy, ctxPath=/ServiceMitarbeiterPlus_IceF
  | aces(Portlet)_WebService, warUrl=.../tmp/deploy/tmp9935ServiceMitarbeiterPlus_Ic
  | eFaces(Portlet)_WebService-exp.war/
  | 17:22:39,187 INFO  [STDOUT] [INFO]
  | ICEsoft Technologies, Inc.
  | ICEfaces 1.8.2
  | Build number: 7
  | Revision: 19321
  | 17:22:40,359 INFO  [STDOUT] [INFO] ViewRootStateManagerImpl constructed with Del
  | egate: com.sun.faces.application.StateManagerImpl at 18f2af0
  | 17:22:46,218 INFO  [STDOUT] [INFO] Clustering has been disabled
  | 17:23:08,453 INFO  [STDOUT] [INFO] Deploying module: addressing-1.5.1 - file:/C:
  | /Programme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/depl
  | oy/tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/mo
  | dules/addressing-1.5.1.mar
  | 17:23:08,609 INFO  [STDOUT] [INFO] Deploying module: metadataExchange-1.5.1 - fi
  | le:/C:/Programme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tm
  | p/deploy/tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-
  | INF/modules/mex-1.5.1.mar
  | 17:23:08,640 INFO  [STDOUT] [INFO] Deploying module: mtompolicy-1.5.1 - file:/C:
  | /Programme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/depl
  | oy/tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/mo
  | dules/mtompolicy-1.5.1.mar
  | 17:23:08,687 INFO  [STDOUT] [INFO] Deploying module: ping-1.5.1 - file:/C:/Progr
  | amme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/deploy/tmp
  | 9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/modules/
  | ping-1.5.1.mar
  | 17:23:08,765 INFO  [STDOUT] [INFO] Deploying module: script-1.5.1 - file:/C:/Pro
  | gramme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/deploy/t
  | mp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/module
  | s/scripting-1.5.1.mar
  | 17:23:08,796 INFO  [STDOUT] [INFO] Deploying module: soapmonitor-1.5.1 - file:/C
  | :/Programme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/dep
  | loy/tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/m
  | odules/soapmonitor-1.5.1.mar
  | 17:23:08,937 INFO  [STDOUT] [WARN] Exception extracting jars into temporary dire
  | ctory : java.io.FileNotFoundException: C:\Programme\JBoss Application Server\jbo
  | ss-portal-2.7.2\server\default\.\tmp\deploy\tmp9935ServiceMitarbeiterPlus_IceFac
  | es(Portlet)_WebService-exp.war\WEB-INF (Zugriff verweigert) : switching to alter
  | nate class loading mechanism
  | 17:23:08,953 INFO  [STDOUT] [INFO] Deploying Exception Occured with java.io.File
  | NotFoundException: C:\Programme\JBoss Application Server\jboss-portal-2.7.2\serv
  | er\default\.\tmp\deploy\tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebServi
  | ce-exp.war\WEB-INF (Zugriff verweigert)
  | java.lang.RuntimeException: java.io.FileNotFoundException: C:\Programme\JBoss Ap
  | plication Server\jboss-portal-2.7.2\server\default\.\tmp\deploy\tmp9935ServiceMi
  | tarbeiterPlus_IceFaces(Portlet)_WebService-exp.war\WEB-INF (Zugriff verweigert)
  |         at org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:829)
  |         at org.apache.axis2.deployment.util.Utils.createClassLoader(Utils.java:8
  | 82)
  |         at org.apache.axis2.jaxws.framework.JAXWSDeployer.deployServicesInWARCla
  | ssPath(JAXWSDeployer.java:100)
  |         at org.apache.axis2.jaxws.framework.JAXWSDeployer.init(JAXWSDeployer.jav
  | a:80)
  |         at org.apache.axis2.deployment.DeploymentEngine.initializeDeployers(Depl
  | oymentEngine.java:989)
  |         at org.apache.axis2.deployment.DeploymentEngine.setConfigContext(Deploym
  | entEngine.java:981)
  |         at org.apache.axis2.deployment.WarBasedAxisConfigurator.setConfigContext
  | (WarBasedAxisConfigurator.java:350)
  |         at org.apache.axis2.context.ConfigurationContextFactory.createConfigurat
  | ionContext(ConfigurationContextFactory.java:89)
  |         at org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisSer
  | vlet.java:525)
  |         at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:443
  | )
  |         at org.apache.axis2.webapp.AxisAdminServlet.init(AxisAdminServlet.java:5
  | 6)
  |         at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.
  | java:1161)
  |         at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:98
  | 1)
  |         at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContex
  | t.java:4071)
  |         at org.apache.catalina.core.StandardContext.start(StandardContext.java:4
  | 375)
  |         at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase
  | .java:790)
  |         at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:77
  | 0)
  |         at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
  | 
  |         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
  | java:39)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:597)
  |         at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.j
  | ava:296)
  |         at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:1
  | 64)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.apache.catalina.core.StandardContext.init(StandardContext.java:53
  | 12)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
  | java:39)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:597)
  |         at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.j
  | ava:296)
  |         at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:1
  | 64)
  |         at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
  |         at org.jboss.web.tomcat.service.TomcatDeployer.performDeployInternal(Tom
  | catDeployer.java:301)
  |         at org.jboss.web.tomcat.service.TomcatDeployer.performDeploy(TomcatDeplo
  | yer.java:104)
  |         at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:375)
  | 
  |         at org.jboss.web.WebModule.startModule(WebModule.java:83)
  |         at org.jboss.web.WebModule.startService(WebModule.java:61)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
  | upport.java:289)
  |         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
  | eanSupport.java:245)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  |         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
  | java:39)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:597)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.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(ServiceControl
  | ler.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(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:597)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.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 $Proxy201.start(Unknown Source)
  |         at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:46
  | 6)
  |         at sun.reflect.GeneratedMethodAccessor105.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:597)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
  | or.java:133)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
  | BeanOperationInterceptor.java:142)
  |         at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor
  | .java:97)
  |         at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(Intercepto
  | rServiceMBeanSupport.java:238)
  |         at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInt
  | erceptor.java:87)
  |         at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.
  | start(SubDeployerInterceptorSupport.java:188)
  |         at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterce
  | ptor.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 $Proxy202.start(Unknown Source)
  |         at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
  |         at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
  |         at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  | sorImpl.java:25)
  |         at java.lang.reflect.Method.invoke(Method.java:597)
  |         at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
  | er.java:155)
  |         at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
  |         at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
  | or.java:133)
  |         at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
  |         at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
  | BeanOperationInterceptor.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 $Proxy9.deploy(Unknown Source)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
  | tScanner.java:421)
  |         at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
  | canner.java:634)
  |         at org.jboss.deployment.scan
  | 17:23:09,062 INFO  [STDOUT] ner.AbstractDeploymentScanner$ScannerThread.doScan(A
  | bstractDeploymentScanner.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.io.FileNotFoundException: C:\Programme\JBoss Application Server\
  | jboss-portal-2.7.2\server\default\.\tmp\deploy\tmp9935ServiceMitarbeiterPlus_Ice
  | Faces(Portlet)_WebService-exp.war\WEB-INF (Zugriff verweigert)
  |         at java.io.FileInputStream.open(Native Method)
  |         at java.io.FileInputStream.<init>(FileInputStream.java:106)
  |         at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLC
  | onnection.java:105)
  |         at java.net.URL.openStream(URL.java:1009)
  |         at org.apache.axis2.deployment.util.Utils.findLibJars(Utils.java:811)
  |         ... 101 more
  | 17:23:09,296 INFO  [STDOUT] [INFO] Deploying Web service: RandomNumber - file:/C
  | :/Programme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/dep
  | loy/tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/s
  | ervices/RandomNumber/
  | 17:23:09,406 INFO  [STDOUT] [INFO] Deploying Web service: version.aar - file:/C:
  | /Programme/JBoss Application Server/jboss-portal-2.7.2/server/default/./tmp/depl
  | oy/tmp9935ServiceMitarbeiterPlus_IceFaces(Portlet)_WebService-exp.war/WEB-INF/se
  | rvices/version.aar
  | 

and the errors i get when i click on any tree node are:

  | HTTP Status 500 -
  | 
  | type Exception report
  | 
  | message
  | 
  | description The server encountered an internal error () that prevented it from fulfilling this request.
  | 
  | exception
  | 
  | java.lang.RuntimeException: wrapped Exception: java.lang.NullPointerException
  | 	com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:156)
  | 	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:56)
  | 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 
  | root cause
  | 
  | java.lang.NullPointerException
  | 	client.ServiceTest.getWebServiceValue(ServiceTest.java:26)
  | 	basic.TreeBean.nodeSelected(TreeBean.java:249)
  | 	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	java.lang.reflect.Method.invoke(Method.java:597)
  | 	org.apache.el.parser.AstValue.invoke(AstValue.java:131)
  | 	org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
  | 	com.sun.faces.application.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
  | 	javax.faces.component.UICommand.broadcast(UICommand.java:380)
  | 	com.icesoft.faces.component.tree.Tree.broadcast(Tree.java:1075)
  | 	javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
  | 	javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:755)
  | 	com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
  | 	com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
  | 	com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
  | 	com.icesoft.faces.webapp.http.core.JsfLifecycleExecutor.apply(JsfLifecycleExecutor.java:18)
  | 	com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.renderCycle(ReceiveSendUpdates.java:132)
  | 	com.icesoft.faces.webapp.http.core.ReceiveSendUpdates.service(ReceiveSendUpdates.java:74)
  | 	com.icesoft.faces.webapp.http.core.RequestVerifier.service(RequestVerifier.java:31)
  | 	com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service(PathDispatcherServer.java:24)
  | 	com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service(BasicAdaptingServlet.java:16)
  | 	com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
  | 	com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service(SessionDispatcher.java:53)
  | 	com.icesoft.faces.webapp.http.servlet.SessionVerifier.service(SessionVerifier.java:26)
  | 	com.icesoft.faces.webapp.http.servlet.PathDispatcher.service(PathDispatcher.java:23)
  | 	com.icesoft.faces.webapp.http.servlet.MainServlet.service(MainServlet.java:131)
  | 	javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	com.icesoft.faces.webapp.xmlhttp.BlockingServlet.service(BlockingServlet.java:56)
  | 	org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 
  | 

I am searching for three days now for the problem without finding any solution. Can anyone please help me in this?
Thanks a lot
Teo

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4268841#4268841

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4268841


From do-not-reply at jboss.com  Fri Dec  4 09:55:48 2009
From: do-not-reply at jboss.com (damienmc3)
Date: Fri, 4 Dec 2009 09:55:48 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Error with registering
	a RESTeasy Providerfactory
Message-ID: <7606264.1259938548970.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I get the following error:

java.lang.ClassCastException: com.sun.jersey.server.impl.provider.RuntimeDelegateImpl cannot be cast to org.jboss.resteasy.spi.ResteasyProviderFactory 
  |         at org.jboss.resteasy.spi.ResteasyProviderFactory.getInstance(ResteasyProviderFactory.java:330) 
  |         at de.webshop.test.util.RegisterResteasy.register(RegisterResteasy.java:11) 
  |         at de.webshop.test.BestellverwaltungTest.setup(BestellverwaltungTest.java:56) 
  |         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
  |         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) 
  |         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
  |         at java.lang.reflect.Method.invoke(Method.java:617) 
  |         at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) 
  |         at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) 
  |         at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) 
  |         at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:27) 
  |         at org.junit.runners.ParentRunner.run(ParentRunner.java:236) 
  |         at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46) 
  |         at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) 
  |         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) 
  |         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) 
  |         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) 
  |         at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

After I run this code:

package de.webshop.test.util;
  | 
  | import org.jboss.resteasy.plugins.providers.RegisterBuiltin;
  | import org.jboss.resteasy.spi.ResteasyProviderFactory;
  | 
  | public abstract class RegisterResteasy {
  | 	private static boolean registered = false;
  | 	
  | 	public static void register() {
  | 		if (!registered) {
  | 			ResteasyProviderFactory resteasyProviderFactory = ResteasyProviderFactory.getInstance();
  | 			RegisterBuiltin.register( resteasyProviderFactory );
  | 			registered = true;
  | 		}
  | 	}
  | }

What can be the reason ? Thanks for help in advance.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269030#4269030

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269030


From do-not-reply at jboss.com  Fri Dec  4 13:19:55 2009
From: do-not-reply at jboss.com (anteo)
Date: Fri, 4 Dec 2009 13:19:55 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: web service called
	from a portlet
Message-ID: <8936929.1259950795332.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

ok that is now resolved

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269075#4269075

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269075


From do-not-reply at jboss.com  Fri Dec  4 17:07:48 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Fri, 4 Dec 2009 17:07:48 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Cannot call JBoss web
	service through intermediary (soapUI).
Message-ID: <33106961.1259964468739.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

I'm having a bit of an odd problem.  I have deployed a dummy JbossWS web service onto JBoss AS 5.0.1 and developed a client for it using Axis 1.5.  This works fine.

I then loaded up soapUI and pointed it to my web service and ran the test suite.  Again, everything worked.

However, when I attempt to connect through a soapUI mock service, I get an "Missing operation for soapAction [http://hello.ws.com/HelloWorld/helloRequest] and body element [{http://hello.ws.com/}hello] with SOAP Version [SOAP 1.1]" error.

The WSDL's for the two web services are identical except that the one deployed by soapUI prefixes with "<?xml version="1.0" encoding="UTF-8" ?>" while the version created by JBoss has no XMLDecl
element.

I'm not sure if this is a JBossWS, Axis or SoapUI, but I figured I'd try here first.  Any one encountered anthing like this before?

soapUI error:

  | org.apache.axis2.AxisFault: Missing operation for soapAction [http://hello.ws.com/HelloWorld/helloRequest] and body element [{http://hello.ws.com/}hello] with SOAP Version [SOAP 1.1]
  | 	at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:517)
  | 	at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:371)
  | 	at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
  | 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
  | 	at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
  | 	at com.ws.hello.HelloWorldServiceStub.hello(HelloWorldServiceStub.java:181)
  | 	at com.test.TestHelloWorld.testHello(TestHelloWorld.java:27)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 	at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  | 	at java.lang.reflect.Method.invoke(Unknown Source)
  | 	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44)
  | 	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
  | 	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41)
  | 	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
  | 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
  | 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
  | 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73)
  | 	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46)
  | 	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180)
  | 	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41)
  | 	at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173)
  | 	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
  | 	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31)
  | 	at org.junit.runners.ParentRunner.run(ParentRunner.java:220)
  | 	at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:46)
  | 	at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
  | 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
  | 

The web service:

  | package com.ws.hello;
  | 
  | import javax.jws.WebService;
  | 
  | 
  | @WebService
  | public class HelloWorld {
  | 	public String hello(String name) {
  | 		return "Hello "+name;
  | 	}
  | }
  | 

The client:

  | package com.test;
  | 
  | import java.io.IOException;
  | import java.rmi.RemoteException;
  | 
  | import org.junit.BeforeClass;
  | import org.junit.Test;
  | 
  | import com.ws.hello.HelloWorldServiceStub;
  | import com.ws.hello.HelloWorldServiceStub.*;
  | 
  | public class TestHelloWorld {
  | 	private static HelloWorldServiceStub stub;
  | 	
  | 	@BeforeClass
  | 	public static void initialize() throws IOException{
  | 		stub = new HelloWorldServiceStub();
  | 	}
  | 	
  | 	@Test
  | 	public void testHello() throws RemoteException{
  | 		Hello h = new Hello();
  | 		h.setArg0("World");
  | 		HelloE e = new HelloE();
  | 		e.setHello(h);
  | 		
  | 		HelloResponse r = stub.hello(e).getHelloResponse();
  | 		System.out.println(r.get_return());
  | 	}
  | }
  | 

The Axis log (long):

  | - mapActionToOperation: Mapping Action to Operation: action: anonRobustOp; operation: org.apache.axis2.description.RobustOutOnlyAxisOperation at 1f1fba0named: {http://ws.apache.org/namespaces/axis2}anonRobustOp
  | - mapActionToOperation: Mapping Action to Operation: action: urn:anonRobustOp; operation: org.apache.axis2.description.RobustOutOnlyAxisOperation at 1f1fba0named: {http://ws.apache.org/namespaces/axis2}anonRobustOp
  | - Client-defined operation name matches default operation name. this may cause interoperability issues.  Name is: {http://ws.apache.org/namespaces/axis2}anonOutonlyOp
  | - mapActionToOperation: Mapping Action to Operation: action: anonOutonlyOp; operation: org.apache.axis2.description.OutOnlyAxisOperation at 13c5982named: {http://ws.apache.org/namespaces/axis2}anonOutonlyOp
  | - mapActionToOperation: Mapping Action to Operation: action: urn:anonOutonlyOp; operation: org.apache.axis2.description.OutOnlyAxisOperation at 13c5982named: {http://ws.apache.org/namespaces/axis2}anonOutonlyOp
  | - mapActionToOperation: Mapping Action to Operation: action: anonOutInOp; operation: org.apache.axis2.description.OutInAxisOperation at 1186fabnamed: {http://ws.apache.org/namespaces/axis2}anonOutInOp
  | - mapActionToOperation: Mapping Action to Operation: action: urn:anonOutInOp; operation: org.apache.axis2.description.OutInAxisOperation at 1186fabnamed: {http://ws.apache.org/namespaces/axis2}anonOutInOp
  | - mapActionToOperation: Mapping Action to Operation: action: hello; operation: org.apache.axis2.description.OutInAxisOperation at 14b7453named: {http://hello.ws.com/}hello
  | - mapActionToOperation: Mapping Action to Operation: action: urn:hello; operation: org.apache.axis2.description.OutInAxisOperation at 14b7453named: {http://hello.ws.com/}hello
  | - Trying to find [org/apache/axis2/deployment/axis2_default.xml] using sun.misc.Launcher$AppClassLoader at 133056f class loader.
  | - About to create XMLInputFactory implementation with classloader=sun.misc.Launcher$AppClassLoader at 133056f
  | - The classloader for javax.xml.stream.XMLInputFactory is: sun.misc.Launcher$AppClassLoader at 133056f
  | - Created XMLInputFactory = class com.ctc.wstx.stax.WstxInputFactory with classloader=sun.misc.Launcher$AppClassLoader at 133056f
  | - Size of XMLInputFactory map =1
  | - isNetworkDetached =false
  | - XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
  | - Builder is already complete.
  | - Handler RequestURIBasedDispatcher added to Phase Transport
  | - Handler SOAPActionBasedDispatcher added to Phase Transport
  | - Handler AddressingBasedDispatcher added to Phase Addressing
  | - Handler RequestURIBasedDispatcher added to Phase Dispatch
  | - Handler SOAPActionBasedDispatcher added to Phase Dispatch
  | - Handler RequestURIOperationDispatcher added to Phase Dispatch
  | - Handler SOAPMessageBodyBasedDispatcher added to Phase Dispatch
  | - Handler HTTPLocationBasedDispatcher added to Phase Dispatch
  | - Handler AddressingBasedDispatcher added to Phase Addressing
  | - Handler RequestURIBasedDispatcher added to Phase Dispatch
  | - Handler SOAPActionBasedDispatcher added to Phase Dispatch
  | - Handler RequestURIOperationDispatcher added to Phase Dispatch
  | - Handler SOAPMessageBodyBasedDispatcher added to Phase Dispatch
  | - Handler HTTPLocationBasedDispatcher added to Phase Dispatch
  | - Deploying module from classpath at 'file:/D:/myName/workspaces/webServices/dummy_ws_client/lib/mex-1.5.jar'
  | - XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
  | - Builder is already complete.
  | - getBundle(org.apache.axis2,org.apache.axis2.i18n,resource,null,...)
  | - loadBundle: Ignoring MissingResourceException: Can't find bundle for base name org.apache.axis2.resource, locale en_CA
  | - Created org.apache.axis2.i18n.resource, linked to parent null
  | - getBundle(org.apache.axis2,org.apache.axis2.i18n,resource,null,...)
  | - org.apache.axis2.i18n.resource::handleGetObject(addingnewmodule)
  | - Adding new module
  | - org.apache.axis2.i18n.resource::handleGetObject(deployingmodule)
  | - Deploying module: metadataExchange-1.5 - file:/D:/myName/workspaces/webServices/dummy_ws_client/lib/mex-1.5.jar
  | - Adding service to allServices map: [HelloWorldService1259962123791_1] 
  | - Adding service to allEndpoints map: (HelloWorldService1259962123791_1,HelloWorldService1259962123791_1HttpSoap11Endpoint) 
  | - Adding service to allEndpoints map: (HelloWorldService1259962123791_1,HelloWorldService1259962123791_1HttpEndpoint) 
  | - Adding service to allEndpoints map: (HelloWorldService1259962123791_1,HelloWorldService1259962123791_1HttpSoap12Endpoint) 
  | - After adding to allEndpoints map, size is 3
  | - Get operation for {http://hello.ws.com/}hello
  | - Found axis operation:  org.apache.axis2.description.OutInAxisOperation at 14b7453
  | - registerOperationContext (false): org.apache.axis2.context.OperationContext at bfc8e0 with key: urn:uuid:99D878B4569EACD35E1259962124262
  | - Entry: OutInAxisOperationClient::execute, true
  | - OutInAxisOperationClient: useAsyncOption null
  | - registerOperationContext (false): org.apache.axis2.context.OperationContext at bfc8e0 with key: urn:uuid:99D878B4569EACD35E1259962124262
  | - msgContext: [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] action: http://hello.ws.com/HelloWorld/helloRequest
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking pre-condition for Phase "OperationOutPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking phase "OperationOutPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking post-conditions for phase "OperationOutPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking pre-condition for Phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking post-conditions for phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking pre-condition for Phase "PolicyDetermination"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking phase "PolicyDetermination"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking post-conditions for phase "PolicyDetermination"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking pre-condition for Phase "MessageOut"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking phase "MessageOut"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking post-conditions for phase "MessageOut"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking pre-condition for Phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Checking post-conditions for phase "Security"
  | - Set parameter http.useragent = Jakarta Commons-HttpClient/3.1
  | - Set parameter http.protocol.version = HTTP/1.1
  | - Set parameter http.connection-manager.class = class org.apache.commons.httpclient.SimpleHttpConnectionManager
  | - Set parameter http.protocol.cookie-policy = default
  | - Set parameter http.protocol.element-charset = US-ASCII
  | - Set parameter http.protocol.content-charset = ISO-8859-1
  | - Set parameter http.method.retry-handler = org.apache.commons.httpclient.DefaultHttpMethodRetryHandler at 1b9240e
  | - Set parameter http.dateparser.patterns = [EEE, dd MMM yyyy HH:mm:ss zzz, EEEE, dd-MMM-yy HH:mm:ss zzz, EEE MMM d HH:mm:ss yyyy, EEE, dd-MMM-yyyy HH:mm:ss z, EEE, dd-MMM-yyyy HH-mm-ss z, EEE, dd MMM yy HH:mm:ss z, EEE dd-MMM-yyyy HH:mm:ss z, EEE dd MMM yyyy HH:mm:ss z, EEE dd-MMM-yyyy HH-mm-ss z, EEE dd-MMM-yy HH:mm:ss z, EEE dd MMM yy HH:mm:ss z, EEE,dd-MMM-yy HH:mm:ss z, EEE,dd-MMM-yyyy HH:mm:ss z, EEE, dd-MM-yyyy HH:mm:ss z]
  | - Java version: 1.5.0_14
  | - Java vendor: Sun Microsystems Inc.
  | - Java class path: D:\myName\workspaces\webServices\dummy_ws_client\bin;D:\myName\workspaces\webServices\dummy_ws_client\properties;D:\myName\workspaces\webServices\dummy_ws_client\lib\activation-1.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axiom-api-1.2.8.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axiom-dom-1.2.8.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axiom-impl-1.2.8.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-adb-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-adb-codegen-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-ant-plugin-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-clustering-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-codegen-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-corba-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-fastinfoset-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-java2wsdl-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-jaxbri-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-jaxws-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-jibx-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-json-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-kernel-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-metadata-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-mtompolicy-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-saaj-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-spring-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-transport-http-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-transport-local-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\axis2-xmlbeans-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\bcel-5.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\commons-codec-1.3.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\commons-fileupload-1.2.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\commons-httpclient-3.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\commons-io-1.4.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\commons-lang-2.3.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\commons-logging-1.1.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\geronimo-annotation_1.0_spec-1.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\geronimo-jaxws_2.1_spec-1.0.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\geronimo-saaj_1.3_spec-1.0.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\geronimo-stax-api_1.0_spec-1.0.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\geronimo-ws-metadata_2.0_spec-1.1.2.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\httpcore-4.0.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jalopy-1.5rc3.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jaxb-api-2.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jaxb-impl-2.1.7.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jaxb-xjc-2.1.7.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jaxen-1.1.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jettison-1.0-RC2.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jibx-bind-1.2.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\jibx-run-1.2.1.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\log4j-1.2.15.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\mail-1.4.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\mex-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\neethi-2.0.4.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\smack-3.0.4.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\smackx-3.0.4.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\soapmonitor-1.5.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\woden-api-1.0M8.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\woden-impl-dom-1.0M8.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\wsdl4j-1.6.2.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\wstx-asl-3.2.4.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\xalan-2.7.0.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\xercesImpl-2.6.2.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\xml-apis-1.3.02.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\xml-resolver-1.2.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\xmlbeans-2.3.0.jar;D:\myName\workspaces\webServices\dummy_ws_client\lib\XmlSchema-1.4.3.jar;D:\myName\opt\eclipse-jee-galileo-SR1-win32\eclipse\plugins\org.junit4_4.5.0.v20090824\junit.jar;D:\myName\opt\eclipse-jee-galileo-SR1-win32\eclipse\plugins\org.hamcrest.core_1.1.0.v20090501071000.jar;/D:/myName/opt/eclipse-jee-galileo-SR1-win32/eclipse/configuration/org.eclipse.osgi/bundles/310/1/.cp/;/D:/myName/opt/eclipse-jee-galileo-SR1-win32/eclipse/configuration/org.eclipse.osgi/bundles/308/1/.cp/;/D:/myName/opt/eclipse-jee-galileo-SR1-win32/eclipse/configuration/org.eclipse.osgi/bundles/309/1/.cp/
  | - Operating system name: Windows XP
  | - Operating system architecture: x86
  | - Operating system version: 5.1
  | - SUN 1.5: SUN (DSA key/parameter generation; DSA signing; SHA-1, MD5 digests; SecureRandom; X.509 certificates; JKS keystore; PKIX CertPathValidator; PKIX CertPathBuilder; LDAP, Collection CertStores)
  | - SunRsaSign 1.5: Sun RSA signature provider
  | - SunJSSE 1.5: Sun JSSE provider(PKCS12, SunX509 key/trust factories, SSLv3, TLSv1)
  | - SunJCE 1.5: SunJCE Provider (implements RSA, DES, Triple DES, AES, Blowfish, ARCFOUR, RC2, PBE, Diffie-Hellman, HMAC)
  | - SunJGSS 1.0: Sun (Kerberos v5)
  | - SunSASL 1.5: Sun SASL provider(implements client mechanisms for: DIGEST-MD5, GSSAPI, EXTERNAL, PLAIN, CRAM-MD5; server mechanisms for: DIGEST-MD5, GSSAPI, CRAM-MD5)
  | - Set parameter http.connection.timeout = 30000
  | - Set parameter http.socket.timeout = 30000
  | - Set parameter http.socket.timeout = 30000
  | - Start getContentType: OMOutputFormat [ mimeBoundary =null rootContentId=null doOptimize=false doingSWA=false isSOAP11=true charSetEncoding=UTF-8 xmlVersion=null contentType=null ignoreXmlDeclaration=false autoCloseWriter=false actionProperty=null optimizedThreshold=0]
  | - getContentType= {text/xml}   OMOutputFormat [ mimeBoundary =null rootContentId=null doOptimize=false doingSWA=false isSOAP11=true charSetEncoding=UTF-8 xmlVersion=null contentType=text/xml ignoreXmlDeclaration=false autoCloseWriter=false actionProperty=null optimizedThreshold=0]
  | - contentType from the OMOutputFormat =text/xml
  | - contentType returned =text/xml; charset=UTF-8
  | - HttpConnectionManager.getConnection:  config = HostConfiguration[host=http://myName1A:8088], timeout = 0
  | - Allocating new connection, hostConfig=HostConfiguration[host=http://myName1A:8088]
  | - Open connection to myName1A:8088
  | - >> "POST /mockHelloWorldBinding HTTP/1.1[\r][\n]"
  | - Adding Host request header
  | - >> "Content-Type: text/xml; charset=UTF-8[\r][\n]"
  | - >> "SOAPAction: "http://hello.ws.com/HelloWorld/helloRequest"[\r][\n]"
  | - >> "User-Agent: Axis2[\r][\n]"
  | - >> "Host: myName1A:8088[\r][\n]"
  | - >> "Transfer-Encoding: chunked[\r][\n]"
  | - >> "[\r][\n]"
  | - start writeTo()
  | -   preserve=false
  | -   isOptimized=false
  | -   isDoingSWA=false
  | - MTOM optimized Threshold value =0
  | - OutputStream =class org.apache.commons.httpclient.ChunkedOutputStream
  | - OMFormat = OMOutputFormat [ mimeBoundary =null rootContentId=null doOptimize=false doingSWA=false isSOAP11=true charSetEncoding=UTF-8 xmlVersion=null contentType=text/xml ignoreXmlDeclaration=false autoCloseWriter=false actionProperty=null optimizedThreshold=0]
  | - About to create XMLOutputFactory implementation with classloader=sun.misc.Launcher$AppClassLoader at 133056f
  | - The classloader for javax.xml.stream.XMLOutputFactory is: sun.misc.Launcher$AppClassLoader at 133056f
  | - Created XMLOutputFactory = class com.ctc.wstx.stax.WstxOutputFactory for classloader=sun.misc.Launcher$AppClassLoader at 133056f
  | - Size of XMLOutputFactory map =1
  | - XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
  | - serialize {http://hello.ws.com/}hello to XMLStreamWriter
  | - Calling MTOMXMLStreamWriter.flush
  | - Calling MTOMXMLStreamWriter.flush
  | - end writeTo()
  | - >> "ec[\r][\n]"
  | - >> "<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><ns1:hello xmlns:ns1="http://hello.ws.com/"><arg0>World</arg0></ns1:hello></soapenv:Body></soapenv:Envelope>"
  | - >> "[\r][\n]"
  | - >> "0"
  | - >> "[\r][\n]"
  | - >> "[\r][\n]"
  | - Request body sent
  | - << "HTTP/1.1 500 Internal Server Error[\r][\n]"
  | - << "HTTP/1.1 500 Internal Server Error[\r][\n]"
  | - << "Content-Type: text/html; charset=iso-8859-1[\r][\n]"
  | - << "Transfer-Encoding: chunked[\r][\n]"
  | - << "Server: Jetty(6.1.x)[\r][\n]"
  | - << "[\r][\n]"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking flowComplete() in Phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking flowComplete() in Phase "MessageOut"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking flowComplete() in Phase "PolicyDetermination"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking flowComplete() in Phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124263] Invoking flowComplete() in Phase "OperationOutPhase"
  | - Could not find a Builder for type (text/html).  Using SOAP.
  | - << "1"
  | - << "9"
  | - << "3"
  | - << "[\r]"
  | - << "[\n]"
  | - << "<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">[\r][\n]"
  | - << "  <soapenv:Body>[\r][\n]"
  | - << "    <soapenv:Fault>[\r][\n]"
  | - << "      <faultcode>Server</faultcode>[\r][\n]"
  | - << "      <faultstring>Missing operation for soapAction [http://hello.ws.com/HelloWorld/helloRequest] and body element [{http://hello.ws.com/}hello] with SOAP Version [SOAP 1.1]</faultstring>[\r][\n]"
  | - << "    </soapenv:Fault>[\r][\n]"
  | - << "  </soapenv:Body>[\r][\n]"
  | - << "</soapenv:Envelope>"
  | - XMLStreamReader is com.ctc.wstx.sr.ValidatingStreamReader
  | - Starting to process SOAP 1.1 message
  | - Build the OMElement Envelope by the StaxSOAPModelBuilder
  | - Build the OMElement Body by the StaxSOAPModelBuilder
  | - Build the OMElement Fault by the StaxSOAPModelBuilder
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking pre-condition for Phase "Addressing"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking phase "Addressing"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking Handler 'AddressingBasedDispatcher' in Phase 'Addressing'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking post-conditions for phase "Addressing"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking pre-condition for Phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking post-conditions for phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking pre-condition for Phase "PreDispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking phase "PreDispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking post-conditions for phase "PreDispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking pre-condition for Phase "Dispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking phase "Dispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking Handler 'RequestURIBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking Handler 'SOAPActionBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking Handler 'RequestURIOperationDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking Handler 'SOAPMessageBodyBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking Handler 'HTTPLocationBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking post-conditions for phase "Dispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking pre-condition for Phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking post-conditions for phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking pre-condition for Phase "OperationInPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking phase "OperationInPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Checking post-conditions for phase "OperationInPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() in Phase "OperationInPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() in Phase "RMPhase"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() in Phase "Dispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() for Handler 'HTTPLocationBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() for Handler 'SOAPMessageBodyBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() for Handler 'RequestURIOperationDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() for Handler 'SOAPActionBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() for Handler 'RequestURIBasedDispatcher' in Phase 'Dispatch'
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() in Phase "PreDispatch"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() in Phase "Security"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() in Phase "Addressing"
  | - [MessageContext: logID=urn:uuid:99D878B4569EACD35E1259962124494] Invoking flowComplete() for Handler 'AddressingBasedDispatcher' in Phase 'Addressing'
  | - Build the OMElement faultcode by the StaxSOAPModelBuilder
  | - Build the OMElement faultstring by the StaxSOAPModelBuilder
  | - << "[\r]"
  | - << "[\n]"
  | - << "0"
  | - << "[\r]"
  | - << "[\n]"
  | - << "[\r]"
  | - << "[\n]"
  | - << "[\r][\n]"
  | - Resorting to protocol version default close connection policy
  | - Should NOT close connection, using HTTP/1.1
  | - Releasing connection back to connection manager.
  | - Freeing connection, hostConfig=HostConfiguration[host=http://myName1A:8088]
  | - Adding connection at: 1259962124492
  | - Notifying no-one, there are no waiting threads
  | 

The WSDL:

  | <?xml version="1.0" encoding="UTF-8"?>
  | <definitions name="HelloWorldService" targetNamespace="http://hello.ws.com/" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://hello.ws.com/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
  |   <types>
  |     <xs:schema targetNamespace="http://hello.ws.com/" version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  |       <xs:element name="hello" type="tns:hello"/>
  |       <xs:element name="helloResponse" type="tns:helloResponse"/>
  |       <xs:complexType name="hello">
  |         <xs:sequence>
  |           <xs:element minOccurs="0" name="arg0" type="xs:string"/>
  |         </xs:sequence>
  |       </xs:complexType>
  |       <xs:complexType name="helloResponse">
  |         <xs:sequence>
  |           <xs:element minOccurs="0" name="return" type="xs:string"/>
  |         </xs:sequence>
  |       </xs:complexType>
  |     </xs:schema>
  |   </types>
  |   <message name="HelloWorld_helloResponse">
  |     <part name="helloResponse" element="tns:helloResponse">
  |     </part>
  |   </message>
  |   <message name="HelloWorld_hello">
  |     <part name="hello" element="tns:hello">
  |     </part>
  |   </message>
  |   <portType name="HelloWorld">
  |     <operation name="hello" parameterOrder="hello">
  |       <input message="tns:HelloWorld_hello">
  |     </input>
  |       <output message="tns:HelloWorld_helloResponse">
  |     </output>
  |     </operation>
  |   </portType>
  |   <binding name="HelloWorldBinding" type="tns:HelloWorld">
  |     <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
  |     <operation name="hello">
  |       <soap:operation soapAction=""/>
  |       <input>
  |         <soap:body use="literal"/>
  |       </input>
  |       <output>
  |         <soap:body use="literal"/>
  |       </output>
  |     </operation>
  |   </binding>
  |   <service name="HelloWorldService">
  |     <port name="HelloWorldPort" binding="tns:HelloWorldBinding">
  |       <soap:address location="http://myName1A:8088/mockHelloWorldBinding"/>
  |     </port>
  |   </service>
  | </definitions>
  | 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269111#4269111

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269111



From do-not-reply at jboss.com  Fri Dec  4 19:22:21 2009
From: do-not-reply at jboss.com (Juergen.Zimmermann)
Date: Fri, 4 Dec 2009 19:22:21 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Error with
	registering a RESTeasy Providerfactory
Message-ID: <13286042.1259972541027.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

You are mixing Jersey and RESTEasy.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269113#4269113

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269113


From do-not-reply at jboss.com  Mon Dec  7 11:48:18 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Mon, 7 Dec 2009 11:48:18 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Cannot call JBoss
	web service through intermediary (soap
Message-ID: <23678264.1260204498567.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Solved it.  The problem seems to be that I didn't use the @WebMethod annotation to define soapAction names.  While you can connect directly without them, it appears that you need them to connect indirectly.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269396#4269396

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269396


From do-not-reply at jboss.com  Mon Dec  7 19:44:56 2009
From: do-not-reply at jboss.com (jim.ma)
Date: Mon, 7 Dec 2009 19:44:56 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Failed to load
	org.jboss.wsf.spi.invocation.WebServiceCo
Message-ID: <30414132.1260233096766.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Can you describe how do you update the JBoss 4.2.3 with jbossws-native-3.1.1GA ?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269469#4269469

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269469


From do-not-reply at jboss.com  Mon Dec  7 20:19:12 2009
From: do-not-reply at jboss.com (shadowcreeper)
Date: Mon, 7 Dec 2009 20:19:12 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - How to recieve
	RPC/encoded SOAP messages in JBoss5?
Message-ID: <2004622.1260235152972.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

For legacy clients which refuse to drop rpc/encoded SOAP format, what can we use to get their messages in JBoss5?

We would love for them to switch over to document/literal (or even rpc/literal) but big companies are extremely reluctant to (read: never will) change. :(

Thanks.
-Shadow

[initially posted this in the sun metro forum on accident, it was meant to go here]

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269473#4269473

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269473


From do-not-reply at jboss.com  Tue Dec  8 09:14:24 2009
From: do-not-reply at jboss.com (pa12399)
Date: Tue, 8 Dec 2009 09:14:24 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: How to recieve
	RPC/encoded SOAP messages in JBoss5?
Message-ID: <21891685.1260281664154.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi

I am having the exact same issue as well. One of my clients is using RPC encoded in their WSDL, which I am having to call. So, I am unable to port the client into the latest version of JBoss. Any pointers would be greatly appreciated.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269585#4269585

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269585


From do-not-reply at jboss.com  Tue Dec  8 10:02:15 2009
From: do-not-reply at jboss.com (trzcina)
Date: Tue, 8 Dec 2009 10:02:15 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - add custom
	HttpSessionListener to Web Services endpoint
Message-ID: <16363345.1260284535817.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

I am using JBOSS JAX-WS Native with my stateless EJB to expose its methods via WS (@WebService annotation) and I need to set my own HttpSessionListener on WS connections (I want to be notified when session is destroyed). I would normally do it in web.xml, but I expose my EJB automagically and I don't define any web.xml. How can I achieve my goal then?

I'd very appreciate any ideas.

Best regards,
Michal Trzcinka

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269596#4269596

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269596


From do-not-reply at jboss.com  Tue Dec  8 10:17:58 2009
From: do-not-reply at jboss.com (pa12399)
Date: Tue, 8 Dec 2009 10:17:58 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Failed to load
	org.jboss.wsf.spi.invocation.WebServiceCo
Message-ID: <6451566.1260285478052.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I had copied ant.properties.example to ant.properties. Then I modified the path in that file to where my JBoss isntance was loaded and then invoked ant to do the install i.e.

ant -f ant.properties

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269597#4269597

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269597


From do-not-reply at jboss.com  Tue Dec  8 10:20:41 2009
From: do-not-reply at jboss.com (magiccreative)
Date: Tue, 8 Dec 2009 10:20:41 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Resteasy + Seam = 403
	Forbidden, any idea why?
Message-ID: <13200975.1260285641628.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

 I have already have the discussion going on the Resteasy mailing list but I would like to ask here as well if someone had experience with this Resteasy and Seam problem.

 Basically I have made my own test project based on the tasks example. At first I am trying a very simple Restful service. Only two GET methods, one returns a String representation of an email and the other Email object - (plain/text) / (application/xml) headers respectively. 

 Now I made a simple client as well which makes request to GET - (plain/txt). It works as expected and I get the String representation of the Email.

 When I try the same with GET - (application/xml) I am getting 403 - Forbidden response. 

 I have been debugging for a day now and I get a feeling the problem lies on the Seam security side because the Resteasy would have returned 401 - Not Authorized.

 Did anyone have similar problem? Any help would be appreciated.

 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269598#4269598

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269598


From do-not-reply at jboss.com  Tue Dec  8 14:10:03 2009
From: do-not-reply at jboss.com (shadowcreeper)
Date: Tue, 8 Dec 2009 14:10:03 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - How to run a Filter
	before the WebService to alter the SOAP
Message-ID: <20605071.1260299403243.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Would somebody please give me some pointers on how to setup an XML translation filter on POST?

The idea is for the JBossWS stuff to see my translated XML to create its message from so the filter must run before the @WebService servlet.

I am trying to get the JBossWS stuff to read RPC/encoded SOAP messages, and was thinking that I might be able to run the XML through a filter on POST to spit out RPC/literal XML that the JBossWS code could then understand.

Thanks.
-Shadow

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269664#4269664

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269664


From do-not-reply at jboss.com  Tue Dec  8 21:53:09 2009
From: do-not-reply at jboss.com (cdebergh)
Date: Tue, 8 Dec 2009 21:53:09 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - WS client reuse http
	connection
Message-ID: <1748657.1260327190001.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Does anyone know how to set the client (generated by wsconsume.sh) to reuse http connections? Can anyone point me in the right direction?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269703#4269703

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269703


From do-not-reply at jboss.com  Tue Dec  8 21:58:52 2009
From: do-not-reply at jboss.com (jim.ma)
Date: Tue, 8 Dec 2009 21:58:52 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Failed to load
	org.jboss.wsf.spi.invocation.WebServiceCo
Message-ID: <5252460.1260327532337.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Did you use "ant deploy-jboss423 " to update ?

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269704#4269704

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269704


From do-not-reply at jboss.com  Wed Dec  9 04:27:07 2009
From: do-not-reply at jboss.com (craiggreenhalgh)
Date: Wed, 9 Dec 2009 04:27:07 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: @WebFault and
	@XmlType issues for Exception classes
Message-ID: <3567768.1260350827469.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi did you come up with a solution for this?

I have the same requirement

Thanks

Craig


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269745#4269745

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269745


From do-not-reply at jboss.com  Wed Dec  9 08:54:19 2009
From: do-not-reply at jboss.com (pa12399)
Date: Wed, 9 Dec 2009 08:54:19 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Failed to load
	org.jboss.wsf.spi.invocation.WebServiceCo
Message-ID: <20752091.1260366859803.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Yes, I did use ant deploy-jboss423 to update the webservices on JBoss 4.2.3. It is still giving this exception.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269795#4269795

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269795


From do-not-reply at jboss.com  Wed Dec  9 13:14:42 2009
From: do-not-reply at jboss.com (mbarker)
Date: Wed, 9 Dec 2009 13:14:42 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Namespace defined in
	method tag
Message-ID: <24094494.1260382482611.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I'm deploying a web service on JBoss 4.2. I am a consumer of a vendor's web service.  I submit my request and receive a response indicating a successful submission.  Some time later, possibly hours, the vendor sends me a status thus I become the provider.

The vendor is sending me the following request.  Notice that the namespace is defined in the tag:  <Callback xmlns=SomeCallback>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  |     <soap:Body>
  |       <Callback xmlns="SomeCallback">
  |         <ID>0</ID>
  |         <ItemID>1362</ItemID>
  |         <Auth>leopard</Auth>
  |         <Status>-900</Status>
  |         <StatusTime>2009-12-08T11:13:52</StatusTime>
  |       </Callback>
  |     </soap:Body>
  | </soap:Envelope>


My test request (below) defines the namespace before the tag is used:  <pos:Callback>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:pos="SomeCallback">
  |    <soapenv:Header/>
  |    <soapenv:Body>
  |       <pos:Callback>
  |          <ID>1</ID>
  |          <ItemID>2</ItemID>
  |          <Auth>smitty</Auth>
  |          <Status>-1000</Status>
  |          <StatusTime>2009-12-08T11:59:59</StatusTime>
  |       </pos:Callback>
  |    </soapenv:Body>
  | </soapenv:Envelope>

Here's my code.  My web service does receive the request from the vendor, but all the objects are null and int is 0. Namespace is the key.  What do I have to change in my code below so that my request matches the vendor's request?   

@WebService(targetNamespace = "SomeCallback")
  | @SOAPBinding(parameterStyle = ParameterStyle.WRAPPED)
  | public class SomeCallback {
  | 
  | 	@WebMethod(operationName = "Callback")
  | 	public @WebResult(name = "CallbackResult", targetNamespace = "SomeCallback")
  | 	int callback(@WebParam(name = "ID") int id,
  | 			@WebParam(name = "ItemID") int itemId,
  | 			@WebParam(name = "Auth") String auth,
  | 			@WebParam(name = "Status") int status,
  | 			@WebParam(name = "StatusTime") Date statusTime) {
  |     }
  | }

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269843#4269843

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269843


From do-not-reply at jboss.com  Wed Dec  9 14:47:48 2009
From: do-not-reply at jboss.com (shadowcreeper)
Date: Wed, 9 Dec 2009 14:47:48 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: How to recieve
	RPC/encoded SOAP messages in JBoss5?
Message-ID: <506931.1260388068885.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

OK, here's what seems to be working for me... It's a horrible hack, but it works...

First, take your WSDL file and turn it into RPC/literal (for me it was as easy as replacing the word "encoded" with "literal").

Next, setup your JBossWS stuff as though you will be receiving RPC/literal documents (from its standpoint, you will).

Now for the tricky part... You will have already setup a servlet (@WebService), which you now need to add an XSLT filter to...

All I had to do to make my SOAP messages understandable to JBossWS was flatten the "multiRef" nodes.

Original SOAP message:

  | <myWebServiceMethod>
  |    <myArgumentObject href="#id0"/>
  | </myWebServiceMethod>
  | <multiRef id="id0" ...>
  |    <actualGutsOfArgument/>
  |    <referencedGutNum2 href="#id2"/>
  | </multiRef>
  | <multiRef id="id2" ...>
  |    <moreActualGuts/>
  | </multiRef>
  | 

Flattened SOAP message:

  | <myWebServiceMethod>
  |    <myArgumentObject id="id0" ...>
  |      <actualGutsOfArgument/>
  |      <referencedGutNum2 id="id2" ...>
  |         <moreActualGuts/>
  |      </referencedGutNum2>
  |    </myArgumentObject>
  | </myWebServiceMethod>
  | 

Note: The only attribute I removed was "href", all of the attributes to the multiRef node became attributes to the node that referenced it (this includes xsi:type info which I believe gets ignored anyway since it is already specified in the XSD file that my WSDL references).

The filter will look something like this:

  | public class MultiRefFlattener
  |    implements Filter
  | {
  |    private Transformer m_transformer = null;
  | 
  |    public void init ( FilterConfig filterConfig )
  |       throws ServletException
  |    {
  |       final String stylePath = filterConfig.getServletContext().getRealPath( "WEB-INF/multi-ref-flattener.xslt" );
  |       final Source styleSource = new StreamSource( stylePath );
  |       final TransformerFactory transformerFactory = TransformerFactory.newInstance();
  |       try
  |       {
  |          m_transformer = transformerFactory.newTransformer( styleSource );
  |       }
  |       catch( TransformerConfigurationException e )
  |       {
  |          throw new ServletException( "Error creating XSLT transformer: ", e );
  |       }
  |    }
  | 
  |    public void doFilter(
  |       final ServletRequest request,
  |       final ServletResponse response,
  |       final FilterChain chain )
  |       throws IOException, ServletException
  |    {
  |       final String requestText;
  |       try
  |       {
  |          final CharArrayWriter caw = new CharArrayWriter();
  |          final StreamResult result  = new StreamResult(caw);
  |          m_transformer.transform(new StreamSource(request.getInputStream()), result);
  |          requestText = caw.toString();
  |       }
  |       catch( TransformerException e )
  |       {
  |          throw new ServletException( "Error filtering data" );
  |       }
  | 
  |       final ServletInputStream requestStream = new ServletInputStream()
  |       {
  |          private int m_column = 0;
  |          public int read ()
  |             throws IOException
  |          {
  |             if( m_column >= requestText.length() )
  |                return -1;
  |             final int character = requestText.charAt( m_column );
  |             ++m_column;
  |             return character;
  |          }
  |       };
  | 
  |       final HttpServletRequest httpServletRequest = (HttpServletRequest)request;
  |       final HttpServletRequestWrapper wrapper = new HttpServletRequestWrapper( httpServletRequest )
  |       {
  |          @Override
  |          public int getContentLength ()
  |          {
  |             return requestText.length();
  |          }
  | 
  |          @Override
  |          public ServletInputStream getInputStream ()
  |             throws IOException
  |          {
  |             return requestStream;
  |          }
  |       };
  |       chain.doFilter( wrapper, response );
  |    }
  | 
  |    public void destroy ()
  |    {
  |       m_transformer = null;
  |    }
  | }
  | 

If anybody has a better way of faking an HttpServletRequest, please let me know.

And here is my flattening XSLT file:

  | <xsl:stylesheet version="1.0"
  |    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
  |    xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  | 
  |    <xsl:template match="/">
  |       <xsl:call-template name="CopyNode"/>
  |    </xsl:template>
  | 
  |    <xsl:template name="CopyNodeRef">
  |       <xsl:param name="elementName"/>
  |       <xsl:param name="hrefId"/>
  |       <xsl:copy>
  |          <xsl:element name="$elementName">
  |             <xsl:for-each select="//multiRef[@id = $hrefId]/@*">
  |                <xsl:copy>
  |                   <xsl:apply-templates mode="keeping"/>
  |                </xsl:copy>
  |             </xsl:for-each>
  |             <xsl:for-each select="//multiRef[@id = $hrefId]/node()[not(@href)]">
  |                <xsl:call-template name="CopyNode"/>
  |             </xsl:for-each>
  |             <xsl:for-each select="//multiRef[@id = $hrefId]/node()[@href]">
  |                <xsl:call-template name="CopyNodeRef">
  |                   <xsl:with-param name="elementName" select="name()"/>
  |                   <xsl:with-param name="hrefId" select="substring(@href, 2)"/>
  |                </xsl:call-template>
  |             </xsl:for-each>
  |          </xsl:element>
  |       </xsl:copy>
  |    </xsl:template>
  | 
  |    <xsl:template name="CopyNode">
  |       <xsl:copy>
  |          <xsl:call-template name="CopyAttributes"/>
  |          <xsl:for-each select="node()[not(@href|@id)]">
  |             <xsl:call-template name="CopyNode"/>
  |          </xsl:for-each>
  |          <xsl:for-each select="node()[@href]">
  |             <xsl:call-template name="CopyNodeRef">
  |                <xsl:with-param name="elementName" select="name()"/>
  |                <xsl:with-param name="hrefId" select="substring(@href, 2)"/>
  |             </xsl:call-template>
  |          </xsl:for-each>
  |       </xsl:copy>
  |    </xsl:template>
  | 
  |    <xsl:template name="CopyAttributes">
  |       <xsl:for-each select="@*">
  |          <xsl:copy>
  |             <xsl:apply-templates mode="keeping"/>
  |          </xsl:copy>
  |       </xsl:for-each>
  |    </xsl:template>
  | 
  | </xsl:stylesheet>
  | 

If anybody has a better idea for a flattener, please let me know.

I hope this helps.
-Shadow

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269863#4269863

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269863


From do-not-reply at jboss.com  Wed Dec  9 15:03:33 2009
From: do-not-reply at jboss.com (shadowcreeper)
Date: Wed, 9 Dec 2009 15:03:33 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: How to run a
	Filter before the WebService to alter the S
Message-ID: <1724387.1260389013050.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Never mind, it was easier than I thought. The servlet doesn't do anything until after the filters run, so all you have to do is pass in a modified ServletRequest to the next filter on the chain.

The trickiest part is faking an HttpServletRequest with the modified String as the ServletInputStream.

Thanks.
-Shadow

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269872#4269872

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269872


From do-not-reply at jboss.com  Wed Dec  9 20:49:16 2009
From: do-not-reply at jboss.com (cdebergh)
Date: Wed, 9 Dec 2009 20:49:16 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: WS client reuse
	http connection
Message-ID: <9825010.1260409756767.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I've discovered the http.maxConnections property for JAX-WS. I understand the default is 5 connections, but I am confused as to why my JAX-WS client is opening more that 5 socket connections if there is a max and http.keepAlive is true?
If anyone could point me in the right direction or let me know if I misunderstood this setting, that would be very appreciated!
I'm hoping to avoid writing a pool for the jax-ws client to limit the number of socket connections.
Previously I used axis2. It has an option HTTPConstants.REUSE_HTTP_CLIENT so it would only use one connection over and over. Perhaps JAX-WS has a similar option?

Thanks!
/Chip 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269904#4269904

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269904


From do-not-reply at jboss.com  Thu Dec 10 10:46:18 2009
From: do-not-reply at jboss.com (narmashan)
Date: Thu, 10 Dec 2009 10:46:18 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - JBOSSWS Webservice
	Error in UNIX
Message-ID: <31728019.1260459978089.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am testing a webservice using JBOSS5,JBOSSWS and jdk 6 in unix system.

My webservice got deployed and worked well in Windows. Client was able to able to access the HTTP response fine. 
Windows XP Environment Tools:
a) JBOSS AS5
b)JBOSS WS
c)JDK 5.0
Steps followed to install in Windows
# From Windows Explorer, navigate to "C:\jbossws-native-bin-dist". Inside the folder, locate the file "ant.properties.example".
# Make a copy of "ant.properties.example", then rename it to "ant.properties".
# Start up your favorite code editor (like UltraEdit32, or Notepad++), then open up "ant.properties" for editing.
# Locate the line "jboss500.home=@jboss500.home@", change it to "jboss500.home=/jboss-5.0.0.GA". Then save it and close the code editor.
# Open Command Prompt, navigate to "C:\jbossws-native-bin-dist". Then run the command "ant deploy-jboss500". When it finishes successfully, JBossWS will be installed and configured properly for use. 

Unix Environment:
JDK 6
JBOSS 5.0

Copied the JBOSSWS jar files from C:\jbossws-native-bin-dist\output\deploy-jboss500folder to corresponding folders in client, bin,common,lib,server in Unix.

When I start the JBOSSAS I am able to view the webservice and wsdl is generated but while testing the webservic in client I get the following error:


javax.xml.ws.WebServiceException: Cannot process response message
	at org.jboss.ws.core.jaxws.client.DispatchSOAPBinding.getReturnObject(DispatchSOAPBinding.java:191)
	at org.jboss.ws.core.jaxws.client.DispatchImpl.getReturnObject(DispatchImpl.java:470)
	at org.jboss.ws.core.jaxws.client.DispatchImpl.invokeInternalSOAP(DispatchImpl.java:264)
	at org.jboss.ws.core.jaxws.client.DispatchImpl.invokeInternal(DispatchImpl.java:170)
	at org.jboss.ws.core.jaxws.client.DispatchImpl.invoke(DispatchImpl.java:133)
	at tutorial.hanbo.webservice.GreetingTestClient2.main(GreetingTestClient2.java:60)
Caused by: javax.xml.soap.SOAPException: Cannot obtain SOAPBody from SOAPMessage
	at javax.xml.soap.SOAPMessage.getSOAPBody(SOAPMessage.java:181)
	at org.jboss.ws.core.jaxws.client.DispatchSOAPBinding.getReturnObject(DispatchSOAPBinding.java:159)


While Analyzing using TCP monitor I find that content length is zero

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1
Content-Length: 0
Date: Thu, 10 Dec 2009 15:27:26 GMT

I assume it has something to do with JBOSSWS jar files used in Unix.

Could anyone help in this regard ? Grealty appreciate it.






View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270026#4270026

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270026


From do-not-reply at jboss.com  Thu Dec 10 13:34:52 2009
From: do-not-reply at jboss.com (narmashan)
Date: Thu, 10 Dec 2009 13:34:52 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBOSSWS Webservice
	Error in UNIX
Message-ID: <28887519.1260470092739.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I made it work by changing the jdk version in Unix to jdk 1.5.
Could anyone say if there is problem with jdk 1.6 and Jbossws ?

Thanks!

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270059#4270059

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270059


From do-not-reply at jboss.com  Thu Dec 10 16:31:55 2009
From: do-not-reply at jboss.com (shadowcreeper)
Date: Thu, 10 Dec 2009 16:31:55 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBOSSWS Webservice
	Error in UNIX
Message-ID: <33554318.1260480715370.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Nope, I'm using Linux 2.6.28-13-generic (Ubuntu 9.4) with java-6-sun-1.6.0.16 (the latest Java6 package) and JBoss 5.1.0.GA. It all works fine for me.

I am, however, also using the JBossWS that was bundled with JBoss 5.1.0.GA (I never did the upgraded JBossWS install that all the guides tell you to).

I started out using Windows, and just copied my whole JBoss directory over to Linux. The only problems I have had were with filename case issues (which could all be fixed by sticking it into a case-insensitive fs -- like vfat).

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270082#4270082

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270082


From do-not-reply at jboss.com  Fri Dec 11 16:57:50 2009
From: do-not-reply at jboss.com (cdebergh)
Date: Fri, 11 Dec 2009 16:57:50 -0500 (EST)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: WS client reuse
	http connection
Message-ID: <22777757.1260568670445.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Figured it out.
The http.maxConnection settings is not a limit on the total connections but rather the maximum connections to keep open after they were used.
In my case I consistently have 10 simultaneous requests. So 10 would open, 5 would close, 5 more would open, 5 more would close, and so on. Those that close stay in the TIME_WAIT state for 60 seconds (OS Configuration). This causes TIME_WAIT connections to build up quickly to around ~600. By increasing the maximum idle connections (http.maxConnections) to something larger like 20, open connections are now around 10-13.
Axis2 only opens one connection per port instance (no pool) whereas JAX-WS pools multiple connections as they are needed. 

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270303#4270303

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270303


From skibaa at gmail.com  Sun Dec 13 12:04:37 2009
From: skibaa at gmail.com (Andrew Skiba)
Date: Sun, 13 Dec 2009 19:04:37 +0200
Subject: [jbossws-users] accumulating files in server/default/data/wsdl
Message-ID: <4A872467-1638-4E78-865A-31AA01A9A9C6@gmail.com>

Hello,

I've encountered a problem with generated WSDL files on jboss-4.2.3.  
To reproduce it, I created an EJB jar with web service class annotated  
like this:

@Stateless(mappedName = ICounterManagerWSRemote.NAME, name =
ICounterManagerWSRemote.NAME, description =
ICounterManagerWSRemote.NAME)
@Remote(ICounterManagerWSRemote.class)
@RemoteBinding(jndiBinding =ICounterManagerWSRemote.NAME_REMOTE)
@WebService(name =
"CounterManagerWS", targetNamespace = "urn:countermanagerws",
serviceName = "CounterManagerWS")
@SOAPBinding(style = SOAPBinding.Style.RPC, parameterStyle =
ParameterStyle.BARE)

Then I created an EAR containing this EJB, a WAR which accesses the WS  
and deployed it on JBoss. Now every time I start the JBoss server, it  
generates a new WSDL like this: server/default/data/wsdl/ 
ServletStateless.ear/ServletStateless-ejb.jar/ 
CounterManagerWS2051720417134744551.
wsdl

When the application has many complex web services, these files become  
quite big, and are generated on every server start. So my question is:  
is this a known issue? What's the best way to handle this problem? Add  
an rm command to JBoss startup script?

Thanks.

Andrew.