From do-not-reply at jboss.com  Tue Sep  1 08:44:48 2009
From: do-not-reply at jboss.com (pio1k)
Date: Tue, 1 Sep 2009 08:44:48 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Heavy load during web
	method call
Message-ID: <27722653.1251809088793.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello everyone!

I have a web service with couple web methods. Those methods are calling quite often (average is about one call of each method per 10 seconds) by .NET client application. After few days of working I checked in JBoss Web Console statistics of calling of those methods. One of them has got average time of call equals about 300 milliseconds but maximum call time is over 70 minutes! I also noticed that when call of this method is very long my CPU is 100% load for all call time.

Maybe someone has got similar problem? My quest is that maybe garbage collector turn on when call was so long.

I'm using:
1) Java 1.5_0_15
2) JBoss 4.2.3
3) -XX:+UseConcMarkSweepGC -XX:+UseParNewGC options for garbage colletor

Regards,
Piter

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

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


From do-not-reply at jboss.com  Tue Sep  1 11:52:24 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Tue, 1 Sep 2009 11:52:24 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Heavy load during
	web method call
Message-ID: <6213723.1251820344045.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

The CMS collector, which you have turned on, needs lots of memory. If the CMS collector ever gets behind in cleaning the tenured generation of the heap, a very expensive "stop the world" collection takes place. I once forced the CMS collector to get behind on a particular app and the garbage collection took around 5 minutes (using the standard collector a Full GC on that same app takes about 2 seconds).

Also, do you have only one CPU? Never use the CMS collector when you have only a single CPU.

Of course, without gathering any GC data, it is all speculation. What data have you gathered so far?

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

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


From do-not-reply at jboss.com  Wed Sep  2 02:56:21 2009
From: do-not-reply at jboss.com (pio1k)
Date: Wed, 2 Sep 2009 02:56:21 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Heavy load during
	web method call
Message-ID: <3366620.1251874581912.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I have CPU with two cores - is it enough?

I have to turn on logging of GC data.

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

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


From do-not-reply at jboss.com  Wed Sep  2 09:26:12 2009
From: do-not-reply at jboss.com (ntsankov)
Date: Wed, 2 Sep 2009 09:26:12 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Unwanted warning
Message-ID: <8305377.1251897972568.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I have a WS client created with wsconsume, but I want to specify the service endpoint at runtime. The solution I found is:

  | MyService stub = new MyService(null, SERVICE_QNAME);
  | MyPortType myPort = stub.getMyPort();
  | ((BindingProvider)myPort).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, endpointUrlString);
  | 

which works ok, except that I get a 
"WARN  [org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl] Cannot get port meta data for: {http://ws...}MyPort"
in the log. I suppose this is caused by the fact that I pass null as wsdl location, but I don't want the client to parse the wsdl each time.
Can someone help me get rid of this warning? Maybe there is a better way to dynamically specify the endpoint?

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

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


From do-not-reply at jboss.com  Wed Sep  2 09:59:48 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Wed, 2 Sep 2009 09:59:48 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - WS-Eventing
	SubscriptionEnd problem
Message-ID: <3116787.1251899988762.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Greetings all,

I am trying to trap the SubscriptionEnd messages but an having no luck. Below are my Class, WSDL and Stacktrace. I am sure it is something small I am overlooking but I can't see it. Any and all help is appreciated.

Earnie!

Class
package org.ebsinc.targeteer.ws;
  | 
  | import javax.jws.WebMethod;
  | import javax.jws.WebParam;
  | import javax.jws.WebService;
  | import javax.xml.ws.addressing.Action;
  | 
  | import org.jboss.logging.Logger;
  | import org.jboss.ws.annotation.EndpointConfig;
  | import org.jboss.ws.extensions.eventing.jaxws.AbstractEventSourceEndpoint;
  | import org.jboss.ws.extensions.eventing.jaxws.SubscriptionEnd;
  | 
  | @WebService(name = "EventSource", portName = "EventSourcePort", targetNamespace = "http://schemas.xmlsoap.org/ws/2004/08/eventing", 
  | wsdlLocation = "/WEB-INF/wsdl/target.wsdl", endpointInterface = "org.jboss.ws.extensions.eventing.jaxws.EventSourceEndpoint")
  | @EndpointConfig(configName = "Standard WSAddressing Endpoint")
  | public class TargeteerRegistrationEndpoint extends AbstractEventSourceEndpoint {
  | 	private static final Logger log = Logger
  | 			.getLogger(TargeteerRegistrationEndpoint.class);
  | 
  | 	@Override
  | 	protected Logger getLogger() {
  | 		return log;
  | 	}
  | 	
  | 	@WebMethod(operationName = "SubscriptionEnd")
  | 	@Action(input = "http://schemas.xmlsoap.org/ws/2004/08/eventing/SubscriptionEnd")
  | 	public void subscriptionEnd(
  | 			@WebParam(name = "SubscriptionEnd", targetNamespace = "http://schemas.xmlsoap.org/ws/2004/08/eventing", 
  | partName = "body") SubscriptionEnd subEnd) {
  | 		log.debug("Subscription is ending " + subEnd);
  | 	}
  | 
  | }
  | 

WSDL
<wsdl:definitions targetNamespace='http://schemas.xmlsoap.org/ws/2004/08/eventing' xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/' xmlns:wsa10='http://www.w3.org/2005/08/addressing' xmlns:wsdl='http://schemas.xmlsoap.org/wsdl/' xmlns:wse='http://schemas.xmlsoap.org/ws/2004/08/eventing' xmlns:xs='http://www.w3.org/2001/XMLSchema'>
  |  <wsdl:types>
  |   <xs:import namespace='http://schemas.xmlsoap.org/ws/2004/08/eventing' schemaLocation='http://localhost:8080/targeteer/subscribe?wsdl&resource=ws-eventing.xsd'/>
  |  </wsdl:types>
  |  <wsdl:message name='GetStatusResponseMsg'>
  |   <wsdl:part element='wse:GetStatusResponse' name='body'></wsdl:part>
  |  </wsdl:message>
  |  <wsdl:message name='GetStatusMsg'>
  |   <wsdl:part element='wse:GetStatus' name='body'></wsdl:part>
  | 
  |  </wsdl:message>
  |  <wsdl:message name='RenewResponseMsg'>
  |   <wsdl:part element='wse:RenewResponse' name='body'></wsdl:part>
  |  </wsdl:message>
  |  <wsdl:message name='SubscriptionEnd'>
  |   <wsdl:part element='wse:SubscriptionEnd' name='body'></wsdl:part>
  |  </wsdl:message>
  |  <wsdl:message name='RenewMsg'>
  |   <wsdl:part element='wse:Renew' name='body'></wsdl:part>
  | 
  |  </wsdl:message>
  |  <wsdl:message name='SubscribeMsg'>
  |   <wsdl:part element='wse:Subscribe' name='body'></wsdl:part>
  |  </wsdl:message>
  |  <wsdl:message name='SubscribeResponseMsg'>
  |   <wsdl:part element='wse:SubscribeResponse' name='body'></wsdl:part>
  |  </wsdl:message>
  |  <wsdl:message name='UnsubscribeMsg'>
  |   <wsdl:part element='wse:Unsubscribe' name='body'></wsdl:part>
  | 
  |  </wsdl:message>
  |  <wsdl:message name='UnsubscribeResponseMsg'></wsdl:message>
  |  <wsdl:portType name='SubscriptionManager'>
  |   <wsdl:operation name='RenewOp'>
  |    <wsdl:input message='wse:RenewMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/Renew'></wsdl:input>
  |    <wsdl:output message='wse:RenewResponseMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/RenewResponse'></wsdl:output>
  |   </wsdl:operation>
  |   <wsdl:operation name='GetStatusOp'>
  |    <wsdl:input message='wse:GetStatusMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/GetStatus'></wsdl:input>
  | 
  |    <wsdl:output message='wse:GetStatusResponseMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/GetStatusResponse'></wsdl:output>
  |   </wsdl:operation>
  |   <wsdl:operation name='UnsubscribeOp'>
  |    <wsdl:input message='wse:UnsubscribeMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/Unsubscribe'></wsdl:input>
  |    <wsdl:output message='wse:UnsubscribeResponseMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/UnsubscribeResponse'></wsdl:output>
  |   </wsdl:operation>
  |  </wsdl:portType>
  |  <wsdl:portType name='EventSource'>
  |   <wsdl:operation name='SubscribeOp'>
  | 
  |    <wsdl:input message='wse:SubscribeMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribe'></wsdl:input>
  |    <wsdl:output message='wse:SubscribeResponseMsg' wsa10:Action='http://schemas.xmlsoap.org/ws/2004/08/eventing/SubscribeResponse'></wsdl:output>
  |   </wsdl:operation>
  |   <wsdl:operation name='SubscriptionEnd'>
  |    <wsdl:output message='wse:SubscriptionEnd'></wsdl:output>
  |   </wsdl:operation>
  |  </wsdl:portType>
  |  <wsdl:binding name='SubscriptionManagerBinding' type='wse:SubscriptionManager'>
  |   <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
  | 
  |   <wsdl:operation name='GetStatusOp'>
  |    <soap:operation soapAction=''/>
  |    <wsdl:input>
  |     <soap:body use='literal'/>
  |    </wsdl:input>
  |    <wsdl:output>
  |     <soap:body use='literal'/>
  |    </wsdl:output>
  |   </wsdl:operation>
  | 
  |   <wsdl:operation name='RenewOp'>
  |    <soap:operation soapAction=''/>
  |    <wsdl:input>
  |     <soap:body use='literal'/>
  |    </wsdl:input>
  |    <wsdl:output>
  |     <soap:body use='literal'/>
  |    </wsdl:output>
  |   </wsdl:operation>
  | 
  |   <wsdl:operation name='UnsubscribeOp'>
  |    <soap:operation soapAction=''/>
  |    <wsdl:input>
  |     <soap:body use='literal'/>
  |    </wsdl:input>
  |    <wsdl:output>
  |     <soap:body use='literal'/>
  |    </wsdl:output>
  |   </wsdl:operation>
  | 
  |  </wsdl:binding>
  |  <wsdl:binding name='EventSourceBinding' type='wse:EventSource'>
  |   <soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
  |   <wsdl:operation name='SubscribeOp'>
  |    <soap:operation soapAction=''/>
  |    <wsdl:input>
  |     <soap:body use='literal'/>
  |    </wsdl:input>
  |    <wsdl:output>
  | 
  |     <soap:body use='literal'/>
  |    </wsdl:output>
  |   </wsdl:operation>
  |   <wsdl:operation name='SubscriptionEnd'>
  |    <soap:operation soapAction=''/>
  |    <wsdl:output>
  |     <soap:body use='literal'/>
  |    </wsdl:output>
  |   </wsdl:operation>
  | 
  |  </wsdl:binding>
  |  <wsdl:service name='EventingService'>
  |   <wsdl:port binding='wse:SubscriptionManagerBinding' name='SubscriptionManagerPort'>
  |    <soap:address location='http://localhost:8080/targeteer/manage'/>
  |   </wsdl:port>
  |   <wsdl:port binding='wse:EventSourceBinding' name='EventSourcePort'>
  |    <soap:address location='http://localhost:8080/targeteer/subscribe'/>
  |   </wsdl:port>
  |  </wsdl:service>
  | 
  | </wsdl:definitions>

StackTrace
09:51:23,562 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
  | javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://schemas.xmlsoap.org/ws/2004/08/eventing}EventSourcePort does not contain operation meta data for: {http://schemas.xmlsoap.org/ws/2004/08/eventing}SubscriptionEnd
  | 	at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:183)
  | 	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.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:285)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
  | 	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.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
  | 	at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:177)
  | 	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:267)
  | 	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:380)
  | 	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:507)
  | 	at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:73)
  | 	at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 	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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
  | 	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)
  | 

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

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


From do-not-reply at jboss.com  Wed Sep  2 10:44:19 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 2 Sep 2009 10:44:19 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Heavy load during
	web method call
Message-ID: <20390983.1251902659646.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

2 cores is adequate, but you have to realize that while the GC is running only one of the cores will be available for the app to use.

For monitoring GC, see my presentation at http://www.cecmg.de/doc/tagung_2007/agenda07/24-mai/2b3-peter-johnson/index.html 

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

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


From do-not-reply at jboss.com  Wed Sep  2 12:03:00 2009
From: do-not-reply at jboss.com (kagey)
Date: Wed, 2 Sep 2009 12:03:00 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - disable client
	chunking in jbossws-3.0.1-native-2.0.4.GA
Message-ID: <32442584.1251907380450.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hey all, 

I have an external webservice endpoint that i have wsconsumed the wsdl for and generated the necessary classes for a client to call the web services. I am dynamically setting the port endpoint at runtime to avoid consuming the wsdl at runtime. the code looks like: 


  | PrincipalManagement princMgmt = new PrincipalManagement(null,
  |                         new QName("http://www.microsoft.com/iptv/bss",
  |                                 "PrincipalManagement"));
  |                 
  |                 PrincipalManagementSoap pms = princMgmt.getPrincipalManagementSoap();
  | 
  |                 ((BindingProvider) pms).getRequestContext().put(
  |                         BindingProvider.ENDPOINT_ADDRESS_PROPERTY,
  |                         "http://" + wsServer
  |                                 + "/bss/PrincipalManagement.asmx");
  | 

