From do-not-reply at jboss.com  Mon Jun  1 09:31:30 2009
From: do-not-reply at jboss.com (martynl)
Date: Mon, 1 Jun 2009 09:31:30 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Web Services failing after deployment
	or restart
Message-ID: <12886284.1243863091001.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

We are encountering a very strange problem with JBoss. We have a number of applications deployed to JBoss using annotated EJB3 web services. Most work 100% fine except for one. Every time we deploy an unrelated app or restart the server, this 1 application keeps dropping the web service. Redeploy that particular application again and the web service is back. I have checked the logs and not seen anything strange happen. The applications deploy and load as would be expected. Is there a possible reason for this strange behaviour as it affects only this 1 application every time.

Kind Regards,

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

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


From do-not-reply at jboss.com  Mon Jun  1 10:14:18 2009
From: do-not-reply at jboss.com (PedroSena)
Date: Mon, 1 Jun 2009 10:14:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Implementing WS-Security Usename
	Token Profile Authentic
Message-ID: <24084588.1243865658872.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I'm trying to implement this solution, but for some reason, the authentication mecanism is not reading correctly my Soap Header.

I saw in log:

2009-06-01 11:09:24,265 DEBUG [org.jboss.security.auth.spi.UsersRolesLoginModule] Bad password for username=null
  | 2009-06-01 11:09:24,265 DEBUG [org.jboss.ejb3.security.Ejb3AuthenticationInterceptor] Authentication failure
  | javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required
  | 	at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:213)
  | 

And I'm sending:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.netsar.com.br/tnw/bus">
  |    <soapenv:Header>
  |       <wsse:Security soapenv:mustUnderstand="1" 
  | 	xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
  |  xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  |          <wsse:UsernameToken wsu:Id="token-1-1236072936329-25515818">
  |             <wsse:Username>submarino</wsse:Username>
  |             <wsse:Password
  | Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">subm4r1n0</wsse:Password>
  |          </wsse:UsernameToken>
  |       </wsse:Security>
  |    </soapenv:Header>
  |    <soapenv:Body>
  |    </soapenv:Body>
  | </soapenv:Envelope>

I'm testing it from SoapUI, the message was made manually.

I created a new login entry on login-config.xml, its loading properly the users, but its not authenticating.

Would appreciate some help here,

Regards,

PS

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

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


From do-not-reply at jboss.com  Mon Jun  1 13:46:21 2009
From: do-not-reply at jboss.com (juno60)
Date: Mon, 1 Jun 2009 13:46:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - wssecurity username token encryption
Message-ID: <10594224.1243878381336.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I am struggling with wssecurity on jboss 5.0.1.GA. I can either properly authenticate to a webservice using an username token or encrypt the whole soap communication using wsse encryption but not both at the same time. I would like to authenticate using the username token and for that token to be encrypted. Should it be possible using typical/standard jboss wsse?

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

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


From do-not-reply at jboss.com  Mon Jun  1 14:12:11 2009
From: do-not-reply at jboss.com (PedroSena)
Date: Mon, 1 Jun 2009 14:12:11 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Implementing WS-Security Usename
	Token Profile Authentic
Message-ID: <1056907.1243879931312.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi Guys,

I made it work with simple Pojos, but with SLSB no way.

What is the trick?

Thanks

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

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


From do-not-reply at jboss.com  Tue Jun  2 06:15:35 2009
From: do-not-reply at jboss.com (PedroSena)
Date: Tue, 2 Jun 2009 06:15:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: wssecurity username token encryption
Message-ID: <20912629.1243937735936.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi juno,

Are you using username token with Stateless Session Beans?

I'm trying to make it and having a hard time.

Can you share your SLSB and other config necessary?

Thanks in advance,

PS

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

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


From do-not-reply at jboss.com  Tue Jun  2 07:54:34 2009
From: do-not-reply at jboss.com (bjoern83)
Date: Tue, 2 Jun 2009 07:54:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Call WebService in EJB 3.0 (Differences
	to EJB 2.1)
Message-ID: <23510929.1243943674698.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,
I had an EJB 2.1 Bean containing a WebService-Method: 

/** @jboss.port-component name="WebServiceControllerService" uri="/VERSION-ejb/WebServiceController"
  |  *                       auth-method="BASIC" transport-guarantee="NONE"
  |  * @ejb.bean name="WebServiceController" display-name="WebServiceController" generate="true"
  |  *           jndi-name="ejb/WebServiceController" local-jndi-name="ejb/WebServiceControllerLocal"
  |  *           view-type="all" type="Stateless"
  |  *
  |  * @ejb.home generate="local,remote"
  |  *
  |  * @ejb.interface generate="local,remote,service-endpoint"
  |  *                remote-class="de.cursor.jevi.server.web.WebServiceController"
  |  *                local-class="de.cursor.jevi.server.web.WebServiceControllerLocal"
  |  *                service-endpoint-class="de.cursor.jevi.server.web.WebServiceControllerService"
  |  */
  | public class WebServiceControllerBean implements SessionBean
  | {
  |     public String search(String xmlSearch)
  |     {
  | 	}
  | }

I called this method using SOAPUI with the following URI: 
http://Nebelos-C2Q:18080/CARMEN-ejb/WebServiceController
which is "MyServer" + "MyJar" + "MyWebServiceClassRemoteInterface".

Now I migrated my class to EJB 3.0:

@Stateless(name = "ejbWebServiceController")
  | @TransactionManagement(TransactionManagementType.CONTAINER)
  | @TransactionAttribute(TransactionAttributeType.SUPPORTS)
  | @PermitAll
  | @WebService
  | @SOAPBinding(style = SOAPBinding.Style.RPC)
  | @SecurityDomain(value = "VERSION")
  | @Clustered(loadBalancePolicy = de.cursor.jboss.cluster.JBossLoadBalancer.class, partition = "DefaultPartition")
  | public class WebServiceControllerBean implements WebServiceControllerLocal, WebServiceController
  | {
  |     @WebMethod(operationName = "search")
  |     public String search(String xmlSearch)
  |     {
  | 	}
  | }

My SOAP-UI call doesn't work any more telling me "The requested resource (/CARMEN-ejb/WebServiceController) is not available.". Can somebody tell me how the new uri would be or (better) how to get the old one?

thanking you in anticipation


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

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


From do-not-reply at jboss.com  Tue Jun  2 07:57:07 2009
From: do-not-reply at jboss.com (bjoern83)
Date: Tue, 2 Jun 2009 07:57:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call WebService in EJB 3.0
	(Differences to EJB 2.1)
Message-ID: <22215666.1243943827948.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Forgot to say: The "VERSION" is replaced by "CARMEN" before deploying the jar.

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

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


From do-not-reply at jboss.com  Tue Jun  2 09:49:49 2009
From: do-not-reply at jboss.com (bjoern83)
Date: Tue, 2 Jun 2009 09:49:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call WebService in EJB 3.0
	(Differences to EJB 2.1)
Message-ID: <20258345.1243950589662.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Ok, I found out that the correct URI seems to be "http://Nebelos-C2Q:18080/CARMEN-CARMEN-ejb/CARMENWebServiceController". But I would prefer to use the old one..

And a different problem occured. The parameter of my method is be default named "arg0". If I use @WebParam to rename it.

    @WebMethod(operationName = "search")
  |     public String search(@WebParam(name="xmlSearch")String xmlSearch)

I get a ParsingException during build process.

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

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


From do-not-reply at jboss.com  Tue Jun  2 12:25:04 2009
From: do-not-reply at jboss.com (pramod_bs)
Date: Tue, 2 Jun 2009 12:25:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: wssecurity username token encryption
Message-ID: <26451229.1243959905113.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"juno60" wrote : I am struggling with wssecurity on jboss 5.0.1.GA. I can either properly authenticate to a webservice using an username token or encrypt the whole soap communication using wsse encryption but not both at the same time. I would like to authenticate using the username token and for that token to be encrypted. Should it be possible using typical/standard jboss wsse?

If you ar elooking for some kind of password digest this might help http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4201637

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

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


From do-not-reply at jboss.com  Wed Jun  3 07:25:09 2009
From: do-not-reply at jboss.com (skhursheedahmed)
Date: Wed, 3 Jun 2009 07:25:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Failed to create a new SAX parser
Message-ID: <4995633.1244028309369.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I was facing same problem but removing following file, it work for me

xm-api.jar
xercesSamples.jar
xercesImpl.jar
xerces-2.6.2.jar

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

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


From do-not-reply at jboss.com  Wed Jun  3 14:20:17 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Wed, 3 Jun 2009 14:20:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Error while installing the native
	JBossWS package
Message-ID: <30942120.1244053217521.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hello All,

I am following the instructions provided here: 
http://www.jboss.org/file-access/default/members/jbossws/downloads/Install-jbossws-native-3.1.1.GA.txt

to install the native pkg. (3.1.1) for JBossWS. I am using JBoss 5.0.0 GA server and I am running into this error:

BUILD FAILED
E:\jbossws-native-bin-dist\build\build-deploy.xml:85: The following error occurred while executing this line:
E:\jbossws-native-bin-dist\build\jbossws-deploy-macros.xml:681: Unable to delete file E:\jboss-5.0.0.GA\lib\endorsed\jaxb-api.jar

I checked the permissions on the lib\endorsed folder and it says a partial Read-only (green box within the read-only box) but even If I remove the read-only restrictions, it keeps coming back and I keep getting this error.

Can anyone point out what's going wrong here.

Thanks for all help

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

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


From do-not-reply at jboss.com  Wed Jun  3 14:44:58 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Wed, 3 Jun 2009 14:44:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while installing the native
	JBossWS package
Message-ID: <25327848.1244054698303.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Is it necessary to install the JBossWS package even if the JBoss server (JBoss-5.0.0.GA) already has the jbossws.sar in it ?

Thanks


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

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


From do-not-reply at jboss.com  Wed Jun  3 15:31:26 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Wed, 3 Jun 2009 15:31:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error while installing the native
	JBossWS package
Message-ID: <9153957.1244057486463.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

OK. I got it to run.
I had to stop JBoss server to install JBossWS.

Thanks

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

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


From do-not-reply at jboss.com  Wed Jun  3 18:55:39 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Wed, 3 Jun 2009 18:55:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Unable to deploy service WAR
Message-ID: <29445221.1244069739375.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I am stuck at the point of deployment of my WAR. (for starters I am not sure if I created the WAR correctly.) but, I get the following error :

15:49:57,468 INFO  [TomcatDeployment] undeploy, ctxPath=/StockQuoteService, vfsUrl=StockQuoteService
.war
15:50:00,218 INFO  [TomcatDeployment] deploy, ctxPath=/StockQuotePortImpl, vfsUrl=StockQuotePortImpl
.war
15:50:00,281 INFO  [[/StockQuotePortImpl]] Marking servlet StockServiceServlethttp as unavailable
15:50:00,281 ERROR [[/StockQuotePortImpl]] Servlet /StockQuotePortImpl threw load() exception
java.lang.ClassCastException: com.sun.samples.StockQuotePortImpl cannot be cast to javax.servlet.Servlet

I am not sure what's going on here. Can someone point me to a resource that would list steps to generate a WAR for the WS and deploy it. I mean, what all goes in the war? does the name of the WAR matter? does the name of the WS implementation file matter? how shd the web.xml look?

Any help will be appreciated.

Thanks

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

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


From do-not-reply at jboss.com  Wed Jun  3 20:03:38 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 3 Jun 2009 20:03:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Unable to deploy service WAR
Message-ID: <22961645.1244073818827.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Is StockQuotePortImpl your class? Is it a servlet? Looks like you have an invalid cast and need to fix your code. The part of the stack trace that you did not post should tell you while line has the problem (assuming you compiled with debug options).