The server also has NTLM authentication required. NTLM authentication is the thing that is breaking when using the newer version. It works fine in jboss 4.2.1, but not in 4.2.3. I believe the reason is because the request made with the older jbossws version does not use chunking (Transfer-Encoding: chunked), but rather specifes the content-length. here are the http header sniffs:
OLD version:

  | POST /bss/PrincipalManagement.asmx?datatype=JBossWSMessage= HTTP/1.1
  | 
  | SOAPAction: "http://www.microsoft.com/iptv/bss/ReadAccount"
  | Content-Type: text/xml; charset=UTF-8
  | JBoss-Remoting-Version: 22
  | User-Agent: JBossRemoting - 2.2.1.GA (Bluto)
  | Host: #.#.#.#
  | Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
  | Connection: keep-alive
  | Content-Length: 185
  | ...
  | 

NEW version:

  | POST /bss/PrincipalManagement.asmx HTTP/1.1
  | SOAPAction: "http://www.microsoft.com/iptv/bss/ReadAccount"
  | Content-Type: text/xml; charset=UTF-8
  | JBoss-Remoting-Version: 22
  | User-Agent: JBossRemoting - 2.2.2.SP11
  | Host: #.#.#.#
  | Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
  | Connection: keep-alive
  | Transfer-Encoding: chunked
  | 

I see a newer version of jbossws (3.2...) has a chunking feature (http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide#Chunked_encoding_setup). Is it possible to disable client chunking on jbossws-3.0.1-native-2.0.4.GA?

Thanks
Kagey

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

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


From do-not-reply at jboss.com  Wed Sep  2 14:28:47 2009
From: do-not-reply at jboss.com (kagey)
Date: Wed, 2 Sep 2009 14:28:47 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Cannot change the
	context root for web service
Message-ID: <12294636.1251916127174.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Try deploying in separate jars, from my experience you can't have two different context roots in the same jar.

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

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


From do-not-reply at jboss.com  Wed Sep  2 14:52:23 2009
From: do-not-reply at jboss.com (kagey)
Date: Wed, 2 Sep 2009 14:52:23 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JAX-WS Web Service
	Authentication (NTLM) against a MS CR
Message-ID: <9474200.1251917543854.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I working with NTLM in a different scenario, and it seems that NTLM doesn't work when chunking is used by the client. Do a sniff on your traffic to see what is going on. If you have the appropriate jbossws version you can turn chunking off (http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide#Chunked_encoding_setup). if You are using 3.2.0 I'm curious as to your results (i am using an older version and still searching for a way to disable chunking).

see my thread at http://www.jboss.org/index.html?module=bb&op=viewtopic&t=160737 for a bigger explanation of my findings.

When the client is using chunking, it seems like the jvm doesn't recognize the 401 that is returned from the server before it sends the first chunk and thus never calls our custom authenticators. When chunking is not used, the client sends its whole request at once and then waits for the response (which is a 401) that triggers the authentication sequence. That's my theory anyway.

GL


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

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


From do-not-reply at jboss.com  Wed Sep  2 15:32:43 2009
From: do-not-reply at jboss.com (kagey)
Date: Wed, 2 Sep 2009 15:32:43 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: disable client
	chunking in jbossws-3.0.1-native-2.0.4.GA
Message-ID: <2712963.1251919963048.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

found the solution: revert to old http 1.0 client config:

  | ((StubExt) pms).setConfigName("HTTP 1.0 Client");
  | 

client configurations found in
jboss/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xml

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

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


From do-not-reply at jboss.com  Wed Sep  2 15:35:14 2009
From: do-not-reply at jboss.com (kagey)
Date: Wed, 2 Sep 2009 15:35:14 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JAX-WS Web Service
	Authentication (NTLM) against a MS CR
Message-ID: <29274672.1251920114514.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I fixed my problem by disabling chunking by reverting the client to a different configuration, you could try:


  | CrmTaskServiceSoap port = (new CrmTaskService(url, new QName("http://schemas.microsoft.com/crm/2007/WebServices", "CrmService")))
  | .getCrmTaskServiceSoap();
  | 
  | ...
  | 
  | ((StubExt) port).setConfigName("HTTP 1.0 Client");
  | 
  | String ret = port.create(ent);
  | 
  | 

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

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


From do-not-reply at jboss.com  Wed Sep  2 15:44:30 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Wed, 2 Sep 2009 15:44:30 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: disable client
	chunking in jbossws-3.0.1-native-2.0.4.GA
Message-ID: <27891501.1251920670207.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

You could also turn off chunking by setting the chunksize to 0 in the jboss/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-client-config.xmlfile:

  <client-config>
    <config-name>Standard Client</config-name>
    http://org.jboss.ws/dispatch/validate
    
      <property-name>http://org.jboss.ws/http#chunksize</property-name>
      <property-value>0</property-value>
    
  </client-config>


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

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


From do-not-reply at jboss.com  Wed Sep  2 16:09:45 2009
From: do-not-reply at jboss.com (kagey)
Date: Wed, 2 Sep 2009 16:09:45 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: disable client
	chunking in jbossws-3.0.1-native-2.0.4.GA
Message-ID: <8915343.1251922185933.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

True, but I don't what to change configuration for other clients running who could be using the same config.

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

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


From do-not-reply at jboss.com  Fri Sep  4 07:49:06 2009
From: do-not-reply at jboss.com (ntsankov)
Date: Fri, 4 Sep 2009 07:49:06 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Unwanted warning
Message-ID: <24839596.1252064946448.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Any hints regarding this problem would be highly appreciated!  

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

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


From do-not-reply at jboss.com  Fri Sep  4 08:11:17 2009
From: do-not-reply at jboss.com (kagey)
Date: Fri, 4 Sep 2009 08:11:17 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Unwanted warning
Message-ID: <1837101.1252066277585.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I've noticed the warning goes away when using jbossws-3.0.1

You could change your log4j settings to only report errors for org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl

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

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


From do-not-reply at jboss.com  Fri Sep  4 09:51:53 2009
From: do-not-reply at jboss.com (Tashtego)
Date: Fri, 4 Sep 2009 09:51:53 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] -
	UnsupportedOperationException: setProperty
Message-ID: <12230846.1252072313726.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

JBoss: 5.1.0.GA
Java: 1.6.1
OS: Win XP Professional

WSDL file gets generated and is listed in:
http://localhost:8080/jbossws/services

I see the methods in eclipse web service explorer:
http://127.0.0.1:1863/wse/wsexplorer/wsexplorer.jsp?org.eclipse.wst.ws.explorer=0

Trying to execute my web service leads to an exception:
anonymous wrote : 
  | 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:87)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:215)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:455)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131)
  | 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
  | 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
  | 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Unknown Source)
  | 

Can anyone help?

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

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


From do-not-reply at jboss.com  Fri Sep  4 10:19:49 2009
From: do-not-reply at jboss.com (ntsankov)
Date: Fri, 4 Sep 2009 10:19:49 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Unwanted warning
Message-ID: <18623447.1252073989052.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Thanks!

The log4j setting will ignore all other (possibly important) warnings and I'd like to avoid it, but the upgrade can be made :)

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

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


From do-not-reply at jboss.com  Fri Sep  4 13:20:54 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Fri, 4 Sep 2009 13:20:54 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re:
	UnsupportedOperationException: setProperty
Message-ID: <23994273.1252084854083.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

A search in the forum of the term "setProperty must be overridden by all subclasses of SOAPMessage" should have resulted in many forum posts that already cover this topic. Typically, the problem is that you are using JDK 6 (which you are), but you downloaded the JDK 5 variant of the JBoss AS binary - downloading the JDK 6 variant should fix this. 

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

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


From do-not-reply at jboss.com  Fri Sep  4 18:04:23 2009
From: do-not-reply at jboss.com (rsobchak)
Date: Fri, 4 Sep 2009 18:04:23 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - having trouble
	specifying namespace
Message-ID: <8470884.1252101863975.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I have a web service on JBoss-4.2.3.GA using JBossWS-native-3.0.3.GA. The web service is currently not specifying a namespace. 
I am having problems specifying the namespace.

The interface is defined as follows 

  | @WebService(name = "MyWebService")
  | @SOAPBinding(style = Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
  | 
  | public interface MyWebService
  | {
  |     public void myMethod(String param1);
  | }
  | 

The implementation is defined as follows

  | @WebService(serviceName = "MyEndpointService",
  |                      portName = "MyEndpointPort",
  |                      endpointInterface = "com.myCompany.MyWebService")
  | @WebContext(contextRoot = "/myCompany", urlPattern = "/myWebService")
  | @Stateless
  | 
  | public class myEJB 
  | {
  |     public void myMethod(String param1)
  |     {
  |     }
  | }
  | 

This deploys and creates a single WSDL in the default (i.e. package) namespace.


When I attempt to specify the targetNamespace, the WSDL is broken into two with one importing the other.

The code with the namespace is as follows


  | @WebService(name = "MyWebService",
  |                      targetNamespace="http://com.myCompany")
  | @SOAPBinding(style = Style.DOCUMENT, use=Use.LITERAL, parameterStyle=ParameterStyle.WRAPPED)
  | 
  | public interface MyWebService
  | {
  |     public void myMethod(String param1);
  | }
  | 


  | @WebService(serviceName = "MyEndpointService",
  |                     portName = "MyEndpointPort",
  |                     targetNamespace="http://com.myCompany"
  |                     endpointInterface = "com.myCompany.MyWebService")
  | @WebContext(contextRoot = "/myCompany", urlPattern = "/myWebService")
  | @Stateless
  | 
  | public class myEJB 
  | {
  |     public void myMethod(String param1)
  |     {
  |     }
  | }
  | 


The resulting WSDL looks like this

  | <definitions name="MyEndpointService" targetNamespace="http://com.myCompany/" xmlns="http://schemas.xmlsoap.org/wsdl/" 
  |              xmlns:jaxws="http://java.sun.com/xml/ns/jaxws" xmlns:ns1="http://default.package/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" 
  |              xmlns:tns="http://com.myCompany/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  |   <import location="http://hostname:8080/myCompany/myWebService?wsdl&resource=MyWebService_PortType12338.wsdl" namespace="http://default.package/" /> 
  |   <service name="MyEndpointService">
  |      <port binding="ns1:MyWebServiceBinding" name="MyEndpointPort">
  |         <soap:address location="http://hostname:8080/myCompany/myWebService" /> 
  |      </port>
  |   </service>
  | </definitions>
  | 

According to the java doc on WebService annotation specifying the same targetNamespace on the interface and implemenation would result in one WSDL 
in the same namespace. Am I missing something?



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

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


From do-not-reply at jboss.com  Sat Sep  5 18:27:55 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Sat, 5 Sep 2009 18:27:55 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: vfs problems with
	jboss web service
Message-ID: <33286634.1252189675943.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

According to the stack trace you provided it won't be web services issue. Try to post your problem to faces forum. 

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

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


From do-not-reply at jboss.com  Sat Sep  5 18:30:26 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Sat, 5 Sep 2009 18:30:26 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: running 'ant
	tests' with 3.2.0.GA fails
Message-ID: <32960036.1252189826263.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

It looks like a test issue, so you can ignore this failure ;)

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

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


From do-not-reply at jboss.com  Wed Sep  9 06:44:11 2009
From: do-not-reply at jboss.com (_guido)
Date: Wed, 9 Sep 2009 06:44:11 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - multiple wsdl request
	from client
Message-ID: <1443561.1252493051738.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

i sniffed the network traffic between my webservice deployed on jboss 5.1 and my standalone webservice client.
 
Everything works fine but the client requests 4 times the wsdl-file from the server before it "really" uses the webservice. 
The debug output at the client didnt tell me why and i didnt find any other hint at the internet.

Do you have an idea?

thanks,
guido




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

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


From do-not-reply at jboss.com  Wed Sep  9 11:32:42 2009
From: do-not-reply at jboss.com (young_matthewd)
Date: Wed, 9 Sep 2009 11:32:42 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Resteasy Mapped
	annotation on class rather than service
Message-ID: <6548709.1252510362148.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

using resteasy 1.1 together with latest jaxb 2.2

using Jackson transformation of JAXB classes and added the Mapped annotation to the called service.  works fine.  but i wanted to add the namespace mapping (to a json name) against the actual JAXB class being marshalled.  so i created a XJC plugin to write the necessary annotation in every class (giving the json name equal to the package name just to keep it simple).  read from the PDF guide that this would work:

"You use the @Mapped annotation on your JAXB classes, on your JAX-RS resource method, or on the parameter you are unmarshalling"

but the namespace isn't recognized at runtime and i get the classic:

"java.lang.IllegalStateException: Invalid JSON namespace"


bug?

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

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


From do-not-reply at jboss.com  Wed Sep  9 17:23:12 2009
From: do-not-reply at jboss.com (fsamz)
Date: Wed, 9 Sep 2009 17:23:12 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Premature end of file
Message-ID: <21307621.1252531392011.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi all
I am having an issue trying to consume java web services from a .net client. It works fine most of the time but every so often jboss throws a fatal error - 'premature end of file' (soap request exception). I have tried looking into the issue but have not found anything that would cause this.
Does any one have any idea what might be causing this?

Thanks
fsamz

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

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


From do-not-reply at jboss.com  Wed Sep  9 18:10:08 2009
From: do-not-reply at jboss.com (gturner)
Date: Wed, 9 Sep 2009 18:10:08 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: http proxy error
	profile
Message-ID: <9558811.1252534208337.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello, I'm having the same problem, opened a bug - 
https://jira.jboss.org/jira/browse/JBREM-1153

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

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


From do-not-reply at jboss.com  Wed Sep  9 18:25:58 2009
From: do-not-reply at jboss.com (rsobchak)
Date: Wed, 9 Sep 2009 18:25:58 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: having trouble
	specifying namespace
Message-ID: <30320805.1252535158849.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Update:

If I use the ant task wsprovide to build the wsdl from the code the wsdl is created with the correct namespace. 

What is different between having JBoss create the wsdl at run-time vs using the wsprovide task to create the wsdl at compile-time? 

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

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


From do-not-reply at jboss.com  Wed Sep  9 23:09:41 2009
From: do-not-reply at jboss.com (spinder)
Date: Wed, 9 Sep 2009 23:09:41 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - JbossWs SSL endpoint:
	enabled how to test?
Message-ID: <4993216.1252552181285.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I have enabled my webservice endpoints over both HTTP and SSL.  I can access the wsdls over both HTTP and HTTPS, but both wsdls point to the HTTP server and port in the wsdl served up.  I know the unsecured access point works but I'd like to verify that the SSL connection works as well if both HTTP and HTTPS are enabled.

I'm generating clients using the wsdlLocation to point to the https endpoint. 

Is there any way to force and verify my SSL jbossws clients to use the SSL connection only?   Anyone ever tried this?  Preliminary tests with jaxws clients seem to always use the HTTP endpoint only... 

Thanks in advance for any suggestions/tips/replies.  

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

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


From do-not-reply at jboss.com  Thu Sep 10 01:53:08 2009
From: do-not-reply at jboss.com (young_matthewd)
Date: Thu, 10 Sep 2009 01:53:08 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Resteasy Mapped
	annotation on class rather than service
Message-ID: <22345971.1252561988326.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

not a bug.....maybe just wishful thinking....

basically i have a carrier class mapped via Hibernate and holds a property mapped to an XML column (feature with DB2 9 and Oracle 10/11).  that property in the xsd schema (which gets parsed by XJC into pojos) is marked as an "xs:any" element.  when i run XJC i populate the generated classes with XmlRootElements and the resteasy Mapped/XmlNsMap so the JSON provider knows how to map namespaces.  thought since the XmlNsMap was defined for every class that the provider would know what to do with the namespaces recursively.  but the XmlNsMap has to be applied to the carrier class.  then everything works fine.

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

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


From do-not-reply at jboss.com  Thu Sep 10 04:05:20 2009
From: do-not-reply at jboss.com (_guido)
Date: Thu, 10 Sep 2009 04:05:20 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: multiple wsdl
	request from client
Message-ID: <24671742.1252569920496.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Not a real solution for this:

*i used the jboss webservice libraries at the client because i needed them to get the WS-Security to work (the jdk6 ws implementation doesnt work for me)

*this configruation i dont need no more, because i dont use the WS-Security to secure my webservices

*i removed the configuration and if i use the jdk ws implementation -> only 1 wsdl request will be done by the client

bye,
guido

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

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


From fodie.toure at gmail.com  Thu Sep 10 05:54:30 2009
From: fodie.toure at gmail.com (fodie toure)
Date: Thu, 10 Sep 2009 11:54:30 +0200
Subject: [jbossws-users] [jbossWS] org.jboss.ws.WSException: Invalid number
	of payload elements: 2
Message-ID: <52c189e70909100254m7eaae752wf997711a85a8b5f3@mail.gmail.com>

Hey everyone.

>From the get go let make clear that i'm pretty to news to JBoss Ws , having
say that here my question:

I have successfully deployed an ebj3 webservice on Jboss-5.0.GA server, when
i try to consume the services from a php5 client i've got this exception
message:

11:14:16,781 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.WSException: Invalid number of payload elements: 2
        at
org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:379)
        at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:194)
        at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        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(SecurityContextEstablishme
        at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmen
        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:601)
        at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)


Does anyone know  what 's my stupe mistake?
please educate me on the exception.

best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090910/d4a1117d/attachment.html 

From fodie.toure at gmail.com  Thu Sep 10 05:59:21 2009
From: fodie.toure at gmail.com (fodie toure)
Date: Thu, 10 Sep 2009 11:59:21 +0200
Subject: [jbossws-users] [jbossws web services users]Invalid number of
	payload elements: 2
Message-ID: <52c189e70909100259n671dd9e8h1d61823be5095d4c@mail.gmail.com>

Hey everyone.

>From the get go let me make clear that i'm pretty to new to JBoss Ws ,
having say that, here my question:

I have successfully deployed an ebj3 webservice on
Jboss-5.0.GA<http://jboss-5.0.ga/>server, when i try to consume the
services from a php5 client i've got this
exception message:

11:14:16,781 ERROR [SOAPFaultHelperJAXWS] SOAP request exception
org.jboss.ws.WSException: Invalid number of payload elements: 2
        at
org.jboss.ws.core.CommonSOAPBinding.unbindRequestMessage(CommonSOAPBinding.java:379)
        at
org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:194)
        at
org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474)
        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(SecurityContextEstablishme
        at
org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmen
        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:601)
        at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
        at java.lang.Thread.run(Thread.java:619)


Does anyone know  what 's my stupid mistake?
please educate me on this particular exception.

best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090910/02dae6db/attachment.html 

From do-not-reply at jboss.com  Thu Sep 10 15:28:59 2009
From: do-not-reply at jboss.com (rsobchak)
Date: Thu, 10 Sep 2009 15:28:59 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: having trouble
	specifying namespace
Message-ID: <3612426.1252610939806.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Update:

I removed the SEI so now the web service looks like this

  | @WebService(serviceName = "MyEndpointService",
  |                     portName = "MyEndpointPort",
  |                     targetNamespace="http://com.myCompany")
  | @WebContext(contextRoot = "/myCompany", urlPattern = "/myWebService")
  | @Stateless
  | 
  | public class MyEJB 
  | {
  |     public void myMethod(String param1)
  |     {
  |     }
  | }
  | 

When this is deployed with JBoss creating the WSDL, the namespace in the WSDL is "http://com.myCompany" with no import of another WSDL.

What am I doing wrong when specifying the SEI and its targetNamespace that causes the WSDL to import another WSDL with the default package as the namespace (and not the targetNamespace)?


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

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


From do-not-reply at jboss.com  Sat Sep 12 10:41:51 2009
From: do-not-reply at jboss.com (agohar)
Date: Sat, 12 Sep 2009 10:41:51 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - JBossWS wsdl not
	accessible
Message-ID: <3071730.1252766511744.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I am currently working on Jboss esb with Jboss 5 and JDK 6. I am trying to use SOAPProcessor action for esb. I've created a webservice using jbossws annotations and deployed it as part of my esb archive. I can see the webservice endpoint from jbossws fine. But when i click it to access the webservice, it doesn't work. I tried to create the webservice client using wsconsume for this service but client can't access wsdl and return 404.  I can see wsdl generated in data folder fine. I've tried to use -b 0.0.0.0 while starting jboss but in vain.

Any idea what i am doing wrong?

Thanks

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

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


From do-not-reply at jboss.com  Mon Sep 14 12:14:28 2009
From: do-not-reply at jboss.com (jasonstratton)
Date: Mon, 14 Sep 2009 12:14:28 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Rehosting Axis web
	services on JBoss
Message-ID: <27741652.1252944868619.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am  working on an effort to rehost a number of web services that use Axis 1 and 2 onto JBoss. I imagine that they could be ported fairly straightforward, but I was wondering whether there would be any advantage converting them over to JBossWS. And if so, would there be any suggestions for approaching this conversion.

My first thought would be to run wsconsume on the existing WSDL and then use the generated endpoint to call the legacy code and rip out the Axis stuff.

Any thoughts would be most welcome. Thank you.

Jason

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

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


From do-not-reply at jboss.com  Mon Sep 14 15:48:18 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Mon, 14 Sep 2009 15:48:18 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - JBossWS on Geronimo?
Message-ID: <30824103.1252957698809.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

Is is possible to deploy a JBossWS web service on Apache Geronimo?  If so, can anyone point me to a guide on how to do so?

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

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


From do-not-reply at jboss.com  Tue Sep 15 04:17:08 2009
From: do-not-reply at jboss.com (dennyxu)
Date: Tue, 15 Sep 2009 04:17:08 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Can not generate java
	bean from a wsdl
Message-ID: <31704943.1253002628986.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi 
I get this error when I try to create a top down web service from a valid wsdl using jbossws jax-ws tools:
Error: Could not import. (use --verbose to see full traces) Error: WsImport invocation failed. Try the verbose switch for more information 

anybody know what's the problem ?

Thanks
Denny

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

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


From do-not-reply at jboss.com  Tue Sep 15 15:28:01 2009
From: do-not-reply at jboss.com (rishikvr)
Date: Tue, 15 Sep 2009 15:28:01 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Having problem
	Deploying web service in jboss-4.2.2.GA AS
Message-ID: <33026665.1253042881423.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am trying to deployed wsdl( code generated by jbossws-native-3.0.5GA) on jboss AS 4.2.2.GA. I am getting the following error when it tries to load the DDMS 2.0 specific files. Have no problem deploying using axis. If any body have similar issues loading the DDMS 2.0 using the jbossws please point me in the right direction. Thanks