By the way, if the class is a servlet then the issue has nothing to do with web services, and thus this post is in the wrong forum (the beginner's forum would have been better).

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

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


From do-not-reply at jboss.com  Thu Jun  4 10:38:08 2009
From: do-not-reply at jboss.com (pgmjsd)
Date: Thu, 4 Jun 2009 10:38:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Manual install into JBoss 4.2.3.GA
Message-ID: <16427154.1244126288856.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hello all,

I was wondering if there is some documentation on how to install JBossWS into JBoss 4.2.3.GA manually.   If not, I suppose I could invoke the ANT installer from my existing ANT 'jboss setup' task, but that might be a lot of work.  So, I just wanted to make sure before going down that road.


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

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


From do-not-reply at jboss.com  Thu Jun  4 15:20:07 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 4 Jun 2009 15:20:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Manual install into JBoss 4.2.3.GA
Message-ID: <33401575.1244143207234.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

You have an Ant "jboss setup" task? Why not unzip the JBoss AS 4.2.3 binary in a temp location, run the WS installer against that, and use the result as the source for your "jboss setup" task?

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

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


From do-not-reply at jboss.com  Fri Jun  5 03:22:14 2009
From: do-not-reply at jboss.com (chiguruvada)
Date: Fri, 5 Jun 2009 03:22:14 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Error installing WebService in
	JAXRPCMetaDataBuilder
Message-ID: <30278994.1244186534526.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi 

I am also getting the same problem.  Please let me know is there any solution for this.  

Thanks 
Ravi kumar chiguruvada

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

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


From do-not-reply at jboss.com  Fri Jun  5 12:25:05 2009
From: do-not-reply at jboss.com (kurtstam)
Date: Fri, 5 Jun 2009 12:25:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.1.2 (Native) released
Message-ID: <26062712.1244219105476.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I noticed the deploy target to jboss4.2 was dropped for this release. Can I still run 3.1.2 on jboss4.2?

thx,

--Kurt

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

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


From do-not-reply at jboss.com  Fri Jun  5 12:25:34 2009
From: do-not-reply at jboss.com (HarishVembu)
Date: Fri, 5 Jun 2009 12:25:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Installing and Configuing jbossws for
	JBOSS App server -- 4.
Message-ID: <16175619.1244219134507.JavaMail.jboss@tmp3.prod.atl2.jboss.com>



Dear All,

I have a serious problem while installing and configuring JBoss server with jbossws .

The version of JBoss app server is 4.2.2 GA
and I am trying to configure with JBoss WS on it to make it ready for  deploying JAX-WS compliant web services.

I tried few versions of jboss-ws available at JBoss download page. On start up in Default mode it throws up errors like the one pasted below. 
I cannot access the webservice at http://localhost:8080/jbossws.

Appreciate your earliest response to resolve this issue.

I checked spf.jar and its present in installation directory


Error on Startup -:
____________________________________________________________

org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment at ce3b62{name=file:/C:/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaData at 19ccb73{name=WSServerConfig bean=org.jboss.wsf.stack.jbws.NativeServerConfig properties=[modifySOAPAddress, webServiceHost, mbeanServer] constructor=null}, AbstractBeanMetaData at f12b72{name=WSSubscriptionManager bean=org.jboss.ws.extensions.eventing.mgmt.SubscriptionManager properties=[bindAddress] constructor=null}, AbstractBeanMetaData at 15b6aad{name=WSMemoryBufferRecorder bean=org.jboss.wsf.framework.management.recording.MemoryBufferRecorder properties=[recording] constructor=null}, AbstractBeanMetaData at b890dc{name=WSLogRecorder bean=org.jboss.wsf.framework.management.recording.LogRecorder properties=[recording] constructor=null}, AbstractBeanMetaData at 12e7cb6{name=StackRequestHandlerFactory bean=org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl properties= constructor=null}, AbstractBeanMetaData at fd9b97{name=WSNativeContextPropertiesDeploymentAspect bean=org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect properties=[provides, contextProperties] constructor=null}, AbstractBeanMetaData at 1f1e666{name=WSNativeEagerInitializeDeploymentAspect bean=org.jboss.wsf.stack.jbws.EagerInitializeDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at 4d40df{name=WSNativeEndpointHandlerDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 1de041e{name=WSNativeEndpointRecordProcessorDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect properties=[requires, provides, mbeanServer, processors] constructor=null}, AbstractBeanMetaData at e05ad6{name=WSNativeEventingDeploymentAspect bean=org.jboss.wsf.stack.jbws.EventingDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 16bb7d9{name=WSNativePublishContractDeploymentAspect bean=org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at f346dc{name=WSNativeServiceEndpointInvokerDeploymentAspect bean=org.jboss.wsf.stack.jbws.ServiceEndpointInvokerDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 1b14530{name=WSNativeRMDeploymentAspect bean=org.jboss.ws.extensions.wsrm.server.RMDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 135877f{name=WSNativeUnifiedMetaDataDeploymentAspect bean=org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 152b6f5{name=WSJAXBIntroDeploymentAspect bean=org.jboss.wsf.stack.jbws.JAXBIntroDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 169a50b{name=WSNativeDeploymentAspectInstallerJSE bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[sortAspectsOnCreate, manager, aspects] constructor=null demands=[WSDeploymentAspectInstallerJSE]}, AbstractBeanMetaData at d297c0{name=WSNativeDeploymentAspectInstallerEJB bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[aspects, sortAspectsOnCreate, manager] constructor=null demands=[WSDeploymentAspectInstallerEJB]}, AbstractBeanMetaData at 1e8e5a7{name=WSNativeDeploymentAspectInstallerEndpointAPI bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[sortAspectsOnCreate, aspects, manager] constructor=null demands=[WSDeploymentAspectInstallerEndpointAPI]}, AbstractBeanMetaData at 13d422d{name=WSKernelLocator bean=org.jboss.wsf.spi.util.KernelLocator properties=[kernel] constructor=null}, AbstractBeanMetaData at c3d062{name=WSMBeanServerLocator bean=org.jboss.wsf.framework.management.MBeanServerLocator properties= constructor=null}, AbstractBeanMetaData at 1a5fb5a{name=WSHTTPServer bean=org.jboss.wsf.container.jboss42.DeploymentAspectHttpServer properties=[runtimeName] constructor=null}, AbstractBeanMetaData at 1906df{name=WSServiceRefHandler bean=org.jboss.wsf.container.jboss42.serviceref.ServiceRefHandlerImpl properties= constructor=null}, AbstractBeanMetaData at 1123c5f{name=ServiceRefHandler bean=org.jboss.wsf.container.jboss42.serviceref.ServiceRefHandlerImpl properties= constructor=null}, AbstractBeanMetaData at 39bf12{name=WSDeployerHook_JAXRPC_PRE_JSE bean=org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPreJSE properties=[phaseOneInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 12f4538{name=WSDeployerHook_JAXRPC_POST_JSE bean=org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPostJSE properties=[phaseTwoInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 69695f{name=WSDeployerHook_JAXRPC_EJB21 bean=org.jboss.wsf.container.jboss42.JAXRPCDeployerHookEJB21 properties=[phaseTwoInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 84de3c{name=WSDeployerHook_JAXWS_PRE_JSE bean=org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE properties=[runtime, phaseOneInterceptors] constructor=null}, AbstractBeanMetaData at 11a47df{name=WSDeployerHook_JAXWS_POST_JSE bean=org.jboss.wsf.container.jboss42.JAXWSDeployerHookPostJSE properties=[phaseTwoInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 648938{name=WSDeployerHook_JAXWS_EJB3 bean=org.jboss.wsf.container.jboss42.JAXWSDeployerHookEJB3 properties=[runtime, phaseTwoInterceptors] constructor=null}, AbstractBeanMetaData at 6cbecf{name=WebserviceJSERuntime bean=org.jboss.wsf.container.jboss42.LazyAssemblyWSFRuntime properties=[invocationHandlerFactory, deploymentAspectManager, runtimeName, endpointRegistry] constructor=null}, AbstractBeanMetaData at 16321e6{name=WebserviceEJBRuntime bean=org.jboss.wsf.container.jboss42.LazyAssemblyWSFRuntime properties=[deploymentAspectManager, invocationHandlerFactory, endpointRegistry, runtimeName] constructor=null}, AbstractBeanMetaData at 14683c0{name=EndpointAPIRuntime bean=org.jboss.wsf.container.jboss42.LazyAssemblyWSFRuntime properties=[deploymentAspectManager, invocationHandlerFactory, runtimeName, endpointRegistry] constructor=null}, AbstractBeanMetaData at 73bc22{name=WSEndpointRegistry bean=org.jboss.wsf.framework.management.ManagedEndpointRegistry properties=[mbeanServer] constructor=null}, AbstractBeanMetaData at 449afc{name=InvocationHandlerFactory bean=org.jboss.wsf.container.jboss42.InvocationHandlerFactoryImpl properties= constructor=null}, AbstractBeanMetaData at 1b3967{name=WSDeploymentAspectManagerJSE bean=org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl properties=[name] constructor=null}, AbstractBeanMetaData at 155d4be{name=WSDeploymentAspectManagerEJB bean=org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl properties=[name] constructor=null}, AbstractBeanMetaData at 21a1e{name=WSDeploymentAspectManagerEndpointAPI bean=org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl properties=[name] constructor=null}, AbstractBeanMetaData at e312{name=WSContainerMetaDataDeploymentAspect bean=org.jboss.wsf.container.jboss42.ContainerMetaDataDeploymentAspect properties=[metaDataAdapter, provides] constructor=null}, AbstractBeanMetaData at 3bce70{name=WSContextRootDeploymentAspect bean=org.jboss.wsf.framework.deployment.BackwardCompatibleContextRootDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 6e56ae{name=WSEndpointAPIDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointAPIDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 1fcbac1{name=WSEndpointAddressDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointAddressDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 148e23b{name=WSEndpointHandlerDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at 1fc9f88{name=WSEndpointLifecycleDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointLifecycleDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 4dd014{name=WSEndpointMetricsDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointMetricsDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 97f621{name=WSEndpointNameDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointNameDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at a02839{name=WSEndpointRegistryDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointRegistryDeploymentAspect properties=[provides, requires] constructor=null demands=[WSEndpointRegistry]}, AbstractBeanMetaData at b0ede6{name=WSModifyWebMetaDataDeploymentAspect bean=org.jboss.wsf.container.jboss42.ModifyWebMetaDataDeploymentAspect properties=[webXMLRewriter, requires] constructor=null}, AbstractBeanMetaData at 1d29a78{name=WSRuntimeLoaderDeploymentAspect bean=org.jboss.wsf.container.jboss42.RuntimeLoaderDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 19b6225{name=WSURLPatternDeploymentAspect bean=org.jboss.wsf.framework.deployment.BackwardCompatibleURLPatternDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at 487c5f{name=WSWebAppDeploymentAspect bean=org.jboss.wsf.container.jboss42.WebAppDeploymentAspect properties=[webXMLRewriter, requires] constructor=null}, AbstractBeanMetaData at dd725b{name=WSWebAppGeneratorDeploymentAspect bean=org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect properties=[provides, securityHandlerEJB3, securityHandlerEJB21, requires] constructor=null}, AbstractBeanMetaData at 7ed081{name=WSFakeWebMetaDataDeploymentAspect bean=org.jboss.wsf.framework.deployment.IdentityDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 1aac775{name=WSApplicationMetaDataAdapterEJB21 bean=org.jboss.wsf.container.jboss42.EJBArchiveMetaDataAdapterEJB21 properties= constructor=null}, AbstractBeanMetaData at 10ce397{name=WSApplicationMetaDataAdapterEJB3 bean=org.jboss.wsf.container.jboss42.EJBArchiveMetaDataAdapterEJB3 properties= constructor=null}, AbstractBeanMetaData at 131f919{name=WSContainerMetaDataAdapter bean=org.jboss.wsf.container.jboss42.ContainerMetaDataAdapter properties=[applicationMetaDataAdapterEJB21, applicationMetaDataAdapterEJB3, webMetaDataAdapter] constructor=null}, AbstractBeanMetaData at 1d91364{name=WSSecurityHandlerEJB21 bean=org.jboss.wsf.container.jboss42.SecurityHandlerEJB21 properties= constructor=null}, AbstractBeanMetaData at 883644{name=WSSecurityHandlerEJB3 bean=org.jboss.wsf.container.jboss42.SecurityHandlerEJB3 properties= constructor=null}, AbstractBeanMetaData at a2ba05{name=WSWebAppDesciptorModifier bean=org.jboss.wsf.container.jboss42.DefaultWebAppDesciptorModifierImpl properties= constructor=null}, AbstractBeanMetaData at 1629e96{name=WSWebMetaDataAdapter bean=org.jboss.wsf.container.jboss42.JSEArchiveMetaDataAdapter properties= constructor=null}, AbstractBeanMetaData at 199a84f{name=WSWebXMLRewriter bean=org.jboss.wsf.container.jboss42.WebXMLRewriterImpl properties=[desciptorModifier] constructor=null}, AbstractBeanMetaData at f8ff42{name=WSDeploymentAspectInstallerJSE bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[aspects, manager, sortAspectsOnCreate] constructor=null}, AbstractBeanMetaData at 13e6346{name=WSDeploymentAspectInstallerEJB bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[manager, aspects, sortAspectsOnCreate] constructor=null}, AbstractBeanMetaData at e7bb91{name=WSDeploymentAspectInstallerEndpointAPI bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[sortAspectsOnCreate, manager, aspects] constructor=null}]}; - nested throwable: (java.lang.IllegalStateException: Incompletely deployed:

*** DEPLOYMENTS IN ERROR:
WSNativePublishContractDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSJAXBIntroDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSSubscriptionManager -> java.lang.NoClassDefFoundError: org/jboss/logging/Logger
WSNativeEventingDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSNativeEagerInitializeDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSNativeServiceEndpointInvokerDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSServerConfig -> java.lang.NoClassDefFoundError: org/jboss/wsf/common/management/AbstractServerConfigMBean
WSNativeUnifiedMetaDataDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
StackRequestHandlerFactory -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/invocation/RequestHandlerFactory

*** DEPLOYMENTS MISSING DEPENDENCIES:
WSNativeDeploymentAspectInstallerEndpointAPI -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspect{Configured:**ERROR**}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:**ERROR**}, WSNativePublishContractDeploymentAspect{Configured:**ERROR**}, WSNativeServiceEndpointInvokerDeploymentAspect{Configured:**ERROR**}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:**ERROR**}, WSJAXBIntroDeploymentAspect{Configured:**ERROR**}, WSDeploymentAspectManagerEndpointAPI{Configured:Installed}, WSDeploymentAspectInstallerEndpointAPI{Create:Installed}, WSDeploymentAspectInstallerEndpointAPI{Start:Installed}
WSNativeDeploymentAspectInstallerEJB -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspect{Configured:**ERROR**}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:**ERROR**}, WSNativePublishContractDeploymentAspect{Configured:**ERROR**}, WSNativeServiceEndpointInvokerDeploymentAspect{Configured:**ERROR**}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:**ERROR**}, WSJAXBIntroDeploymentAspect{Configured:**ERROR**}, WSDeploymentAspectManagerEJB{Configured:Installed}, WSDeploymentAspectInstallerEJB{Create:Installed}, WSDeploymentAspectInstallerEJB{Start:Installed}
WSNativeDeploymentAspectInstallerJSE -> WSDeploymentAspectManagerJSE{Configured:Installed}, WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:**ERROR**}, WSNativePublishContractDeploymentAspect{Configured:**ERROR**}, WSNativeServiceEndpointInvokerDeploymentAspect{Configured:**ERROR**}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:**ERROR**}, WSNativeEagerInitializeDeploymentAspect{Configured:**ERROR**}, WSJAXBIntroDeploymentAspect{Configured:**ERROR**}, WSDeploymentAspectInstallerJSE{Create:Installed}, WSDeploymentAspectInstallerJSE{Start:Installed}
)
	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
	at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.startService(JBossBeanDeployment.java:86)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy19.start(Unknown Source)
	at org.jboss.deployment.SimpleSubDeployerSupport.startService(SimpleSubDeployerSupport.java:356)
	at org.jboss.deployment.SimpleSubDeployerSupport.start(SimpleSubDeployerSupport.java:127)
	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
	at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.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)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.start(Unknown Source)
	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
	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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.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 $Proxy5.deploy(Unknown Source)
	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
	at org.jboss.Main.boot(Main.java:200)
	at org.jboss.Main$1.run(Main.java:508)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Incompletely deployed:

*** DEPLOYMENTS IN ERROR:
WSNativePublishContractDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSJAXBIntroDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSSubscriptionManager -> java.lang.NoClassDefFoundError: org/jboss/logging/Logger
WSNativeEventingDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSNativeEagerInitializeDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSNativeServiceEndpointInvokerDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
WSServerConfig -> java.lang.NoClassDefFoundError: org/jboss/wsf/common/management/AbstractServerConfigMBean
WSNativeUnifiedMetaDataDeploymentAspect -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/deployment/DeploymentAspect
StackRequestHandlerFactory -> java.lang.NoClassDefFoundError: org/jboss/wsf/spi/invocation/RequestHandlerFactory

*** DEPLOYMENTS MISSING DEPENDENCIES:
WSNativeDeploymentAspectInstallerEndpointAPI -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspect{Configured:**ERROR**}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:**ERROR**}, WSNativePublishContractDeploymentAspect{Configured:**ERROR**}, WSNativeServiceEndpointInvokerDeploymentAspect{Configured:**ERROR**}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:**ERROR**}, WSJAXBIntroDeploymentAspect{Configured:**ERROR**}, WSDeploymentAspectManagerEndpointAPI{Configured:Installed}, WSDeploymentAspectInstallerEndpointAPI{Create:Installed}, WSDeploymentAspectInstallerEndpointAPI{Start:Installed}
WSNativeDeploymentAspectInstallerEJB -> WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEagerInitializeDeploymentAspect{Configured:**ERROR**}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:**ERROR**}, WSNativePublishContractDeploymentAspect{Configured:**ERROR**}, WSNativeServiceEndpointInvokerDeploymentAspect{Configured:**ERROR**}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:**ERROR**}, WSJAXBIntroDeploymentAspect{Configured:**ERROR**}, WSDeploymentAspectManagerEJB{Configured:Installed}, WSDeploymentAspectInstallerEJB{Create:Installed}, WSDeploymentAspectInstallerEJB{Start:Installed}
WSNativeDeploymentAspectInstallerJSE -> WSDeploymentAspectManagerJSE{Configured:Installed}, WSNativeContextPropertiesDeploymentAspect{Configured:Installed}, WSNativeEndpointHandlerDeploymentAspect{Configured:Installed}, WSNativeEndpointRecordProcessorDeploymentAspect{Configured:Installed}, WSNativeEventingDeploymentAspect{Configured:**ERROR**}, WSNativePublishContractDeploymentAspect{Configured:**ERROR**}, WSNativeServiceEndpointInvokerDeploymentAspect{Configured:**ERROR**}, WSNativeRMDeploymentAspect{Configured:Installed}, WSNativeUnifiedMetaDataDeploymentAspect{Configured:**ERROR**}, WSNativeEagerInitializeDeploymentAspect{Configured:**ERROR**}, WSJAXBIntroDeploymentAspect{Configured:**ERROR**}, WSDeploymentAspectInstallerJSE{Create:Installed}, WSDeploymentAspectInstallerJSE{Start:Installed}

	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:241)
	at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:173)
	at org.jboss.kernel.deployment.jboss.JBossBeanDeployment.startService(JBossBeanDeployment.java:82)
	... 94 more
08:47:03,917 INFO  [Embedded] Catalina naming disabled
08:47:04,480 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\jdk1.5\jre\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\Java\jre1.6.0_07\bin\client;C:\Program Files\Java\jre1.6.0_07\bin;C:\oracle\product\10.2.0\client_1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\RSA Security\RSA SecurID Software Token\;C:\Program Files\Hummingbird\Connectivity\9.00\Security\Kerberos\;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Private Shell;C:\jdk1.5\jre\lib;C:\jdk1.5\jre\bin;C:\jdk1.5\bin;C:\jdk1.5\lib;C:\Program Files\TortoiseSVN\bin;C:\apache-ant-1.7.1\bin;C:\jboss-4.2.2.GA\server\messaging\deploy\arsys.war\WEB-INF\lib
08:47:04,620 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
08:47:04,620 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
08:47:04,620 INFO  [Catalina] Initialization processed in 706 ms
08:47:04,620 INFO  [StandardService] Starting service jboss.web
08:47:04,636 INFO  [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
08:47:04,699 INFO  [Catalina] Server startup in 74 ms
08:47:04,949 INFO  [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
08:47:06,042 INFO  [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
08:47:06,246 ERROR [MainDeployer] Could not create deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws-management.war/
java.lang.NoClassDefFoundError: javax/servlet/http/HttpServlet
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
	at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:200)
	at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
	at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
	at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:527)
	at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.getEndpointBeans(JAXWSDeployerHookPreJSE.java:141)
	at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.isWebServiceDeployment(JAXWSDeployerHookPreJSE.java:114)
	at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:87)
	at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy45.create(Unknown Source)
	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
	at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.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 $Proxy43.addDeployer(Unknown Source)
	at org.jboss.web.tomcat.service.JBossWeb.startService(JBossWeb.java:500)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
	at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:109)
	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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.start(Unknown Source)
	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
	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.GeneratedMethodAccessor18.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)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.start(Unknown Source)
	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
	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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.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 $Proxy5.deploy(Unknown Source)
	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
	at org.jboss.Main.boot(Main.java:200)
	at org.jboss.Main$1.run(Main.java:508)
	at java.lang.Thread.run(Thread.java:595)
08:47:06,261 ERROR [MainDeployer] DeploymentException while trying to deploy a package with a new deployer
org.jboss.deployment.DeploymentException: Could not create deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws-management.war/; - nested throwable: (java.lang.NoClassDefFoundError: javax/servlet/http/HttpServlet)
	at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:53)
	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:991)
	at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:818)
	at org.jboss.deployment.MainDeployer.addDeployer(MainDeployer.java:368)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.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 $Proxy43.addDeployer(Unknown Source)
	at org.jboss.web.tomcat.service.JBossWeb.startService(JBossWeb.java:500)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.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.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97)
	at org.jboss.deployment.SubDeployerInterceptor.invokeNext(SubDeployerInterceptor.java:124)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:109)
	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.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at org.jboss.system.ServiceController.start(ServiceController.java:435)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.start(Unknown Source)
	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
	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.GeneratedMethodAccessor18.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)
	at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
	at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
	at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
	at $Proxy0.start(Unknown Source)
	at org.jboss.system.ServiceController.start(ServiceController.java:417)
	at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy4.start(Unknown Source)
	at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
	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 org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:585)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
	at org.jboss.mx.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 $Proxy5.deploy(Unknown Source)
	at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
	at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
	at org.jboss.Main.boot(Main.java:200)
	at org.jboss.Main$1.run(Main.java:508)
	at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoClassDefFoundError: javax/servlet/http/HttpServlet
	at java.lang.ClassLoader.defineClass1(Native Method)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
	at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
	at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
	at org.jboss.mx.loading.RepositoryClassLoader.loadClassLocally(RepositoryClassLoader.java:200)
	at org.jboss.mx.loading.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:131)
	at org.jboss.mx.loading.LoadMgr3.nextTask(LoadMgr3.java:399)
	at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:527)
	at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:415)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.getEndpointBeans(JAXWSDeployerHookPreJSE.java:141)
	at org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE.isWebServiceDeployment(JAXWSDeployerHookPreJSE.java:114)
	at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:87)
	at org.jboss.wsf.container.jboss42.DeployerInterceptor.create(DeployerInterceptor.java:79)
	at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.create(SubDeployerInterceptorSupport.java:180)
	at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:91)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
	at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
	at $Proxy45.create(Unknown Source)
	at org.jboss.deployment.MainDeployer.create(MainDeployer.java:969)
	... 115 more