14:44:03,616 ERROR [JBossXSErrorHandler] JBossWS_metadata.dod.mil_mdr_ns_DDMS_2.0_4300038152969289372.xsd[domain:http://www.w3.org/TR/xml-schema-1]::[key=src-resolve.4.2]::Message=src-resolve.4.2: Error resolving component 'ns3:type'. It was detected that 'ns3:type' is in namespace 'http://www.w3.org/1999/xlink', but components from this namespace are not referenceable from schema document 'file:/
C:/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metadata.dod.mil_mdr_ns_DDM
S_2.0_4300038152969289372.xsd'. If this is the incorrect namespace, perhaps the prefix of 'ns3:type' needs to be changed. If this is the correct namespace, then  an appropriate 'import' tag should be added to 'file:/C:/jboss-4.2.2.GA/server/default/tmp/jbossws/JBossWS_metadata.dod.mil_mdr_ns_DDMS_2.0_4300038152969289372
.xsd'.

14:44:03,616 ERROR [JBossXSErrorHandler] JBossWS_metadata.dod.mil_mdr_ns_DDMS_2.
0_4300038152969289372.xsd[domain:http://www.w3.org/TR/xml-schema-1]::[key=s4s-elt-invalid-content.1]::Message=s4s-elt-invalid-content.1: The content of '#AnonType_linkRelatedResourceRelatedResourcesType' is invalid.  Element 'attribute' is invalid, misplace, or occurs too often

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

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


From do-not-reply at jboss.com  Tue Sep 15 16:42:12 2009
From: do-not-reply at jboss.com (neillott)
Date: Tue, 15 Sep 2009 16:42:12 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - JBoss 5.1.0 GA
	Webservice Stack question
Message-ID: <12869644.1253047332598.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I noticed there are three different webservice stacks, native jboss, apache cxf, and metro.  

Can you use all stacks simultaneously in one jboss instance?

Thanks,

Neil

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

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


From do-not-reply at jboss.com  Tue Sep 15 19:34:11 2009
From: do-not-reply at jboss.com (meetoblivion)
Date: Tue, 15 Sep 2009 19:34:11 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Can not generate
	java bean from a wsdl
Message-ID: <5415691.1253057651226.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

did you try using the verbose option? do you have the WSDL available for us to look at?

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

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


From do-not-reply at jboss.com  Wed Sep 16 02:18:54 2009
From: do-not-reply at jboss.com (dennyxu)
Date: Wed, 16 Sep 2009 02:18:54 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Can not generate
	java bean from a wsdl
Message-ID: <19467286.1253081934009.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Just found the issue should be related to the jira https://jira.jboss.org/jira/browse/JBWS-2687, it says that you guys will provide a "nocompile" option in command line, which version of SOA-P / EAP will contain this fix?

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

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


From do-not-reply at jboss.com  Wed Sep 16 02:43:14 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Wed, 16 Sep 2009 02:43:14 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBoss 5.1.0 GA
	Webservice Stack question
Message-ID: <10047131.1253083394270.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Only one SOAP stack can be used in one JBoss instance.

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

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


From do-not-reply at jboss.com  Thu Sep 17 10:16:34 2009
From: do-not-reply at jboss.com (karnivas)
Date: Thu, 17 Sep 2009 10:16:34 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - HTTPRouter and
	Attachments
Message-ID: <11182061.1253196994701.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

We are using jboss-soa-p.4.3.0

We are trying to send an attachment with the request through SOAP UI to a ESB Service which has Apache HTTP Router.

SAXParseException - "Content not allowed in prolog" is been thrown.

Why the HTTPRouter is throwing this exception ? 
Is there a way to set the Content-Type as TEXT ?

Any thoughts might be helpful

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

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


From do-not-reply at jboss.com  Thu Sep 17 13:42:21 2009
From: do-not-reply at jboss.com (andrei.harangus)
Date: Thu, 17 Sep 2009 13:42:21 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re:
	NotSerializableException: org.jboss.ws.core.soap.SOAPFau
Message-ID: <9401968.1253209341272.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Using JBoss 4.2.3GA, jbossws 3.0.1
Have the same issue basically.
Has this been fixed / is it considered "fixable"?

  | org.jboss.soa.esb.couriers.CourierMarshalUnmarshalException: Failed to serialize ESB Message.
  | at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:203)
  | at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:189)
  | at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:860)
  | at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.faultTo(ActionProcessingPipeline.java:810)
  | at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:665)
  | at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:585)
  | at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:419)
  | at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:548)
  | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
  | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
  | at java.lang.Thread.run(Thread.java:619)
  | Caused by: java.io.IOException: Util.serialize caught XMLStreamException:
  | at org.jboss.soa.esb.util.Util.serialize(Util.java:197)
  | at org.jboss.internal.soa.esb.couriers.JmsCourier.deliver(JmsCourier.java:197)
  | ... 10 more
  | Caused by: javax.xml.stream.XMLStreamException: org.jboss.soa.esb.MarshalException: Failed to encode value
  | at org.jboss.internal.soa.esb.message.format.xml.marshal.MarshalUnmarshalManager.marshal(MarshalUnmarshalManager.java:149)
  | at org.jboss.internal.soa.esb.message.format.xml.BodyImpl.writeChildContent(BodyImpl.java:146)
  | at org.jboss.internal.soa.esb.util.stax.ElementContent.writeContent(ElementContent.java:41)
  | at org.jboss.internal.soa.esb.util.stax.StreamHelper.writeElement(StreamHelper.java:125)
  | at org.jboss.internal.soa.esb.message.format.xml.MessageImpl.writeChildContent(MessageImpl.java:230)
  | at org.jboss.internal.soa.esb.util.stax.ElementContent.writeContent(ElementContent.java:41)
  | at org.jboss.soa.esb.util.Util.serialize(Util.java:188)
  | ... 11 more
  | Caused by: org.jboss.soa.esb.MarshalException: Failed to encode value
  | at org.jboss.internal.soa.esb.message.format.xml.marshal.SerializedMarshalUnmarshalPlugin.marshal(SerializedMarshalUnmarshalPlugin.java:87)
  | at org.jboss.internal.soa.esb.message.format.xml.marshal.MarshalUnmarshalManager.marshal(MarshalUnmarshalManager.java:145)
  | ... 17 more
  | Caused by: java.io.NotSerializableException: org.jboss.ws.core.soap.SOAPFaultImpl
  | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
  | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
  | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
  | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  | at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
  | at java.lang.Throwable.writeObject(Throwable.java:648)
  | at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)
  | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:597)
  | at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
  | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
  | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
  | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
  | at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:416)
  | at java.lang.Throwable.writeObject(Throwable.java:648)
  | at sun.reflect.GeneratedMethodAccessor157.invoke(Unknown Source)
  | at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | at java.lang.reflect.Method.invoke(Method.java:597)
  | at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
  | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
  | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
  | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
  | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
  | at org.jboss.internal.soa.esb.util.Encoding.encodeObject(Encoding.java:59)
  | at org.jboss.internal.soa.esb.message.format.xml.marshal.SerializedMarshalUnmarshalPlugin.marshal(SerializedMarshalUnmarshalPlugin.java:83)
  | ... 18 more
  | 

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

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


From do-not-reply at jboss.com  Thu Sep 17 14:29:36 2009
From: do-not-reply at jboss.com (neillott)
Date: Thu, 17 Sep 2009 14:29:36 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - JBoss 3.2.0 native
	stack won't start
Message-ID: <24311985.1253212176883.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

If I take jboss 5.1.0.GA-jdk6 and the jboss 3.2.0 native stack it won't start.

I install the jboss 3.2.0 native stack by changing the ant.properties.example and pointing it to my jboss home directory.  In addition, I change the jboss.server.instance=all.

I start jboss using run.sh -c all

I get the following exception:

2009-09-17 12:24:02,597 INFO  [org.jboss.web.WebService] (main) Using RMI server codebase: http://127.0.0.1:8083/
2009-09-17 12:24:06,629 ERROR [STDERR] (main) [Deprecated] Xalan: org.apache.xml.serializer.XMLEntities
2009-09-17 12:24:08,309 WARN  [org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext] (main) Unable to register deployment mbean WSKernelLocator
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="WSKernelLocator",type=Component already registered.
	at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:756)
	at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:233)
	at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
	at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426)
	at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)
	at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.registerMBeans(AbstractDeploymentContext.java:1030)
	at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.addComponent(AbstractDeploymentContext.java:722)
	at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.addComponent(AbstractDeploymentUnit.java:251)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:52)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
	at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
	at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
	at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
	at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
	at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
	at org.jboss.Main.boot(Main.java:221)
	at org.jboss.Main$1.run(Main.java:556)
	at java.lang.Thread.run(Thread.java:637)
2009-09-17 12:24:08,320 WARN  [org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext] (main) Unable to register deployment mbean WSMBeanServerLocator
javax.management.InstanceAlreadyExistsException: jboss.deployment:id="WSMBeanServerLocator",type=Component already registered.
	at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistry.java:756)
	at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:233)
	at sun.reflect.GeneratedMethodAccessor75.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
	at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
	at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
	at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
	at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
	at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
	at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
	at org.jboss.mx.server.MBeanServerImpl$3.run(MBeanServerImpl.java:1431)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:1426)
	at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.java:376)
	at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.registerMBeans(AbstractDeploymentContext.java:1030)
	at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentContext.addComponent(AbstractDeploymentContext.java:722)
	at org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit.addComponent(AbstractDeploymentUnit.java:251)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:52)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
	at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
	at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
	at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
	at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
	at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
	at org.jboss.Main.boot(Main.java:221)
	at org.jboss.Main$1.run(Main.java:556)
	at java.lang.Thread.run(Thread.java:637)
2009-09-17 12:24:08,396 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Real: name=vfsfile:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/ state=PreReal mode=Manual requiredState=Real
org.jboss.deployers.spi.DeploymentException: Error deploying: vfsfile:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/
	at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:136)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.deploy(AbstractRealDeployerWithInput.java:125)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployerWithInput.internalDeploy(AbstractRealDeployerWithInput.java:102)
	at org.jboss.deployers.spi.deployer.helpers.AbstractComponentDeployer.internalDeploy(AbstractComponentDeployer.java:78)
	at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
	at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
	at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
	at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
	at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
	at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
	at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:361)
	at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
	at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
	at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
	at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
	at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
	at org.jboss.system.server.profileservice.repository.AbstractProfileService.activateProfile(AbstractProfileService.java:306)
	at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:271)
	at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
	at org.jboss.Main.boot(Main.java:221)
	at org.jboss.Main$1.run(Main.java:556)
	at java.lang.Thread.run(Thread.java:637)
Caused by: java.lang.IllegalArgumentException: Exception loading class for ScopeKey addition.
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:67)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.deploy(BeanMetaDataFactoryVisitor.java:126)
	... 34 more
Caused by: java.lang.ClassNotFoundException: org.jboss.wsf.container.jboss50.transport.DeploymentAspectHttpServer from BaseClassLoader at 24459efb{VFSClassLoaderPolicy at 56c88357{name=vfsfile:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/ domain=ClassLoaderDomain at 1afd1810{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss.bootstrap.NoAnnotationURLClassLoader at f7e6a96} roots=[MemoryContextHandler at 103215428[path= context=vfsmemory://a3z30-dco8i7-fzptyx1n-1-fzptz3de-e real=vfsmemory://a3z30-dco8i7-fzptyx1n-1-fzptz3de-e], FileHandler at 1722395267[path=jbossws.deployer context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/], DelegatingHandler at 217690909[path=jbossws.deployer/FastInfoset.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/FastInfoset.jar], DelegatingHandler at 1566456722[path=jbossws.deployer/jboss-jaxb-intros.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/jboss-jaxb-intros.jar], DelegatingHandler at 1436098081[path=jbossws.deployer/jbossws-common.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/jbossws-common.jar], DelegatingHandler at 931738734[path=jbossws.deployer/jbossws-framework.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/jbossws-framework.jar], DelegatingHandler at 282148414[path=jbossws.deployer/jbossws-jboss510.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/jbossws-jboss510.jar], DelegatingHandler at 424501522[path=jbossws.deployer/jbossws-native-core.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/jbossws-native-core.jar], DelegatingHandler at 656404920[path=jbossws.deployer/jettison.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/jettison.jar], DelegatingHandler at 573995801[path=jbossws.deployer/netty.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/netty.jar], DelegatingHandler at 650885083[path=jbossws.deployer/policy.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/policy.jar], DelegatingHandler at 143892163[path=jbossws.deployer/wsdl4j.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/wsdl4j.jar], DelegatingHandler at 328997019[path=jbossws.deployer/xmlsec.jar context=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/ real=file:/Users/neil/Business/SnowyRangeConsulting/projects/twc/depot/server/ivy/thirdparty-repository-redist/jboss/jboss/MAS/intellij/server/all/deployers/jbossws.deployer/xmlsec.jar]]  delegates=null exported=[, org.jboss.ws.tools.schema, com.ibm.wsdl.xml, org.codehaus.jettison.json, org.jboss.wsf.common.injection.finders, org.jboss.ws.extensions.wsrm.protocol.spec200502, org.apache.xml.security.resource.schema, javax.wsdl.extensions.mime, org.jboss.ws.extensions.wsrm.protocol, schema, org.apache.xml.security.utils, com.ibm.wsdl.util, org.apache.xml.security.exceptions, org.jboss.ws.extensions.wsrm.protocol.spec200702, org.jboss.wsf.stack.jbws, org.jboss.netty.bootstrap, org.jboss.ws.metadata.builder.jaxrpc, org.jboss.netty.handler.timeout, META-INF.maven.org.codehaus.jettison.jettison, org.jboss.ws.extensions.policy.deployer, org.jboss.ws.extensions.wsrm.transport, org.jboss.webservices.integration.deployers.deployment, javax.wsdl, org.jboss.ws.extensions.addressing.map, org.jboss.ws.jaxrpc, org.jboss.ws.tools.wsdl, org.jboss.netty.handler.codec.replay, org.jboss.netty.handler.codec.string, org.jboss.wsf.test, org.jvnet.fastinfoset, org.jboss.ws.extensions.eventing.jaxws, org.jboss.ws.extensions.eventing.deployment, com.ibm.wsdl.extensions.schema, org.jboss.netty.container.microcontainer, org.jboss.webservices.integration.invocation, org.jboss.webservices.integration.config, org.jboss.netty.container.guice, org.jboss.wsf.common.management, org.jboss.ws.extensions.validation, org.jboss.ws.core.client.ssl, javax.wsdl.extensions, com.sun.xml.fastinfoset.dom, org.jboss.netty.buffer, javax.wsdl.factory, org.jboss.ws.metadata.wsdl.xsd, org.jboss.netty.handler.codec.http, com.sun.xml.fastinfoset.org.apache.xerces.util, org.jboss.ws.core.jaxws.spi, org.jboss.wsf.common.concurrent, com.sun.xml.fastinfoset.tools, org.apache.xml.security.keys.storage, META-INF.services, com.sun.xml.fastinfoset.stax.events, org.apache.xml.security.resource, org.jboss.ws.extensions.addressing.metadata, org.jboss.ws.core.jaxrpc.handler, org.jboss.ws.extensions.eventing.mgmt, META-INF.maven.org.jboss.ws.native.jbossws-native-core, org.jboss.netty.util.internal, org.jboss.netty.handler.logging, com.sun.xml.fastinfoset.resources, org.jboss.ws.extensions.security.element, org.jboss.jaxb.intros.configmodel, org.jboss.ws.extensions.wsrm, META-INF.maven.org.jboss.ws.jbossws-framework, javax.xml.crypto.dsig.keyinfo, org.jboss.netty.util, org.jboss.ws.core.soap, javax.wsdl.extensions.schema, org.jboss.wsf.common.addressing, org.jboss.netty.handler.execution, org.apache.xml.security.keys, org.jboss.ws.extensions.policy.deployer.domainAssertion, org.jvnet.fastinfoset.stax, org.jboss.ws.tools.metadata, org.jboss.ws.core.jaxws.handler, dtd, org.jboss.ws.extensions.wsrm.server, org.jboss.ws.metadata.umdm, org.codehaus.jettison.mapped, javax.xml.crypto.dsig.dom, com.sun.xml.fastinfoset.stax.util, org.jboss.wsf.framework.invocation, org.jboss.ws.extensions.wsrm.common, org.jboss.wsf.common.handler, org.jboss.ws.extensions.addressing.soap, com.sun.xml.fastinfoset.vocab, org.jboss.ws.metadata.accessor, org.jboss.ws.core, org.jboss.ws.core.jaxws.client, com.sun.xml.fastinfoset.alphabet, org.jboss.wsf.common.utils, javax.xml.crypto.dsig.spec, org.jboss.ws.extensions.wsrm.transport.backchannel, org.jboss.ws.metadata.config.binding, org.apache.xml.security.c14n.implementations, com.ibm.wsdl, org.jboss.ws.extensions.wsrm.api, org.jboss.ws.tools.client, org.jboss.ws.tools.interfaces, org.jboss.wsf.framework.serviceref, org.jboss.ws.extensions.eventing.metadata, org.jboss.netty.handler.codec.embedder, org.jboss.ws.extensions.eventing.common, org.apache.ws.policy, org.jboss.netty.channel.socket.oio, org.jboss.ws.core.binding, org.jboss.ws.metadata.builder, org.jboss.netty.handler.codec.frame, org.jboss.ws.extensions.wsrm.protocol.spi, org.jboss.ws.extensions.xop, org.jboss.netty.handler.codec.oneone, com.ibm.wsdl.extensions.soap12, org.apache.xml.security.keys.storage.implementations, org.jboss.ws.extensions.wsrm.jaxws, org.jboss.ws.extensions.policy.deployer.exceptions, org.jboss.ws.core.transport.jms, com.sun.xml.fastinfoset.stax, javax.wsdl.extensions.soap, org.jvnet.fastinfoset.sax, META-INF, org.jboss.ws.extensions.security.jaxrpc, org.jboss.ws.metadata.jaxrpcmapping, org.jboss.ws.feature, org.jboss.ws.extensions.wsrm.common.serialization, org.jboss.netty.channel.socket, org.jboss.ws.core.soap.attachment, org.apache.xml.security.transforms.params, org.jboss.ws.tools.jaxws.impl, javax.wsdl.extensions.soap12, org.jboss.ws.tools.helpers, org.jcp.xml.dsig.internal, org.jboss.ws.tools.factories, javax.wsdl.extensions.http, org.jboss.ws.core.jaxws.wsaddressing, org.jboss.netty.channel.xnio, org.jboss.webservices.integration.util, org.codehaus.jettison, javax.wsdl.xml, org.jboss.ws.tools.io, org.jboss.netty.channel.local, org.apache.xml.security.transforms, org.jboss.wsf.common.reflection, org.jboss.wsf.common.injection.resolvers, org.jboss.ws.extensions.policy.metadata, org.jboss.wsf.common.integration, org.jboss.wsf.framework.management.recording, org.jboss.webservices.integration.deployers, org.apache.xml.security.utils.resolver, org.apache.xml.security.encryption, META-INF.license, org.jboss.netty.channel.socket.nio, org.jboss.ws.extensions.policy, org.jvnet.fastinfoset.sax.helpers, org.jboss.ws.core.client, com.sun.xml.fastinfoset.stax.factory, org.jboss.ws.extensions.addressing.jaxrpc, org.apache.xml.security.algorithms.implementations, org.jboss.netty.channel, javax.xml.crypto, org.jboss.wsf.framework.deployment, org.jboss.ws.extensions.wsrm.policy, org.jboss.webservices.integration.tomcat, org.jboss.netty.container.spring, com.ibm.wsdl.extensions.mime, org.jboss.ws.extensions.security.operation, org.apache.xml.security.keys.keyresolver.implementations, org.jboss.ws.extensions.policy.deployer.util, org.jboss.ws.extensions.security.exception, org.jboss.ws.core.jaxrpc, org.apache.xml.security.algorithms, org.jboss.ws.util.xml, org.jboss.ws.extensions.addressing.jaxws, org.jboss.jaxb.intros.handlers, org.jboss.ws.metadata.config.jaxrpc, org.codehaus.jettison.badgerfish, org.apache.xml.security.keys.content.keyvalues, org.apache.xml.security, org.apache.xml.security.keys.content, org.apache.ws.policy.util, org.jboss.ws.extensions.xop.jaxws, org.jboss.wsf.common.servlet, org.jboss.webservices.integration.injection, org.jboss.netty.container.osgi, org.jboss.ws.core.server, com.sun.xml.fastinfoset.algorithm, META-INF.maven.org.jboss.ws.jbossws-common, org.apache.xml.security.utils.resolver.implementations, com.ibm.wsdl.util.xml, org.jboss.ws.metadata.wsdl, org.codehaus.jettison.util, com.ibm.wsdl.factory, org.jboss.ws.extensions.addressing, org.apache.xml.security.signature, org.jboss.ws.annotation, org.jboss.ws.extensions.xop.jaxrpc, org.jboss.ws.extensions.eventing, org.jboss.webservices.integration.metadata, org.jboss.ws.extensions.json, org.jboss.ws.metadata.builder.jaxws, org.jboss.ws.metadata.config.jaxws, org.jboss.ws.tools.mapping, META-INF.maven.org.jboss.ws.jbossws-jboss510, org.jboss.ws.core.utils, org.jboss.ws.extensions.security, org.apache.xml.security.keys.keyresolver, org.jboss.ws.extensions.wsrm.persistence, org.jboss.ws.tools.ant, org.jboss.netty.handler.codec.serialization, org.jboss.ws.tools.config, org.jboss.ws.tools.exceptions, org.jboss.ws.metadata.wsse, org.jboss.ws.extensions.security.jaxws, org.jcp.xml.dsig.internal.dom, org.jboss.webservices.integration.security, org.jboss.netty.handler.codec.base64, org.apache.xml.security.transforms.implementations, org.jboss.jaxb.intros, org.jboss.ws.metadata.wsdl.xmlschema, org.jboss.ws.tools, org.jboss.ws.core.jaxrpc.binding.jbossxb, org.jboss.ws.core.jaxws.binding, com.ibm.wsdl.extensions, org.jboss.ws.metadata.config, org.jboss.ws.extensions.wsrm.config, org.jboss.ws.extensions.policy.annotation, org.jboss.netty.handler.ssl, com.sun.xml.fastinfoset.util, com.sun.xml.fastinfoset, org.jboss.netty.handler.codec.protobuf, org.jboss.netty.channel.socket.http, org.jboss.netty.channel.group, org.jboss.ws.extensions.security.nonce, org.apache.xml.security.c14n.helper, org.jboss.wsf.framework.http, org.jboss.wsf.framework.management, org.jboss.wsf.common.logging, org.jboss.ws.core.jaxrpc.binding, org.jboss.netty.logging, META-INF.maven.org.jboss.netty.netty, org.apache.xml.security.c14n, org.jboss.ws.core.jaxrpc.client, com.ibm.wsdl.extensions.soap, org.jboss.ws.core.jaxws, org.apache.xml.security.keys.content.x509, org.jboss.wsf.common, org.jboss.ws, org.jboss.wsf.common.injection, com.ibm.wsdl.extensions.http, org.jboss.ws.extensions.security.auth.callback, com.sun.xml.fastinfoset.sax, javax.xml.crypto.dsig, org.jboss.netty.handler.stream, org.jboss.wsf.framework, javax.xml.crypto.dom] <IMPORT-ALL>NON_EMPTY}}
	at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:448)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:254)
	at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataFactoryVisitor.addBeanComponent(BeanMetaDataFactoryVisitor.java:63)
	... 35 more

And the following exception when I go to:
http://localhost:8080/jbossws/services

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

javax.servlet.ServletException: Servlet.init() for servlet ContextServlet threw exception
	org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
	org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	java.lang.Thread.run(Thread.java:637)

root cause

org.jboss.wsf.spi.WSFException: Failed to provide SPI 'class org.jboss.wsf.spi.management.EndpointRegistryFactory'
	org.jboss.wsf.framework.DefaultSPIProvider.getSPI(DefaultSPIProvider.java:149)
	org.jboss.wsf.framework.management.ContextServlet.init(ContextServlet.java:63)
	org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
	org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
	org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
	org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
	org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
	org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
	org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
	org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
	org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	java.lang.Thread.run(Thread.java:637)

Thanks,

Neil


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

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



From do-not-reply at jboss.com  Fri Sep 18 10:28:52 2009
From: do-not-reply at jboss.com (andrei.harangus)
Date: Fri, 18 Sep 2009 10:28:52 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re:
	NotSerializableException: org.jboss.ws.core.soap.SOAPFau
Message-ID: <3695605.1253284132775.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Sorry, it's jbossws 3.1.0

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

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


From do-not-reply at jboss.com  Fri Sep 18 11:49:55 2009
From: do-not-reply at jboss.com (dietice)
Date: Fri, 18 Sep 2009 11:49:55 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Port does not contain
	operation meta data for
Message-ID: <16556683.1253288995800.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

hi there. i have created a ws wich works as expected in e.g. soapUI.

but i have a few problems with a clint. its generated xml:


  | <?xml version="1.0"?>
  | <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
  | xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:SupportServiceSvc="http://ws.controller.mydomain.de/" xsl:version="1.0">
  |   <soap:Body>
  |     <login xsi:type="SupportServiceSvc:login">
  |       <username>admin</username>
  |       <password>admin</password>
  |     </login>
  |   </soap:Body>
  | </soap:Envelope>
  | 

is rejected with 

  | 17:32:32,703 ERROR [SOAPFaultHelperJAXRPC] SOAP request exception
  | javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://ws.controller.support.navitas.de/}SupportServicePort does not contain operation meta data for:
  |  login
  | 

and 


  | <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
  |    <env:Header/>
  |    <env:Body>
  |       <env:Fault>
  |          <faultcode>env:Client</faultcode>
  |          <faultstring>Endpoint {http://ws.controller.support.navitas.de/}SupportServicePort does not contain operation meta data for: login</faultstring>
  |       </env:Fault>
  |    </env:Body>
  | </env:Envelope>
  | 

the xml seems to be the same with soapUI except this "<login xsi:type="SupportServiceSvc:login">" stuff instead of "<SupportServiceSvc:login>" which is generated by e.g soapUI


  | <?xml version="1.0"?>
  | <soap:Envelope 
  | 
  | xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" 
  | xmlns:xsl="http://www.w3.org/1999/XSL/Transform" 
  | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
  | xmlns:xs="http://www.w3.org/2001/XMLSchema" 
  | xmlns:SupportServiceSvc="http://ws.controller.support.navitas.de/" 
  | xsl:version="1.0">
  | 
  |   <soap:Body>
  |     <SupportServiceSvc:login>
  |       <username>admin</username>
  |       <password>admin</password>
  |     </SupportServiceSvclogin>
  |   </soap:Body>
  | </soap:Envelope>
  | 

how do i make jboss accept this xml?

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

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


From do-not-reply at jboss.com  Mon Sep 21 01:58:18 2009
From: do-not-reply at jboss.com (richard.opalka@jboss.com)
Date: Mon, 21 Sep 2009 01:58:18 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JBoss 3.2.0 native
	stack won't start
Message-ID: <11689829.1253512698734.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Neil,

   this was fixed in trunk. See JBWS-2759 for available workarounds.

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

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


From do-not-reply at jboss.com  Mon Sep 21 14:51:32 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Mon, 21 Sep 2009 14:51:32 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Creating two
	difference WS-Eventing events in the same conte
Message-ID: <17778342.1253559092637.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Greetings all,

As I understand the WS-Eventing section of the doc, I need to create a class that extends AbstractEventSourceEndpoint and one that extends AbstractSubscriptionManagerEndpoint for each event I want to define. The reason being that each event, presumably, has a different wsdl associated with it which defines the event message. I was able to implement a single event within a web context and am not trying to implement a second. However, when I look at the wsdls for the two events, the soap:address of the wsdl:port in the wsdl:service name="EventingService" for each points to the same location. I expected it to point to two difference addresses? Am I missing something or this the expected behavior? If the later, how do I register more than one event within the same web context with different wsdls?

Earnie! 

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

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


From do-not-reply at jboss.com  Tue Sep 22 13:26:19 2009
From: do-not-reply at jboss.com (earniedyke)
Date: Tue, 22 Sep 2009 13:26:19 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Creating two
	difference WS-Eventing events in the same c
Message-ID: <758302.1253640379724.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

After some more trial-and-error I have discovered that if I have more than one Event Source endpoint defined in a war within an ear the last endpoint defined as a servlet in the web.xml becomes the soap:address in the wsdl:service definition for all Service endpoints. Can I only define one service endpoint per war?

Earnie!

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

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


From do-not-reply at jboss.com  Tue Sep 22 23:41:07 2009
From: do-not-reply at jboss.com (pramod_bs)
Date: Tue, 22 Sep 2009 23:41:07 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - jbossws 5
Message-ID: <31821954.1253677267928.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I was having a web services client in 4.2.1. When I moved the client to Jboss 5.1 environment (with the default jbossws native) I get the following error.(Version: jbossws-native-3.1.2.GA 
Build: 200905081542 )


  | 
  | 23:27:52,860 ERROR [CommonClient] Exception caught while (preparing for) performing the invocation: 
  | javax.xml.ws.soap.SOAPFaultException: An empty soap message was received.
  | 	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.invoke(ClientProxy.java:150)
  | 	at $Proxy437.search(Unknown Source)
  | 	at gov.gsa.autoauctions.services.ThunderStoneSearchClient.doThunderStoneSearch(ThunderStoneSearchClient.java:55)
  | 	at gov.gsa.autoauctions.session.ThunderStoneSearchFacade.thunderSearch(ThunderStoneSearchFacade.java:574)
  | 	at gov.gsa.autoauctions.session.ThunderStoneSearchFacade.doTextSearch(ThunderStoneSearchFacade.java:121)
  | 	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.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
  | 	at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
  | 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor$InvocationContext.proceed(InvocationContextInterceptor.java:138)
  | 	at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
  | 	at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:29)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:31)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
  | 	at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50)
  | 	at sun.reflect.GeneratedMethodAccessor378.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.ejb3.interceptors.aop.EJB3InterceptorInterceptor.invoke(EJB3InterceptorInterceptor.java:83)
  | 	at org.jboss.ejb3.interceptors.aop.EJB3InterceptorInterceptor.invoke(EJB3InterceptorInterceptor.java:70)
  | 	at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:59)
  | 	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
  | 	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
  | 	at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source)
  | 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 	at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
  | 	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_2743224.invoke(InvocationContextInterceptor_z_fillMethod_2743224.java)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
  | 	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_2743224.invoke(InvocationContextInterceptor_z_setup_2743224.java)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:60)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
  | 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
  | 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
  | 	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
  | 	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
  | 	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
  | 	at $Proxy434.doTextSearch(Unknown Source)
  | 	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.seam.util.Reflections.invoke(Reflections.java:22)
  | 	at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
  | 	at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
  | 	at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:43)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
  | 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 	at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
  | 	at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54)
  | 	at org.javassist.tmp.java.lang.Object_$$_javassist_3.doTextSearch(Object_$$_javassist_3.java)
  | 	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.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329)
  | 	at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:274)
  | 	at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59)
  | 	at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65)
  | 	at org.jboss.el.parser.AstValue.invoke(AstValue.java:96)
  | 	at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
  | 	at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
  | 	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
  | 	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
  | 	at javax.faces.component.UICommand.broadcast(UICommand.java:387)
  | 	at org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
  | 	at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
  | 	at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
  | 	at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
  | 	at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
  | 	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
  | 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
  | 	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
  | 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
  | 	at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
  | 	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
  | 	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368)
  | 	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495)
  | 	at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
  | 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 	at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 	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.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
  | 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
  | 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 	at java.lang.Thread.run(Thread.java:595)
  | 23:27:57,529 ERROR [STDERR] javax.xml.ws.soap.SOAPFaultException: An empty soap message was received.
  | 23:27:57,529 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:84)
  | 23:27:57,529 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:107)
  | 23:27:57,529 ERROR [STDERR] 	at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579)
  | 23:27:57,529 ERROR [STDERR] 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381)
  | 23:27:57,529 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:290)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
  | 23:27:57,544 ERROR [STDERR] 	at $Proxy437.search(Unknown Source)
  | 23:27:57,544 ERROR [STDERR] 	at gov.gsa.autoauctions.services.ThunderStoneSearchClient.doThunderStoneSearch(ThunderStoneSearchClient.java:55)
  | 23:27:57,544 ERROR [STDERR] 	at gov.gsa.autoauctions.session.ThunderStoneSearchFacade.thunderSearch(ThunderStoneSearchFacade.java:574)
  | 23:27:57,544 ERROR [STDERR] 	at gov.gsa.autoauctions.session.ThunderStoneSearchFacade.doTextSearch(ThunderStoneSearchFacade.java:121)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 23:27:57,544 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor$InvocationContext.proceed(InvocationContextInterceptor.java:138)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:28)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:77)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:29)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:31)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.GeneratedMethodAccessor378.invoke(Unknown Source)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 23:27:57,544 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.EJB3InterceptorInterceptor.invoke(EJB3InterceptorInterceptor.java:83)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.EJB3InterceptorInterceptor.invoke(EJB3InterceptorInterceptor.java:70)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:59)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 23:27:57,544 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_2743224.invoke(InvocationContextInterceptor_z_fillMethod_2743224.java)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_2743224.invoke(InvocationContextInterceptor_z_setup_2743224.java)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:60)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:81)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:176)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.session.SessionSpecContainer.invoke(SessionSpecContainer.java:216)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164)
  | 23:27:57,544 ERROR [STDERR] 	at $Proxy434.doTextSearch(Unknown Source)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 23:27:57,544 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:43)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.core.SynchronizationInterceptor.aroundInvoke(SynchronizationInterceptor.java:32)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54)
  | 23:27:57,544 ERROR [STDERR] 	at org.javassist.tmp.java.lang.Object_$$_javassist_3.doTextSearch(Object_$$_javassist_3.java)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  | 23:27:57,544 ERROR [STDERR] 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  | 23:27:57,544 ERROR [STDERR] 	at java.lang.reflect.Method.invoke(Method.java:585)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:329)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:274)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.el.parser.AstMethodSuffix.getValue(AstMethodSuffix.java:59)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.el.parser.AstMethodSuffix.invoke(AstMethodSuffix.java:65)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.el.parser.AstValue.invoke(AstValue.java:96)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
  | 23:27:57,544 ERROR [STDERR] 	at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
  | 23:27:57,544 ERROR [STDERR] 	at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
  | 23:27:57,544 ERROR [STDERR] 	at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at javax.faces.component.UICommand.broadcast(UICommand.java:387)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:321)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:296)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:253)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:466)
  | 23:27:57,544 ERROR [STDERR] 	at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
  | 23:27:57,544 ERROR [STDERR] 	at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
  | 23:27:57,544 ERROR [STDERR] 	at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
  | 23:27:57,544 ERROR [STDERR] 	at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:368)
  | 23:27:57,544 ERROR [STDERR] 	at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:495)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:56)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
  | 23:27:57,544 ERROR [STDERR] 	at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
  | 23:27:57,544 ERROR [STDERR] 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
  | 23:27:57,544 ERROR [STDERR] 	at java.lang.Thread.run(Thread.java:595)
  | 
  | 