08:47:06,402 INFO  [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
08:47:06,574 INFO  [TomcatDeployer] deploy, ctxPath=/juddi, warUrl=.../deploy/juddi-service.sar/juddi.war/
08:47:06,792 INFO  [RegistryServlet] Loading jUDDI configuration.
08:47:06,808 INFO  [RegistryServlet] Resources loaded from: /WEB-INF/juddi.properties
08:47:06,808 INFO  [RegistryServlet] Initializing jUDDI components.
08:47:08,042 INFO  [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
08:47:09,074 INFO  [MailService] Mail Service bound to java:/Mail
08:47:09,339 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
08:47:09,433 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
08:47:09,542 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
08:47:09,589 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
08:47:09,683 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
08:47:09,730 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
08:47:09,777 INFO  [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
08:47:09,871 INFO  [QuartzResourceAdapter] start quartz!!!
08:47:10,011 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
08:47:10,042 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
08:47:10,042 INFO  [RAMJobStore] RAMJobStore initialized.
08:47:10,042 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
08:47:10,042 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
08:47:10,042 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
08:47:11,574 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
08:47:12,011 INFO  [A] Bound to JNDI name: queue/A
08:47:12,011 INFO  [B] Bound to JNDI name: queue/B
08:47:12,011 INFO  [C] Bound to JNDI name: queue/C
08:47:12,011 INFO  [D] Bound to JNDI name: queue/D
08:47:12,027 INFO  [ex] Bound to JNDI name: queue/ex
08:47:12,058 INFO  [testTopic] Bound to JNDI name: topic/testTopic
08:47:12,058 INFO  [securedTopic] Bound to JNDI name: topic/securedTopic
08:47:12,058 INFO  [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
08:47:12,058 INFO  [testQueue] Bound to JNDI name: queue/testQueue
08:47:12,168 INFO  [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
08:47:12,199 INFO  [DLQ] Bound to JNDI name: queue/DLQ
08:47:12,386 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
08:47:12,402 INFO  [TomcatDeployer] deploy, ctxPath=/arsys, warUrl=.../deploy/arsys.war/
08:47:12,480 WARN  [config] Unable to process deployment descriptor for context 'null'
08:47:13,371 INFO  [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
08:47:13,464 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo at 4cd4229b { url=file:/C:/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws-management.war/ }
  deployer: MBeanProxyExt[jboss.web:service=WebServer]
  status: Deployment FAILED reason: javax/servlet/http/HttpServlet
  state: FAILED
  watch: file:/C:/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws-management.war/WEB-INF/web.xml
  altDD: null
  lastDeployed: 1244216826230
  lastModified: 1244180980984
  mbeans:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.beans:service=JBossBeanDeployment,name='jbossws.sar#jbossws.beans'
  State: FAILED
  Reason: org.jboss.deployment.DeploymentException: Cannot start AbstractKernelDeployment at ce3b62{name=file:/C:/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml installed=true beans=[AbstractBeanMetaData at 19ccb73{name=WSServerConfig bean=org.jboss.wsf.stack.jbws.NativeServerConfig properties=[modifySOAPAddress, webServiceHost, mbeanServer] constructor=null}, AbstractBeanMetaData at f12b72{name=WSSubscriptionManager bean=org.jboss.ws.extensions.eventing.mgmt.SubscriptionManager properties=[bindAddress] constructor=null}, AbstractBeanMetaData at 15b6aad{name=WSMemoryBufferRecorder bean=org.jboss.wsf.framework.management.recording.MemoryBufferRecorder properties=[recording] constructor=null}, AbstractBeanMetaData at b890dc{name=WSLogRecorder bean=org.jboss.wsf.framework.management.recording.LogRecorder properties=[recording] constructor=null}, AbstractBeanMetaData at 12e7cb6{name=StackRequestHandlerFactory bean=org.jboss.wsf.stack.jbws.RequestHandlerFactoryImpl properties= constructor=null}, AbstractBeanMetaData at fd9b97{name=WSNativeContextPropertiesDeploymentAspect bean=org.jboss.wsf.framework.deployment.ContextPropertiesDeploymentAspect properties=[provides, contextProperties] constructor=null}, AbstractBeanMetaData at 1f1e666{name=WSNativeEagerInitializeDeploymentAspect bean=org.jboss.wsf.stack.jbws.EagerInitializeDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at 4d40df{name=WSNativeEndpointHandlerDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 1de041e{name=WSNativeEndpointRecordProcessorDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointRecordProcessorDeploymentAspect properties=[requires, provides, mbeanServer, processors] constructor=null}, AbstractBeanMetaData at e05ad6{name=WSNativeEventingDeploymentAspect bean=org.jboss.wsf.stack.jbws.EventingDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 16bb7d9{name=WSNativePublishContractDeploymentAspect bean=org.jboss.wsf.stack.jbws.PublishContractDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at f346dc{name=WSNativeServiceEndpointInvokerDeploymentAspect bean=org.jboss.wsf.stack.jbws.ServiceEndpointInvokerDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 1b14530{name=WSNativeRMDeploymentAspect bean=org.jboss.ws.extensions.wsrm.server.RMDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 135877f{name=WSNativeUnifiedMetaDataDeploymentAspect bean=org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 152b6f5{name=WSJAXBIntroDeploymentAspect bean=org.jboss.wsf.stack.jbws.JAXBIntroDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 169a50b{name=WSNativeDeploymentAspectInstallerJSE bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[sortAspectsOnCreate, manager, aspects] constructor=null demands=[WSDeploymentAspectInstallerJSE]}, AbstractBeanMetaData at d297c0{name=WSNativeDeploymentAspectInstallerEJB bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[aspects, sortAspectsOnCreate, manager] constructor=null demands=[WSDeploymentAspectInstallerEJB]}, AbstractBeanMetaData at 1e8e5a7{name=WSNativeDeploymentAspectInstallerEndpointAPI bean=org.jboss.wsf.framework.deployment.DeploymentAspectInstaller properties=[sortAspectsOnCreate, aspects, manager] constructor=null demands=[WSDeploymentAspectInstallerEndpointAPI]}, AbstractBeanMetaData at 13d422d{name=WSKernelLocator bean=org.jboss.wsf.spi.util.KernelLocator properties=[kernel] constructor=null}, AbstractBeanMetaData at c3d062{name=WSMBeanServerLocator bean=org.jboss.wsf.framework.management.MBeanServerLocator properties= constructor=null}, AbstractBeanMetaData at 1a5fb5a{name=WSHTTPServer bean=org.jboss.wsf.container.jboss42.DeploymentAspectHttpServer properties=[runtimeName] constructor=null}, AbstractBeanMetaData at 1906df{name=WSServiceRefHandler bean=org.jboss.wsf.container.jboss42.serviceref.ServiceRefHandlerImpl properties= constructor=null}, AbstractBeanMetaData at 1123c5f{name=ServiceRefHandler bean=org.jboss.wsf.container.jboss42.serviceref.ServiceRefHandlerImpl properties= constructor=null}, AbstractBeanMetaData at 39bf12{name=WSDeployerHook_JAXRPC_PRE_JSE bean=org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPreJSE properties=[phaseOneInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 12f4538{name=WSDeployerHook_JAXRPC_POST_JSE bean=org.jboss.wsf.container.jboss42.JAXRPCDeployerHookPostJSE properties=[phaseTwoInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 69695f{name=WSDeployerHook_JAXRPC_EJB21 bean=org.jboss.wsf.container.jboss42.JAXRPCDeployerHookEJB21 properties=[phaseTwoInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 84de3c{name=WSDeployerHook_JAXWS_PRE_JSE bean=org.jboss.wsf.container.jboss42.JAXWSDeployerHookPreJSE properties=[runtime, phaseOneInterceptors] constructor=null}, AbstractBeanMetaData at 11a47df{name=WSDeployerHook_JAXWS_POST_JSE bean=org.jboss.wsf.container.jboss42.JAXWSDeployerHookPostJSE properties=[phaseTwoInterceptors, runtime] constructor=null}, AbstractBeanMetaData at 648938{name=WSDeployerHook_JAXWS_EJB3 bean=org.jboss.wsf.container.jboss42.JAXWSDeployerHookEJB3 properties=[runtime, phaseTwoInterceptors] constructor=null}, AbstractBeanMetaData at 6cbecf{name=WebserviceJSERuntime bean=org.jboss.wsf.container.jboss42.LazyAssemblyWSFRuntime properties=[invocationHandlerFactory, deploymentAspectManager, runtimeName, endpointRegistry] constructor=null}, AbstractBeanMetaData at 16321e6{name=WebserviceEJBRuntime bean=org.jboss.wsf.container.jboss42.LazyAssemblyWSFRuntime properties=[deploymentAspectManager, invocationHandlerFactory, endpointRegistry, runtimeName] constructor=null}, AbstractBeanMetaData at 14683c0{name=EndpointAPIRuntime bean=org.jboss.wsf.container.jboss42.LazyAssemblyWSFRuntime properties=[deploymentAspectManager, invocationHandlerFactory, runtimeName, endpointRegistry] constructor=null}, AbstractBeanMetaData at 73bc22{name=WSEndpointRegistry bean=org.jboss.wsf.framework.management.ManagedEndpointRegistry properties=[mbeanServer] constructor=null}, AbstractBeanMetaData at 449afc{name=InvocationHandlerFactory bean=org.jboss.wsf.container.jboss42.InvocationHandlerFactoryImpl properties= constructor=null}, AbstractBeanMetaData at 1b3967{name=WSDeploymentAspectManagerJSE bean=org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl properties=[name] constructor=null}, AbstractBeanMetaData at 155d4be{name=WSDeploymentAspectManagerEJB bean=org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl properties=[name] constructor=null}, AbstractBeanMetaData at 21a1e{name=WSDeploymentAspectManagerEndpointAPI bean=org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl properties=[name] constructor=null}, AbstractBeanMetaData at e312{name=WSContainerMetaDataDeploymentAspect bean=org.jboss.wsf.container.jboss42.ContainerMetaDataDeploymentAspect properties=[metaDataAdapter, provides] constructor=null}, AbstractBeanMetaData at 3bce70{name=WSContextRootDeploymentAspect bean=org.jboss.wsf.framework.deployment.BackwardCompatibleContextRootDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 6e56ae{name=WSEndpointAPIDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointAPIDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 1fcbac1{name=WSEndpointAddressDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointAddressDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 148e23b{name=WSEndpointHandlerDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointHandlerDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at 1fc9f88{name=WSEndpointLifecycleDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointLifecycleDeploymentAspect properties=[requires] constructor=null}, AbstractBeanMetaData at 4dd014{name=WSEndpointMetricsDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointMetricsDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 97f621{name=WSEndpointNameDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointNameDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at a02839{name=WSEndpointRegistryDeploymentAspect bean=org.jboss.wsf.framework.deployment.EndpointRegistryDeploymentAspect properties=[provides, requires] constructor=null demands=[WSEndpointRegistry]}, AbstractBeanMetaData at b0ede6{name=WSModifyWebMetaDataDeploymentAspect bean=org.jboss.wsf.container.jboss42.ModifyWebMetaDataDeploymentAspect properties=[webXMLRewriter, requires] constructor=null}, AbstractBeanMetaData at 1d29a78{name=WSRuntimeLoaderDeploymentAspect bean=org.jboss.wsf.container.jboss42.RuntimeLoaderDeploymentAspect properties=[provides, requires] constructor=null}, AbstractBeanMetaData at 19b6225{name=WSURLPatternDeploymentAspect bean=org.jboss.wsf.framework.deployment.BackwardCompatibleURLPatternDeploymentAspect properties=[requires, provides] constructor=null}, AbstractBeanMetaData at 487c5f{name=WSWebAppDeploymentAspect bean=org.jboss.wsf.container.jboss42.WebAppDeploymentAspect properties=[webXMLRewriter, requires] constructor=null}, AbstractBeanMetaData at dd725b{name=WSWebAppGeneratorDeploymentAspect bean=org.jboss.wsf.framework.deployment.WebAppGeneratorDeploymentAspect properties=[provides, securityHandlerEJB3, securityHandlerEJB21, requires] constructor=null}, AbstractBeanMetaData at 7ed081{name=WSFakeWebMetaDataDeploymentAspect bean=org.jboss.wsf.framework.deployment.IdentityDeploymentAspect properties=[provides] constructor=null}, AbstractBeanMetaData at 1aac775{name=WSApplicationMetaDataAdapterEJB21 bean=org.jboss.wsf.container.jboss42.EJBArchiveMetaDataAdapterEJB21 properties= constructor=null}, AbstractBeanMetaData at 10ce397{name=WSApplicationMetaDataAdapterEJB3 bean=org.jboss.wsf.container.jboss42.EJBArchiveMetaDataAdapterEJB3 properties= constructor=null}, AbstractBeanMetaData at 131f919{name=WSContainerMetaDataAdapter bean=org.jboss.wsf.container.jboss42.ContainerMetaDataAdapter properties=[applicationMetaDataAdapterEJB21, applicationMetaDataAdapterEJ

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

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



From do-not-reply at jboss.com  Fri Jun  5 15:54:31 2009
From: do-not-reply at jboss.com (phadnism)
Date: Fri, 5 Jun 2009 15:54:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - publish https endpoints for non-secure
	service behind ssl pr
Message-ID: <19865758.1244231671560.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Running JBoss 4.3 EAP

We need to be able to publish https endpoint/soap address locations for a web service behind an ssl proxy. If we declare the service as secure to do that, when a request comes in over ssl, the proxy terminates ssl and passes http to jboss which throws a redirect as it's not secure.

If we publish as non-secure, we get http endpoints. if client accesses over http, the proxy throws a redirect to https (port 80 is not open). the soap client does not follow redirects as the http spec forbids automated clients to follow redirects on POST.

So we basically need a way to publish secure urls while still declaring the service as non-secure.

I tried setting below in jboss-beans.xml :

${jboss.bind.address}
true
443

This does not rewrite the protocol to https/443.



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

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


From do-not-reply at jboss.com  Fri Jun  5 15:55:51 2009
From: do-not-reply at jboss.com (phadnism)
Date: Fri, 5 Jun 2009 15:55:51 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: publish https endpoints for
	non-secure service behind ss
Message-ID: <16665490.1244231751123.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Guess I lost xml tags, above values are for:

webServiceHost
modifySOAPAddress
webServiceSecurePort


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

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


From do-not-reply at jboss.com  Mon Jun  8 01:49:49 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 8 Jun 2009 01:49:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.1.2 (Native) released
Message-ID: <24703248.1244440189105.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

No, see Supported Target Containers Matrix

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

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


From do-not-reply at jboss.com  Mon Jun  8 01:52:17 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 8 Jun 2009 01:52:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Installing and Configuing jbossws
	for JBOSS App server -
Message-ID: <23818991.1244440337134.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

   how did you install JBossWS? Using our provided deploy-jbossXYZ ant targets?
What JBossWS version did you use?

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

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


From do-not-reply at jboss.com  Mon Jun  8 01:53:44 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 8 Jun 2009 01:53:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: publish https endpoints for
	non-secure service behind ss
Message-ID: <436145.1244440424809.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

JBoss EAP is not supported via user forums. Consider using our professional services.

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

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


From do-not-reply at jboss.com  Tue Jun  9 16:46:25 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Tue, 9 Jun 2009 16:46:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JAXWS handlers
Message-ID: <29600169.1244580385522.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hello,

I am new to JBossWS and my task is to get a given WS work with Handlers. The handlers are responsible for securing the SOAP Request through another API (to be precise - OpenSSO STS API)

I got this to work on Weblogic container and since JAX WS is a standard followed by JBoss also, I would assume, the same handler implementation would work here too (with minor config changes). But, I get the following exception when I run the client.


  | 13:32:06,250 ERROR [STDERR] java.lang.IllegalArgumentException: SOAPElement expected
  | 13:32:06,250 ERROR [STDERR]     at org.jboss.ws.core.soap.SOAPBodyImpl.convertToBodyElement(SOAPBody
  | Impl.java:296)
  | 13:32:06,250 ERROR [STDERR]     at org.jboss.ws.core.soap.SOAPBodyImpl.appendChild(SOAPBodyImpl.java
  | :200)
  | 13:32:06,250 ERROR [STDERR]     at com.sun.identity.wss.sts.TrustAuthorityClient.getTrustResponse(Tr
  | ustAuthorityClient.java:566)
  | 13:32:06,250 ERROR [STDERR]     at com.sun.identity.wss.sts.TrustAuthorityClient.getSTSToken(TrustAu
  | thorityClient.java:540)
  | 13:32:06,250 ERROR [STDERR]     at com.sun.identity.wss.sts.TrustAuthorityClient.getSecurityToken(Tr
  | ustAuthorityClient.java:280)
  | 13:32:06,250 ERROR [STDERR]     at com.sun.identity.wss.sts.TrustAuthorityClient.getSecurityToken(Tr
  | ustAuthorityClient.java:108)
  | 13:32:06,312 ERROR [STDERR]     at com.sun.identity.wss.security.handler.SOAPRequestHandler.secureRe
  | quest(SOAPRequestHandler.java:607)
  | 13:32:06,312 ERROR [STDERR]     at com.sun.samples.ClientHandler.handleMessage(ClientHandler.java:70
  | )
  | 13:32:06,312 ERROR [STDERR]     at com.sun.samples.ClientHandler.handleMessage(ClientHandler.java:1)
  | 
  | 13:32:06,312 ERROR [STDERR]     at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessag
  | e(HandlerChainExecutor.java:305)
  | 

I am not sure what's causing this exception so for debugging, I start with the handler config files for JBoss. The handler on the client side looks like the following. Does it look right or am I missing something here?


  | <bindings xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  |     xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
  |     wsdlLocation="http://localhost:8080/StockQuoteImpl?WSDL"
  |     xmlns="http://java.sun.com/xml/ns/jaxws">
  |     <bindings node="wsdl:definitions"  
  |         xmlns:jws="http://java.sun.com/xml/ns/javaee">
  |     <handler-chains xmlns="http://java.sun.com/xml/ns/javaee">
  |        <handler-chain>
  |          <handler>
  |           <handler-class>com.sun.samples.ClientHandler</handler-class>
  |          </handler>   
  | 	   </handler-chain>
  |      </handler-chains> 
  | </bindings>
  | </bindings>

On the server side it is as follows:


  | <?xml version="1.0" encoding="UTF-8"?>
  | <handler-config>
  | <handler-chains xmlns="http://java.sun.com/xml/ns/javaee">
  |   <handler-chain>
  |   <handler-chain-name>SimpleChain</handler-chain-name>
  |      <handler>
  |         <handler-name>handler1</handler-name>
  |         <handler-class>com.sun.samples.ServerHandler</handler-class>
  |      </handler>
  |    </handler-chain>
  | </handler-chains>
  | </handler-config>
  | 

Any insights/useful hints will be greatly appreciated.

Thanks

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

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


From do-not-reply at jboss.com  Tue Jun  9 21:44:44 2009
From: do-not-reply at jboss.com (hargurjas)
Date: Tue, 9 Jun 2009 21:44:44 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - wsconsume issue
Message-ID: <13314283.1244598284161.JavaMail.jboss@tmp3.prod.atl2.jboss.com>



Hi I am trying to create Java class objects for a wsdl file and getting an error message:

[ERROR] operation "getDocument": more than one part bound to body

Is anybody know how to resolve this issue.

Thanks
Regards,
Raj

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

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


From do-not-reply at jboss.com  Wed Jun 10 15:02:00 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Wed, 10 Jun 2009 15:02:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS handlers
Message-ID: <21438776.1244660520345.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Little bit of googling leads to some issues with the SAAJ implementation from JBoss.

Can anyone please tell me if there is a workaround? 

Thanks

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

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


From do-not-reply at jboss.com  Wed Jun 10 19:06:32 2009
From: do-not-reply at jboss.com (gkim)
Date: Wed, 10 Jun 2009 19:06:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceContext injection. Was it
	fixed or not?
Message-ID: <19952180.1244675192215.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm having the same problem. Does anyone have a solution or workaround? I'm using JBoss 4.2.3 and JBossWS 3.1.1.GA.

@Resource
WebServiceContext wsCtx;

always returns null.

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

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


From do-not-reply at jboss.com  Thu Jun 11 02:08:58 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 11 Jun 2009 02:08:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: WebServiceContext injection. Was it
	fixed or not?
Message-ID: <6103253.1244700538277.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

This is fixed since JBossWS 3.1.2

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

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


From do-not-reply at jboss.com  Thu Jun 11 02:12:32 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Thu, 11 Jun 2009 02:12:32 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS handlers
Message-ID: <1758469.1244700752990.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

What JBossWS version are you using?

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

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


From do-not-reply at jboss.com  Thu Jun 11 06:21:27 2009
From: do-not-reply at jboss.com (agomese)
Date: Thu, 11 Jun 2009 06:21:27 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - About WS client security (obfuscation
	required ?)
Message-ID: <26757001.1244715687138.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hello all,

I'm developing a client (Swing-based) software which allows to send/receive files from a JBoss AS central repository, using the JBossWS web service implementation. The JBossWS version we use is the one that is bundled within the JBoss AS version, in order to ensure compatibility. 

To allow this communication, our swing-based client software is going to be released with the required JBossWS client jars (taken from the JBossAS distribution). For now, we plan to put those JBossWS jars in a "lib" folder, placed directly under the client software's root folder. The rest of the client's code (the "proprietary" part) will be obfuscated.

My question is : in your opinion, should the JBossWS client jars be protected through the same obfuscation mecanism, in order to ensure maximum security ? And BTW, does JBoss authorize such mecanism for the jars/sources they deliver ?

I tried to found related questions on this forum and on the web, but found none. Actually, we are affraid one could override the endpoint's adress by switching the original JBossWS client jars placed in the "lib" folder, in order to obtain the sent/received files from the remote AS.

We are already securing the communication through HTTPS transport, signature and encryption. However, the client keystore providing the security configuration is not going to be part of the obfuscation process, as it has to be specific per customer (please note that the JBoss AS install is specific per customer too, and so each client specific keystore is associated to a server specific keystore). We believe one could change this client keystore, create a fake endpoint with a new server keystore, and redirect traffic to this fake endpoint by changing the JBossWS client jars. But maybe are we being a bit paranoiac ?

Our configuration : 
- JDK 5
- JBoss AS 4.2.3 with JBossWS native 3.0.1

Any opinion about this point would be appreciated.


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

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


From do-not-reply at jboss.com  Thu Jun 11 12:28:22 2009
From: do-not-reply at jboss.com (lafr)
Date: Thu, 11 Jun 2009 12:28:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: NotSerializableException:
	org.jboss.ws.core.soap.SOAPFau
Message-ID: <20170162.1244737702188.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I downloaded jbossws-3.0.1-native-2.0.4.GA-src
and modified src/main/java/org/jboss/ws/core/soap/SOAPFaultElementImpl.java
and
src/main/java/org/jboss/ws/core/soap/SOAPFaultImpl.java
adding an "implements java.io.Serializable" to their class definition.
This helped me to avoid the NotSerializableException.

In the scenario the problem problem occurred, there are three apps involved.
The MS Axapta system as the WS-provider.
An EAR / EJB3 app as the WS-consumer.
And an standalone java app as the driver of this (unit test) calling the EJB3 session beans via their remote interface.

The WS provider gets an exception and send this to WS consumer using a SOAPFault.
The WS consumer does not catch the exception, so it has to be transferred to the client.
And as this is a remote client the SOAPFault has to serialized.
And there the Exception occurred while trying to send the SOAPFault from JBoss-Server to the standalone client app using serialization.


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

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


From do-not-reply at jboss.com  Thu Jun 11 12:39:08 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Thu, 11 Jun 2009 12:39:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS handlers
Message-ID: <29079665.1244738348875.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

It's JBossWS 3.1.1 native on JBoss 5.0.0.
I tired the JBoss with jdk 6 (copied jars to endorsed dir) and with jdk 5 but I get same issue.
I also tried with the 3.1.1 metro but I could not even deploy my web service to that one. The same webservice that worked with the native, did not work with metro !!

Thanks
Kamna

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

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


From do-not-reply at jboss.com  Thu Jun 11 13:06:45 2009
From: do-not-reply at jboss.com (lafr)
Date: Thu, 11 Jun 2009 13:06:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call WebService in EJB 3.0
	(Differences to EJB 2.1)
Message-ID: <7618858.1244740005903.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

You did not mention the JBoss version you are using.
We are using JBoss-4.2.4GA including jbossws-3.0.1-native-2.0.4.GA.

You can find out the service URIs by looking at http://Nebelos-C2Q:18080/jbossws/.

You can define the name of the service:
@WebService(serviceName = "WebServiceController")

The naming of parameters using @WebParam(name="...") works for us.
This might have to do with the JBoss/JBoss-WS version you're using 

P.S.: are you working for Cursor Software AG in Germany?


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

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


From do-not-reply at jboss.com  Thu Jun 11 14:43:33 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Thu, 11 Jun 2009 14:43:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS handlers
Message-ID: <323392.1244745813050.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

OK. so, it worked fine with the metro stack of jbossws (3.1.1)
Had to change the web service  a little but.

Thanks


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

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


From do-not-reply at jboss.com  Thu Jun 11 17:42:04 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Thu, 11 Jun 2009 17:42:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAXWS handlers
Message-ID: <23988903.1244756524710.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Seems to be working fine with Metro and CXF.
Still not working with the native :(

One thing I noticed is that the endorsed folder has the native jboss jars for jaxws, saaj etc. but the other two are not dependent on that.

Is this the problem? How can we override these jars and use the saaj-impl and saaj-api even with the native jbossws dist ?

Thanks


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

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


From do-not-reply at jboss.com  Thu Jun 11 21:35:55 2009
From: do-not-reply at jboss.com (kj_newbie)
Date: Thu, 11 Jun 2009 21:35:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - wsconsume ant task
Message-ID: <2886696.1244770555939.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hello,

I am getting the following error when using the wsconsume ant task:


  | taskdef class org.jboss.wsf.spi.tools.ant.WSConsumeTask cannot be found
  | 

This is my build.xml


  | <path id="class.path">
  | 		    <pathelement path="C:\Program Files\Java\jdk1.5.0_19\lib\tools.jar"/>
  | 		  	<pathelement path="E:\jboss\jboss-5.0.0.GA\client\streambuffer.jar"/>
  | 		    <pathelement path="E:\jboss\jboss-5.0.0.GA\client\stax-ex.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\saaj-api.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\saaj-impl.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\jbossws-common.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\jaxws-api.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\jaxws-tools.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\jaxws-rt.jar"/>
  | 		<pathelement path="E:\jboss\jboss-5.0.0.GA\client\xmlsec.jar"/>
  | 		    <pathelement path="E:\jboss\jboss-5.0.0.GA\client\*.jar"/>
  | 		    <pathelement path="E:\jboss\jboss-5.0.0.GA\lib\*.jar"/>
  | 		    <pathelement path="E:\jboss\jboss-5.0.0.GA\lib\endorsed\jaxb-api.jar"/>
  | 		    <pathelement path="E:\jboss\jboss-5.0.0.GA\lib\endorsed\activation.jar"/>
  | 	</path>
  | 	
  | 	<taskdef name="wsconsume" 
  | 					classname="org.jboss.wsf.spi.tools.ant.WSConsumeTask">
  | 		<classpath path="class.path"/>
  | 	</taskdef>
  | 		
  | 	
  | 	
  | 	<target name="generate-from-wsdl">
  | 	
  | 		<wsconsume
  | 			fork="true"
  | 			binding="wsdl/stock.xsd"
  | 		    keep="true"
  | 		    destdir="generated"
  | 		    sourcedestdir="gen-src"
  | 		    package="com.sun.samples"
  | 			wsdlLocation="/WEB-INF/wsdl/stockservice.wsdl"
  | 			wsdl="wsdl/stockservice.wsdl">			
  | 		</wsconsume>
  | 			
  | 	
  | 	</target>
  | 

Can anyone point out..what ma I missing ?

Thanks

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

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


From do-not-reply at jboss.com  Mon Jun 15 12:13:25 2009
From: do-not-reply at jboss.com (wwu)
Date: Mon, 15 Jun 2009 12:13:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - does jbossws-metro tests works on JBAS
	5.x ?
Message-ID: <12233834.1245082405776.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

hello,

I have tried on several Jboss server (5.0.0, 5.0.1, 5.1.0). with the 
latest release of jbossws-metro (3.1.1, 3.1.0), is seems that the tests have a very low success rate (less than 4%).

This is installation of jbossws-metro-3.1.0

It seems that Jboss is not able to find the Class java.lang.NoClassDefFoundError: com/sun/xml/ws/api/wsdl/writer/WSDLGeneratorExtension

this class belongs to jaxws-rt.jar. 
After the installation of jbossws-metro-3.1.0, this jar be found in the following place : 
<JBOSS_HOME>/client/jaxws-rt.jar
<JBOSS_HOME>/server/default/deployers/jbossws.deployer/jaxws-rt.jar

I tried to copy the jar from <JBOSS_HOME>/server/default/deployers/jbossws.deployer

running in verbose:class mode, I can see that the jar is loaded by the JBAS however I still get the same error message.

Does Jbossws-metro really support the 5.x trunk of Jboss as this page says
http://jbossws.jboss.org/mediawiki/index.php?title=Supported_Target_Containers  ???

thank you for your time and consideration


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

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


From do-not-reply at jboss.com  Mon Jun 15 13:04:10 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 15 Jun 2009 13:04:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: does jbossws-metro tests works on
	JBAS 5.x ?
Message-ID: <23482149.1245085450317.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Sure, 100% tests passing with all the supported target containers is a requirement for release.

I suspect you're suffering from a installation issue. Did you properly installed jbossws-metro using the ant deploy-jboss5xx target? Also double-check you don't have jbossws-native jars in the endorsed lib dir.


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

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


From do-not-reply at jboss.com  Tue Jun 16 04:03:26 2009
From: do-not-reply at jboss.com (wwu)
Date: Tue, 16 Jun 2009 04:03:26 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: does jbossws-metro tests works on
	JBAS 5.x ?
Message-ID: <29883555.1245139406257.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

true, my bald.
With your confirmation, I reinstall everything (jdk 1.5 / JBAS / jbossws-metro).
I had some library messing up with JBAS.

thank you for your quick reply

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

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


From do-not-reply at jboss.com  Tue Jun 16 05:48:56 2009
From: do-not-reply at jboss.com (kenshiro2000)
Date: Tue, 16 Jun 2009 05:48:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - C# fat client using Windows Integrated
	Authentication over W
Message-ID: <24591431.1245145736171.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I have a very complex architecture and I need some clarifications about the Windows Integrated Authentications and its capability.

I have fat C# client that needs to call an EJB3 in JBoss (on Linux) via WS. This is very easy to implement, but when I have to design the client authentication here is the problem. I don't want that my WS will be invoked by everyone!

I do not want the user re-insert their Windows logon credentials in their C# fat client, I think it is a big security issue because someone could rewrite a trojan fat client and logs all the users credentials!

So the question is how can I pass the Windows Principals over WS to JBoss and authenticate this Principals? Do I have to use JAAS and some PAM? is this possible in a JBoss on a Linux machine?

Some references could be very heplful for me.


P.S. this same post was posted in the MSDN forum. Sorry for the cross post but I need WS for interoperability so I think in this case cross-post should be allowed

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

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


From do-not-reply at jboss.com  Tue Jun 16 05:57:15 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 16 Jun 2009 05:57:15 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: C# fat client using Windows
	Integrated Authentication ov
Message-ID: <25016746.1245146235761.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

http://www.jboss.org/community/wiki/JBossWS-Authentication

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

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


From do-not-reply at jboss.com  Tue Jun 16 08:27:04 2009
From: do-not-reply at jboss.com (rhyali)
Date: Tue, 16 Jun 2009 08:27:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Binary attachment without WSDL parameter
Message-ID: <30416384.1245155224373.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

is it possible to attach random binary data as an additional attachment besides the usual SOAP request, without "mentioning" it in the WSDL?

So the service consumer sends a request to the provider (CRUD operations), and I now want to attach binary data, but can't/want to put this into the WSDL. The provider should then check if there are additional attachments and should be able to reference them.

As far as I understood, swaRef or MTOM+XOP aren't suitable for such a scenario.

Does someone have an idea how to achieve this with jbossWS?

Regards - Peter

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

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


From do-not-reply at jboss.com  Tue Jun 16 10:04:28 2009
From: do-not-reply at jboss.com (kenshiro2000)
Date: Tue, 16 Jun 2009 10:04:28 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: C# fat client using Windows
	Integrated Authentication ov
Message-ID: <4684180.1245161068378.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thanks Alessio. 

The link you sent me it will be very useful only for the Server side. As I wrote in my first post I don't want the user rewrite in the (Windows) client side their credentials. I would like to use the Windows logon Credentials e pass them to JBoss via WS.

I saw the Kerberos Token Profile 1.0 but as I can see there isn't any implementation for JBossWS. 

Am I making a mistake?

"alessio.soldano at jboss.com" wrote : http://www.jboss.org/community/wiki/JBossWS-Authentication

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

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


From do-not-reply at jboss.com  Tue Jun 16 17:57:00 2009
From: do-not-reply at jboss.com (jpredpos)
Date: Tue, 16 Jun 2009 17:57:00 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - ports
Message-ID: <19114843.1245189420688.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

hi, 

it `s possible to assing a port of a WS REST ?
I have 4 proyects and I need everyone in differents ports.

thanks!

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

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


From do-not-reply at jboss.com  Wed Jun 17 06:21:48 2009
From: do-not-reply at jboss.com (thomas2008ch)
Date: Wed, 17 Jun 2009 06:21:48 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - How to configure the wsdlLocation......
Message-ID: <10083274.1245234108214.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi all,

I programmed a WS and the WS-Client. I deployed both onto the same application server. This means they are local. From the client the web service can be access by "http://localhost:8080/myWS/myws?wsdl".

But now I have to deploy these onto an instance on another application server. Since this server has more than one instances, so I can't use the "http://localhost:8080/myWS/myws?wsdl" any more but somewhat like: "http://ip-address:8080/myWS/myws?wsdl"

My question: how can I configure the application server so that I can still use ""http://localhost:8080/myWS/myws?wsdl" from the client and the server will map this to "http://ip-address:8080/myWS/myws?wsdl"?

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

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


From do-not-reply at jboss.com  Wed Jun 17 07:55:56 2009
From: do-not-reply at jboss.com (Tashtego)
Date: Wed, 17 Jun 2009 07:55:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - SOAP request exception
	(SOAPFaultHelperJAXWS)
Message-ID: <1871218.1245239757005.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi.

I am using jboss-4.2.3.GA (will be extended through ESB 4.5 later, isnt yet configured). I developed some stateless session beans which were give the annotations @WebService and @WebMethod. After deploying to JBoss and testing my service with my own webService client on the server that runs jboss, it works correct.

But trying a .net client on another machine gives me an exception like following. Does anyone have any idea how to solve this? Thanks in advance.

anonymous wrote : 
  | 13:46:06,765 ERROR [SOAPFaultHelperJAXWS] 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.(SOAPMessageImpl.java:83)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:217)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:195)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:447)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	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:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	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:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Unknown Source)
  | 13:46:06,765 ERROR [RequestHandlerImpl] Error processing web service request
  | org.jboss.ws.WSException: java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at org.jboss.ws.WSException.rethrow(WSException.java:68)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:325)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	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:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	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:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Unknown Source)
  | Caused by: 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.(SOAPMessageImpl.java:83)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:174)
  | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
  | 	at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:488)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	... 22 more
  | 13:46:06,796 ERROR [[PersonActions]] Servlet.service() for servlet PersonActions threw 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.(SOAPMessageImpl.java:83)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:171)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:174)
  | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104)
  | 	at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:488)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	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:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	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:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
  | 	at java.lang.Thread.run(Unknown Source)
  | 
  | 

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

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


From do-not-reply at jboss.com  Wed Jun 17 13:10:58 2009
From: do-not-reply at jboss.com (kyle.bober)
Date: Wed, 17 Jun 2009 13:10:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss 4.2.1 and Apache CXF 2.2.2 Client
	Code and AsyncHandle
Message-ID: <31479472.1245258658617.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

 I have implemented an Asynchronous web service call using the Call back
 approach via an AsyncHandler. I have noticed an issue where the remote web
 service is throwing a SOAPFaultException. The issue is the AsynHandler code
 I wrote does not seem to catch the exception. In fact it never receives a
 response at all. I am using Apache CXF 2.1.2 to generate the client side
 code

 How do I handle this accordingly???

 Here is the code making the Asynchronous request ::

 // Asynchronous WS callback approach
 ServiceAsyncHandler serviceAsyncHandler = new
 ServiceAsyncHandler(aSomeObject1, aSomeObject2);
 Future<?> response = thePort.getAnalysisAsync(criteria,
 serviceAsyncHandler);

 Here is the AsyncHandler code ::

 /**
  * Aysynchronous KATDataService Handler
  */
 public void handleResponse(Response response) {
      try {
               Object object = response.get();
               this.analysis = (Analysis)object;

                 // Do some processing here on the response

               } catch(SOAPFaultException ex) {
                       LOGGER.error("ERROR : KATDataServiceAsyncHandler", ex);
               } catch (InterruptedException ex) {
                       LOGGER.error("ERROR : KATDataServiceAsyncHandler", ex);
               } catch (ExecutionException ex) {
                       LOGGER.error("ERROR : KATDataServiceAsyncHandler", ex);
               }
       }
 }

 It also seems if I place a snippet of code after I make the Asynchronous
 web service request like so ::

 try {
      response.isDone()
 } catch(SOAPFaultException ex) {
      LOGGER.error("ERROR : Calling Remote Web Service", ex);
 }

 It will catch the SOAPFaultExcpetion occasionally but not all the time so
 this is not 100% reliable. I still have an issue where the
 SOAPFaultExcpetion falls through the cracks and is not caught by either the
 AsynchHandler or the code making the Asynchronous web service call.

 Please can someone explain why this is and how I go about resolving this
 issue.

 -Kyle

13:03:04,062 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation: 
javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> TSAKeywordAnalysisServices.katAnalysisException: KAT Data Service Exception:  ---> System.Exception: Target Page URL did not have any data.
   at clsDataService.getKATAnalysis(KATAnalysisCriteria request) in c:\Hudson\jobs\KAT Data Service\workspace\main\App_Code\clsDataService.cs:line 70
   at KATDataService10.getKATAnalysis(KATAnalysisCriteria request) in c:\Hudson\jobs\KAT Data Service\workspace\main\App_Code\KATDataService1.0.cs:line 27
   --- End of inner exception stack trace ---
   at KATDataService10.getKATAnalysis(KATAnalysisCriteria request) in c:\Hudson\jobs\KAT Data Service\workspace\main\App_Code\KATDataService1.0.cs:line 32
   --- End of inner exception stack trace ---
	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	at org.jboss.ws.core.jaxws.client.ClientProxy.access$000(ClientProxy.java:60)
	at org.jboss.ws.core.jaxws.client.ClientProxy$AsyncRunnable.run(ClientProxy.java:260)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)
13:03:04,062 ERROR [ClientProxy] Cannot dispatch message
javax.xml.ws.soap.SOAPFaultException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> TSAKeywordAnalysisServices.katAnalysisException: KAT Data Service Exception:  ---> System.Exception: Target Page URL did not have any data.
   at clsDataService.getKATAnalysis(KATAnalysisCriteria request) in c:\Hudson\jobs\KAT Data Service\workspace\main\App_Code\clsDataService.cs:line 70
   at KATDataService10.getKATAnalysis(KATAnalysisCriteria request) in c:\Hudson\jobs\KAT Data Service\workspace\main\App_Code\KATDataService1.0.cs:line 27
   --- End of inner exception stack trace ---
   at KATDataService10.getKATAnalysis(KATAnalysisCriteria request) in c:\Hudson\jobs\KAT Data Service\workspace\main\App_Code\KATDataService1.0.cs:line 32
   --- End of inner exception stack trace ---
	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
	at org.jboss.ws.core.jaxws.client.ClientProxy.access$000(ClientProxy.java:60)
	at org.jboss.ws.core.jaxws.client.ClientProxy$AsyncRunnable.run(ClientProxy.java:260)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
	at java.util.concurrent.FutureTask.run(FutureTask.java:123)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
	at java.lang.Thread.run(Thread.java:595)


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

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


From do-not-reply at jboss.com  Wed Jun 17 13:17:33 2009
From: do-not-reply at jboss.com (kyle.bober)
Date: Wed, 17 Jun 2009 13:17:33 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Achieving asynchronous
	communications
Message-ID: <23284993.1245259053451.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Did you have any luck in reaching a conclusion. I am currently using JBoss 4.2.1 to make asynchronous web service calls to a .NET webservice. We used Apache CXF 2.2.2 to generate the client side code and are using the callback handler approach. I can make a successful call to the webserivce and recieve a valid response successfully. But if we recieve a Web Service Fault from the .NET service it fall through the cracks and is not caught by our application code.

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

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


From koxkorrita at laudio.info  Wed Jun 17 16:08:47 2009
From: koxkorrita at laudio.info (Koxkorrita)
Date: Wed, 17 Jun 2009 22:08:47 +0200
Subject: [jbossws-users] Exception in thread "main"
	javax.xml.ws.WebServiceException: No Content-type in the header!
Message-ID: <000601c9ef87$6cf1a910$46d4fb30$@info>

Hello

i have made one webservice for deploing into my jbosss using jaxws and also
i have made  one client for this.

 

when i execute the client appears this error:

 

Exception in thread "main" javax.xml.ws.WebServiceException: No Content-type
in the header!

      at
com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransport
Pipe.java:163)

      at com.sun.xml.xwss.XWSSClientPipe.process(XWSSClientPipe.java:118)

      at
com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:1
15)

      at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)

      at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)

      at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)

      at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)

      at com.sun.xml.ws.client.Stub.process(Stub.java:248)

      at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)

      at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:10
9)

      at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89
)

      at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)

      at $Proxy34.getLineasDeSubvencionRequest(Unknown Source)

      at EkirolTramitacionWSCliente.main(EkirolTramitacionWSCliente.java:35)

 

 

the code of the client is:

            ServicioWS service = new ServicioWS();

              Servicio portType = service.getServicioPort();

              LineasRequestType p = new LineasRequestType();

              p.setCodigo("entidad");

              p.setDescripcion("la desc");

              

portType.getLineasRequest(p);

 

can you help me?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090617/76bde491/attachment.html 

From do-not-reply at jboss.com  Thu Jun 18 05:08:38 2009
From: do-not-reply at jboss.com (rhyali)
Date: Thu, 18 Jun 2009 05:08:38 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Binary attachment without WSDL
	parameter
Message-ID: <31613039.1245316118491.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

If it is not possible with JBossWS, is it probably achievable with SAAJ?

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

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


From do-not-reply at jboss.com  Thu Jun 18 05:15:34 2009
From: do-not-reply at jboss.com (prakash_jboss)
Date: Thu, 18 Jun 2009 05:15:34 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Handling empty HTTP POST in JAX-WS
Message-ID: <4056404.1245316534490.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi All,

I want to respond to an Empty HTTP POST (with out any body) from my JAX-WS web service.
I tried adding handlers (both Logical and SOAP handlers). But the server throws exception and the handlers were NOT called.

10:49:04,790 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.core.CommonSOAPFaultException: Endpoint {http://acs.mobax.com/}ACSPort does not contain operation meta data for empty soap body

I want to handle the request at the HTTP level itself.
Any suggestion would be really helpful to me.

Thanks and Best Regards,
Prakash

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

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


From mathivanan.t at gmail.com  Thu Jun 18 05:56:56 2009
From: mathivanan.t at gmail.com (Mathi)
Date: Thu, 18 Jun 2009 11:56:56 +0200
Subject: [jbossws-users] 
	java.lang.ClassCastException: org.jboss.ws.core.soap.
	SOAPMessageImpl
Message-ID: <163ab6c60906180256l30c7cb56uf6b56e04edbda7aa@mail.gmail.com>

Hi All,
I am new to webservice..
I have created client webservice (java classes using wscompile tool) to
access the webservice (http://....?wsdl) and get theexchangerates.
 when i execute the client webservice.. i get the following exception



  java.lang.ClassCastException: org.jboss.ws.core.soap.SOAPMessageImpl
       at
com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:248)
       at
com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:341)
       at
com.acer.emb.webservice.client.test.MNBArfolyamServiceSoap_Stub.getCurrentExchangeRates(MNBArfolyamServiceSoap_Stub.java:83)
       at
com.acer.emb.webservice.client.test.HungaryExchangeRateStub.main(HungaryExchangeRateStub.java:12)


I would be grateful, if u guys give me suggestions/guidance..



  thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090618/da29830c/attachment.html 

From do-not-reply at jboss.com  Thu Jun 18 07:57:24 2009
From: do-not-reply at jboss.com (Tashtego)
Date: Thu, 18 Jun 2009 07:57:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SOAP request exception
	(SOAPFaultHelperJAXWS)
Message-ID: <27761798.1245326244867.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)

RMI works, SOAP fails. Could need help with this one ;( I read it may be a way to copy files from jboss into its endorsed directory so that it overrides my JavaSE 6 version installed ?

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

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


From do-not-reply at jboss.com  Thu Jun 18 09:02:35 2009
From: do-not-reply at jboss.com (Tashtego)
Date: Thu, 18 Jun 2009 09:02:35 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SOAP request exception
	(SOAPFaultHelperJAXWS)
Message-ID: <18870634.1245330155061.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

http://www.mail-archive.com/cxf-user at incubator.apache.org/msg03493.html

?

anything true about that?

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

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


From do-not-reply at jboss.com  Thu Jun 18 10:00:53 2009
From: do-not-reply at jboss.com (Tashtego)
Date: Thu, 18 Jun 2009 10:00:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: SOAP request exception
	(SOAPFaultHelperJAXWS)
Message-ID: <3744162.1245333653299.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

The file jboss-saaj.jar must be copied from \\jboss-4.2.3.GA\lib to \\jboss-4.2.3.GA\lib\endorsed. Problem solved.

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

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


From do-not-reply at jboss.com  Thu Jun 18 07:36:39 2009
From: do-not-reply at jboss.com (amitru)
Date: Thu, 18 Jun 2009 07:36:39 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - two services in one jboss instance with
	different soap:addre
Message-ID: <22718027.1245324999502.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

hi, 

I am using jboss4.2.3 GA/java 1.5 and my requirement is to deploy two different services in one jboss instance, but the two services should have different soap:address. 

Right now the soap:address is being dervied from jboss-bean.xml's webServerHost...etc settings. 

Could any one help me on this.

Thanks,
Amit

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

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


From koxkorrita at laudio.info  Sat Jun 20 05:24:24 2009
From: koxkorrita at laudio.info (Koxkorrita)
Date: Sat, 20 Jun 2009 11:24:24 +0200
Subject: [jbossws-users] Exception in thread "main"
	javax.xml.ws.WebServiceException: No Content-type in the header!
Message-ID: <002801c9f188$e6b5a500$b420ef00$@info>

Hello
i have made one webservice for deploing into my jbosss using jaxws and also
i have made  one client for this.

when i execute the client appears this error:

Exception in thread "main" javax.xml.ws.WebServiceException: No Content-type
in the header!
      at
com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransport
Pipe.java:163)
      at com.sun.xml.xwss.XWSSClientPipe.process(XWSSClientPipe.java:118)
      at
com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:1
15)
      at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
      at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
      at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
      at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
      at com.sun.xml.ws.client.Stub.process(Stub.java:248)
      at com.sun.xml.ws.client.sei.SEIStub.doProcess(SEIStub.java:135)
      at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:10
9)
      at
com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89
)
      at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118)
      at $Proxy34.getLineasDeSubvencionRequest(Unknown Source)
      at EkirolTramitacionWSCliente.main(EkirolTramitacionWSCliente.java:35)


the code of the client is:
            ServicioWS service = new ServicioWS();
              Servicio portType = service.getServicioPort();
              LineasRequestType p = new LineasRequestType();
              p.setCodigo("entidad");
              p.setDescripcion("la desc");
              
portType.getLineasRequest(p);

can you help me?




From do-not-reply at jboss.com  Sat Jun 20 11:55:50 2009
From: do-not-reply at jboss.com (donakalz)
Date: Sat, 20 Jun 2009 11:55:50 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem creating SOAP Envelop (Android
	Client using Seam Web
Message-ID: <26708777.1245513350760.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi Guys,

I am trying to connect to webservices in jboss(using seam) from a google android phone. So far, I implemented all the necessary beans and android classes. Unfortunately, I am getting an exception on the server side after the request is dispatched from the android emulator, java.lang.IllegalArgumentException: Cannot create SOAP envelope from: methodCall. I have tried everything I can but to no success. On the other hand, when I try to connect to the service from SOAP UI, everything works great. Please if you have any clue, help! Thanks a lot in advance. 

Interface

  | 
  | package de.iu.soko.web.webservice;
  | 
  | import javax.ejb.Remote;
  | 
  | 
  | @Remote
  | public interface SokoServiceRemote {
  | 	
  | 	
  | 	public String hello();
  | }
  | 


Stateless Web Service Facade

  | 
  | package de.iu.soko.web.webservice;
  | 
  | import javax.ejb.Stateless;
  | import javax.jws.WebMethod;
  | import javax.jws.WebService;
  | import javax.jws.soap.SOAPBinding;
  | import org.jboss.seam.annotations.In;
  | import org.jboss.seam.annotations.Name;
  | import org.jboss.seam.contexts.Contexts;
  | import org.jboss.seam.security.Identity;
  | 
  | @Stateless
  | @WebService(name = "SokoService", serviceName = "SokoService")
  | @SOAPBinding(style = SOAPBinding.Style.RPC)
  | @Name("sokoServiceCallHandler")
  | public class SokoService implements SokoServiceRemote {
  | 
  | 	@Logger
  | 	private Log log;
  | 	
  | 	@In(required=true)
  | 	Identity identity;
  | 
  | 	
  | 	
  | 	@WebMethod
  | 	public String hello(){
  | 		
  | 		return "Hello from a seam component";
  | 	}
  | }
  | 
  | 



standard-ws-config xml file

  | 
  | <jaxws-config xmlns="urn:jboss:jaxws-config:2.0"
  | 
  | 	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:javaee="http://java.sun.com/xml/ns/javaee"
  | 
  | 	xsi:schemaLocation="urn:jboss:jaxws-config:2.0 jaxws-config_2_0.xsd">
  | 
  | 	<endpoint-config>
  | 
  | 		<config-name>Seam WebService Endpoint</config-name>
  | 
  | 		<pre-handler-chains>
  | 
  | 			<javaee:handler-chain>
  | 
  | 				<javaee:protocol-bindings>##SOAP11_HTTP
  | 				</javaee:protocol-bindings>
  | 
  | 				<javaee:handler>
  | 
  | 					<javaee:handler-name>SOAP Request Handler</javaee:handler-name>
  | 
  | 					<javaee:handler-class>org.jboss.seam.webservice.SOAPRequestHandler
  | 					</javaee:handler-class>
  | 
  | 				</javaee:handler>
  | 
  | 			</javaee:handler-chain>
  | 
  | 		</pre-handler-chains>
  | 
  | 	</endpoint-config>
  | 
  | </jaxws-config>
  | 
  | 




entries in web.xml


  | 
  | <filter>
  |      <filter-name>Seam Context Filter</filter-name>
  |      <filter-class>org.jboss.seam.web.ContextFilter</filter-class>
  |   </filter>
  | 
  |   <filter-mapping>
  |      <filter-name>Seam Context Filter</filter-name>
  |      <url-pattern>/test</url-pattern>        
  |   </filter-mapping>
  | 
  | 
  | 
  | <servlet-mapping>
  |   <servlet-name>AndroidService</servlet-name>
  |   <url-pattern>/androidService</url-pattern>
  |  </servlet-mapping>
  |  <servlet>
  |   <servlet-name>AndroidService</servlet-name>
  |   <servlet-class>de.iu.soko.web.webservice.SokoService</servlet-class>
  |  </servlet>
  | 





SOAP UI request

  | POST http://sylar:8080/soko-web/androidService?wsdl HTTP/1.1
  | Content-Type: text/xml;charset=UTF-8
  | SOAPAction: ""
  | User-Agent: Jakarta Commons-HttpClient/3.1
  | Host: sylar:8080
  | Content-Length: 219
  | 
  | <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:web="http://webservice.web.soko.iu.de/">
  |    <soapenv:Header/>
  |    <soapenv:Body>
  |       <web:hello/>
  |    </soapenv:Body>
  | </soapenv:Envelope>
  | 
  | 




SOAP UI Response

  | <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  |    <env:Header>
  |       <seam:conversationId xmlns:seam="http://www.jboss.org/seam/webservice">21</seam:conversationId>
  |    </env:Header>
  |    <env:Body>
  |       <web:helloResponse xmlns:web="http://webservice.web.soko.iu.de/">
  |          <return>Hello from a seam component</return>
  |       </web:helloResponse>
  |    </env:Body>
  | </env:Envelope>
  | 
  | 



The Exception

  | 
  | java.lang.IllegalArgumentException: Cannot create SOAP envelope from: methodCall
  | 	at org.jboss.ws.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:70)
  | 	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:124)
  | 	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:96)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:262)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:185)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:389)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122)
  | 	at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
  | 	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:230)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
  | 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Thread.java:595)
  | 
  | 

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

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


From do-not-reply at jboss.com  Sun Jun 21 20:28:17 2009
From: do-not-reply at jboss.com (saul_bull)
Date: Sun, 21 Jun 2009 20:28:17 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAX-WS from Sessions Bean fails due
	to missing org/jboss
Message-ID: <11963822.1245630497345.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

aaahola que tal

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

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


From do-not-reply at jboss.com  Sun Jun 21 20:36:01 2009
From: do-not-reply at jboss.com (saul_bull)
Date: Sun, 21 Jun 2009 20:36:01 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JAX-WS from Sessions Bean fails due
	to missing org/jboss
Message-ID: <29638397.1245630961640.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

aqa

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

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


From do-not-reply at jboss.com  Mon Jun 22 07:30:43 2009
From: do-not-reply at jboss.com (bjoern83)
Date: Mon, 22 Jun 2009 07:30:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Call WebService in EJB 3.0
	(Differences to EJB 2.1)
Message-ID: <31169876.1245670243222.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I use JBoss 4.2.2a.
The problem was already solved by using the @WebContext and @WebParam annotations. The problem was, that @WebParam can not be used if the interfaces are generated. Therefore they are hard coded now. 

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

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


From do-not-reply at jboss.com  Mon Jun 22 10:08:10 2009
From: do-not-reply at jboss.com (germanescobar)
Date: Mon, 22 Jun 2009 10:08:10 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Jboss 4.2.3 Virtual Host Configuration
Message-ID: <25345727.1245679690542.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I'm trying to configure a Web Service on a virtual host using the @WebContext annotation. However, I know that there is an issue "JBWS-981 Virtual Host configuration for EJB endpoints" that ignores the virtualHosts parameter of the @WebContext annotation. This is fixed in JBossWS native 3.0.3 and JBoss 5.

I would like to know if there is some workaround to configure the virtual host in JBoss 4.2.3. I updated to JBossWS 3.0.3 but no success. Maybe with some XML configuration instead of the annotation?

Thank you!

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

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


From do-not-reply at jboss.com  Mon Jun 22 09:56:09 2009
From: do-not-reply at jboss.com (thorsten-schmid@web.de)
Date: Mon, 22 Jun 2009 09:56:09 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Connect- and read-timeout properties
	for JBossWS-Native
Message-ID: <12743482.1245678969675.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Does anyone know the names of the properties for setting the 

1. connect-timeout and the 
2. read-timeout

for a JBossWS-Native client?

I found several properties for the read-timeout, e.g. on http://jbossws.jboss.org/mediawiki/index.php/JAX-RPC_User_Guide 

  |    /** ClientTimeout property: org.jboss.ws.timeout */
  |    static final String PROPERTY_CLIENT_TIMEOUT = "org.jboss.ws.timeout";

With this property the read-timeout can be set in the following way:

   bindingProvider.getRequestContext().put("org.jboss.ws.timeout", new Integer(1000));

Besides this property I found "org.jboss.webservice.client.timeout" and "org.jboss.webservice.timeout" in the internet.

Which property name is the correct one for setting the read-timeout and which is the correct one for a connect-timeout?

Currently we are using JBossAS Version 4.3.0_eap_cp02.

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

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


From do-not-reply at jboss.com  Mon Jun 22 15:11:07 2009
From: do-not-reply at jboss.com (klowtherjr)
Date: Mon, 22 Jun 2009 15:11:07 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Cannot find child element: parameters
Message-ID: <4079421.1245697867888.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi all,

I'm working with wsdl2java generated classes making an rpc call in JBoss 4.2.3 to a WSDL on another platform.
This seems to work fine until the response comes back to the client.  The response comes back as follows.


  | <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  |    <soapenv:Body>
  |       <wmscr:SubmitPirepResponse xsi:schemaLocation="urn:faa:nas:wmscr:1:0 SubmitPirep.xsd" xmlns:aw="urn:faa:nas:swim:aviationwx:1:0" xmlns:swim="urn:bhmi:wmscr:swim:1:0" xmlns:wmscr="urn:faa:nas:wmscr:1:0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  |    </soapenv:Body>
  | </soapenv:Envelope>
  | 

My client errors out with the following message that I'll truncate to keep the post short(er):

Exception Stack Trace:javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Cannot find child element: parameters
	at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
... (truncated here)
Caused by: org.jboss.ws.WSException: Cannot find child element: parameters
	at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:917)
	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634)
	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380)
	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
	... 105 more
(truncated here as well)

This indicates to me that the response is not sending a  tag when the client clearly expects it.
I can see a  tag in the inbound request when the request gets to the web service.  My question is where does the requirement for this tag come from (SOAP?, JAXB?).
I cannot find a mention of it anywhere in any of the specs I've been looking at.  It's probably right in front of my face and I'm just not seeing it.

Thank you for any light you can shed on this issue.

Ken

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

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


From do-not-reply at jboss.com  Mon Jun 22 16:12:08 2009
From: do-not-reply at jboss.com (klowtherjr)
Date: Mon, 22 Jun 2009 16:12:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Cannot find child element:
	parameters
Message-ID: <839935.1245701528570.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

All,

It appears this is a SOAP-specific requirement dealing with RPC.  My understanding is that this is described in section 7 of the SOAP specification.

Thanks,

Ken

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

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


From do-not-reply at jboss.com  Tue Jun 23 00:20:43 2009
From: do-not-reply at jboss.com (Semaphore_ham)
Date: Tue, 23 Jun 2009 00:20:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - non-HTTP request or response:
	xfire-WebService (jsr181) in J
Message-ID: <24684752.1245730843774.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi all,

i'm running a xfire-based WS in JBoss-4.2.2-GA without any problems, but when i've deployed this WS into JBoss-5.1.0 and try to connect to it using
http://myservername.mydomain.org.8080/MyWebService/services/MyWebService?wsdl, than i always get an exception:

18:47:27,234 ERROR [[XFireServlet]] Servlet.service() for servlet XFireServlet threw exception
javax.servlet.ServletException: non-HTTP request or response

The full background including the implementation:

##################################
Web.xml:
##################################

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
  <display-name>ZuluWebServiceWeb</display-name>
  <context-param>
      <param-name>contextConfigLocation</param-name>
      <param-value>/WEB-INF/applicationContext.xml classpath:org/codehaus/xfire/spring/xfire.xml</param-value>
  </context-param>
  
     <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
    
  
    <servlet-name>XFireServlet</servlet-name>
    <display-name>XFire Servlet</display-name>
    <servlet-class>
        org.codehaus.xfire.spring.XFireSpringServlet
    </servlet-class>
  
  
	<servlet-name>context</servlet-name>
	<servlet-class>org.springframework.web.context.ContextLoaderServlet</servlet-class>
	<load-on-startup>1</load-on-startup>
  
    
        <servlet-name>xfire</servlet-name>
        <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
    
   <servlet-mapping>
        <servlet-name>xfire</servlet-name>
        <url-pattern>/*</url-pattern>
   </servlet-mapping>
  <servlet-mapping>
    <servlet-name>XFireServlet</servlet-name>
    <url-pattern>/servlet/XFireServlet/*</url-pattern>
  </servlet-mapping>
  <servlet-mapping>
    <servlet-name>XFireServlet</servlet-name>
    <url-pattern>/services/*</url-pattern>
  </servlet-mapping>
</web-app>


##################################
applicationContext.xml: (the key-words have been shortened, because of filtering of them here in the forum)
##################################

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE beans PUBLIC "-//SPRING//DTD BEAN//EN" "http://www.springframework.org/dtd/spring-beans.dtd">
<b.ns>
	
	<b.n id="webAnnotations" class="org.codehaus.xfire.annotations.jsr181.Jsr181WebAnnotations"/>
	<b.n id="handlerMapping" class="org.codehaus.xfire.spring.remoting.Jsr181HandlerMapping">
		<pr.prty name="typeMappingRegistry" ref="xfire.typeMappingRegistry" />
		<pr.prty name="xfire" ref="xfire" />
  		<pr.prty name="webAnnotations" ref="webAnnotations" />
	</b.n>
	<b.n class="org.springframework.web.servlet.handler.SimpleUrlHandlerMapping">
  		<pr.prty name="urlMap">
    		<m.p>
		    	<e..try key="/">
        			<ref b.n="handlerMapping"/>
      			</e..try>
    		</m.p>
  		</pr.prty>
	</b.n>
	<b.n id="myWebService" class="com.mycomp.myservices.spring.service.MyWebServiceImpl"/>
</b.ns>

##################################
MyWebServiceImpl:
##################################

package com.mycomp.myservices.spring.service;

import java.io.UnsupportedEncodingException;

import javax.jws.WebService;

import org.apache.log4j.Logger;

import com.mycomp.myservices.security.MyBlowfishCryptoEngine;
import com.mycomp.myservices.spring.bean.MyWebService;
import com.mycomp.myservices.spring.bean.MyWebServiceQueryContainer;

@WebService(name = "MyWebService", serviceName = "MyWebService", endpointInterface="com.mycomp.myservices.spring.service.MyWebServiceInterface")
public class MyWebServiceImpl implements MyWebServiceInterface {

##################################
MyWebService:
##################################

package com.mycomp.myservices.spring.service;

import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;

import com.mycomp.myservices.spring.bean.MyWebServiceContainer;

@WebService(name = "MyWebService", targetNamespace = "http://service.spring.myservices.mycomp.com")
public interface MyWebServiceInterface {
    @WebMethod(operationName = "getMyWebServiceContainer")
    @WebResult(name="myWebServiceContainer")
	public MyWebServiceContainer getMyWebServiceContainer(@WebParam(name = "userId")String userId, @WebParam(name = "customer")String customer, @WebParam(name = "appId")String appId, 
			@WebParam(name = "token")String token) throws Exception;
    
	public void setMyWebServiceContainer(@WebParam(name = "MyWebServiceContainer")MyWebServiceContainer container);
	public MyWebServiceContainer getMyWebServiceContainer();
	public void setMyWebServiceContainer(@WebParam(name = "MyWebServiceContainer")MyWebServiceContainer myWebServiceContainer);
}

##################################
MyWebServiceWebServiceConnector:
##################################
package com.mycomp.myservices.client;

import java.util.ArrayList;
import java.util.HashMap;

import org.apache.log4j.Logger;
import org.codehaus.xfire.annotations.AnnotationServiceFactory;
import org.codehaus.xfire.client.XFireProxyFactory;
import org.codehaus.xfire.service.Service;

import com.mycomp.myservices.auth.model.MyWebServiceModelListContainer;
import com.mycomp.myservices.constants.MyWebServiceLDAPConstants;
import com.mycomp.myservices.db.model.MyWebServiceAuthModel;
import com.mycomp.myservices.spring.bean.MyWebServiceContainer;
import com.mycomp.myservices.spring.bean.MyWebServiceAuthModelSingleList;
import com.mycomp.myservices.spring.bean.MyWebServiceListAttribute;
import com.mycomp.myservices.spring.bean.MyWebServiceSingleAttribute;
import com.mycomp.myservices.spring.service.MyWebServiceInterface;

public class MyWebServiceWebServiceConnector {
	
	public MyWebServiceConnector() {}

	private MyWebServiceSingleAttribute[] myWebServiceSingleAttribute;
	private MyWebServiceListAttribute[] myWebServiceListAttribute;
	private MyWebServiceAuthModelSingleList[] myWebServiceAuthModelSingleList;
	private HashMap userMap = new HashMap();
	
	private static Logger logger = Logger.getLogger(MyWebServiceConnector.class);

	
	public HashMap getMyWebServiceFromWebService(String uid, String customer, String appId, String token, String webserviceURL) {
		try {
			final Service model = new AnnotationServiceFactory().create(MyWebServiceInterface.class);
			final MyWebServiceInterface service = (MyWebServiceInterface)new XFireProxyFactory().create(model, webserviceURL);
			...
			...
			...
			

##################################
Full startup log:
##################################


18:44:56,625 INFO  [ServerImpl] Starting JBoss (Microcontainer)...
18:44:56,625 INFO  [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)
18:44:56,625 INFO  [ServerImpl] Bootstrap URL: null
18:44:56,625 INFO  [ServerImpl] Home Dir: C:\Programme\jboss-5.1.0.GA
18:44:56,625 INFO  [ServerImpl] Home URL: file:/C:/Programme/jboss-5.1.0.GA/
18:44:56,625 INFO  [ServerImpl] Library URL: file:/C:/Programme/jboss-5.1.0.GA/lib/
18:44:56,625 INFO  [ServerImpl] Patch URL: null
18:44:56,625 INFO  [ServerImpl] Common Base URL: file:/C:/Programme/jboss-5.1.0.GA/common/
18:44:56,625 INFO  [ServerImpl] Common Library URL: file:/C:/Programme/jboss-5.1.0.GA/common/lib/
18:44:56,625 INFO  [ServerImpl] Server Name: default
18:44:56,625 INFO  [ServerImpl] Server Base Dir: C:\Programme\jboss-5.1.0.GA\server
18:44:56,625 INFO  [ServerImpl] Server Base URL: file:/C:/Programme/jboss-5.1.0.GA/server/
18:44:56,625 INFO  [ServerImpl] Server Config URL: file:/C:/Programme/jboss-5.1.0.GA/server/default/conf/
18:44:56,625 INFO  [ServerImpl] Server Home Dir: C:\Programme\jboss-5.1.0.GA\server\default
18:44:56,625 INFO  [ServerImpl] Server Home URL: file:/C:/Programme/jboss-5.1.0.GA/server/default/
18:44:56,625 INFO  [ServerImpl] Server Data Dir: C:\Programme\jboss-5.1.0.GA\server\default\data
18:44:56,625 INFO  [ServerImpl] Server Library URL: file:/C:/Programme/jboss-5.1.0.GA/server/default/lib/
18:44:56,625 INFO  [ServerImpl] Server Log Dir: C:\Programme\jboss-5.1.0.GA\server\default\log
18:44:56,625 INFO  [ServerImpl] Server Native Dir: C:\Programme\jboss-5.1.0.GA\server\default\tmp\native
18:44:56,625 INFO  [ServerImpl] Server Temp Dir: C:\Programme\jboss-5.1.0.GA\server\default\tmp
18:44:56,625 INFO  [ServerImpl] Server Temp Deploy Dir: C:\Programme\jboss-5.1.0.GA\server\default\tmp\deploy
18:44:57,203 INFO  [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/Programme/jboss-5.1.0.GA/server/default/conf/bootstrap.xml
18:44:57,859 INFO  [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
18:44:57,859 INFO  [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
18:44:58,140 INFO  [CopyMechanism] VFS temp dir: C:\Programme\jboss-5.1.0.GA\server\default\tmp
18:44:58,187 INFO  [ZipEntryContext] VFS force nested jars copy-mode is enabled.
18:44:59,078 INFO  [ServerInfo] Java version: 1.6.0_14,Sun Microsystems Inc.
18:44:59,078 INFO  [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
18:44:59,078 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Client VM 14.0-b16,Sun Microsystems Inc.
18:44:59,078 INFO  [ServerInfo] OS-System: Windows XP 5.1,x86
18:44:59,078 INFO  [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms128m -Xmx512m -XX:MaxPermSize=256m -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:2112 
18:44:59,125 INFO  [JMXKernel] Legacy JMX core initialized
18:45:00,656 INFO  [ProfileServiceBootstrap] Loading profile: ProfileKey at 14ffc5[domain=default, server=default, name=default]
18:45:02,234 INFO  [WebService] Using RMI server codebase: http://127.0.0.1:8083/
18:45:07,765 INFO  [NativeServerConfig] JBoss Web Services - Stack Native Core
18:45:07,765 INFO  [NativeServerConfig] 3.1.2.GA
18:45:08,281 INFO  [AttributeCallbackItem] Owner callback not implemented.
18:45:09,796 INFO  [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl at 181c4a1[ defaultDomain='jboss' ]
18:45:32,687 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 30323935{vfsfile:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
18:45:32,687 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 30323935{vfsfile:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
18:45:32,687 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 30323935{vfsfile:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
18:45:32,687 INFO  [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext at 30323935{vfsfile:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/profileservice-secured.jar/}
18:45:35,453 INFO  [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
18:45:35,640 INFO  [MailService] Mail Service bound to java:/Mail
18:46:09,953 WARN  [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
18:46:09,968 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
18:46:10,125 WARN  [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
18:46:10,203 INFO  [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA) - JBoss Inc.
18:46:10,203 INFO  [TransactionManagerService] Setting up property manager MBean and JMX layer
18:46:10,593 INFO  [TransactionManagerService] Initializing recovery manager
18:46:10,937 INFO  [TransactionManagerService] Recovery manager configured
18:46:10,937 INFO  [TransactionManagerService] Binding TransactionManager JNDI Reference
18:46:11,000 INFO  [TransactionManagerService] Starting transaction recovery manager
18:46:11,781 INFO  [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Programme\Java\jre6\bin;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Programme\Java\jre6\bin\client;C:\Programme\Java\jre6\bin;C:\Programme\Oracle\product\10.2.0\client_1\bin;C:\Programme\Oracle\bin;c:\windows\system32;c:\Programme\Oracle\product\10.2.0\client_1;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH;C:\Programme\QuickTime\QTSystem\;C:\Programme\Gemeinsame Dateien\DivX Shared\;C:\Programme\IDM Computer Solutions\UltraEdit\;C:\Programme\SSH Communications Security\SSH Secure Shell
18:46:11,875 INFO  [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
18:46:11,875 INFO  [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
18:46:11,921 INFO  [StandardService] Starting service jboss.web
18:46:11,921 INFO  [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.3.GA
18:46:12,031 INFO  [Catalina] Server startup in 158 ms
18:46:12,062 INFO  [TomcatDeployment] deploy, ctxPath=/invoker
18:46:13,609 INFO  [TomcatDeployment] deploy, ctxPath=/web-console
18:46:14,203 INFO  [TomcatDeployment] deploy, ctxPath=/jbossws
18:46:14,359 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
18:46:14,375 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
18:46:14,406 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
18:46:14,421 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
18:46:14,437 INFO  [RARDeployment] Required license terms exist, view vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
18:46:14,593 INFO  [SimpleThreadPool] Job execution threads will use class loader of thread: main
18:46:14,640 INFO  [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
18:46:14,640 INFO  [RAMJobStore] RAMJobStore initialized.
18:46:14,640 INFO  [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
18:46:14,640 INFO  [StdSchedulerFactory] Quartz scheduler version: 1.5.2
18:46:14,640 INFO  [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
18:46:14,875 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=jdbc/mydbsecrd' to JNDI name 'java:jdbc/mydbsecrd'
18:46:16,078 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
18:46:16,765 INFO  [ServerPeer] JBoss Messaging 1.4.3.GA server [0] started
18:46:16,906 INFO  [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
18:46:16,906 INFO  [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
18:46:16,921 INFO  [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
18:46:16,921 INFO  [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
18:46:17,000 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
18:46:17,000 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 1a30c5d started
18:46:17,000 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
18:46:17,000 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 101170f started
18:46:17,000 INFO  [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
18:46:17,000 INFO  [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory at 1822d97 started
18:46:17,171 INFO  [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
18:46:33,671 INFO  [JBossASKernel] Created KernelDeployment for: profileservice-secured.jar
18:46:33,671 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
18:46:33,671 INFO  [JBossASKernel]   with dependencies:
18:46:33,671 INFO  [JBossASKernel]   and demands:
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
18:46:33,671 INFO  [JBossASKernel] 	jboss.ejb:service=EJBTimerService
18:46:33,671 INFO  [JBossASKernel]   and supplies:
18:46:33,671 INFO  [JBossASKernel] 	Class:org.jboss.profileservice.spi.ProfileService
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureProfileService/remote
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService
18:46:33,671 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3) to KernelDeployment of: profileservice-secured.jar
18:46:33,671 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
18:46:33,671 INFO  [JBossASKernel]   with dependencies:
18:46:33,671 INFO  [JBossASKernel]   and demands:
18:46:33,671 INFO  [JBossASKernel] 	jboss.ejb:service=EJBTimerService
18:46:33,671 INFO  [JBossASKernel]   and supplies:
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager
18:46:33,671 INFO  [JBossASKernel] 	Class:org.jboss.deployers.spi.management.deploy.DeploymentManager
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureDeploymentManager/remote
18:46:33,671 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3) to KernelDeployment of: profileservice-secured.jar
18:46:33,671 INFO  [JBossASKernel] installing bean: jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
18:46:33,671 INFO  [JBossASKernel]   with dependencies:
18:46:33,671 INFO  [JBossASKernel]   and demands:
18:46:33,671 INFO  [JBossASKernel] 	jboss.ejb:service=EJBTimerService
18:46:33,671 INFO  [JBossASKernel]   and supplies:
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView
18:46:33,671 INFO  [JBossASKernel] 	Class:org.jboss.deployers.spi.management.ManagementView
18:46:33,671 INFO  [JBossASKernel] 	jndi:SecureManagementView/remote
18:46:33,671 INFO  [JBossASKernel] Added bean(jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3) to KernelDeployment of: profileservice-secured.jar
18:46:33,687 INFO  [EJB3EndpointDeployer] Deploy AbstractBeanMetaData at 16220e2{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
18:46:33,687 INFO  [EJB3EndpointDeployer] Deploy AbstractBeanMetaData at 1c62c02{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
18:46:33,687 INFO  [EJB3EndpointDeployer] Deploy AbstractBeanMetaData at 7c3633{name=jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint bean=org.jboss.ejb3.endpoint.deployers.impl.EndpointImpl properties=[container] constructor=null autowireCandidate=true}
18:46:33,828 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3
18:46:33,843 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureDeploymentManager ejbName: SecureDeploymentManager
18:46:33,968 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

	SecureDeploymentManager/remote - EJB3.x Default Remote Business Interface
	SecureDeploymentManager/remote-org.jboss.deployers.spi.management.deploy.DeploymentManager - EJB3.x Remote Business Interface

18:46:34,078 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3
18:46:34,078 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureManagementView ejbName: SecureManagementView
18:46:34,093 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

	SecureManagementView/remote - EJB3.x Default Remote Business Interface
	SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView - EJB3.x Remote Business Interface

18:46:34,156 INFO  [SessionSpecContainer] Starting jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3
18:46:34,156 INFO  [EJBContainer] STARTED EJB: org.jboss.profileservice.ejb.SecureProfileServiceBean ejbName: SecureProfileService
18:46:34,156 INFO  [JndiSessionRegistrarBase] Binding the following Entries in Global JNDI:

	SecureProfileService/remote - EJB3.x Default Remote Business Interface
	SecureProfileService/remote-org.jboss.profileservice.spi.ProfileService - EJB3.x Remote Business Interface

18:46:34,375 INFO  [TomcatDeployment] deploy, ctxPath=/admin-console
18:46:34,500 INFO  [config] Initializing Mojarra (1.2_12-b01-FCS) for context '/admin-console'
18:46:39,375 INFO  [TomcatDeployment] deploy, ctxPath=/MyWebService
18:46:41,734 ERROR [STDERR] log4j:ERROR A "org.jboss.logging.appender.FileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
18:46:41,734 ERROR [STDERR] log4j:ERROR The class "org.apache.log4j.Appender" was loaded by 
18:46:41,734 ERROR [STDERR] log4j:ERROR [BaseClassLoader at 13f425b{vfszip:/C:/Programme/jboss-5.1.0.GA/server/default/deploy/MyWebService.war/}] whereas object of type 
18:46:41,734 ERROR [STDERR] log4j:ERROR "org.jboss.logging.appender.FileAppender" was loaded by [org.jboss.bootstrap.NoAnnotationURLClassLoader at b64435].
18:46:41,734 ERROR [STDERR] log4j:ERROR Could not instantiate appender named "FILE".
18:46:41,781 INFO  [STDOUT] 18:46:41,781 INFO  [ContextLoader] Root WebApplicationContext: initialization started
18:46:41,781 INFO  [[/MyWebService]] Loading Spring root WebApplicationContext
18:46:41,843 INFO  [STDOUT] 18:46:41,843 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from ServletContext resource [/WEB-INF/applicationContext.xml]
18:46:41,843 INFO  [STDOUT] 18:46:41,843 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/xfire.xml]
18:46:41,843 INFO  [STDOUT] 18:46:41,843 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/customEditors.xml]
18:46:42,250 INFO  [STDOUT] 18:46:42,250 INFO  [CollectionFactory] Commons Collections 3.x available
18:46:42,359 INFO  [STDOUT] 18:46:42,359 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/xfire.xml]
18:46:42,359 INFO  [STDOUT] 18:46:42,359 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/customEditors.xml]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.customEditorConfigurer': replacing [Root bean: class [org.springframework.beans.factory.config.CustomEditorConfigurer]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/customEditors.xml]] with [Root bean: class [org.springframework.beans.factory.config.CustomEditorConfigurer]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/customEditors.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.serviceRegistry': replacing [Root bean: class [org.codehaus.xfire.service.DefaultServiceRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.DefaultServiceRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.transportManager': replacing [Root bean: class [org.codehaus.xfire.transport.DefaultTransportManager]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=initialize; destroyMethodName=dispose; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.transport.DefaultTransportManager]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=initialize; destroyMethodName=dispose; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire': replacing [Root bean: class [org.codehaus.xfire.DefaultXFire]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.DefaultXFire]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.typeMappingRegistry': replacing [Root bean: class [org.codehaus.xfire.aegis.type.DefaultTypeMappingRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=createDefaultMappings; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.aegis.type.DefaultTypeMappingRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=createDefaultMappings; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.aegisBindingProvider': replacing [Root bean: class [org.codehaus.xfire.aegis.AegisBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.aegis.AegisBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.serviceFactory': replacing [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.servletController': replacing [Root bean: class [org.codehaus.xfire.transport.http.XFireServletController]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.transport.http.XFireServletController]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.messageServiceFactory': replacing [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.messageBindingProvider': replacing [Root bean: class [org.codehaus.xfire.service.binding.MessageBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.binding.MessageBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,375 INFO  [STDOUT] 18:46:42,375 INFO  [XmlWebApplicationContext] Bean factory for application context [Root WebApplicationContext]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [xfire.customEditorConfigurer,xfire.serviceRegistry,xfire.transportManager,xfire,xfire.typeMappingRegistry,xfire.aegisBindingProvider,xfire.serviceFactory,xfire.servletController,xfire.messageServiceFactory,xfire.messageBindingProvider,webAnnotations,handlerMapping,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping,profileService]; root of BeanFactory hierarchy
18:46:42,390 INFO  [STDOUT] 18:46:42,390 INFO  [XmlWebApplicationContext] 14 beans defined in application context [Root WebApplicationContext]
18:46:42,515 INFO  [STDOUT] 18:46:42,515 INFO  [XmlWebApplicationContext] Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource at 180feb]
18:46:42,515 INFO  [STDOUT] 18:46:42,515 INFO  [XmlWebApplicationContext] Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster at 19e3f3d]
18:46:42,515 INFO  [STDOUT] 18:46:42,515 INFO  [UiApplicationContextUtils] Unable to locate ThemeSource with name 'themeSource': using default [org.springframework.ui.context.support.ResourceBundleThemeSource at a500c8]
18:46:42,515 INFO  [STDOUT] 18:46:42,515 INFO  [DefaultListableBeanFactory] Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [xfire.customEditorConfigurer,xfire.serviceRegistry,xfire.transportManager,xfire,xfire.typeMappingRegistry,xfire.aegisBindingProvider,xfire.serviceFactory,xfire.servletController,xfire.messageServiceFactory,xfire.messageBindingProvider,webAnnotations,handlerMapping,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping,profileService]; root of BeanFactory hierarchy]
18:46:42,828 INFO  [STDOUT] 18:46:42,828 INFO  [Jsr181HandlerMapping] Exposing  service {http://service.spring.myservices.mycomp.com}MyWebService to /services/MyWebService
18:46:42,843 INFO  [STDOUT] 18:46:42,843 INFO  [ContextLoader] Using context class [org.springframework.web.context.support.XmlWebApplicationContext] for root WebApplicationContext
18:46:42,843 INFO  [STDOUT] 18:46:42,843 INFO  [ContextLoader] Root WebApplicationContext: initialization completed in 1062 ms
18:46:42,843 INFO  [STDOUT] 18:46:42,843 INFO  [ContextLoader] Root WebApplicationContext: initialization started
18:46:42,843 INFO  [[/MyWebService]] Loading Spring root WebApplicationContext
18:46:42,843 INFO  [STDOUT] 18:46:42,843 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from ServletContext resource [/WEB-INF/applicationContext.xml]
18:46:42,843 INFO  [STDOUT] 18:46:42,843 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/xfire.xml]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/customEditors.xml]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/xfire.xml]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlBeanDefinitionReader] Loading XML bean definitions from class path resource [org/codehaus/xfire/spring/customEditors.xml]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.customEditorConfigurer': replacing [Root bean: class [org.springframework.beans.factory.config.CustomEditorConfigurer]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/customEditors.xml]] with [Root bean: class [org.springframework.beans.factory.config.CustomEditorConfigurer]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/customEditors.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.serviceRegistry': replacing [Root bean: class [org.codehaus.xfire.service.DefaultServiceRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.DefaultServiceRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.transportManager': replacing [Root bean: class [org.codehaus.xfire.transport.DefaultTransportManager]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=initialize; destroyMethodName=dispose; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.transport.DefaultTransportManager]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=initialize; destroyMethodName=dispose; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire': replacing [Root bean: class [org.codehaus.xfire.DefaultXFire]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.DefaultXFire]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.typeMappingRegistry': replacing [Root bean: class [org.codehaus.xfire.aegis.type.DefaultTypeMappingRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=createDefaultMappings; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.aegis.type.DefaultTypeMappingRegistry]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=createDefaultMappings; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.aegisBindingProvider': replacing [Root bean: class [org.codehaus.xfire.aegis.AegisBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.aegis.AegisBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.serviceFactory': replacing [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.servletController': replacing [Root bean: class [org.codehaus.xfire.transport.http.XFireServletController]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.transport.http.XFireServletController]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.messageServiceFactory': replacing [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.binding.ObjectServiceFactory]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Overriding bean definition for bean 'xfire.messageBindingProvider': replacing [Root bean: class [org.codehaus.xfire.service.binding.MessageBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]] with [Root bean: class [org.codehaus.xfire.service.binding.MessageBindingProvider]; abstract=false; singleton=true; lazyInit=false; autowire=0; dependencyCheck=0; initMethodName=null; destroyMethodName=null; factoryMethodName=null; factoryBeanName=null; defined in class path resource [org/codehaus/xfire/spring/xfire.xml]]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlWebApplicationContext] Bean factory for application context [Root WebApplicationContext]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [xfire.customEditorConfigurer,xfire.serviceRegistry,xfire.transportManager,xfire,xfire.typeMappingRegistry,xfire.aegisBindingProvider,xfire.serviceFactory,xfire.servletController,xfire.messageServiceFactory,xfire.messageBindingProvider,webAnnotations,handlerMapping,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping,profileService]; root of BeanFactory hierarchy
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlWebApplicationContext] 14 beans defined in application context [Root WebApplicationContext]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlWebApplicationContext] Unable to locate MessageSource with name 'messageSource': using default [org.springframework.context.support.DelegatingMessageSource at caaca5]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [XmlWebApplicationContext] Unable to locate ApplicationEventMulticaster with name 'applicationEventMulticaster': using default [org.springframework.context.event.SimpleApplicationEventMulticaster at c998f]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [UiApplicationContextUtils] Unable to locate ThemeSource with name 'themeSource': using default [org.springframework.ui.context.support.ResourceBundleThemeSource at 135848a]
18:46:42,859 INFO  [STDOUT] 18:46:42,859 INFO  [DefaultListableBeanFactory] Pre-instantiating singletons in factory [org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [xfire.customEditorConfigurer,xfire.serviceRegistry,xfire.transportManager,xfire,xfire.typeMappingRegistry,xfire.aegisBindingProvider,xfire.serviceFactory,xfire.servletController,xfire.messageServiceFactory,xfire.messageBindingProvider,webAnnotations,handlerMapping,org.springframework.web.servlet.handler.SimpleUrlHandlerMapping,profileService]; root of BeanFactory hierarchy]
18:46:42,984 INFO  [STDOUT] 18:46:42,984 INFO  [Jsr181HandlerMapping] Exposing  service {http://service.spring.myservices.mycomp.com}MyWebService to /services/MyWebService
18:46:42,984 INFO  [STDOUT] 18:46:42,984 INFO  [ContextLoader] Using context class [org.springframework.web.context.support.XmlWebApplicationContext] for root WebApplicationContext
18:46:42,984 INFO  [STDOUT] 18:46:42,984 INFO  [ContextLoader] Root WebApplicationContext: initialization completed in 141 ms
18:46:43,718 INFO  [TomcatDeployment] deploy, ctxPath=/MyTestClientWebApp
18:46:45,578 INFO  [TomcatDeployment] deploy, ctxPath=/
18:46:45,687 INFO  [TomcatDeployment] deploy, ctxPath=/jmx-console
18:46:45,812 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
18:46:45,859 INFO  [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
18:46:45,875 INFO  [ServerImpl] JBoss (Microcontainer) [5.1.0.GA (build: SVNTag=JBoss_5_1_0_GA date=200905221053)] Started in 1m:49s:250ms


##################################
Exception during first call of WebService via browser with:

http://myservername.mydomain.org.8080/MyWebService/services/MyWebService?wsdl

##################################

18:47:27,234 ERROR [[XFireServlet]] Servlet.service() for servlet XFireServlet threw exception
javax.servlet.ServletException: non-HTTP request or response
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:851)
	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(Unknown Source)

########################################################################################################################################



Does anyone has an idea, what goes wrong ?

Thanks and best regards.


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

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


From do-not-reply at jboss.com  Tue Jun 23 05:36:40 2009
From: do-not-reply at jboss.com (newman79)
Date: Tue, 23 Jun 2009 05:36:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: EJB Web Service Stateful?
Message-ID: <4945722.1245749800676.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi all,

I'm a little new with JbossWS, so maybe the answer is trivial ...

My web service seems to be stateless : does it mean that an object of my endpoint class is instanciated at each request ?

But I'd like to create a webservice that keep some objects for all its life (like count in shaikbash's example).

Does anyone know
how can I correctly prevent instanciation of my endpoint class at each request and keep the same since start deplyment to undeployment ?

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

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


From do-not-reply at jboss.com  Tue Jun 23 10:46:54 2009
From: do-not-reply at jboss.com (jena435)
Date: Tue, 23 Jun 2009 10:46:54 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Not able to generate the wsdl
Message-ID: <30011161.1245768414591.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,
I am pretty new to jbossws. I am trying to expose my ejb as webservices and have been try a very trivial example for test. I can register the endpoint but does not generate the wsdl file.

this is the basic service I am trying to test on.

@Stateless
@WebService(name = "additionService", serviceName = "additionService", targetNamespace = "http://eardeployment.jaxws/")
//@SOAPBinding(style = SOAPBinding.Style.RPC)
@SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE)
@WebContext(contextRoot = "/test")
public class Addition {

    @WebMethod(operationName = "add")
    public int add(@WebParam(name = "i") int i, @WebParam(name = "j") int j) {
        int k = i + j;
        return k;
    }
}

The ERRORS that I get are :

javax.servlet.ServletException: Servlet.init() for servlet Addition threw exception
	org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	java.lang.Thread.run(Thread.java:595)

root cause

java.lang.ClassCastException: org.jboss.wsf.framework.DefaultSPIProviderResolver
	org.jboss.wsf.spi.SPIProviderResolver.getInstance(SPIProviderResolver.java:38)
	org.jboss.wsf.stack.jbws.EndpointServlet.init(EndpointServlet.java:68)
	org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	java.lang.Thread.run(Thread.java:595)

Any help in providing some enlightenment will be greatly appreciated.

Thanks,
RJ


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

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


From do-not-reply at jboss.com  Tue Jun 23 12:29:22 2009
From: do-not-reply at jboss.com (lonojohnson)
Date: Tue, 23 Jun 2009 12:29:22 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Slow response time and performance
Message-ID: <10815666.1245774562308.JavaMail.jboss@tmp3.prod.atl2.jboss.com>


Running JBoss 5.0.1 GA with the JBoss native WS stack.

I am running a simple WS service, all it does is echo back the string that was sent from the client application.  The response time of the web service averages about 110 msec.  A simple Java app will respond in < 5-10 msec.  I would appear that there is > 100 msec of overhead with the Web Service.  This seems hard to believe.

I assume that there is some sort of polling or other event-waiting processes that are involved.  Are there configuration setting that can reduce this overhead?  Any info would be appreciated.  Thanks in advance.

Regards,
CJ   

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

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


From do-not-reply at jboss.com  Tue Jun 23 13:01:57 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 23 Jun 2009 13:01:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not able to generate the wsdl
Message-ID: <1736858.1245776517538.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hmm, you're using a lot more annotations than I used for a simple service. See here for a complete example: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4182251 Try using the minimal number of annotations (and annotation attributes) first and see if that works. If so, then the issue is with one of the annotations.

Also, the stack trace you posted appears to be what is shown in the browser. There should also be an exception in the console log - could you post that?

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

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


From do-not-reply at jboss.com  Tue Jun 23 13:31:55 2009
From: do-not-reply at jboss.com (jena435)
Date: Tue, 23 Jun 2009 13:31:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not able to generate the wsdl
Message-ID: <24546846.1245778315060.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Peter,
I tried using the example you have mentioned but I still get the errors. The errors that is in the console log.

13:28:33,507 ERROR [[/hello]] StandardWrapper.Throwable
java.lang.ClassCastException: org.jboss.wsf.framework.DefaultSPIProviderResolver
	at org.jboss.wsf.spi.SPIProviderResolver.getInstance(SPIProviderResolver.java:38)
	at org.jboss.wsf.stack.jbws.EndpointServlet.init(EndpointServlet.java:68)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
	at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	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:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	at java.lang.Thread.run(Thread.java:595)
13:28:33,507 ERROR [[HelloService]] Allocate exception for servlet HelloService
java.lang.ClassCastException: org.jboss.wsf.framework.DefaultSPIProviderResolver
	at org.jboss.wsf.spi.SPIProviderResolver.getInstance(SPIProviderResolver.java:38)
	at org.jboss.wsf.stack.jbws.EndpointServlet.init(EndpointServlet.java:68)
	at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1161)
	at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:806)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:129)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
	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:157)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
	at java.lang.Thread.run(Thread.java:595)

Thanks in advance.
RJ

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

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


From do-not-reply at jboss.com  Tue Jun 23 13:50:18 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 23 Jun 2009 13:50:18 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not able to generate the wsdl
Message-ID: <2106844.1245779418228.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

What version of JBoss AS are you using? Did you compile your web service using the JARs from that same version?

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

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


From do-not-reply at jboss.com  Tue Jun 23 13:55:56 2009
From: do-not-reply at jboss.com (jena435)
Date: Tue, 23 Jun 2009 13:55:56 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not able to generate the wsdl
Message-ID: <7677483.1245779756836.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Peter,
I am using jboss 4.2.3 ga.

Thanks,
RJ

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

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


From do-not-reply at jboss.com  Tue Jun 23 13:56:45 2009
From: do-not-reply at jboss.com (jena435)
Date: Tue, 23 Jun 2009 13:56:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not able to generate the wsdl
Message-ID: <17137487.1245779805367.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

yes the jars are from the same version.

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

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


From do-not-reply at jboss.com  Tue Jun 23 19:12:58 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 23 Jun 2009 19:12:58 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Not able to generate the wsdl
Message-ID: <5040928.1245798778840.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I copied your code, as is, into one of my web service classes, compiled and deployed to AS 4.2.3, and I get the WSDL without any problems.

So now the question is how is your web service different from mine. I assume you are packaging it as a JAR file - could you post the JAR file contents. You can get that by running "jar -tf xxx.jar" where xxx.jar is the name of your JAR file.

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

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


From do-not-reply at jboss.com  Wed Jun 24 03:49:40 2009
From: do-not-reply at jboss.com (newman79)
Date: Wed, 24 Jun 2009 03:49:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Simple webservice : only one instance
	for all users
Message-ID: <30022853.1245829780394.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi all,

I'm a little new with JbossWS, so maybe the answer is trivial ...

My web service seems to be stateless : does it mean that an object of my endpoint class is instanciated at each request ?

But I'd like my webservice to keep the same endpoint class instance along all webservice lifetime ...

Does anyone know
how can I correctly prevent instanciation of my endpoint class at each request and keep the same since start deplyment to undeployment ?

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

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


From do-not-reply at jboss.com  Wed Jun 24 04:43:04 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 24 Jun 2009 04:43:04 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Simple webservice : only one
	instance for all users
Message-ID: <23884557.1245832984485.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"newman79" wrote : 
  | Does anyone know
  | how can I correctly prevent instanciation of my endpoint class at each request and keep the same since start deplyment to undeployment ?
Upgrade to JBossWS 3.1.2

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

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


From yhenden at sopragroup.com  Wed Jun 24 11:42:56 2009
From: yhenden at sopragroup.com (Henden Yasemin)
Date: Wed, 24 Jun 2009 17:42:56 +0200
Subject: [jbossws-users] java.lang.ClassCastException when calling a
	WebService
Message-ID: <10643_1245858191_4A42498F_10643_1023301_1_375BF4705DE42C43937DF48DA7E5845C93FEE6@WBE13.ancy.fr.sopra>

Hi, 
 
I'm trying to call a WebService Method but I get this exception : 
 
javax.servlet.ServletException: java.lang.ClassCastException:
org.jboss.ws.core.jaxws.spi.ProviderImpl cannot be cast to
javax.xml.ws.spi.Provider
 
org.apache.struts.action.RequestProcessor.processException(RequestProces
sor.java:520)
 
org.apache.struts.action.RequestProcessor.processActionPerform(RequestPr
ocessor.java:427)
 
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:
228)
 org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
 org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
 javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
 
org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilte
r.java:96)
 
 
Both applications are deployed on Jboss 5.0.1 
I've generated the stubs using wsconsume
I use JDK 1.6
 
Anybody has any idea of where it's coming from ?
Thanks in advance, 
 
Yasemin
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090624/040c828e/attachment.html 

From yhenden at sopragroup.com  Thu Jun 25 08:46:54 2009
From: yhenden at sopragroup.com (Henden Yasemin)
Date: Thu, 25 Jun 2009 14:46:54 +0200
Subject: [jbossws-users] java.lang.ClassCastException when calling a
Message-ID: <10645_1245934016_4A4371C0_10645_4931927_1_375BF4705DE42C43937DF48DA7E5845C94034C@WBE13.ancy.fr.sopra>

I fixed the problem.
It was due to a missing jar : JAXWS2.1.jar
Y.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090625/7273a568/attachment.html 

From do-not-reply at jboss.com  Thu Jun 25 09:00:53 2009
From: do-not-reply at jboss.com (rangalo)
Date: Thu, 25 Jun 2009 09:00:53 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBOSS-5.1.0.GA web service client
	doesn't work ( runtime mod
Message-ID: <24759205.1245934853601.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I have a simple hello-world EJB3 successfully deployed as web service. I can check it with url: http://localhost:8080/jbossws/services


Following is the client which works for Glassfish but doesn't work for JBOSS
 

  | package com.hardik.mejb;
  | 
  | import java.net.MalformedURLException;
  | import java.net.URL;
  | import javax.xml.namespace.QName;
  | import javax.xml.ws.Service;
  | 
  | public class JAXWSClient {
  | 	
  | 	private static String host = "localhost";
  | 	private static String portType = "HelloBean";
  | 	private static String serviceName = "Greeter";
  | 	private static String serviceName_jboss = "hello-ws-hello-ws";
  | 
  | 	// works for glassfish
  | 	// private static String serviceEndpointAddress = "http://"+ host+ ":8080/" + serviceName;
  | 	
  | 	// should work for jboss
  | 	private static String serviceEndpointAddress = "http://"+ host+ ":8080/" + serviceName_jboss;
  | 	
  | 	private static String namespace = "http://mejb.hardik.com/";
  | 	
  | 	public static void main(String[] args) {
  | 		
  | 		URL wsdlLocation = null;
  | 		try {
  | 			String urlstr = serviceEndpointAddress + "/" + portType + "?WSDL";
  | 			System.out.println(urlstr);
  | 			wsdlLocation = new URL(urlstr);
  | 		} catch (MalformedURLException e) {
  | 			// TODO Auto-generated catch block
  | 			e.printStackTrace();
  | 		}
  | 		
  | 		QName serviceNameQ = new QName(namespace,serviceName);		
  | 		// dynamic service usage
  | 		Service service = Service.create(wsdlLocation, serviceNameQ);
  | 		Hello firstGreeterPort =  service.getPort(Hello.class);
  | 		
  | 		// Object beans[] = service.getPorts();
  | 		System.out.println("1: "+ firstGreeterPort.hello());		
  | 	}
  | }
  | 

Here is how I execute the client and the error I get: 

wsrunclient.sh  -cp "lib/*:dist/hello-client.jar:jboss-generated/*"  com.hardik.mejb.JAXWSClient
  | http://localhost:8080/hello-ws-hello-ws/HelloBean?WSDL
  | Exception in thread "main" com.sun.xml.internal.ws.model.RuntimeModelerException: runtime modeler error: Wrapper class com.hardik.mejb.jaxws.Hello is not found. Have you run APT to generate them?
  |         at com.sun.xml.internal.ws.model.RuntimeModeler.getClass(RuntimeModeler.java:256)
  |         at com.sun.xml.internal.ws.model.RuntimeModeler.processDocWrappedMethod(RuntimeModeler.java:567)
  |         at com.sun.xml.internal.ws.model.RuntimeModeler.processMethod(RuntimeModeler.java:514)
  |         at com.sun.xml.internal.ws.model.RuntimeModeler.processClass(RuntimeModeler.java:341)
  |         at com.sun.xml.internal.ws.model.RuntimeModeler.buildRuntimeModel(RuntimeModeler.java:227)
  |         at com.sun.xml.internal.ws.client.WSServiceDelegate.addSEI(WSServiceDelegate.java:588)
  |         at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:291)
  |         at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:274)
  |         at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:302)
  |         at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:306)
  |         at javax.xml.ws.Service.getPort(Service.java:161)
  |         at com.hardik.mejb.JAXWSClient.main(Unknown Source)
  | 

 Do I need to generate something ? Am I missing some jar file(s) ? 

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

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


From do-not-reply at jboss.com  Thu Jun 25 09:27:55 2009
From: do-not-reply at jboss.com (joaobmonteiro)
Date: Thu, 25 Jun 2009 09:27:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem on receiving an object holding
	datetime
Message-ID: <426529.1245936475441.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi guys,

I have many services that use complex objects holding datetime (java.util.Date) values. The problem is that I always get null for datetime attributes. How can I solve this? 
I'm using JBoss AS 4.2.3-jdk6 and my ws clients are written in Delphi 7.

My classes:


  | public class Document implements Serializable {
  | 	
  | 	private static final long serialVersionUID = 2964445290986713245L;
  | 	private Date date;
  |        //getters and setters
  | }
  | 

My ws looks like this:


  | @Stateless
  | @WebService
  | @SOAPBinding(style=Style.RPC)
  | public class DateServices {
  | 	
  | 	@WebMethod
  | 	public Date dateNow(){
  | 		return new Date();
  | 	}
  | 	@WebMethod
  | 	public void printDate(@WebParam(name="documento", mode=Mode.IN) Documento documento){
  | 		if(documento.getDate() == null)
  | 			return;
  | 		SimpleDateFormat dateFormat = new SimpleDateFormat("dd/MM/yyyy");
  | 		String data = dateFormat.format(documento.getDate());
  | 		System.out.println(data);
  | 	}
  | }
  | 

Regards,




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

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


From do-not-reply at jboss.com  Thu Jun 25 09:36:24 2009
From: do-not-reply at jboss.com (pramod_bs)
Date: Thu, 25 Jun 2009 09:36:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem on receiving an object
	holding datetime
Message-ID: <29661461.1245936984236.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

One area you might want to look at is if the client is sending the date in the correct format. 


  | XS:DATETIME FORMAT expects --> 2005-05-27T14:11:00.000
  | 

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

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


From do-not-reply at jboss.com  Thu Jun 25 09:48:52 2009
From: do-not-reply at jboss.com (arjunpnair)
Date: Thu, 25 Jun 2009 09:48:52 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - JBoss SOAP stack and DTD's
Message-ID: <31362054.1245937732690.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi,

I have a query regarding JBoss SOAP stack. Generally some SOAP stacks process DTDs. Some vendors offer patches to cope with this threat.

I want to know whether JBOSS SOAP stack process DTDs ?

Regards,
Arjun

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

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


From do-not-reply at jboss.com  Thu Jun 25 11:03:21 2009
From: do-not-reply at jboss.com (lonojohnson)
Date: Thu, 25 Jun 2009 11:03:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBOSS-5.1.0.GA web service client
	doesn't work ( runtime
Message-ID: <30577686.1245942201468.JavaMail.jboss@tmp3.prod.atl2.jboss.com>


Not sure if this is the problem, but are you running JBoss native stack ver 3.1.2 GA?.  That is the only native WS stack that is supported under 5.1.0 GA.  See the following link: http://jbossws.jboss.org/mediawiki/index.php?title=Supported_Target_Containers 

CJ

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

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


From do-not-reply at jboss.com  Thu Jun 25 11:08:21 2009
From: do-not-reply at jboss.com (lonojohnson)
Date: Thu, 25 Jun 2009 11:08:21 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Slow response time and performance
Message-ID: <11146607.1245942501204.JavaMail.jboss@tmp3.prod.atl2.jboss.com>


My bad, I was measuring the WebService initialization time.  As it turns out, the actual service response time is much shorter.

CJ

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

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


From do-not-reply at jboss.com  Thu Jun 25 11:21:05 2009
From: do-not-reply at jboss.com (rangalo)
Date: Thu, 25 Jun 2009 11:21:05 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBOSS-5.1.0.GA web service client
	doesn't work ( runtime
Message-ID: <26030079.1245943265801.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi, 
I think I am running the native stack 3.1.2 GA

I see following in my server.log file...


  | 2009-06-25 11:22:19,559 INFO  [org.jboss.web.WebService] (main) Using RMI server codebase: http://127.0.0.1:8083/
  | 2009-06-25 11:22:24,783 INFO  [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) JBoss Web Services - Stack Native Core
  | 2009-06-25 11:22:24,783 INFO  [org.jboss.wsf.stack.jbws.NativeServerConfig] (main) 3.1.2.GA
  | 

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

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


From do-not-reply at jboss.com  Thu Jun 25 10:09:25 2009
From: do-not-reply at jboss.com (joaobmonteiro)
Date: Thu, 25 Jun 2009 10:09:25 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Problem on receiving an object
	holding datetime
Message-ID: <10516785.1245938965438.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thanks pramod_bs,

We've already inspected that. However, we discovered some differences between xml formats when using complex types. The Delphi client generates different patterns when using complex object holding date values and jboss ws is not able to translate that. Maybe later I post the soap envelops for you guys.

Fortunately, our Delphi Jedi wake up and remake an Soap update code. Now, everything works fine!

For sure, someone is not following the soap spec... 

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

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


From do-not-reply at jboss.com  Fri Jun 26 01:31:08 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Fri, 26 Jun 2009 01:31:08 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBOSS-5.1.0.GA web service client
	doesn't work ( runtime
Message-ID: <22670989.1245994268943.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"rangalo" wrote : 
  | wsrunclient.sh  -cp "lib/*:dist/hello-client.jar:jboss-generated/*"  com.hardik.mejb.JAXWSClient
  |   | http://localhost:8080/hello-ws-hello-ws/HelloBean?WSDL
  |   | 
lib/*: is invalid. This will be the reason of your problems.

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

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


From do-not-reply at jboss.com  Fri Jun 26 04:52:49 2009
From: do-not-reply at jboss.com (rangalo)
Date: Fri, 26 Jun 2009 04:52:49 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBOSS-5.1.0.GA web service client
	doesn't work ( runtime
Message-ID: <33092398.1246006369148.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Thanks, 

Now I have at least some other error !

If I use only lib I get this error, I think it is related to stax implementation.


Am I missing some jar?


  | [hardik at antariksh: HelloWsClient]$ wsrunclient.sh  -cp "dist/hello-client.jar:jboss-generated:lib"  com.hardik.mejb.JAXWSClient
  | http://localhost:8080/Greeter/HelloBean?WSDL
  | Exception in thread "main" java.lang.ExceptionInInitializerError
  |         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
  |         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
  |         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
  |         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
  |         at java.lang.Class.newInstance0(Class.java:355)
  |         at java.lang.Class.newInstance(Class.java:308)
  |         at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:31)
  |         at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:128)
  |         at javax.xml.ws.spi.Provider.provider(Provider.java:83)
  |         at javax.xml.ws.Service.<init>(Service.java:56)
  |         at com.hardik.mejb.Greeter.<init>(Greeter.java:45)
  |         at com.hardik.mejb.JAXWSClient.main(Unknown Source)
  | Caused by: javax.xml.ws.WebServiceException: Error creating JAXBContext for W3CEndpointReference. 
  |         at com.sun.xml.internal.ws.spi.ProviderImpl$2.run(ProviderImpl.java:201)
  |         at com.sun.xml.internal.ws.spi.ProviderImpl$2.run(ProviderImpl.java:196)
  |         at java.security.AccessController.doPrivileged(Native Method)
  |         at com.sun.xml.internal.ws.spi.ProviderImpl.getEPRJaxbContext(ProviderImpl.java:196)
  |         at com.sun.xml.internal.ws.spi.ProviderImpl.<clinit>(ProviderImpl.java:67)
  |         ... 12 more
  | Caused by: javax.xml.bind.JAXBException: Provider com.sun.xml.bind.v2.ContextFactory not found
  |  - with linked exception:
  | [java.security.PrivilegedActionException: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory]
  |         at javax.xml.bind.ContextFinder.loadClass(ContextFinder.java:192)
  |         at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:205)
  |         at javax.xml.bind.ContextFinder.find(ContextFinder.java:388)
  |         at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:574)
  |         at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:522)
  |         at com.sun.xml.internal.ws.spi.ProviderImpl$2.run(ProviderImpl.java:199)
  |         ... 16 more
  | Caused by: java.security.PrivilegedActionException: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory
  |         at java.security.AccessController.doPrivileged(Native Method)
  |         at javax.xml.bind.ContextFinder.loadClass(ContextFinder.java:175)
  |         ... 21 more
  | Caused by: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory
  |         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
  |         at java.security.AccessController.doPrivileged(Native Method)
  |         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
  |         at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
  |         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
  |         at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
  |         at javax.xml.bind.ContextFinder$1.run(ContextFinder.java:180)
  |         at javax.xml.bind.ContextFinder$1.run(ContextFinder.java:176)
  |         ... 23 more
  | 



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

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


From do-not-reply at jboss.com  Fri Jun 26 07:28:57 2009
From: do-not-reply at jboss.com (rangalo)
Date: Fri, 26 Jun 2009 07:28:57 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBOSS-5.1.0.GA web service client
	doesn't work ( runtime
Message-ID: <4937940.1246015737301.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

This was indeed a missing jars in classpath problem.

I had to add following to the classpath:

  | $ echo $CLASSPATH 
  | jboss_libs/jboss-common-core.jar:jboss_libs/jbossall-client.jar:jboss_libs/jbossws-spi.jar:jboss_libs/jbossws-native-core.jar:jboss_libs/jbossws-native-client.jar::jboss_libs/jaxb-impl.jar:jboss_libs/jboss-xml-binding.jar:jboss_libs/stax-api.jar:jboss_libs/wstx.jar:jboss_libs/jboss-logging-jdk.jar:jboss_libs/jboss-logging-spi.jar:jboss_libs/jbossws-common.jar:jboss_libs/wsdl4j.jar:jboss_libs/mail.jar:jboss_libs/policy.jar:jboss_libs/commons-logging.jar:jboss_libs/javassist.jar:jboss_libs/jboss-remoting.jar
  | 

All these libs were from jboss/client 

But after the client started working, I had following exception in server.log.


  | 3:29:21,925 ERROR [[HelloBean]] Servlet.service() for servlet HelloBean threw exception
  | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
  | 	at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
  | 	at org.jboss.ws.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:87)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.createSOAPMessage(SOAPFaultHelperJAXWS.java:295)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:256)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:187)
  | 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102)
  | 	at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496)
  | 	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:619)
  | 
  | 


On client side it looks like following:

  | $ wsrunclient.sh  -cp "dist/hello-client.jar:jboss-generated:lib:$CLASSPATH"  com.hardik.mejb.JAXWSClient
  | http://localhost:8080/hello-ws-hello-ws/HelloBean?WSDL
  | [Fatal Error] :-1:-1: Premature end of file.
  | 2: null
  | 

I installed JBOSS from jboss-5.1.0.GA-jdk6.zip  file.

thanks & regards.

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

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


From do-not-reply at jboss.com  Fri Jun 26 11:18:43 2009
From: do-not-reply at jboss.com (lindabaja)
Date: Fri, 26 Jun 2009 11:18:43 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Data conversion - urgent
Message-ID: <22982040.1246029523680.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Yesterday, in our company we moved all our webservices from Weblogic to JBoss.
There is a wierd error that we are seeing.
A response:
< Amount >0.000000000000000< /Amount >

is being rendered in jboss as :
< Amount >0E-15< /Amount >
As a result, our clients are unable to p[rocess this.
Does anyone know why, or what can be done to rectify.

Type is decimal - 

Thank you
Karthik 

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

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


From do-not-reply at jboss.com  Fri Jun 26 18:41:40 2009
From: do-not-reply at jboss.com (babernat)
Date: Fri, 26 Jun 2009 18:41:40 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: wsconsume ant task
Message-ID: <18800347.1246056100364.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

"kj_newbie" wrote : 
  | 
  | Can anyone point out..what ma I missing ?
  | 

It looks like you're missing the jar: jbossws-spi.jar

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

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


From do-not-reply at jboss.com  Fri Jun 26 18:59:47 2009
From: do-not-reply at jboss.com (babernat)
Date: Fri, 26 Jun 2009 18:59:47 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Can someone confirm this wsconsume ant
	task behavior?
Message-ID: <16924115.1246057187471.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm using the version included with JBoss AS 5.1.0.GA and it appears the wsdl attribute is using the location of the build file as the base directory for the relative path instead of what is defined in the basedir attribute for the ant project.

For example if I have the following ant build script located in a directory C:/myproject/build


  | <project name="MyProject" basedir="../">
  |   <property environment="env"/>
  |   <path id="jboss.client.classpath">
  |     <fileset dir="${JBoss.client.lib}">
  |       <include name="**/*.jar"/>
  |     </fileset>
  |   </path>
  |   <taskdef name="wsconsume" classname="org.jboss.wsf.spi.tools.ant.WSConsumeTask" classpathref="jboss.client.classpath"/>
  |   <target name="generate-service">
  |     <wsconsume keep="true" package="com.whatever" destdir="build/gen" wsdl="build/tmpxml/MyProject.wsdl" verbose="true"/>
  |   </target>
  | </project>
  | 

It appears that wsconsume is looking for the wsdl in:
c:\myproject\build\build\tmpxml\MyProject.wsdl

instead of:
c:\myproject\build\tmpxml\MyProject.wsdl

Since the basedir on the project is set to: ../ I would expect it to look for the wsdl relative to one directory higher. In fact this is how even the destdir attribute works. The way the wsdl attribute references files seems to be different from destdir and most other ant tasks I've seen.

Am I completely stupid and just missing something or does this not seem right?

Thanks.

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

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


From do-not-reply at jboss.com  Mon Jun 29 06:11:45 2009
From: do-not-reply at jboss.com (creaturita)
Date: Mon, 29 Jun 2009 06:11:45 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBossWS Metro 3.1.1 on AS 5.1.0
	Startup errors?
Message-ID: <853529.1246270305891.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Did you find any solution? I have the same problem

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

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


From do-not-reply at jboss.com  Mon Jun 29 08:49:20 2009
From: do-not-reply at jboss.com (mtirumalreddy)
Date: Mon, 29 Jun 2009 08:49:20 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Using JBossWS-CXF for EJB3.0 Webservice
	endpoints
Message-ID: <20640134.1246279760554.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Hi All,

We are going to use JBoss AS 4.2.3 and EJB3.0 in our new project. But my concern is whether EJB3.0 endpoints are supported by CXF or not? I read in one article saying CXF does not implement JSR-109. So it will not support EJB endpoints. But there are some work arounds. 

I searched but i didn't find any suitable articles on this. Can anyone worked before using this combination. Please help me on this.

Please see this.
https://issues.apache.org/jira/browse/CXF-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644784

Regards,
Tirumal Reddy M



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

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


From do-not-reply at jboss.com  Mon Jun 29 09:24:24 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 29 Jun 2009 09:24:24 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using JBossWS-CXF for EJB3.0
	Webservice endpoints
Message-ID: <15971399.1246281864946.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

There are many testscases showing usage of ejb3 webservice endpoints in the jbossws testsuite, just take a look.
JSR109 is actually not supported with CXF, but that's most probably not an issue for you, as you'd use jaxws for the ejb3 endpoints.

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

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


From do-not-reply at jboss.com  Mon Jun 29 09:33:55 2009
From: do-not-reply at jboss.com (mtirumalreddy)
Date: Mon, 29 Jun 2009 09:33:55 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: Using JBossWS-CXF for EJB3.0
	Webservice endpoints
Message-ID: <15871831.1246282435432.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

alessio soldano,

Thanks a lot for your quick reply.
I need one more help. iam a bit confused over selecting WS Stack in JBoss. iam suggesting Metro Stack, but our architect is suggesting CXF. I have seen many WS Stack comparision charts. According to my opinion, metro will be providing more features than that of Native or CXF. Can you please suggest me in this regard.



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

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


From do-not-reply at jboss.com  Tue Jun 30 05:49:12 2009
From: do-not-reply at jboss.com (konstt2000)
Date: Tue, 30 Jun 2009 05:49:12 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Problem JBOSS-5.1.GA-jdk6 and
	WebService:SOAP request except
Message-ID: <23801939.1246355352289.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

I'm work with jboss-5.1.0.GA-jdk6.

I can see the WSDL but if I try to do a call to the WS:

11:43:08,396 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
	at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441)
	at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:87)

I've inside $JBOSS_HOME/lib/ensored:
jbossws-native-saaj.jar
jbossws-native-jaxrpc.jar
jbossws-native-jaxws.jar
jbossws-native-jaxws-ext.jar


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

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


From do-not-reply at jboss.com  Tue Jun 30 08:26:31 2009
From: do-not-reply at jboss.com (rangalo)
Date: Tue, 30 Jun 2009 08:26:31 -0400 (EDT)
Subject: [jbossws-users] [JBossWS] - Re: JBOSS-5.1.0.GA web service client
	doesn't work ( runtime
Message-ID: <22861577.1246364791827.JavaMail.jboss@tmp3.prod.atl2.jboss.com>

Any idea ?

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

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