Please help...What could be the problem

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

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


From do-not-reply at jboss.com  Wed Sep 23 06:07:59 2009
From: do-not-reply at jboss.com (SkyMe)
Date: Wed, 23 Sep 2009 06:07:59 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - log4j for several apps
Message-ID: <9640928.1253700479279.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello everyone!
I want to deploy several .ear apps to the JBoss AS and I want them to use separate log4j configs (e.g. each project uses its own log4j.xml).
I've found advices about using separate log4j configs for diffrent contexts for one app, but the question is about diffrent apps.
Thank you!

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

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


From do-not-reply at jboss.com  Wed Sep 23 06:59:48 2009
From: do-not-reply at jboss.com (SkyMe)
Date: Wed, 23 Sep 2009 06:59:48 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: log4j for several
	apps
Message-ID: <12646376.1253703588403.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I redirected this subj into appropriate topic.
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256590#4256590

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

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


From do-not-reply at jboss.com  Wed Sep 23 07:49:35 2009
From: do-not-reply at jboss.com (beve)
Date: Wed, 23 Sep 2009 07:49:35 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - @Resource injection
	for jaxws handler support in AS 4.2.3
Message-ID: <10790002.1253706575815.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi, 

I've stumbled across this issue: http://jira.jboss.org/jira/browse/JBWS-2074 which has been fixed and included in 3.2.1.GA.
In the release notes (http://jboss.org/file-access/default/members/jbossws/downloads/ReleaseNotes-jbossws-native-3.1.2.GA.txt) 
I found :
anonymous wrote : * [JBWS-2074] - Resource injection in jaxws endpoints and handlers

I also noticed the following:
anonymous wrote : * [JBWS-2612] - Remove AS 4.2.x support from all stacks

Does this mean that I cannot upgrade jbossws on AS 4.2.3 to support Resource injection?

I've been trying to upgrade jbossws but without any luck and just wanted to know if this is possible.

Thanks,

/Daniel

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

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


From do-not-reply at jboss.com  Wed Sep 23 08:37:59 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 23 Sep 2009 08:37:59 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: @Resource
	injection for jaxws handler support in AS 4.2.
Message-ID: <362044.1253709479320.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Daniel,
I'm sorry, the latest JBossWS version supporting AS 4.2.3.GA is JBossWS 3.1.1.
http://www.jboss.org/community/wiki/JBossWS-SupportedTargetContainers


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

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


From do-not-reply at jboss.com  Wed Sep 23 08:40:50 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 23 Sep 2009 08:40:50 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Can not generate
	java bean from a wsdl
Message-ID: <24448676.1253709650310.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Depends on when the fix for that is ported to EAP branch. If you're allowed to, verify there's a JBPAPP jira issue for porting that immediately as soon as it's done upstream, otherwise create it.
If you're not allowed to just let me know.

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

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


From do-not-reply at jboss.com  Wed Sep 23 09:01:21 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 23 Sep 2009 09:01:21 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: JbossWs SSL
	endpoint: enabled how to test?
Message-ID: <21820816.1253710881387.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,
take a look at http://www.jboss.org/community/wiki/JBossWS-UserGuide#Address_rewrite.
Besides that, you can force the endpoint address to use in the client, casting the port to BindingProvider and then setting it there.

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

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


From do-not-reply at jboss.com  Wed Sep 23 09:59:48 2009
From: do-not-reply at jboss.com (adinn)
Date: Wed, 23 Sep 2009 09:59:48 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Intermittent failures
	in multithreaded test
Message-ID: <13936157.1253714388269.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I am getting intermittent and varying errors out of the Netty/SOAP layer when running the JBossTS WSTX tests on JBossAS 6.0.0 trunk i.e. using JBossWS 3.2.0 Native. The error does not vary from run to run but different errors manifest if I modify the test or run it under different circumstances. Here is one sample stack trace:

  | 13:54:39,868 ERROR [org.jboss.ws.core.CommonClient] Exception caught while (preparing for) performing the invocation: : org.jboss.ws.WSException: Cannot obtain deserializer factory for: [xmlType={http://docs.oasis-open.org/ws-tx/wscoor/2006/06}RegisterResponseType,javaType=class org.oasis_open.docs.ws_tx.wscoor._2006._06.RegisterResponseType]
  | 	at org.jboss.ws.core.soap.XMLContent.getDeserializerFactory(XMLContent.java:285)
  | 	at org.jboss.ws.core.soap.XMLContent.unmarshallObjectContents(XMLContent.java:176)
  | 	at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:96)
  | 	at org.jboss.ws.core.soap.SOAPContentElement.transitionTo(SOAPContentElement.java:140)
  | 	at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:85)
  | 	at org.jboss.ws.core.soap.SOAPContentElement.getObjectValue(SOAPContentElement.java:172)
  | 	at org.jboss.ws.core.EndpointInvocation.transformPayloadValue(EndpointInvocation.java:273)
  | 	at org.jboss.ws.core.EndpointInvocation.getReturnValue(EndpointInvocation.java:197)
  | 	at org.jboss.ws.core.CommonClient.syncOutputParams(CommonClient.java:512)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:398)
  | 	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.invoke(ClientProxy.java:150)
  | 	at $Proxy177.registerOperation(Unknown Source)
  | 	at com.arjuna.wsc11.RegistrationCoordinator.register(RegistrationCoordinator.java:56)
  | 	at com.arjuna.mwlabs.wst11.at.remote.TransactionManagerImple.registerParticipant(TransactionManagerImple.java:191)
  | 	at com.arjuna.mwlabs.wst11.at.remote.TransactionManagerImple.enlistForCompletion(TransactionManagerImple.java:136)
  | 	at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.enlistCompletionParticipants(UserTransactionImple.java:224)
  | 	at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:89)
  | 	at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.begin(UserTransactionImple.java:75)
  | 	at com.arjuna.wst11.tests.junit.basic.ThreadedObject.run(ThreadedTransaction.java:53)
  | 

and here is another


  | 13:54:41,828 ERROR [org.jboss.ws.core.CommonClient] Exception caught while (preparing for) performing the invocation: : java.lang.IllegalStateException: Cannot find property: javax.xml.ws.handler.message.outbound
  | 	at org.jboss.ws.core.jaxws.handler.MessageContextJAXWS.processPivot(MessageContextJAXWS.java:110)
  | 	at org.jboss.ws.core.jaxws.client.ClientImpl.processPivot(ClientImpl.java:355)
  | 	at org.jboss.ws.core.CommonClient.processPivotInternal(CommonClient.java:480)
  | 	at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:347)
  | 	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.invoke(ClientProxy.java:150)
  | 	at $Proxy178.commitOperation(Unknown Source)
  | 	at com.arjuna.webservices11.wsat.client.CompletionCoordinatorClient.sendCommit(CompletionCoordinatorClient.java:87)
  | 	at com.arjuna.wst11.stub.CompletionStub.commit(CompletionStub.java:44)
  | 	at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.commitWithoutAck(UserTransactionImple.java:333)
  | 	at com.arjuna.mwlabs.wst11.at.remote.UserTransactionImple.commit(UserTransactionImple.java:116)
  | 	at com.arjuna.wst11.tests.junit.basic.ThreadedObject.run(ThreadedTransaction.java:61)
  | 

As you no doubt have already deciphered from the stack trace one of these exceptions happens under the TX begin operation and the other under the TX commit.

After seeing these two errors I then get repeated errors when I rerun the test

  | 14:50:23,718 ERROR [org.jboss.ws.core.soap.EnvelopeBuilderDOM] Exception while building envelope: ClientAbortException:  java.io.IOException: Invalid chunk header
  | 	at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:342)
  | 	at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:372)
  | 	at org.apache.catalina.connector.InputBuffer.readByte(InputBuffer.java:354)
  | 	at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:105)
  | 	at org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read(Unknown Source)
  | 	at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
  | 	at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown Source)
  | 	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
  | 	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
  | 	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
  | 	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
  | 	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
  | 	at org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:201)
  | 	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:84)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:294)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:453)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:294)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:204)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:130)
  | 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:273)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277)
  | 	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:126)
  | 	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:358)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
  | 	at java.lang.Thread.run(Thread.java:619)
  | Caused by: java.io.IOException: Invalid chunk header
  | 	at org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:278)
  | 	at org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:132)
  | 	at org.apache.coyote.http11.InternalInputBuffer.doRead(InternalInputBuffer.java:706)
  | 	at org.apache.coyote.Request.doRead(Request.java:428)
  | 	at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:332)
  | 	... 41 more
  | 


  | 14:50:23,736 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception: org.jboss.ws.core.CommonSOAPFaultException
  | 	at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:94)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:294)
  | 	at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:453)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:294)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:204)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:130)
  | 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:273)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277)
  | 	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:126)
  | 	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:358)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
  | 	at java.lang.Thread.run(Thread.java:619)
  | 

and also


  | 14:50:23,736 ERROR [org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC] SOAP request exception: javax.xml.rpc.soap.SOAPFaultException
  | 	at org.jboss.ws.core.jaxrpc.SOAPFaultHelperJAXRPC.exceptionToFaultMessage(SOAPFaultHelperJAXRPC.java:189)
  | 	at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:183)
  | 	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:490)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:294)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:204)
  | 	at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:130)
  | 	at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
  | 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
  | 	at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
  | 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:273)
  | 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
  | 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:277)
  | 	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:126)
  | 	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:358)
  | 	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
  | 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
  | 	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
  | 	at java.lang.Thread.run(Thread.java:619)
  | 

My test runs 10 web service transactions in parallel, each in its own thread. The TX begin operation employs a JaxWS request to activate the TX and a second JAxWS request to register the client as a termination client. The latter is where the first error manifests. The commit operation employs JaxWS request to actually terminate the TX and this is where the second error manifests.

Which of the initial two errors actually happens and in how many of the threads depends upon what I run. When I run the full WSTX 1.1. test suite in a newly booted AS I get multiple instances of each of the initial two  exceptions in various of the threads yetsome threads also run without exceptions. If I cut out all other tests in the test suite the multi-threaded test runs without error. In other circumstances I have just seen multiple occurences of the second error.

The same test code ran without error on 5.1.0.GA.



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

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


From do-not-reply at jboss.com  Wed Sep 23 10:22:25 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 23 Sep 2009 10:22:25 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Intermittent
	failures in multithreaded test
Message-ID: <925644.1253715745285.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Andrew,
any chance you can try with trunk or a SNAPSHOT/Beta1 of 3.2.1 I can produce for you? Asking as a lot has changed in the mean time...

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

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


From do-not-reply at jboss.com  Wed Sep 23 10:26:11 2009
From: do-not-reply at jboss.com (pramod_bs)
Date: Wed, 23 Sep 2009 10:26:11 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: jbossws 5
Message-ID: <19412794.1253715971023.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Environment
JBoss 5.1
jbossws-native-3.1.2.GA 
Seam 2.1

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

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


From do-not-reply at jboss.com  Wed Sep 23 12:50:13 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Wed, 23 Sep 2009 12:50:13 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Intermittent
	failures in multithreaded test
Message-ID: <11373245.1253724613341.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

JBossWS-Native 3.2.1.Beta1 is in the repo now. Can you try with that please? Thanks!

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

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


From do-not-reply at jboss.com  Thu Sep 24 02:42:31 2009
From: do-not-reply at jboss.com (nicholasDK)
Date: Thu, 24 Sep 2009 02:42:31 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Error when calling web
	service within JBoss
Message-ID: <13554565.1253774551772.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I'm working on a java application which uses a simple dummy web service for test purposes.

My app is deployed in an ear-file placed in the JBoss 4.2.2 Deploy folder. The web services is a jar-file deployed in the Deploy folder as well.

My problem is that the application 'hangs' whenever it comes to the web service call within the code. So basically the app tries to calls a web service in the same app server (JBoss).

If i change my endpoint from using localhost for the address and instead use a web service on another machine on the internet everything works fine.

Does anyone have an idea of what could be the problem?? Thanks...

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

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


From do-not-reply at jboss.com  Thu Sep 24 03:21:44 2009
From: do-not-reply at jboss.com (beve)
Date: Thu, 24 Sep 2009 03:21:44 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: @Resource
	injection for jaxws handler support in AS 4.2.
Message-ID: <7446151.1253776904724.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Alessio, 

No problems, just happy to know that I should not continue trying to upgrade :)

Thanks,

/Daniel

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

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


From do-not-reply at jboss.com  Thu Sep 24 04:00:37 2009
From: do-not-reply at jboss.com (Josief)
Date: Thu, 24 Sep 2009 04:00:37 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: error when using
	wsgen to generet wsdl
Message-ID: <4891682.1253779237461.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

The topic was sleeping but I had the same issue and I found this solution, using wsgen as an ant  task:

The problem was the classpath. This is my wsgen task:

		
			
		
		
			
				
				
				
			
		
	

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

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


From do-not-reply at jboss.com  Thu Sep 24 04:01:41 2009
From: do-not-reply at jboss.com (Josief)
Date: Thu, 24 Sep 2009 04:01:41 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: error when using
	wsgen to generet wsdl
Message-ID: <226372.1253779301792.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

<target name="build-server-java" description="Generate the WSDL files for the webservices" depends="compile">
  | 		<taskdef name="wsgen" classname="com.sun.tools.ws.ant.WsGen">
  | 			<classpath refid="build.classpath" />
  | 		</taskdef>
  | 		<wsgen genwsdl="true" keep="true" verbose="true" destdir="${wsdl.dir}" sei="yourPackage.YourClass">
  | 			<classpath>
  | 				<pathelement path="${lib.dir}/ejb-api.jar"/>
  | 				<pathelement path="${lib.dir}/jboss-seam.jar"/>
  | 				<path location="${jar.dir}" />
  | 			</classpath>
  | 		</wsgen>
  | 	</target>

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

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


From do-not-reply at jboss.com  Thu Sep 24 11:00:10 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Thu, 24 Sep 2009 11:00:10 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Error when calling
	web service within JBoss
Message-ID: <10611518.1253804410336.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

How are you starting the app server? Are you using the -b option and if so what hostname/IP address are you passing?

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

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


From do-not-reply at jboss.com  Thu Sep 24 11:19:18 2009
From: do-not-reply at jboss.com (skerstetter)
Date: Thu, 24 Sep 2009 11:19:18 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Cannot Access Secure
	EJB3 Web Service
Message-ID: <6865868.1253805558378.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I have a web service that worked fine in AS 4.2.1GA, but since porting to 5.1.0GA, I have been unable to access it if it is secure.  If I remove authMethod=BASIC setting of the WebContext, I can access the ejb, but it is not secure.

I am using the native stack, version 3.2.0GA.

Here is my interface definition (simplified):

  | @WebService
  | @SOAPBinding(style = SOAPBinding.Style.RPC)
  | public interface Inquiry { 
  | 
  |     String echo(@WebParam(name="echoText", mode=Mode.IN) String echoText);
  | 

Here is my EJB3 definition:

  | @WebService(endpointInterface="com.foo.Inquiry")
  | @WebContext(contextRoot="check-inquiry", /* SEK TODO: not working */ authMethod="BASIC" /**/, secureWSDLAccess=false) 
  | @Stateless
  | @SecurityDomain("my-security-domain")
  | @TransactionAttribute(TransactionAttributeType.SUPPORTS)  //we do not require a transaction. we do not perform any updates.
  | @Interceptors({PerformanceProfiler.class, ExceptionLogger.class})
  | public class InquiryImpl extends BasePersistentContextHolder implements Inquiry {
  | 
  |     @Override
  |     public String echo(final String echoText) {
  |         getLog().debug("echo=[" + echoText+ "]");
  |         return echoText;
  |     }
  | 

Here is my jax-rpc client code:

  |     private Inquiry getService(final String username, final String password, final boolean withAuth) throws MalformedURLException, ServiceException {
  |         Stub stub = (Stub) new InquiryService_Impl().getInquiryPort();
  |         stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, "http://localhost:8080/check-inquiry/InquiryImpl?wsdl");
  | 
  |         
  |         if (withAuth) {
  |             stub._setProperty(javax.xml.rpc.Stub.USERNAME_PROPERTY, username);
  |             stub._setProperty(javax.xml.rpc.Stub.PASSWORD_PROPERTY, password);
  |         }
  |         
  |         return (Inquiry) stub;
  |     }
  | 

Let's see, I've got the custom security domain configured in conf/login-config.xml.  I've read through the documentation and tried a number of things with other configuration files, like jboss-wsse-server.xml in META-INF.  Nothing has worked.  I am deploying as an ejb-jar file inside of an ear file.

I'm hoping that someone can see some inconsistency in this all that I have missed. 

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

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


From do-not-reply at jboss.com  Thu Sep 24 11:30:09 2009
From: do-not-reply at jboss.com (skerstetter)
Date: Thu, 24 Sep 2009 11:30:09 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Cannot Access
	Secure EJB3 Web Service
Message-ID: <3985215.1253806209203.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

here is the unit test failure:


  | 	request requires HTTP authentication: Unauthorized; nested exception is: request requires HTTP authentication: Unauthorized

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

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


From do-not-reply at jboss.com  Thu Sep 24 17:10:23 2009
From: do-not-reply at jboss.com (Oberiko)
Date: Thu, 24 Sep 2009 17:10:23 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - WSDL 2.0 supported?
Message-ID: <20627487.1253826623919.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hello,

This likely seems like an obvious question, but both Google and the search on these forums is turning up almost nothing.

Does JBossWS (native) support WSDL 2.0?  If so, are there any drawbacks to using it (i.e., can't use WS-RM or anything).

Thanks.

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

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


From do-not-reply at jboss.com  Fri Sep 25 08:28:34 2009
From: do-not-reply at jboss.com (adinn)
Date: Fri, 25 Sep 2009 08:28:34 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Intermittent
	failures in multithreaded test
Message-ID: <13228043.1253881714330.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Alessio,

I will try it as soon as I can.


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

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


From do-not-reply at jboss.com  Fri Sep 25 11:26:27 2009
From: do-not-reply at jboss.com (lespoches)
Date: Fri, 25 Sep 2009 11:26:27 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: avoid
	lazy-initialization exceptions
Message-ID: <32995119.1253892387904.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I think the solution is to use @XmlAccessorFactory on Entity Bean and override default accessor ! 
But by default, Jboss do not exploit this annotation when creating JAXBContext and i can't find how to enable this Binding customization.

If anyone have an idea, help would be greatly appreciated 
Jo

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

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


From do-not-reply at jboss.com  Fri Sep 25 11:28:38 2009
From: do-not-reply at jboss.com (sthatcher)
Date: Fri, 25 Sep 2009 11:28:38 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Authenticating SOAP
	Requests with WSSE UsernameToken does no
Message-ID: <20242820.1253892518598.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I have created a simple EJB3 project and exposed it as a web service (your typical Echo service).  I'm using WSSE UsernameToken headers in the SOAP requests to send authentication info.  I can successfully authenticate using a username and digesting the password (e.g. Base64 encode of the SHA-1 hash).

However, when I encorporate the Created node and add to the digest I get an "Invalid User" exception. But, I can use just the hash of the password (without the created node) and authenticate successfully.  According to the docs from the OASIS site the digest is computed as (taken from Web Services Security UsernameToken Profile):

  | Password_Digest = Base64 ( SHA-1 ( nonce + created + password ) ) 
  | 

I'm currently not using a Nonce since the spec says that both the Nonce and the Created are optional. 

It's as if the server is ignoring the fact that the created node exists.  I'm not fully confident that I have the jboss-wsse-server.xml file set up or even the security header.  See below for the appropriate files.  Any thoughts would be appreciated.

EJB3 Service:

  | package com.test;
  | 
  | import javax.annotation.security.RolesAllowed;
  | import javax.ejb.Stateless;
  | import javax.jws.WebMethod;
  | import javax.jws.WebParam;
  | import javax.jws.WebResult;
  | import javax.jws.WebService;
  | 
  | import org.jboss.ws.annotation.EndpointConfig;
  | 
  | @Stateless
  | @WebService(endpointInterface = "com.test.IEchoSession", serviceName="EchoService", portName="EchoServiceSOAP")
  | @EndpointConfig(configName = "Standard WSSecurity Endpoint")
  | public class EchoSession implements IEchoSession {
  | 
  | 	/**
  | 	 * 
  | 	 */
  | 	private static final long serialVersionUID = 1L;
  | 
  | 	@Override
  | 	@WebMethod(operationName="Echo")
  | 	@WebResult(partName="EchoResponse")
  | 	@RolesAllowed(value={"friend"})
  | 	public String echo(@WebParam(partName="text") String text) {
  | 		return "You said: " + text;
  | 	}
  | 
  | }
  | 

jboss.xml (in the EJB3 META-INF folder):
<?xml version="1.0" encoding="utf-8"?>
  | <jboss>        
  | 	<security-domain>java:/jaas/MyRealm</security-domain>
  | 	<webservices>
  | 		<context-root>/echo</context-root>
  | 	</webservices>
  | 	 <enterprise-beans>
  | 		<session>
  | 			<ejb-name>EchoSession</ejb-name>
  | 			<port-component>
  | 				<port-component-name>EchoSession</port-component-name>
  | 				<port-component-uri>/EchoService</port-component-uri>
  | 				<transport-guarantee>NONE</transport-guarantee>
  | 				<secure-wsdl-access>false</secure-wsdl-access>
  | 			</port-component>
  | 		</session>
  | 	</enterprise-beans>      
  | 
  | </jboss> 

jboss-wsse-server.xml (also in the META-INF):
<jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
  |                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |                    xsi:schemaLocation="http://www.jboss.com/ws-security/config
  |                    http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd">
  |      <config>
  |      	<username/>
  |      	<timestamp ttl="300"/>
  |   		<timestamp-verification createdTolerance="100" warnCreated="false" expiresTolerance="100" warnExpires="false" />
  | 	    <authenticate>
  | 	      <usernameAuth/>
  | 	    </authenticate>
  |      </config>
  |   </jboss-ws-security>
  | 

On the client side (flex component) the following header get's added to the request:

	
  | private function addWSSEHeader(): SOAPHeader {
  | 	
  | 	var date : Date = new Date();
  | 	_ds = getDateString(date);
  | 	date.minutes += 3;
  | 
  | 	var plain : String = SHA1.hashToBase64(password.text);
  | 	
  | 	_password = SHA1.hashToBase64(_ds + password.text);
  | 	
  | 	trace("plain: " + plain);
  | 	trace("timestamp " + _password);
  |     var usernameTokenXML:XML =
  |         <wsse:Security 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">
  | 			<wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  | 				<wsu:Created>{_ds}</wsu:Created>
  | 				<wsu:Expires>{getDateString(date)}</wsu:Expires>
  | 			</wsu:Timestamp>			                
  |             <wsse:UsernameToken>
  |                 <wsse:Username Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">{username.text}</wsse:Username>
  |                 <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"
  |                     xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">{_password}</wsse:Password>
  | 				<wsu:Created>{_ds}</wsu:Created>
  |             </wsse:UsernameToken>
  |         </wsse:Security>
  |                 
  |     var wsse: Namespace = new Namespace("http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd");
  |     var wsseSecurity: QName = new QName(wsse.uri, "Security");
  |     var header: SOAPHeader = new SOAPHeader(wsseSecurity, {"wsse":"Security"});
  |     header.content = usernameTokenXML;
  | 
  |     return header;
  | }
  | 
  | 

And here is an example of the SOAP message:

  | <SOAP-ENV:Envelope xmlns:SOAP-ENV='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'><SOAP-ENV:Header><wsse:Security 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'>
  |       <wsu:Timestamp>
  |         <wsu:Created>2009-09-25T13:07:29Z</wsu:Created>
  |         <wsu:Expires>2009-09-25T13:10:29Z</wsu:Expires>
  |       </wsu:Timestamp>
  |       <wsse:UsernameToken>
  |         <wsse:Username Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd'>kermit</wsse:Username>
  |         <wsse:Password Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest'>lKnNIypKvfb27kzvQynQtS+iNUc=</wsse:Password>
  |         <wsu:Created>2009-09-25T13:07:29Z</wsu:Created>
  |       </wsse:UsernameToken>
  |     </wsse:Security></SOAP-ENV:Header><SOAP-ENV:Body>
  |     <tns:echo xmlns:tns='http://test.com/'>
  |       <arg0>test</arg0>
  |     </tns:echo>
  |   </SOAP-ENV:Body></SOAP-ENV:Envelope>
  | 

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

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


From do-not-reply at jboss.com  Fri Sep 25 16:27:20 2009
From: do-not-reply at jboss.com (jorgerst)
Date: Fri, 25 Sep 2009 16:27:20 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Exception with X509
	certificates on jbossws-native-3.1.1.GA
Message-ID: <2763386.1253910440539.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi!
  
  I'm having trouble to use WS-Security with X509 certificates. I've followed the instructions of the wiki ( http://www.jboss.org/community/wiki/JBossWS-NativeUserGuide#WSSecurity ). But when I invoke my service (using SoapUI, correctly configured with a X509 signed and encrypted SOAP request) I am getting the following exception:

ERROR [WSSecurityDispatcher] Internal error occured handling inbound message:
  | org.jboss.ws.extensions.security.exception.WSSecurityException: Currently only SubjectKeyIdentifiers are supported, was passed: http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3

Plus, my jboss-wsse-server.xml is like this:


  | <jboss-ws-security xmlns="http://www.jboss.com/ws-security/config"
  | 	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  | 	xsi:schemaLocation="http://www.jboss.com/ws-security/config jboss-wsse-server.xsd">    
  | 
  | 	<key-store-file>WEB-INF/wsse.keystore</key-store-file>
  | 	<key-store-password>jbossws</key-store-password>
  | 	<trust-store-file>WEB-INF/wsse.truststore</trust-store-file>
  | 	<trust-store-password>jbossws</trust-store-password>
  | 
  | 	<config>
  | 		<encrypt type="x509v3" alias="wsse" />
  | 		<sign type="x509v3" alias="wsse" />		
  | 		<requires>
  | 			<encryption />
  | 			<signature />
  | 		</requires>
  | 		<timestamp ttl="300" />
  | 	</config>
  | </jboss-ws-security>

  I'm using Sun JDK 1.5.0.15, JBoss AS 4.2.3 and jbossws-native-3.1.1.GA. 

  I'm not very familiar with the security stuff, so please, if anybody could help it will be great!
  
  Thanks in advance!

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

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


From do-not-reply at jboss.com  Fri Sep 25 21:32:18 2009
From: do-not-reply at jboss.com (sthatcher)
Date: Fri, 25 Sep 2009 21:32:18 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Authenticating
	SOAP Requests with WSSE UsernameToken doe
Message-ID: <12101930.1253928738422.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

I did a bit more investigation on this and found the crux of the issue but I'm not sure how to solve it.  In the login configuration for the realm you are supposed to use a UsernameTokenCallback object to update the digest based on the existence of a nonce or created.  However, on debugging, these values are always null.  And the init function sends a map with both keys (nonce and created) set to null.  So the question is what other configuration do I need to tell JBoss to pull out these header nodes and send to the callback handler.

The specific login config is as follows:

  |   <application-policy name="MyRealm">
  |     <authentication>
  |       <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule"
  |         flag="required">
  |     <!--
  |         <module-option name="usersProperties">props/myrealm-users.properties</module-option>
  |         <module-option name="rolesProperties">props/myrealm-roles.properties</module-option> -->
  |        <module-option name = "dsJndiName">java:/WSExampleDS</module-option>
  |        <module-option name = "principalsQuery">SELECT password FROM users WHERE username=?</module-option>
  |        <module-option name = "rolesQuery">SELECT r.role, 'Roles' FROM roles r join users u on u.id = r.userid WHERE u.username=?</module-option>
  |       <module-option name="hashAlgorithm">SHA</module-option>
  |       <module-option name="hashEncoding">BASE64</module-option>
  |       <module-option name="hashUserPassword">false</module-option>
  |       <module-option name="hashStorePassword">true</module-option>
  |  
  |         <module-option name="unauthenticatedIdentity">anonymous</module-option>
  |       <module-option name="storeDigestCallback">org.jboss.ws.extensions.security.auth.callback.UsernameTokenCallback</module-option>
  | 
  |       </login-module>
  |     </authentication>
  |   </application-policy>
  |  

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

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


From do-not-reply at jboss.com  Sat Sep 26 23:52:03 2009
From: do-not-reply at jboss.com (sthatcher)
Date: Sat, 26 Sep 2009 23:52:03 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Authenticating
	SOAP Requests with WSSE UsernameToken doe
Message-ID: <13800813.1254023523337.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Never mind, this is due to bug https://jira.jboss.org/jira/browse/JBWS-2640

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

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


From do-not-reply at jboss.com  Mon Sep 28 03:36:05 2009
From: do-not-reply at jboss.com (nicholasDK)
Date: Mon, 28 Sep 2009 03:36:05 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Error when calling
	web service within JBoss
Message-ID: <17047720.1254123365777.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Peter.
Thanks for answering my question.
I'm starting the server by running \jboss\bin\run.bat. I pass in some arguments from the batch file. One of these are the endpoint address: http://127.0.0.1:8080/[foldername]/[webservice_name]?wsdl. I'm ot using the -b parameter as far as i can see.

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

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


From do-not-reply at jboss.com  Mon Sep 28 07:45:13 2009
From: do-not-reply at jboss.com (adinn)
Date: Mon, 28 Sep 2009 07:45:13 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Intermittent
	failures in multithreaded test
Message-ID: <17140921.1254138313495.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi Alessio,

I built and installed the new stack and the problem went away :-)


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

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


From do-not-reply at jboss.com  Mon Sep 28 11:11:36 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Mon, 28 Sep 2009 11:11:36 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Intermittent
	failures in multithreaded test
Message-ID: <31952483.1254150696887.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

That's really good to know Andrew, thanks for the tests.
The GA version of 3.2.1 is coming around the end of October, btw.

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

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


From do-not-reply at jboss.com  Mon Sep 28 11:21:25 2009
From: do-not-reply at jboss.com (PeterJ)
Date: Mon, 28 Sep 2009 11:21:25 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Error when calling
	web service within JBoss
Message-ID: <18345998.1254151285667.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

When you start the app server, a few lines before the "started in xxx seconds" message there is a message that looks like this:

2009-09-20 12:03:28,485 INFO  [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080

Post what you are getting.


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

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


From do-not-reply at jboss.com  Tue Sep 29 13:37:27 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 29 Sep 2009 13:37:27 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: avoid
	lazy-initialization exceptions
Message-ID: <7179368.1254245847876.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

You can provide your own JAXBContextFactory, take a look at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory for instance. This way you can setup the property you need in the context at creation.

Then make sure your context factory is loaded by the JBossWS ServiceLoader (basically you might want to either set your factory through a System property or add a org.jboss.ws.core.jaxws.JAXBContextFactory file in META-INF/services somewhere in the classpath).

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

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


From do-not-reply at jboss.com  Tue Sep 29 13:39:32 2009
From: do-not-reply at jboss.com (alessio.soldano@jboss.com)
Date: Tue, 29 Sep 2009 13:39:32 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: avoid
	lazy-initialization exceptions
Message-ID: <7259358.1254245972992.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

INteresting link to better follow this topic: http://blogs.sun.com/searls/entry/jaxb_custom_accessor_for_marshalling

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

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


From do-not-reply at jboss.com  Wed Sep 30 03:53:52 2009
From: do-not-reply at jboss.com (lespoches)
Date: Wed, 30 Sep 2009 03:53:52 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: avoid
	lazy-initialization exceptions
Message-ID: <21107155.1254297232735.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

"alessio.soldano at jboss.com" wrote : You can provide your own JAXBContextFactory, take a look at org.jboss.ws.core.jaxws.CustomizableJAXBContextFactory for instance. This way you can setup the property you need in the context at creation.
  | 
  | Then make sure your context factory is loaded by the JBossWS ServiceLoader (basically you might want to either set your factory through a System property or add a org.jboss.ws.core.jaxws.JAXBContextFactory file in META-INF/services somewhere in the classpath).

Is there any sample on how to do that ?
Thanks a lot
Jonathan

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

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


From do-not-reply at jboss.com  Wed Sep 30 13:20:14 2009
From: do-not-reply at jboss.com (naduvath)
Date: Wed, 30 Sep 2009 13:20:14 -0400 (EDT)
Subject: [jbossws-users] [JBoss Web Services Users] - Re: Creating two
	difference WS-Eventing events in the same c
Message-ID: <19219481.1254331214699.JavaMail.jboss@nukes01.app.mwc.hst.phx2.redhat.com>

Hi,

I am implementing WS-Eventing on native stack of JBoss. Can you provide some samples of the same.

Thanks,
Sethu

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

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