From do-not-reply at jboss.com Mon Mar 2 01:29:43 2009 From: do-not-reply at jboss.com (chuaky) Date: Mon, 2 Mar 2009 01:29:43 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Upgrade AS 4.2.3 WS to 3.0.5 Message-ID: <32146957.1235975383038.JavaMail.jboss@colo-br-02.atl.jboss.com> hi, Recently i upgraded the WS module in Jboss Portal 2.7.1 (using AS 4.2.3) because i want to run it offline and there is this issue here: http://www.jboss.org/community/docs/DOC-12633 Later i notice that jbossws-client.jar is missing from my AS installation/client folder. It seems that jbossws-client.jar has been removed since jbossws-3.0.2. What is the new jars files after 3.0.2 that are equivalent to the old jbossws-client.jar. I need them to make a standalone web service client. Thank you. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214068#4214068 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214068 From do-not-reply at jboss.com Mon Mar 2 07:02:57 2009 From: do-not-reply at jboss.com (lukeb) Date: Mon, 2 Mar 2009 07:02:57 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Help with authMethod and security after JBoss501 upgrade Message-ID: <23092667.1235995377958.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm upgrading from 422 to 501 and I'm having security related issues which I'll explain below. I have a legacy webservice I expose in the following way. | @Stateless | @WebService(name = "MyWebService", targetNamespace = "http://my.services.web", serviceName = "MyWebServiceName") | @WebContext(contextRoot = "/MyEar", transportGuarantee = "NONE", authMethod = "NONE") | @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.WRAPPED, style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL) | @PermitAll | public final class MyWebServiceBean { | | @WebMethod | @PermitAll | public final String doStuff() { | return "i've done stuff"; | } | } | In 501 this all deploys ok and I can see the wsdl in the jbossws console. However when I try to call the webservice from my test harness, I get a 403 forbidden at the client and the following in the logs: | 10:32:14,657 DEBUG [MapperListener] Handle jboss.web:type=RequestProcessor,worker=http-0.0.0.0-8080,name=HttpRequest1 type : JMX.mbean.registered | 10:32:14,766 TRACE [SecurityRolesAssociation] Setting threadlocal:{} | 10:32:14,766 TRACE [JaccContextValve] MetaData:org.jboss.metadata.web.jboss.JBossWebMetaData at 1f:principalToRoleSetMap{} | 10:32:14,766 DEBUG [AuthenticatorBase] Security checking request POST /MyEar/MyWebServiceBean | 10:32:14,766 DEBUG [RealmBase] Checking constraint 'SecurityConstraint[/MyWebServiceBean]' against POST //MyWebServiceBean --> true | 10:32:14,782 DEBUG [AuthenticatorBase] Calling hasUserDataPermission() | 10:32:14,782 DEBUG [RealmBase] User data constraint has no restrictions | 10:32:14,828 TRACE [JBossAuthorizationContext] Control flag for entry:org.jboss.security.authorization.config.AuthorizationModuleEntry{org.jboss.security.authorization.mo | dules.DelegatingAuthorizationModule:{}REQUIRED}is:[REQUIRED] | 10:32:14,844 DEBUG [AuthenticatorBase] Calling authenticate() | 10:32:14,844 DEBUG [[/MyEar] User authentication is not required | 10:32:14,844 DEBUG [AuthenticatorBase] Calling accessControl() | 10:32:14,844 DEBUG [RealmBase] Checking roles null | 10:32:14,860 DEBUG [RealmBase] No user authenticated, cannot grant access | 10:32:14,860 TRACE [JBossWebRealm] hasResourcePerm:RealmBase says:false::Authz framework says:false:final=false | 10:32:14,860 DEBUG [AuthenticatorBase] Failed accessControl() test | 10:32:14,860 TRACE [SecurityRolesAssociation] Setting threadlocal:null | 10:32:14,860 TRACE [SecurityRolesAssociation] Setting threadlocal:null | The parts of the logging above that stand out to me are, [/MyEar] User authentication is not required and [RealmBase] No user authenticated, cannot grant access ...and these seem at odds with each other. I've tried setting @SecurityDomain to "" and that didn't make any difference. Note that my stateless bean is within an ejb3 jar within an ear. The ear has a custom security-domain declared in the jboss-app.xml. Does anyone have any suggestions, I need to web service to ideally work as before, changing the clients would have to be a last resort. Thanks Luke View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214137#4214137 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214137 From do-not-reply at jboss.com Mon Mar 2 08:05:29 2009 From: do-not-reply at jboss.com (jej2003) Date: Mon, 2 Mar 2009 08:05:29 -0500 (EST) Subject: [jbossws-users] [JBossWS] - RestEasy Security Message-ID: <21236351.1235999129106.JavaMail.jboss@colo-br-02.atl.jboss.com> Has anyone had success with getting the Servlet security to work with RestEasy? To this point I have not been able to successfully limit access a to a resource. Following this guide http://www.jboss.org/file-access/default/members/resteasy/freezone/docs/1.0.0.GA/userguide/html_single/index.html chapter 25 I have got the resource asking for authentication, but when I enter a user that does not have the appropriate role the servlet still allows access. Has anyone seen this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214156#4214156 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214156 From do-not-reply at jboss.com Mon Mar 2 08:53:55 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 2 Mar 2009 08:53:55 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Upgrade AS 4.2.3 WS to 3.0.5 Message-ID: <6452699.1236002035574.JavaMail.jboss@colo-br-02.atl.jboss.com> "chuaky" wrote : What is the new jars files after 3.0.2 that are equivalent to the old jbossws-client.jar? jbossws-native-client.jar View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214175#4214175 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214175 From do-not-reply at jboss.com Mon Mar 2 09:00:45 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 2 Mar 2009 09:00:45 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Help with authMethod and security after JBoss501 upgrade Message-ID: <22825142.1236002445147.JavaMail.jboss@colo-br-02.atl.jboss.com> Follow up: JBWS-2565 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214176#4214176 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214176 From do-not-reply at jboss.com Mon Mar 2 09:10:23 2009 From: do-not-reply at jboss.com (lukeb) Date: Mon, 2 Mar 2009 09:10:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Help with authMethod and security after JBoss501 upgrade Message-ID: <392232.1236003023267.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for the prompt reply Richard, do you want me to flesh out the jIRA or is the forum link sufficient? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214180#4214180 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214180 From do-not-reply at jboss.com Mon Mar 2 09:12:41 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 2 Mar 2009 09:12:41 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Help with authMethod and security after JBoss501 upgrade Message-ID: <19036311.1236003161782.JavaMail.jboss@colo-br-02.atl.jboss.com> Forum link is sufficient ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214181#4214181 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214181 From do-not-reply at jboss.com Mon Mar 2 09:28:42 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 2 Mar 2009 09:28:42 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Help with authMethod and security after JBoss501 upgrade Message-ID: <17654393.1236004122252.JavaMail.jboss@colo-br-02.atl.jboss.com> Could you provide the simple test case that reproduces the problem? It will speed up the bugfix process ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214188#4214188 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214188 From do-not-reply at jboss.com Mon Mar 2 12:40:44 2009 From: do-not-reply at jboss.com (md5georg) Date: Mon, 2 Mar 2009 12:40:44 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Errors Web Service Client Message-ID: <24944407.1236015644352.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, set the jboss endorsed dirs property in your start script: ex: set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\server\hepp\lib\endorsed and add the file: jboss-soapmessage-4.0.4.GA.jar in it. Chers! /Georg View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214253#4214253 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214253 From do-not-reply at jboss.com Mon Mar 2 17:35:29 2009 From: do-not-reply at jboss.com (djkrite) Date: Mon, 2 Mar 2009 17:35:29 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Trying to specify SOAP 1.2 in EJB. Message-ID: <11957182.1236033329271.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm running JBoss 4.2.3 on Java 1.5. I would like to use SOAP 1.2 with my web service endpoint but when I try to specify with: @BindingType(value="http://www.w3.org/2003/05/soap/bindings/HTTP/") | | or | | @BindingType(javax.xml.ws.soap.SOAPBinding.SOAP12HTTP_BINDING) and then throw a SOAP 1.2 fault in my code, I get this: | javax.ejb.EJBException: java.lang.UnsupportedOperationException: SOAP 1.1 Fault does not support the concept of Role Is there anyway to specify SOAP 1.2? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214314#4214314 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214314 From do-not-reply at jboss.com Mon Mar 2 20:14:57 2009 From: do-not-reply at jboss.com (chuaky) Date: Mon, 2 Mar 2009 20:14:57 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Upgrade AS 4.2.3 WS to 3.0.5 Message-ID: <8853079.1236042897553.JavaMail.jboss@colo-br-02.atl.jboss.com> hi richard, It works, just that the jbossws-native-client.jar file is pretty small (~5k), as compared to it predecessor jbossws-client.jar (~1.6M). By including the jbossws-native-client.jar, can it run offline as a standalone client or would it "load" other jars? Many thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214337#4214337 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214337 From do-not-reply at jboss.com Tue Mar 3 01:05:20 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Tue, 3 Mar 2009 01:05:20 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <20718988.1236060320177.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all Now that we could not log to database directly. We did the following work around. Wrote the log events as xml elements, using XMLLayout and then watch the log file. Whenever, the log file changed, the application starts and log are inserted into db Next issue we are facing is there is no link between the request and response. Is there any means to identify the response for particular request? or can be extend JBOSS web Trace class? regards KRS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214361#4214361 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214361 From do-not-reply at jboss.com Tue Mar 3 01:19:04 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 3 Mar 2009 01:19:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Trying to specify SOAP 1.2 in EJB. Message-ID: <1177309.1236061144204.JavaMail.jboss@colo-br-02.atl.jboss.com> Which JBossWS version are you using? Yesterday we released JBossWS 3.1.0 downloadable here. Can you reproduce your problem with JBossWS 3.1.0 too? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214365#4214365 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214365 From do-not-reply at jboss.com Tue Mar 3 01:20:04 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 3 Mar 2009 01:20:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Upgrade AS 4.2.3 WS to 3.0.5 Message-ID: <22775732.1236061204803.JavaMail.jboss@colo-br-02.atl.jboss.com> Our distribution jars don't download other jars from internet. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214366#4214366 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214366 From do-not-reply at jboss.com Tue Mar 3 01:21:18 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 3 Mar 2009 01:21:18 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Upgrade AS 4.2.3 WS to 3.0.5 Message-ID: <15173273.1236061278595.JavaMail.jboss@colo-br-02.atl.jboss.com> "chuaky" wrote : jbossws-native-client.jar file is pretty small (~5k), as compared to it predecessor jbossws-client.jar (~1.6M) There were huge JBossWS project structure refactorings in JBossWS 3.x series View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214368#4214368 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214368 From do-not-reply at jboss.com Tue Mar 3 01:26:03 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 3 Mar 2009 01:26:03 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <32684405.1236061563072.JavaMail.jboss@colo-br-02.atl.jboss.com> "mobaxkrs" wrote : Next issue we are facing is there is no link between the request and response. | Is there any means to identify the response for particular request? | I'd suggest to use our Records Management Framework. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214371#4214371 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214371 From do-not-reply at jboss.com Tue Mar 3 01:32:23 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 3 Mar 2009 01:32:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <24758993.1236061943686.JavaMail.jboss@colo-br-02.atl.jboss.com> Another option you have is to use WS-Addressing in your web services and use MessageID correlation identifier to identify which response belongs to which request. Then you could identify related messages using your log4j integration work you already did ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214374#4214374 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214374 From do-not-reply at jboss.com Tue Mar 3 03:10:24 2009 From: do-not-reply at jboss.com (santskumar) Date: Tue, 3 Mar 2009 03:10:24 -0500 (EST) Subject: [jbossws-users] [JBossWS] - developing Web service using JBOSS ESB Message-ID: <11657491.1236067824567.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, can any one please give me information how to develop a web service using JBOSS ESB. Thanks and regards, Santhosh Kumar. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214400#4214400 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214400 From do-not-reply at jboss.com Tue Mar 3 04:19:31 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 3 Mar 2009 04:19:31 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JBossWS 3.1.0 released Message-ID: <3989695.1236071971026.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm happy to announce the release of JBossWS 3.1.0 GA which includes Native, CXF and Metro integration. For a list of the new features, improvements and bug fixes, please refer the release notes available here: http://labs.jboss.com/file-access/default/members/jbossws/downloads/ReleaseNotes-jbossws-native-3.1.0.GA.txt The supported target containers for this release are JBoss 4.2.3.GA, JBoss 5.0.0.GA and JBoss 5.0.1.GA. The binaries, including the samples can be obtained here: http://labs.jboss.com/jbossws/downloads/ Installation instructions can be found here: http://jbossws.jboss.org/mediawiki/index.php/Main_Page To get started please have a look at the Quick Start and User Guide: http://jbossws.jboss.org/mediawiki/index.php/Quick_Start http://jbossws.jboss.org/mediawiki/index.php/JAX-WS_User_Guide If you don't know it already, you'll be surprised how easy it is to do Web Services. Many thanks to the team and contributors making this release possible. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214415#4214415 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214415 From do-not-reply at jboss.com Tue Mar 3 05:38:52 2009 From: do-not-reply at jboss.com (dhanushgopinath) Date: Tue, 3 Mar 2009 05:38:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - WS-Security on POJO Endpoint in JBOSSWS 3.1.0 Message-ID: <2229789.1236076732869.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am using the latest jboss 3.1.0 on my JBOSS AS 4.2.3. I have a sample web service which is a POJO Endpoint I made from the WSDL(using top down approach). Do I need to give the @EndpointConfig annotation in this case? I gave it and deployed the webservice and when I invoked the service I got a ClassCastException java.lang.ClassCastException: org.jboss.ws.core.soap.EnvelopeBuilderDOM I then removed this annotationand gave the annotation as per the sample in jboss download(SecureEndpointImpl.java). It deployed successfully but never worked properly. What ever the user name or role it returned successfully. Here are my configurations jboss-wsse-server.xml | | | | | | | | | | | | | service | @Stateless(name = "AWFUtilityServicePortType") | @SecurityDomain("JBossWS") | @RolesAllowed("friend") | @WebService(serviceName = "AWFUtilityService", targetNamespace = "http://www.test.com/WF/Framework/AWFUtilityService", | endpointInterface = "com.test.wf.framework.awfutilityservice.AWFUtilityServicePortType", portName="AWFUtilityServicePort",wsdlLocation="WEB-INF/wsdl/AWFUtilityService.wsdl") | public class AWFUtilityServiceImpl implements AWFUtilityServicePortType { | | public String getID(String id) | throws GetCorrelationIDFault { | return "Hello World " + id; | } | | } | Is there something else that needs to be configured? Please let me know Thanks Dhanush View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214466#4214466 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214466 From do-not-reply at jboss.com Tue Mar 3 08:29:14 2009 From: do-not-reply at jboss.com (djkrite) Date: Tue, 3 Mar 2009 08:29:14 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Trying to specify SOAP 1.2 in EJB. Message-ID: <32934558.1236086954367.JavaMail.jboss@colo-br-02.atl.jboss.com> Current version: jbossws-3.0.1-native-2.0.4.GA I'll try the new one and let you know if it happens. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214505#4214505 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214505 From do-not-reply at jboss.com Tue Mar 3 20:20:50 2009 From: do-not-reply at jboss.com (chuaky) Date: Tue, 3 Mar 2009 20:20:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Upgrade AS 4.2.3 WS to 3.0.5 Message-ID: <23839616.1236129650797.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks Richard, i understand. Now to upgrade to 3.1. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214719#4214719 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214719 From do-not-reply at jboss.com Tue Mar 3 22:50:17 2009 From: do-not-reply at jboss.com (vdurbha) Date: Tue, 3 Mar 2009 22:50:17 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Specify WS-Security Handler using JEE standards Message-ID: <33200427.1236138618008.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm using JBoss 5.0.0 GA and the native web services stack to create and deploy web services. I use JBoss specific annotation in my endpoint as follows: @EndpointConfig(configName="Standard WSSecurity Endpoint") Is it possible to avoid using this JBoss specific annotation and use JEE standard annotation @HandlerChain and specify the handlers? Also when I'm creating a standalone web service client, I had to include this line in my client to make it work. ((StubExt)port).setConfigName("Standard WSSecurity Client"); Is it possible to avoid this and set handlers through code using into the BindingProvider? When I tried to do both the above, I wasn't able to get the web service working? If anyone can share their experiences doing this, it would be of great help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214730#4214730 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214730 From do-not-reply at jboss.com Tue Mar 3 23:57:06 2009 From: do-not-reply at jboss.com (dhanushgopinath) Date: Tue, 3 Mar 2009 23:57:06 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WS-Security on POJO Endpoint in JBOSSWS 3.1.0 Message-ID: <19874901.1236142626920.JavaMail.jboss@colo-br-02.atl.jboss.com> Seeing no replies here, I guess I might have confused you ppl here. This is what I did 1. Implemented a Web Service in Top Down Approach. 2. Added Following annotations at SecurityDomain("JBossWS") | @EndpointConfig(configName="Standard WSSecurity Endpoint", configFile="META-INF/standard-jaxws-endpoint-config.xml") | @WebService(serviceName = "AWFUtilityService", targetNamespace = "http://www.test.com/WF/Framework/AWFUtilityService", | endpointInterface = "com.test.wf.framework.awfutilityservice.AWFUtilityServicePortType", | portName="AWFUtilityServicePort",wsdlLocation="WEB-INF/wsdl/AWFUtilityService.wsdl") 3. Wrote the jboss-wsse-server.xml as per the test suite | | | | | | | | | friend | | | | | | | 4. Edited the jboss-web.xml like this | | | java:/jaas/JBossWS | /AWFUtilityServiceWSS | 5. Edited the web.xml like this | | AWFUtilityService | | com.test.wf.framework.awfutilityservice.AWFUtilityServiceImpl | | | | AWFUtilityService | /AWFUtilityService | | | | BASIC | JBossWS | | | friend | | | index.jsp | | And deployed the application. While deploying I see the following entry in the server log | | ServerEndpointMetaData: | type=JAXWS | qname={http://www.test.com/WF/Framework/AWFUtilityService}AWFUtilityServicePort | id=jboss.ws:context=AWFUtilityServiceWSS,endpoint=AWFUtilityService | address=http://192.168.1.97:8080/AWFUtilityServiceWSS/AWFUtilityService | binding=http://schemas.xmlsoap.org/wsdl/soap/http | linkName=AWFUtilityService | implName=com.test.wf.framework.awfutilityservice.AWFUtilityServiceImpl | seiName=com.test.wf.framework.awfutilityservice.AWFUtilityServicePortType | serviceMode=null | portComponentName=null | contextRoot=/AWFUtilityServiceWSS | urlPattern=/AWFUtilityService | configFile=META-INF/standard-jaxws-endpoint-config.xml | configName=Standard Endpoint | authMethod=null | transportGuarantee=NONE | secureWSDLAccess=false | properties={} | | OperationMetaData: | qname={http://www.test.com/WF/Framework/AWFUtilityService}GetID | javaName=getID | style=document/literal/BARE | oneWay=false | soapAction=http://www.test.com/WF/Framework/AWFUtilityService/GetID | ParameterMetaData: | xmlName={http://www.test.com/WF/Framework/AWFUtilityService}CorrelationID | partName=CorrelationID | xmlType={http://www.w3.org/2001/XMLSchema}string | javaType=java.lang.String | mode=IN | inHeader=false | index=0 | ReturnMetaData: | xmlName={http://www.test.com/WF/Framework/AWFUtilityService}CorrelationIDValue | partName=CorrelationIDValue | xmlType={http://www.w3.org/2001/XMLSchema}string | javaType=java.lang.String | mode=OUT | inHeader=false | index=-1 | FaultMetaData | xmlName={http://www.test.com/WF/Framework/AWFUtilityService}GetIDFault | xmlType={http://www.test.com/WF/Framework/AWFUtilityService}GetIDFault | javaType=com.test.wf.framework.awfutilityservice.GetIDFault | faultBean=com.test.wf.framework.faultschema.GetIDComplexType | | HandlerMetaDataJAXWS: | type=POST | name=WSSecurity Handler | class=class org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer | params=[] | protocols=##SOAP11_HTTP ##SOAP11_HTTP_MTOM | services=null | ports=null | | Why is the item in bold(configName=Standard Endpoint ) like that? Shouldn't that value be Standard WSSecurity Endpoint? I then called the Service with my WS Sec Client code given belowpublic static void main(String[] args) { | try { // Call Web Service Operation | | String url = "http://192.168.1.97:8070/AWFUtilityServiceWSS/AWFUtilityService?wsdl"; | | URL wsdlURL = new URL(url); | URL securityURL = new File("F:\\Workflow_Code\\Sample-EPM-FW-BasedWorkflows\\WSSecClient\\src\\wssecclient\\jboss-wsse-client.xml").toURL(); | QName serviceName = new QName("http://www.test.com/WF/Framework/AWFUtilityService", "AWFUtilityService"); | Service service = Service.create(wsdlURL, serviceName); | AWFUtilityServicePortType port = (AWFUtilityServicePortType) service.getPort(AWFUtilityServicePortType.class); | ((StubExt) port).setSecurityConfig(securityURL.toExternalForm()); | ((StubExt) port).setConfigName("Standard WSSecurity Client"); | | | Map reqContext = ((BindingProvider) port).getRequestContext(); | reqContext.put(BindingProvider.USERNAME_PROPERTY, "kermit"); | reqContext.put(BindingProvider.PASSWORD_PROPERTY, "thefrog"); | | reqContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, url); | | java.lang.String partGetIDRequest = "hello"; | java.lang.String result = port.getID(partGetIDRequest); | System.out.println("Result = " + result); When I call the service I get the following exception at the server side. 2009-03-03 19:04:52,547 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml; charset=UTF-8] | 2009-03-03 19:04:52,594 DEBUG [org.jboss.ws.metadata.umdm.EndpointMetaData] Configure SOAPBinding | 2009-03-03 19:04:52,594 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception | java.lang.ClassCastException: org.jboss.ws.core.soap.EnvelopeBuilderDOM | at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:285) | 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:803) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | at java.lang.Thread.run(Thread.java:595) | 2009-03-03 19:04:52,610 DEBUG [org.jboss.wsf.stack.jbws.RequestHandlerImpl] END handleRequest: jboss.ws:context=AWFUtilityServiceWSS,endpoint=AWFUtilityService | 2009-03-03 19:04:52,610 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 1383942 (Thread http-192.168.1.97-8080-1) | 2009-03-03 19:04:52,610 ERROR [org.jboss.wsf.stack.jbws.RequestHandlerImpl] Error processing web service request | org.jboss.ws.WSException: java.lang.ClassCastException: org.jboss.ws.core.soap.MessageFactoryImpl | at org.jboss.ws.WSException.rethrow(WSException.java:68) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:336) | 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:803) | I understand this is because of the presence of the jboss-native-core.jar in my web service application. But I need that to add the @EndpointConfig annotation. Is it possible to remove the jar and retain the annotation? Or is there any other way to avoid the class cast exception. More than that is the way I am implementing this correct ? Please help. Many thanks in advance View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214744#4214744 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214744 From do-not-reply at jboss.com Wed Mar 4 02:37:57 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 4 Mar 2009 02:37:57 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <21469014.1236152277926.JavaMail.jboss@colo-br-02.atl.jboss.com> How to enable recording - which file has the configuration View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214780#4214780 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214780 From do-not-reply at jboss.com Wed Mar 4 03:22:03 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 4 Mar 2009 03:22:03 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <30750208.1236154923222.JavaMail.jboss@colo-br-02.atl.jboss.com> Read Records Management Framework documentation above, please. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214792#4214792 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214792 From do-not-reply at jboss.com Wed Mar 4 09:25:14 2009 From: do-not-reply at jboss.com (nicvas) Date: Wed, 4 Mar 2009 09:25:14 -0500 (EST) Subject: [jbossws-users] [JBossWS] - How can I print to log file input soap request and response? Message-ID: <24010516.1236176714342.JavaMail.jboss@colo-br-02.atl.jboss.com> How can I print to log file input soap request and response? For example: @WebService( ) public class ARE_GetBanner { @WebMethod(operationName = "GetBanner") public GetBannerOutputData GetBanner(@WebParam(name = "inputdata") org.isc.are.ws.GetBannerInputData inputdata) { ????log soap request???? --- my flow logic --- ????log soap response???? } Who have any idea? Thanks in advanced. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214918#4214918 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214918 From do-not-reply at jboss.com Wed Mar 4 10:34:39 2009 From: do-not-reply at jboss.com (Ian Ashley) Date: Wed, 4 Mar 2009 10:34:39 -0500 (EST) Subject: [jbossws-users] [JBossWS] - WSDL - convert to MTOM Message-ID: <14050861.1236180879952.JavaMail.jboss@colo-br-02.atl.jboss.com> What is the best way to convert the code generated by WSConsume to support MTOM transfers of the base64Binary elements? Is there a recipe anywhere? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214936#4214936 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214936 From do-not-reply at jboss.com Wed Mar 4 12:07:47 2009 From: do-not-reply at jboss.com (Ian Ashley) Date: Wed, 4 Mar 2009 12:07:47 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSDL - convert to MTOM Message-ID: <22306891.1236186467227.JavaMail.jboss@colo-br-02.atl.jboss.com> To provide a bit more information we are used complex types containing base64Binary encoded data, for example | | | | | | | | | | | | The generated interface is /** | * | * @param asset | * @param values | * @param assetRef | * @param leafName | * @param sessionId | * @param nodeRef | * @throws SessionExpiredException | * @throws NsteinDPSErrorException | */ | @WebMethod(operationName = "StoreAsset", action = "StoreAsset") | @RequestWrapper(localName = "StoreAsset", targetNamespace = "http://services.nstein.com/NsteinDPS", className = "com.nstein.services.nsteindps.StoreAsset") | @ResponseWrapper(localName = "StoreAssetResponse", targetNamespace = "http://services.nstein.com/NsteinDPS", className = "com.nstein.services.nsteindps.StoreAssetResponse") | public void storeAsset( | @WebParam(name = "sessionId", targetNamespace = "http://services.nstein.com/NsteinDPS") | String sessionId, | @WebParam(name = "assetRef", targetNamespace = "http://services.nstein.com/NsteinDPS", mode = WebParam.Mode.INOUT) | Holder assetRef, | @WebParam(name = "nodeRef", targetNamespace = "http://services.nstein.com/NsteinDPS") | String nodeRef, | @WebParam(name = "leafName", targetNamespace = "http://services.nstein.com/NsteinDPS") | String leafName, | @WebParam(name = "values", targetNamespace = "http://services.nstein.com/NsteinDPS") | List values, | @WebParam(name = "asset", targetNamespace = "http://services.nstein.com/NsteinDPS") | byte[] asset) | throws NsteinDPSErrorException, SessionExpiredException | ; | I believe that byte[] asset needs to be changed to DataHandler asset but doing this alone doesn't seem to work. Any pointers as to what else is required or link to an example would be very helpful. Thanks in advance, Ian View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214966#4214966 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214966 From do-not-reply at jboss.com Wed Mar 4 13:11:09 2009 From: do-not-reply at jboss.com (Ian Ashley) Date: Wed, 4 Mar 2009 13:11:09 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSDL - convert to MTOM Message-ID: <6427260.1236190269243.JavaMail.jboss@colo-br-02.atl.jboss.com> Finally cracked it. Changing the WSDL to | resolved the problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214985#4214985 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214985 From do-not-reply at jboss.com Wed Mar 4 14:03:43 2009 From: do-not-reply at jboss.com (jej2003) Date: Wed, 4 Mar 2009 14:03:43 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: RestEasy Security Message-ID: <6741944.1236193423355.JavaMail.jboss@colo-br-02.atl.jboss.com> The issue is with the web.xml shipped with RestEasy, there is a typo in the file it currently reads resteasy.resource.method-interceptors where it should be resteasy.resource.method.interceptors Everything is working fine now. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214994#4214994 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214994 From do-not-reply at jboss.com Wed Mar 4 15:44:56 2009 From: do-not-reply at jboss.com (djkrite) Date: Wed, 4 Mar 2009 15:44:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Trying to specify SOAP 1.2 in EJB. Message-ID: <18438012.1236199496608.JavaMail.jboss@colo-br-02.atl.jboss.com> I installed JBoss 5.0.1 and JBossWS 3.1.0, the problem still exists. Here is a stack trace: | 15:40:39,149 ERROR [STDERR] java.lang.UnsupportedOperationException: SOAP 1.1 Fault does not support the concept of Role | 15:40:39,150 ERROR [STDERR] at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultRole(SOAPFaultImpl.java:628) | 15:40:39,150 ERROR [STDERR] at com.example.webservice.endpoint.PBXInterfaceImpl.createSOAPFault(PBXInterfaceImpl.java:57) | 15:40:39,150 ERROR [STDERR] at com.example.webservice.endpoint.PBXInterfaceImpl.passedValidation(PBXInterfaceImpl.java:351) | 15:40:39,150 ERROR [STDERR] at com.example.webservice.endpoint.PBXInterfaceImpl.updateAllRooms(PBXInterfaceImpl.java:189) | 15:40:39,150 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 15:40:39,150 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 15:40:39,150 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 15:40:39,150 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeTarget(MethodInvocation.java:122) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111) | 15:40:39,150 ERROR [STDERR] at org.jboss.ejb3.EJBContainerInvocationWrapper.invokeNext(EJBContainerInvocationWrapper.java:69) | 15:40:39,150 ERROR [STDERR] at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.invoke(InterceptorSequencer.java:73) | 15:40:39,150 ERROR [STDERR] at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) | 15:40:39,150 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 15:40:39,150 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 15:40:39,150 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 15:40:39,150 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:585) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:174) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,150 ERROR [STDERR] at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_4679956.invoke(InvocationContextInterceptor_z_fillMethod_4679956.java) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,150 ERROR [STDERR] at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_4679956.invoke(InvocationContextInterceptor_z_setup_4679956.java) | 15:40:39,150 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,151 ERROR [STDERR] at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62) | 15:40:39,151 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,151 ERROR [STDERR] at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56) | 15:40:39,151 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,151 ERROR [STDERR] at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | 15:40:39,151 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,151 ERROR [STDERR] at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) | 15:40:39,151 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,151 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) | 15:40:39,228 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,228 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | 15:40:39,228 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) | 15:40:39,228 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,228 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) | 15:40:39,228 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,228 ERROR [STDERR] at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42) | 15:40:39,228 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:201) | 15:40:39,229 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) | 15:40:39,229 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) | 15:40:39,229 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | 15:40:39,229 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) | 15:40:39,229 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) | 15:40:39,229 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:372) | 15:40:39,229 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessContainer.invokeEndpoint(StatelessContainer.java:727) | 15:40:39,229 ERROR [STDERR] at org.jboss.wsf.container.jboss50.invocation.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:96) | 15:40:39,229 ERROR [STDERR] at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219) | 15:40:39,229 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:474) | 15:40:39,229 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) | 15:40:39,229 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) | 15:40:39,229 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) | 15:40:39,229 ERROR [STDERR] at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) | 15:40:39,229 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | 15:40:39,229 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | 15:40:39,229 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | 15:40:39,229 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | 15:40:39,229 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | 15:40:39,229 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | 15:40:39,277 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) | 15:40:39,277 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) | 15:40:39,277 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) | 15:40:39,277 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) | 15:40:39,277 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126) | 15:40:39,277 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) | 15:40:39,277 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | 15:40:39,277 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | 15:40:39,278 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) | 15:40:39,278 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | 15:40:39,278 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) | 15:40:39,278 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) | 15:40:39,278 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) | 15:40:39,278 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | 15:40:39,278 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) | 15:40:39,278 WARN [StatelessBeanContext] EJBTHREE-1337: do not get WebServiceContext property from stateless bean context, it should already have been injected | 15:40:39,283 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | javax.ejb.EJBException: javax.xml.ws.soap.SOAPFaultException | at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:77) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) | 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.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | 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.stateless.StatelessContainer.localInvoke(StatelessContainer.java:372) | at org.jboss.ejb3.stateless.StatelessContainer.invokeEndpoint(StatelessContainer.java:727) | at org.jboss.wsf.container.jboss50.invocation.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:96) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219) | 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(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:601) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) | Caused by: javax.xml.ws.soap.SOAPFaultException | at com.example.webservice.endpoint.PBXInterfaceImpl.createSOAPFault(PBXInterfaceImpl.java:66) | at com.example.webservice.endpoint.PBXInterfaceImpl.passedValidation(PBXInterfaceImpl.java:351) | at com.example.webservice.endpoint.PBXInterfaceImpl.updateAllRooms(PBXInterfaceImpl.java:189) | 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.InterceptorSequencer.invoke(InterceptorSequencer.java:73) | at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) | 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.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_4679956.invoke(InvocationContextInterceptor_z_fillMethod_4679956.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_4679956.invoke(InvocationContextInterceptor_z_setup_4679956.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.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.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | ... 48 more | 15:40:39,285 ERROR [SOAPFaultHelperJAXWS] Error creating SOAPFault message | javax.xml.soap.SOAPException: {http://schemas.xmlsoap.org/soap/envelope/}Sender is not a standard SOAP 1.2 Code value | at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:222) | at org.jboss.ws.core.soap.SOAPFaultImpl.setFaultCode(SOAPFaultImpl.java:182) | at org.jboss.ws.core.soap.SOAPBodyImpl.addFault(SOAPBodyImpl.java:120) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.populateSOAPFault(SOAPFaultHelperJAXWS.java:244) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:204) | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:179) | at org.jboss.ws.core.jaxws.binding.SOAP12BindingJAXWS.createFaultMessageFromException(SOAP12BindingJAXWS.java:110) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277) | 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(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:601) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) | 15:40:39,291 WARN [ServiceEndpointInvoker] Exception while processing handleFault: | javax.ejb.EJBException: javax.xml.ws.soap.SOAPFaultException | at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:77) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:190) | 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.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | 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.stateless.StatelessContainer.localInvoke(StatelessContainer.java:372) | at org.jboss.ejb3.stateless.StatelessContainer.invokeEndpoint(StatelessContainer.java:727) | at org.jboss.wsf.container.jboss50.invocation.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:96) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219) | 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(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:601) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) | Caused by: javax.xml.ws.soap.SOAPFaultException | at com.example.webservice.endpoint.PBXInterfaceImpl.createSOAPFault(PBXInterfaceImpl.java:66) | at com.example.webservice.endpoint.PBXInterfaceImpl.passedValidation(PBXInterfaceImpl.java:351) | at com.example.webservice.endpoint.PBXInterfaceImpl.updateAllRooms(PBXInterfaceImpl.java:189) | 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.InterceptorSequencer.invoke(InterceptorSequencer.java:73) | at org.jboss.ejb3.interceptors.aop.InterceptorSequencer.aroundInvoke(InterceptorSequencer.java:59) | 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.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_4679956.invoke(InvocationContextInterceptor_z_fillMethod_4679956.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_4679956.invoke(InvocationContextInterceptor_z_setup_4679956.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.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.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | ... 48 more | 15:40:39,480 ERROR [SOAPFaultHelperJAXWS] SOAP request exception | javax.xml.ws.WebServiceException: Cannot create SOAPFault message for: javax.ejb.EJBException: javax.xml.ws.soap.SOAPFaultException | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:195) | at org.jboss.ws.core.jaxws.binding.SOAP12BindingJAXWS.createFaultMessageFromException(SOAP12BindingJAXWS.java:110) | at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671) | at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:277) | 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(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:601) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215025#4215025 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215025 From do-not-reply at jboss.com Wed Mar 4 23:27:10 2009 From: do-not-reply at jboss.com (Grid.Qian) Date: Wed, 4 Mar 2009 23:27:10 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: 'the command is too long' when run wsprovide.bat Message-ID: <25128394.1236227230629.JavaMail.jboss@colo-br-02.atl.jboss.com> I tested it according to your said, but the error occured too. "PeterJ" wrote : Try placing the command into a *.bat file and run the bat file. I think this has something to do with the input handler for Command Prompt and putting the command into a *.bat file might get around it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215091#4215091 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215091 From do-not-reply at jboss.com Thu Mar 5 01:21:02 2009 From: do-not-reply at jboss.com (PeterJ) Date: Thu, 5 Mar 2009 01:21:02 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: 'the command is too long' when run wsprovide.bat Message-ID: <19720077.1236234062069.JavaMail.jboss@colo-br-02.atl.jboss.com> Just a thought - are you really using colons (:) to separate JAR files in the classpath? Since you are running on Windows (which I assume is the case since you specifically mentioned wsprovide.bat), you should really be using semicolons (;). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215106#4215106 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215106 From do-not-reply at jboss.com Thu Mar 5 02:09:13 2009 From: do-not-reply at jboss.com (dhanushgopinath) Date: Thu, 5 Mar 2009 02:09:13 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WS-Security on POJO Endpoint in JBOSSWS 3.1.0 Message-ID: <18624398.1236236953617.JavaMail.jboss@colo-br-02.atl.jboss.com> Guys, I got it working. I will write a detailed document on the same and update it here. Thanks Dhanush View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215110#4215110 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215110 From do-not-reply at jboss.com Thu Mar 5 02:47:47 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Thu, 5 Mar 2009 02:47:47 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <14672566.1236239267938.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I read through the Records management framework documentation. But i Could not figure out how to achieve it.. The implementation portion in the document is not clear. Somehow i figured out /home/krs/mobicents-all-1.2.0.BETA3-jboss-4.2.2.GA/jboss-4.2.2.GA/server/default/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml and added the bean properties for the recorders. Don't know it is what we need to do. Where will the logged information available.. How to get that.. Could u specify implementation specific details.. or point to any other links View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215120#4215120 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215120 From do-not-reply at jboss.com Thu Mar 5 02:57:51 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Thu, 5 Mar 2009 02:57:51 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <23250853.1236239871491.JavaMail.jboss@colo-br-02.atl.jboss.com> Also i found that the default standard endpoint config at jboss-4.2.2.GA/server/default/deploy/jbossws.sar/META-INF/standard-jaxws-endpoint-config.xml has no Element in it The config is | Standard Endpoint | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215122#4215122 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215122 From do-not-reply at jboss.com Thu Mar 5 04:13:08 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Thu, 5 Mar 2009 04:13:08 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <23255436.1236244388375.JavaMail.jboss@colo-br-02.atl.jboss.com> The documentation clearly says the Record Management is available starting from version 2.0.3. Which version of JBossWS are you using? The version that comes with JBoss 4.2.2.GA is 2.0.1.SP2, thus if you did not change anything about that, you would simply need to upgrade to a more recent version. In that case, take a look at the supported target containers matrix : http://jbossws.jboss.org/mediawiki/index.php?title=Supported_Target_Containers This said, for a simple use of the Record Management with Native stack you don't need to do anything special besides going to the JMX console and activate the recording flag in the already installed LogRecorder instance for you endpoint. No implementation required, no changes to the endpoint config required (assuming you're using one of the provided endpoint configuration). The LogRecorder will simply log every message going through your endpoint into your server.log. Further customization and usescases are explained in the documentation, I'm sure you'll understand everything easily once you have that stuff (i.e. you using a jbossws version that has that). Also consider taking a look at the testcases in the sources, package org.jboss.test.ws.management.recording. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215153#4215153 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215153 From do-not-reply at jboss.com Thu Mar 5 06:29:36 2009 From: do-not-reply at jboss.com (dhanushgopinath) Date: Thu, 5 Mar 2009 06:29:36 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Implementing WS-Security Usename Token Profile Authenticatio Message-ID: <14306980.1236252576713.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, The below mentioned steps will help you implementing WS-Security Usename Token Profile on for POJO based Webservices. This example is done with JBOSS 4.2.3 AS with JBOSS Native WS 3.1.0. Assumptions 1. This is a step by step example of implementing the Username Token Authentication Profile of WS Security (based on http://xml.coverpages.org/WSS-UsernameTokenProfile-20040315.pdf ) using the JBOSS WS version 3.1.0. 2. JBOSS AS version 4.2.3 is installed. 3. JBOSS WS 3.1.0 is deployed onto the JBOSS AS by following the instructions in the location http://www.jboss.org/file-access/default/members/jbossws/downloads/Install-jbossws-native-3.1.0.GA.txt 4. The web service implementation is already created using the Top Down approach. 5. JBOSS_HOME is the home directory of JBOSSAS where jboss-4.2.3.GA is unzipped. 6. While writing the WS Service Client we assume that the client side stubs are already provided. 7. Username and Password used in this implementation is the JBOSS default username and password (kermit=thefrog) Steps - Server Side 1. Add the annotation @SecurityDomain("JBossWS") to the implementation class of web service. a. This requires the importing of the package org.jboss.annotation.security.SecurityDomain to the web service and hence will need the jar jboss-annotations-ejb3.jar in the classpath of your application. This jar is available in the JBOSS_HOME/client directory. b. This security domain (JBossWS )should be available under the application policy category in the login configuration xml file in JBOSS_HOME/server/default/conf/login-config.xml. (I guess it should be possible to add a custom security domain by adding a separate application policy configuration on to this file. But I have not tested it though. ) 2. Create a file jboss-web.xml under the WEB-INF directory of your application and add the following content to the XML file. | | | | java:/jaas/JBossWS | /CONTEXT_ROOT_OF_YOUR_APP | | 3. Copy the file standard-jaxws-endpoint-config.xml from the location JBOSS_HOME\server\default\deploy\jbossws.sar\META-INF to the META-INF directory of your application and edit it as follows. a. Remove all the endpoint config elements () except the one with the config name (Standard WSSecurity Endpoint). Your standard-jaxws-endpoint-config.xml should look like this. | | | | Standard WSSecurity Endpoint | | | ##SOAP11_HTTP ##SOAP11_HTTP_MTOM | | WSSecurity Handler | org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerServer | | | Recording Handler | org.jboss.wsf.framework.invocation.RecordingServerHandler | | | | | 4. Create the Server side WSSE declaration (jboss-wsse-server.xml) file as per the Jboss WS 3.1.0 User guide (http://jbossws.jboss.org/mediawiki/index.php?title=WS-Security_options#POJO_Endpoint_-_Authentication_and_Authorization) in the WEB-INF directory of your application. The contents can be as given below or can be according to the above link if your want to provide role level security. | | | | | | | | | 5. Export the application WAR file and deploy it in JBOSS. Your application should deploy successfully. Check the log file to know more details. Steps - Client Side To test the application's Web Service Security we can write a sample WS Client. Before that we need to edit jbossws-users.properties file in the location JBOSS_HOME\ server\default\conf\props because the default JBossWS security domain look for the users configured in this file. Add users to this file in the username=password form. The steps to write the client are as given below. 1. Create the Client side WSSE declaration (jboss-wsse-client.xml) file in a location accessible to the web service client. The contents should be as per the JBOSS WS User guide (http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#Client_side_WSSE_declaration_.28jboss-wsse-client.xml.29 ). Since we are using Username Token Authentication, the contents of this file should be as follows. | | | | | | | 2. Create the WS Service Client. The important code fragment is as given below. This will require the importing of the package org.jboss.ws.core.StubExt which is available in the jar, jboss-native-core.jar. So this jar should be added to the client class path. The skeleton code is as given. | | String url = "YOUR_DEPLOYED_WSDL_URL"; | URL wsdlURL = new URL(url); | URL clientSideSecurityfile = new File("jboss-wsse-client.xml").toURL(); | QName serviceName = new QName(SERVICE_TARGET_NS, SERVICE_NAME); | Service service = Service.create(wsdlURL, serviceName); | | //Get the Web Service Interface PORT | AWFUtilityServicePortType port = (AWFUtilityServicePortType) service.getPort(AWFUtilityServicePortType.class); | | //Set the Security Configurations | ((StubExt) port).setSecurityConfig(clientSideSecurityfile.toExternalForm()); | ((StubExt) port).setConfigName("Standard WSSecurity Client"); | | //Set the user name password | Map reqContext = ((BindingProvider) port).getRequestContext(); | reqContext.put(BindingProvider.USERNAME_PROPERTY, "kermit"); | reqContext.put(BindingProvider.PASSWORD_PROPERTY, "thefrog"); | reqContext.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, url); | | //Make the Call | java.lang.String partGetIDRequest = "Hello World"; | java.lang.String result = port.getID(partGetIDRequest); | System.out.println("Result = " + result); | 3. So there is it we are all set. Make the call you can see the SOAP Messages when the user name and password matches a. In Bound | | | | | kermit | thefrog | | | | | Hi | | | b. Out Bound | | | Hello World, Your ID is 1 | | | c. When the User name and Password doesn't match the following SOAP fault is thrown. | | | | wsse:FailedAuthentication | The security token could not be authenticated or authorized. | | | | Hope these steps helps. If you find any issues after implementing by these steps, please post it here. Thanks & Regards Dhanush View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215231#4215231 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215231 From do-not-reply at jboss.com Thu Mar 5 09:47:30 2009 From: do-not-reply at jboss.com (kringdahl) Date: Thu, 5 Mar 2009 09:47:30 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: What could cause a null Endpoint? Message-ID: <32401909.1236264450182.JavaMail.jboss@colo-br-02.atl.jboss.com> I actually moved on from the CXF implementation to the native implementation and I do not seem to have my deployment config any more. Sorry about that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215337#4215337 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215337 From do-not-reply at jboss.com Thu Mar 5 12:15:15 2009 From: do-not-reply at jboss.com (glen_s) Date: Thu, 5 Mar 2009 12:15:15 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Use of JAX-RPC in JBoss 4.2.3 Message-ID: <27204617.1236273315708.JavaMail.jboss@colo-br-02.atl.jboss.com> I'll answer my own question in case anyone is trying to solve the same problem I had. I found a tutorial at http://jaitechwriteups.blogspot.com/2006/12/simple-webservice-on-jboss-using-axis.html which admittedly was written for JBoss 4.0.4, but in comments seemed to indicate would work with Axis 1.4 on JBoss 4.2.x. By following the tutorial I was able to get a client web service running that uses soap encoding including for soap encoded arrays (particularly unsupported it seems, since from my understanding of some JBossWS documentation, JBossWS in previous versions did support soap encoding in part--just not for soap encoded arrays). To jump to the chase, I simply put the following JARs from Axis 1.4 in my EAR's lib directory: axis.jar, axit-ant.jar, commons-discovery-0.2.jar, jaxrpc.jar, saaj.jar, wsdl4j-1.5.1.jar No modifications were necessary to the JARs included in JBoss libs nor to the configuration of any classloader. Do take note that if one tries to use Axis 1.4 to implement the server for a web service, some extra configuration seem to be necessary. In my case, I only needed a client so the above JARs in the EAR's lib were enough. But since I was initially following the above tutorial quite closely, and the tutorial does take you down the path of enabling a server, I did encounter and come up with a solution for enabling a server. I found that the compiler was not able to find J2EE classes in the compiler's classpath, which I fixed by copying jboss-j2ee.jar and servlet-api.jar from the JBoss default server's lib directory to my EAR's lib. As to whether this is the "right" thing to do to enable an Axis implemented server, I'm not sure, but I didn't try too hard since it wasn't part of my goal. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215414#4215414 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215414 From do-not-reply at jboss.com Thu Mar 5 12:21:48 2009 From: do-not-reply at jboss.com (glen_s) Date: Thu, 5 Mar 2009 12:21:48 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Use of JAX-RPC in JBoss 4.2.3 Message-ID: <13813363.1236273708975.JavaMail.jboss@colo-br-02.atl.jboss.com> I realize I didn't make clear in the above reply why I was suddenly was talking about Axis rather than JWSDP. As mentioned in my original message, my ultimate goal was to write a client that can use SOAP encoding. So the strategy I used was to "Switch to some other web service client library that supports soap encoding (that I'm not aware of) that can be configured to run on JBoss AS 4.2.3 " This other library turned out to be Axis 1.x. The idea to switch to Axis 1.x was given to me in a JavaRanch suggestion as well as suggestions from Glassfish forums for how to get SOAP encoding support when running on GlassFish. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215417#4215417 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215417 From do-not-reply at jboss.com Fri Mar 6 00:20:42 2009 From: do-not-reply at jboss.com (mayankmit2002) Date: Fri, 6 Mar 2009 00:20:42 -0500 (EST) Subject: [jbossws-users] [JBossWS] - SOAP not working with Jboss 5 Message-ID: <11612217.1236316842263.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello All, We've an application that is exposed to the third party as a web service, Right now we are using Jboss 4.2.2 with JDK 1.6.0_11 on Windows XP machine. For test purpose, we've a .Net client, that connects to our service through SOAP. But now the problem is, when we deploy the same application on Jboss 5.0.0 GA, our .Net client is unable to connect to our service. Although, wsdl is published well, and is accessible on the web ( we didn't make any changes in the context path or wsdl publish location). Whenever, our .Net clients now try to connect the service, following exception is thrown on the | See the end of this message for details on invoking | just-in-time (JIT) debugging instead of this dialog box. | | ************** Exception Text ************** | System.Security.SecurityException: Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. | at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) | at System.Security.CodeAccessPermission.Demand() | at System.Net.HttpWebRequest..ctor(Uri uri, ServicePoint servicePoint) | at System.Net.HttpRequestCreator.Create(Uri Uri) | at System.Net.WebRequest.Create(Uri requestUri, Boolean useUriBase) | at System.Net.WebRequest.Create(Uri requestUri) | at System.Web.Services.Protocols.WebClientProtocol.GetWebRequest(Uri uri) | at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebRequest(Uri uri) | at System.Web.Services.Protocols.SoapHttpClientProtocol.GetWebRequest(Uri uri) | at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) | at CMS_API_Test.perspectiveService.PerspectiveMgtAPI.endSession(sessionId arg0) | at CMS_API_Test.Form1.cB_Connect_CheckedChanged(Object sender, EventArgs e) | at System.Windows.Forms.CheckBox.OnCheckedChanged(EventArgs e) | at System.Windows.Forms.CheckBox.set_CheckState(CheckState value) | at System.Windows.Forms.CheckBox.set_Checked(Boolean value) | at CMS_API_Test.Form1.cB_Connect_CheckedChanged(Object sender, EventArgs e) | at System.Windows.Forms.CheckBox.OnCheckedChanged(EventArgs e) | at System.Windows.Forms.CheckBox.set_CheckState(CheckState value) | at System.Windows.Forms.CheckBox.OnClick(EventArgs e) | at System.Windows.Forms.CheckBox.OnMouseUp(MouseEventArgs mevent) | at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) | at System.Windows.Forms.Control.WndProc(Message& m) | at System.Windows.Forms.ButtonBase.WndProc(Message& m) | at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) | at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) | at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) | The action that failed was: | Demand | The type of the first permission that failed was: | System.Net.WebPermission | The Zone of the assembly that failed was: | Intranet but the same application is working fine with Jboss 4.2.2, Is there any change in the security attributes of Jboss WS, if any, how to modify them. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215570#4215570 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215570 From do-not-reply at jboss.com Fri Mar 6 08:26:05 2009 From: do-not-reply at jboss.com (Sancheski) Date: Fri, 6 Mar 2009 08:26:05 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Handler execution order in handler chain Message-ID: <16009015.1236345965470.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I have defined three handlers in a handler chain as follows: | | | | | | | Handler 1 | | test.HandlerOne | | | | Handler 2 | | test.HandlerTwo | | | | Handler 3 | | test.HandlerThree | | | | | | I thought that the handler execution order was going to be: handler 1, handler 2 and handler 3. But what really happened was that handlers were executed in reverse order, that is: Handler 3, handler 2, and handler 1. My handlers implement javax.xml.ws.handler.soap.SOAPHandler and I am using jbossws 3.0.4.GA. How can I set the handler execution order ? Are handlers in handler chain executed in reverse order as they are defined in the handler definition? Thanks in advance, David Sancho View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215702#4215702 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215702 From do-not-reply at jboss.com Fri Mar 6 08:36:34 2009 From: do-not-reply at jboss.com (vdurbha) Date: Fri, 6 Mar 2009 08:36:34 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Specify WS-Security Handler using JEE standards Message-ID: <15043149.1236346594728.JavaMail.jboss@colo-br-02.atl.jboss.com> After trying various options, I finally figured out a way to write a completely generic client by removing the StubExt dependency. This was achieved by using the @HandlerChain annotation on the Service class. This may also work if we use the annotation on the SEI. And then I defined the handler in an xml and referred to it in the annotation as follows: @HandlerChain(file="HelloWorldHandlerChain.xml") But the server side endpoint still does not work if I use @HandlerChain annotation instead of @EndpointConfig to set the security handler. After digging into the source code of JBossWS and the log files for a few hours, I understood that for the WS-Security handler to work correctly, it has to be configured as a POST Handler type. When I used @HandlerChain annotation, it is configured as ENDPOINT Handler type. I was not able to find anyway to specify the type of handler in a standard way. So for now, I'm guessing there is no escape from the @EndpointConfig proprietary annotation. Can someone please confirm the same? I would love to hear that I"m wrong with this because it is not a good idea to fill the source code with proprietary stuff. Doing this in a JBoss specific configuration file will be more cleaner as the code can then easily migrated to a different server without changes to source code. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215707#4215707 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215707 From do-not-reply at jboss.com Fri Mar 6 10:39:31 2009 From: do-not-reply at jboss.com (janekdb2) Date: Fri, 6 Mar 2009 10:39:31 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Changing of soap:address location Message-ID: <27198487.1236353972418.JavaMail.jboss@colo-br-02.atl.jboss.com> I was able to edit jbossws.beans/META-INF/jboss-beans.xml to change this | | to the public facing url, | | Versions: JBoss 4.2.2.GA JBossWS Native 3.0.3.GA libapache-mod-jk 1.2.18-3 apache 1.3.34-4.1 Changed part of jboss-beans.xml | | | | | | | true | | | 80 | | I commented out the webServiceHost property and uncommented the webServicePort port setting it to 80. It would be better if JBossWS could also get the port from the requesters protocol port. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4215755#4215755 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4215755 From do-not-reply at jboss.com Mon Mar 9 04:47:08 2009 From: do-not-reply at jboss.com (ayan13s) Date: Mon, 9 Mar 2009 04:47:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Error calling external webservice from JBOSS ESB action Message-ID: <2139707.1236588428792.JavaMail.jboss@colo-br-02.atl.jboss.com> We are facing issues in external web service call from esb action. Our web service client works perfectly when we call it from a standalone java program. But it throws NullPointerException when we try calling it from ESB action. We compared the request being passed to the service and found out the following. Signature in the request is being sent as a binary security token, but webservice expects subject key identifier. Our standard-jaxws-client-config.xml has 'Standard WSSecurity Client' config(only) and in our jboss-wsse-client.xml file we have correct configuration() and we are setting it properly in the client using the following code. URL securityURL = new File("jboss-wsse-client.xml").toURL(); ((StubExt)impService).setSecurityConfig(securityURL.toExternalForm()); We are able to call the service successfully from standalone java app using same client. But when we try to invoke it from ESB, security token is being set incorrectly. Request token reference when calling from jboss esb action - Request as it should be - IR8MMN/HOdj8ZC2YJWlBgsqYbLo= Server side log - 15:51:04,328 ERROR [HandlerChainExecutor] Exception during handler processing java.lang.NullPointerException at org.jboss.ws.extensions.security.SecurityStore.validateCertificate(SecurityStore.java:501) at org.jboss.ws.extensions.security.BinarySecurityTokenValidator.validateToken(BinarySecurityTokenValidator.java:47) at org.jboss.ws.extensions.security.element.SecurityHeader.(SecurityHeader.java:78) at org.jboss.ws.extensions.security.SecurityDecoder.decode(SecurityDecoder.java:175) Any pointer would be of great help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216099#4216099 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216099 From tanmay.pradhan at exilant.com Mon Mar 9 22:13:45 2009 From: tanmay.pradhan at exilant.com (tanmay pradhan) Date: Mon, 9 Mar 2009 19:13:45 -0700 Subject: [jbossws-users] SOAP over JMS Message-ID: Hi, I am trying to define a web service with SOAP over JMS. Went through the jbossws user guide. ( http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#JMS_Transport_Clients ) However the following line in the wsdl example was not clear to me. Is 'replyToName' a key word which is used to specify the response queue name? or is there other way to specify the request and reponse queue for a web service in the wsdl file? Could anybody point me to some good examples for SOAP over JMS? The versions I am using are: ----------------------------------------- JBoss AS 4.2.3.GA jbossws-3.0.1-native-2.0.4.GA jboss-messaging-1.4.2.GA (yes I am using JBoss Messaging instead of JBossMQ). Thanks in advance for the help. regards, Tanmay -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090309/c7b5174c/attachment.html From ropalka at redhat.com Tue Mar 10 02:39:16 2009 From: ropalka at redhat.com (Richard Opalka) Date: Tue, 10 Mar 2009 07:39:16 +0100 Subject: [jbossws-users] SOAP over JMS In-Reply-To: References: Message-ID: <49B60B14.4010103@redhat.com> Hi Tanmay, see inlined comments below: Richard tanmay pradhan wrote: > Hi, > I am trying to define a web service with SOAP over JMS. Went through the > jbossws user guide. > ( > http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#JMS_Transport_Clients > ) > > However the following line in the wsdl example was not clear to me. > > location='jms://queue/RequestQueue?replyToName=queue/ResponseQueue'/> > > Is 'replyToName' a key word which is used to specify the response queue > name? > Exactly > or is there other way to specify the request and reponse queue for a web > service in the wsdl file? > No AFAIK > Could anybody point me to some good examples for SOAP over JMS? > Download our SVN repo from http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk and have a look to jms sample, i.e.: # test resources trunk/modules/testsuite/native-tests/src/test/resources/jaxws/samples/jmstransport # test sources trunk/modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport > The versions I am using are: > ----------------------------------------- > JBoss AS 4.2.3.GA > jbossws-3.0.1-native-2.0.4.GA > jboss-messaging-1.4.2.GA (yes I am using JBoss Messaging instead of > JBossMQ). > I suggest you to upgrade to * JBossWS 3.1.0 (latest releases incorporating many bugfixes and enhancements) * JBossAS 5.0.1 for the same reason > Thanks in advance for the help. > > regards, > Tanmay > > transport='http://www.example.org/2006/06/soap/bindings/JMS/'/> > > > > namespace='http://org.jboss.ws/samples/jmstransport' use='literal'/> > > > namespace='http://org.jboss.ws/samples/jmstransport' use='literal'/> > > > > > > > location='jms://queue/RequestQueue?replyToName=queue/ResponseQueue'/> > > > > > ------------------------------------------------------------------------ > > _______________________________________________ > jbossws-users mailing list > jbossws-users at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbossws-users > -- B.Sc. Richard Opalka Senior Software Engineer JBoss, a division of Red Hat Mobile: +420 731 186 942 Mail: ropalka at redhat.com From do-not-reply at jboss.com Tue Mar 10 09:59:41 2009 From: do-not-reply at jboss.com (dendroid66) Date: Tue, 10 Mar 2009 09:59:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Type mapping trouble with JAX-WS and EJB3 Message-ID: <10438661.1236693581560.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, In fact I'm looking for an answer to excatly the same question. Probably, a library is needed, but I'm not 100% sure. ;) Have a nice day. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216583#4216583 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216583 From do-not-reply at jboss.com Tue Mar 10 10:59:58 2009 From: do-not-reply at jboss.com (Poonam7) Date: Tue, 10 Mar 2009 10:59:58 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Failed to create a new SAX parser Message-ID: <8747066.1236697198978.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am facing the same issue as mentioned above, there is no solution mentioned, can anyone please help? I am using xercesImpl.jar in jboss-5.0.0.GA\lib\endorsed folder, I added -Djava.endorsed.dirs=$JBOSS_HOME/lib/endorsed in JAVA_OPTS in run.conf, Still it does not work I get the same error org.jboss.xb.binding.JBossXBException: Failed to create a new SAX parser View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216612#4216612 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216612 From tanmay.pradhan at exilant.com Tue Mar 10 11:51:16 2009 From: tanmay.pradhan at exilant.com (tanmay pradhan) Date: Tue, 10 Mar 2009 08:51:16 -0700 Subject: [jbossws-users] SOAP over JMS In-Reply-To: <49B60B14.4010103@redhat.com> References: <49B60B14.4010103@redhat.com> Message-ID: Hi Richard, Thank you for the help. I will take a look at the examples in svn. regards, Tanmay On Mon, Mar 9, 2009 at 11:39 PM, Richard Opalka wrote: > Hi Tanmay, > > see inlined comments below: > > Richard > > tanmay pradhan wrote: > >> Hi, >> I am trying to define a web service with SOAP over JMS. Went through the >> jbossws user guide. >> ( >> >> http://jbossws.jboss.org/mediawiki/index.php?title=JAX-WS_User_Guide#JMS_Transport_Clients >> ) >> >> However the following line in the wsdl example was not clear to me. >> >> > location='jms://queue/RequestQueue?replyToName=queue/ResponseQueue'/> >> >> Is 'replyToName' a key word which is used to specify the response queue >> name? >> >> > Exactly > >> or is there other way to specify the request and reponse queue for a web >> service in the wsdl file? >> >> > No AFAIK > >> Could anybody point me to some good examples for SOAP over JMS? >> >> > Download our SVN repo from > http://anonsvn.jboss.org/repos/jbossws/stack/native/trunk > and have a look to jms sample, i.e.: > > # test resources > > trunk/modules/testsuite/native-tests/src/test/resources/jaxws/samples/jmstransport > # test sources > > trunk/modules/testsuite/native-tests/src/test/java/org/jboss/test/ws/jaxws/samples/jmstransport > >> The versions I am using are: >> ----------------------------------------- >> JBoss AS 4.2.3.GA >> jbossws-3.0.1-native-2.0.4.GA >> jboss-messaging-1.4.2.GA (yes I am using JBoss Messaging instead of >> JBossMQ). >> >> > I suggest you to upgrade to > * JBossWS 3.1.0 (latest releases incorporating many bugfixes and > enhancements) > * JBossAS 5.0.1 for the same reason > >> Thanks in advance for the help. >> >> regards, >> Tanmay >> >> > transport='http://www.example.org/2006/06/soap/bindings/JMS/'/> >> >> >> >> > namespace='http://org.jboss.ws/samples/jmstransport' use='literal'/> >> >> >> > namespace='http://org.jboss.ws/samples/jmstransport' use='literal'/> >> >> >> >> >> >> >> > location='jms://queue/RequestQueue?replyToName=queue/ResponseQueue'/> >> >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> jbossws-users mailing list >> jbossws-users at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbossws-users >> >> > > > -- > B.Sc. Richard Opalka > Senior Software Engineer > JBoss, a division of Red Hat > > Mobile: +420 731 186 942 > Mail: ropalka at redhat.com > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090310/ae4566f8/attachment.html From do-not-reply at jboss.com Tue Mar 10 14:03:27 2009 From: do-not-reply at jboss.com (glasscat) Date: Tue, 10 Mar 2009 14:03:27 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Generating WSDL from request/response Message-ID: <5866735.1236708207804.JavaMail.jboss@colo-br-02.atl.jboss.com> Is there any tools to generate WSDL given the SOAP request and response? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216689#4216689 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216689 From do-not-reply at jboss.com Wed Mar 11 04:53:12 2009 From: do-not-reply at jboss.com (Sancheski) Date: Wed, 11 Mar 2009 04:53:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.ClassCastException: org.jboss.ws.core.jaxws.sp Message-ID: <1467633.1236761592729.JavaMail.jboss@colo-br-02.atl.jboss.com> I have the same problem, have you fixed it? Thanks in advance! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216873#4216873 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216873 From do-not-reply at jboss.com Wed Mar 11 04:57:35 2009 From: do-not-reply at jboss.com (Sancheski) Date: Wed, 11 Mar 2009 04:57:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Handler execution order in handler chain Message-ID: <14566326.1236761855157.JavaMail.jboss@colo-br-02.atl.jboss.com> This is how it works, taking the descriptor file from last post: Handlers in server side - Server in: 1) Handler 3 2) Handler 2 3) Handler 1 - Server out: 1) Handler 1 2) Handler 2 3) Handler 3 Handlers in client side - Client out: 1) Handler 1 2) Handler 2 3) Handler 3 - Client in: 1) Handler 3 2) Handler 2 3) Handler 1 See HandlerChainExecutor class. Cheers, David Sancho View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216874#4216874 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216874 From do-not-reply at jboss.com Wed Mar 11 04:57:55 2009 From: do-not-reply at jboss.com (getaceres) Date: Wed, 11 Mar 2009 04:57:55 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.ClassCastException: org.jboss.ws.core.jaxws.sp Message-ID: <19884023.1236761875943.JavaMail.jboss@colo-br-02.atl.jboss.com> I have the same problem. I've upgraded to JBossWS 3.1 and my Web Service clients executing in JBoss are throwing this exception. I'm going back to 3.0.5 until this is fixed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216875#4216875 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216875 From do-not-reply at jboss.com Wed Mar 11 05:48:19 2009 From: do-not-reply at jboss.com (rodosa) Date: Wed, 11 Mar 2009 05:48:19 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.ClassCastException: org.jboss.ws.core.jaxws.sp Message-ID: <26552744.1236764899403.JavaMail.jboss@colo-br-02.atl.jboss.com> I don't remember how I fixed it, because I've had a lot of problems with WS in Jboss and Jboss jbpm. The solution was in the libraries, the libraries that I used was wrong. Read this and take special attention at libraries [url]http://jbossws.jboss.org/mediawiki/index.php?title=Install_JBossWS [/url] Now, I tell us some changes I did with libraries. Hope this help us. Good luck!!! In case, Jboss-4.0.5 I think that I've replaced: --> commons-httpclient.jar for commons-httpclient-3.1.jar in jboss-4.0.5.GA\client folder. In case, Jboss jbpm3.2.2 I think that I've replaced: -->jboss-jaxws.jar_ for jboss-jaxws-ext.jar in C:\jbpm-jpdl-3.2.3\server\server\jbpm\lib -->jboss-jaxws.jar_ for jboss-jaxws-ext.jar in C:\jbpm-jpdl-3.2.3\server\server\jbpm\lib in C:\jbpm-jpdl-3.2.3\server\lib\endorsed In case, Jboss jbpm3.2.2 I think that I've deleted -->jboss-jaxws.jar of C:\jbpm-jpdl-3.2.3\server\client and C:\jbpm-jpdl-3.2.3\server\server\jbpm\deploy\jbossws.sar -->jbpm-jpdl.jar_ in C:\jbpm-jpdl-3.2.3\server\server\jbpm\lib I've created some post relacionates with WS. Maybe these could help us a little: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=147494 http://www.jboss.org/index.html?module=bb&op=viewtopic&t=147344 http://www.jboss.org/index.html?module=bb&op=viewtopic&t=147234 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216893#4216893 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216893 From do-not-reply at jboss.com Wed Mar 11 09:09:04 2009 From: do-not-reply at jboss.com (razshaar) Date: Wed, 11 Mar 2009 09:09:04 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JAXRPCMetaDataBuilder throws Exception: Message-ID: <32608852.1236776944961.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm running on Jboss4.2.3. when starting the server getting the following warning from JAXRPCMetaDataBuilder.class: Cannot obtain fault type for element: {http://www.MySite.com}MyException. It seems that the everything works fine. Does anyone know the reason for such warn? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216947#4216947 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216947 From do-not-reply at jboss.com Wed Mar 11 13:51:14 2009 From: do-not-reply at jboss.com (zzuli) Date: Wed, 11 Mar 2009 13:51:14 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problem of getting asynchronous response Message-ID: <5201519.1236793874241.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi,everyone: I'm getting started with JAX-WS, and get stuck with getting the asynchronous message response. The code: private void getStudentList(JAXWS ws) throws Exception{ GetStudentListRequest request= new GetStudentListRequest(); request.setDepId(1); ws.getStuListAsync(request, new GetStudentListCallBack() ); System.out.println("print immediately after call ws."); try { Thread.sleep(20000); } catch (InterruptedException e) { } } private class GetStudentListCallBack implements javax.xml.ws.AsyncHandler{ public void handleResponse(Response res) { System.out.println("test1"); try{ System.out.println("test2"); System.out.println(res.get()); }catch (Exception e) { } } } When i run the code, i get "test1" and "test2" printed, but there's no result of res.get(), it seems that the "get()" method-call is blocked, but there's no exception. If i try "res.isDone()", i can get "true". I use jboss5.0.1 Could anyone help me? Thanks a lot. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217102#4217102 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217102 From tanmay.pradhan at exilant.com Wed Mar 11 17:51:28 2009 From: tanmay.pradhan at exilant.com (tanmay pradhan) Date: Wed, 11 Mar 2009 14:51:28 -0700 Subject: [jbossws-users] SOAP/JMS topic with multiple service instance Message-ID: Hi, I need a help for the following configuration. I need to define a web service (with SOAP over JMS). For scalability purpose I need to deploy multiple instances of the same web service. But all the instances of the service are subscriber to a single topic ( name is 'testTopic'). How do I specify that the message should be removed from the topic after read by one subscriber? I guess by this load balancing can be done. Default configuration for testTopic in destinations-service.xml is extracted below: jboss .messaging:service=ServerPeer jboss.messaging:service=PostOffice Where can I get the explanation for all possible attributes/tags used to configure a topic in destinations-service.xml? Please correct me if my approach for achieving scalability by deploying multiple instance of same web service (war files) listening on a single topic is wrong. The versions I am using are: ----------------------------------------- JBoss AS 4.2.3.GA jbossws-3.0.1-native-2.0.4.GA jboss-messaging-1.4.2.GA regards, Tanmay -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090311/07d2ee3b/attachment.html From do-not-reply at jboss.com Wed Mar 11 19:12:41 2009 From: do-not-reply at jboss.com (jnorris10) Date: Wed, 11 Mar 2009 19:12:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebServiceContext injection. Was it fixed or not? Message-ID: <21498393.1236813161401.JavaMail.jboss@colo-br-02.atl.jboss.com> "thomas.diesler at jboss.com" wrote : Your field cannot be private, use | | | | @Resource | | WebServiceContext context; | | | Why does this restriction exist? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217208#4217208 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217208 From do-not-reply at jboss.com Thu Mar 12 03:40:43 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Thu, 12 Mar 2009 03:40:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebServiceContext injection. Was it fixed or not? Message-ID: <13249258.1236843643729.JavaMail.jboss@colo-br-02.atl.jboss.com> "jnorris10" wrote : "thomas.diesler at jboss.com" wrote : Why does this restriction exist? | According to javax.annotation.Resource javadoc you can use private qualifier as well. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217288#4217288 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217288 From do-not-reply at jboss.com Thu Mar 12 09:42:03 2009 From: do-not-reply at jboss.com (teraryan) Date: Thu, 12 Mar 2009 09:42:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - have interceptors fire when calling web service method from Message-ID: <15677829.1236865323348.JavaMail.jboss@colo-br-02.atl.jboss.com> I posted this in EJB3, but maybe JBossWS is a better forum. It's easiest to explain by giving an example. I have an EJB3 stateless session / web method annotated with interceptors: | @Interceptors({a.class, b.class}) | @WebMethod | public String processService(String request) | Now I need to create another method that, instead of returning a String, returns a more complex object, ie. But the more complex Object can be created using a String from calling processService(), ie. | @WebMethod | public ComplexObject processServiceComplex(String request) { | return new ComplexObject(processService(request)); | } | But when I do this (implementing processServiceComplex in the same class as processService), the interceptors for processService don't fire. Is there any way I can get them to fire? I can't use all the interceptors on processServiceComplex, because some of them expect a String as the return value. I also want both methods to be available in the same web services interface, although they don't necessarily need to be in the same class. Basically, I want to re-use the interceptors if possible. Is there any way to do this? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217456#4217456 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217456 From do-not-reply at jboss.com Thu Mar 12 11:40:43 2009 From: do-not-reply at jboss.com (priyanjan) Date: Thu, 12 Mar 2009 11:40:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://mtn/ Message-ID: <25025147.1236872443371.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using Jrun4 server and some web services deployed on it.Client application,that accessing these services is deployed on JBoss 4.0.4.GA server.both servers are on same machine.JBoss server url is SSL secured.I wish to migrate web services from JRun server to JBoss 4.0.5.GA(same server on which client application is running).I have created web services for jboss(java classes are same as deployed on jrun server) and deployed on same server.Client application retrieves web service url from a property file.i have configured this property file with my new web service url(url of web services that are deployed on Jboss).But when i try to access these services from client application, an exception is thrown.This is as follows: javax.xml.rpc.soap.SOAPFaultException: Endpoint {http://mtn/jaws}WebServiceRegistrationPort does not contain operation meta data for: {http://soapinterop.org/}webUserRegistration at org.jboss.ws.server.ServiceEndpointInvoker.getDispatchDestination(ServiceEndpointInvoker.java:181) at org.jboss.ws.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:107) at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:209) at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355) at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595) WebServiceRegistration is a web service that is deployed on JBoss server. Please help me to sort out this problem. waiting for your suggestions -- priyanjan View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217537#4217537 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217537 From do-not-reply at jboss.com Thu Mar 12 12:15:21 2009 From: do-not-reply at jboss.com (erahamim) Date: Thu, 12 Mar 2009 12:15:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Cannot obtain fault type for elemet Message-ID: <12637295.1236874521365.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I have just migrate from jboss 4.0.5 to jboss 4.2.3. In the new jboss I'm getting the following warning on my web services: JAXRPCMetaDataBuilder - Cannot obtain fault type for element: {http://www.opentv.co.il}TriggerException. TriggerException is an exception that is thrown from a number of web services in a different packages. I found out that if I duplicate the exception class and place it in the package of each web service the warning stop. Is there any other way to do it? I have lots of web services but I want to use only single class. Thanks, Eyal. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217558#4217558 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217558 From do-not-reply at jboss.com Thu Mar 12 12:33:26 2009 From: do-not-reply at jboss.com (nicvas) Date: Thu, 12 Mar 2009 12:33:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: How can I print to log file input soap request and respo Message-ID: <24977751.1236875606096.JavaMail.jboss@colo-br-02.atl.jboss.com> Solution for: server: jbossas 4.2.1.GA server library: jbossws-1.2 source library: jbossws-src-1.2.1.GA in http://www.jboss.org/jbossws/downloads/ jar_path: jboss/server/default/deploy/jbossws.sar/jbossws-core.jar package: org.jboss.ws.core.jaxws class: JAXBDeserializer method: public Object deserialize(QName xmlName, QName xmlType, Source xmlFragment, SerializationContext serContext) throws BindingException Must be add the code below: String sourceString = sourceToString(xmlFragment); if(log.isDebugEnabled()) log.debug("InputSourceString: "+sourceString); below the method upgraded: public Object deserialize(QName xmlName, QName xmlType, Source xmlFragment, SerializationContext serContext) throws BindingException { if(log.isDebugEnabled()) log.debug("deserialize: [xmlName=" + xmlName + ",xmlType=" + xmlType + "]"); Object value = null; try { String sourceString = sourceToString(xmlFragment); if(log.isDebugEnabled()) log.debug("InputSourceString: "+sourceString); Class[] javaTypes = (Class[])serContext.getProperty(SerializationContextJAXWS.CONTEXT_TYPES); TypeMappingImpl typeMapping = serContext.getTypeMapping(); Class javaType = typeMapping.getJavaType(xmlType); // es. javaType: class org.isc.are.ws.jaxws.GetBanner JAXBContext jaxbContext = getJAXBContext(javaTypes); Unmarshaller unmarshaller = jaxbContext.createUnmarshaller(); //SchemaFactory schemaFactory = SchemaFactory.newInstance(XMLConstants.W3C_XML_SCHEMA_NS_URI); //Source schemaSource = new StreamSource(new File("/home/jboss/jboss/testdatasource/ARE_GetBannerService.xsd")); //Schema schema = schemaFactory.newSchema(schemaSource); //unmarshaller.setSchema(schema); unmarshaller.setAttachmentUnmarshaller( new AttachmentUnmarshallerImpl()); JAXBElement jbe = unmarshaller.unmarshal(xmlFragment, javaType); value = jbe.getValue(); if(log.isDebugEnabled()) log.debug("deserialized: " + (value != null ? value.getClass().getName() : null)); //deserialized: org.isc.are.ws.jaxws.GetBanner } catch (Exception ex) { log.error("error during deserialize.", ex); handleUnmarshallException(ex); } return value; } View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217571#4217571 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217571 From do-not-reply at jboss.com Thu Mar 12 15:03:03 2009 From: do-not-reply at jboss.com (pablinkus) Date: Thu, 12 Mar 2009 15:03:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Casting porblem Message-ID: <21748865.1236884583868.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'm quite new with web services, so perhaps it is a stupid question. I'm working with JBoss 4.2.2 and I've installed JBossws-native 3.0.5. I've created a simple web service with he method that receive and List of objects. Something like this: public long startTramitadorInstance(String processName, List < Product > productList) Product is a superclass and I've set in it the @XmlSeeAlso tag with the subclasses. I use the wscompile included in the jbossws-native package tool to generate classese from the WSDL. And if I call this method from a client and the List is formed for several subclasses of the superclass, I always get an Exception: Caused by: java.lang.ClassCastException: com..beans.product.Product cannot be cast to com..beans.product.Subproduct Is that normal? Cann't I use superclasses or abstract classes in the methods of the web service? Am I doing something wrong? Thanks in advance Pablo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217622#4217622 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217622 From do-not-reply at jboss.com Thu Mar 12 16:47:51 2009 From: do-not-reply at jboss.com (pablinkus) Date: Thu, 12 Mar 2009 16:47:51 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance - JbossWS Message-ID: <12025714.1236890871530.JavaMail.jboss@colo-br-02.atl.jboss.com> I've just opened a post with the same question. Do anybody has some clue about what it is happening? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217647#4217647 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217647 From do-not-reply at jboss.com Fri Mar 13 03:39:40 2009 From: do-not-reply at jboss.com (pablinkus) Date: Fri, 13 Mar 2009 03:39:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance - JbossWS Message-ID: <7809751.1236929980889.JavaMail.jboss@colo-br-02.atl.jboss.com> By the way, I have been reading some posts related with this inheritance problem in JbossWS but with older versions. I'm using the last one, so I suppose it is solve and I'm doing somethhing wrong, Thanks again View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217735#4217735 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217735 From do-not-reply at jboss.com Fri Mar 13 15:42:47 2009 From: do-not-reply at jboss.com (pablinkus) Date: Fri, 13 Mar 2009 15:42:47 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance - JbossWS Message-ID: <8603638.1236973367324.JavaMail.jboss@colo-br-02.atl.jboss.com> Is it real the anybody had to deal with inheritance with service and found a solution? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4217952#4217952 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4217952 From do-not-reply at jboss.com Sat Mar 14 11:32:31 2009 From: do-not-reply at jboss.com (clust3r) Date: Sat, 14 Mar 2009 11:32:31 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wsprovide fails - JAXB-API problem Message-ID: <9181485.1237044751817.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi there, I just tried to use wsprovide to generate the JAX-WS portable artifacts for my web service but it fails: anonymous wrote : java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/programme/Java/jboss-4.2.3.GA/client/jaxb-impl.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/) I already tried to move the jaxb-api.jar from %JBOSS_HOME%/lib to %JBOSS_HOME%/lib/endorsed but that had no effect... I'm using JBoss 4.2.3GA and JDK 1.6.0_12, any ideas how to fix this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218029#4218029 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218029 From do-not-reply at jboss.com Mon Mar 16 03:48:45 2009 From: do-not-reply at jboss.com (manasamurthy) Date: Mon, 16 Mar 2009 03:48:45 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBoss ws-security client error Message-ID: <18378691.1237189725442.JavaMail.jboss@colo-br-02.atl.jboss.com> When I run my web service client war, I get the below error. These are the steps I have followed: 1. Generate code using wsconsume 2. Deploy both client and server (server running locally) 3. Add jboss-wsse-client.xml appropriately 4. On the first call to the server after getting port I get the exception: [Fatal Error] :-1:-1: Premature end of file. 2009-03-16 00:44:28,298 -0700 ERROR [org.jboss.ws.extensions.security.jaxws.WSSecurityHandler] uniqueId=ec95a826-a291-47ab-abbe-17ecd2435531 hostname=pditvm10286 requestURI=/billing/payment-request/list.url clientIP=127.0.0.1 (abc at gmail.com) Cannot handle inbound ws-security javax.xml.soap.SOAPException: Cannot obtain SOAPHeader from SOAPMessage at javax.xml.soap.SOAPMessage.getSOAPHeader(SOAPMessage.java:202) at org.jboss.ws.extensions.security.WSSecurityDispatcher.handleInbound(WSSecurityDispatcher.java:113) at org.jboss.ws.extensions.security.jaxws.WSSecurityHandler.handleInboundSecurity(WSSecurityHandler.java:78) at org.jboss.ws.extensions.security.jaxws.WSSecurityHandlerClient.handleInbound(WSSecurityHandlerClient.java:40) at org.jboss.ws.core.jaxws.handler.GenericHandler.handleMessage(GenericHandler.java:55) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:295) at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:140) at org.jboss.ws.core.jaxws.client.ClientImpl.callResponseHandlerChain(ClientImpl.java:168) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:363) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy304.initializeItemCatalogService(Unknown Source) My jboss-wsse-client.xml looks like this I have ensured the server code works, by writing a standalone client with the same code and it runs fine. Am I missing anything? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218142#4218142 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218142 From do-not-reply at jboss.com Mon Mar 16 05:00:20 2009 From: do-not-reply at jboss.com (pablinkus) Date: Mon, 16 Mar 2009 05:00:20 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: wsprovide fails - JAXB-API problem Message-ID: <24809134.1237194020158.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, for running JBossWS with JDK 6 I followed these steps: http://jbossws.jboss.org/mediawiki/index.php?title=Install_JBossWS I hope it helps View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218151#4218151 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218151 From do-not-reply at jboss.com Tue Mar 17 01:41:29 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Tue, 17 Mar 2009 01:41:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebServices logging Message-ID: <22062345.1237268489634.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all Thanks for the reply and your time, Now, I have moved to jboss 4.2.3 GA. I could find the record processors installed. I enabled recording for both log recorder and memory buffer recorder. In the web service endpoint, I provided the config | @WebService() | @EndpointConfig(configName = "Standard Endpoint") | @SOAPBinding(style = SOAPBinding.Style.DOCUMENT) | I had enabled web service trace too, in the jboss_log4j.xml But could not find any recording in server.log :-( regards KRS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218477#4218477 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218477 From do-not-reply at jboss.com Tue Mar 17 06:08:09 2009 From: do-not-reply at jboss.com (pmckeown) Date: Tue, 17 Mar 2009 06:08:09 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wsprovide & packages with multiple services Message-ID: <18703694.1237284489556.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all, I've been searching the forums and not been able to find any posts regarding this issue and I'm new to JBoss so apologies if this has been previously covered. I'm attempting to expose the business layer of our application as Web Services. As the business layer has already been written, and is used by other parts of the application, one of the requirements of this project is that it doesn't change, so I'm tasked with only using annotations to mark up our code, to create the Web Services. However, I'm running into an issue when I expose 2 services in the same package. ServiceX and ServiceY both have a create() method that take an XTransferObject and a YTransferObject as parameters. However, when the wsdl and proxy classes are created by wsprovide, the first service's generated code (com.mypackage.jaxws.Create.java) is being overwritten by the second service's generated code as both method's are named the same. My question is, is there any way to easily alter the code generated by wsprovide, so that it either a) names the created classes using both the class and method names, i.e. com.mypackage.jaxws.ServiceX_Create.java and com.mypackage.jaxws.ServiceY_Create.java or b) names the package using the annotated class name, such as com.mypackage.servicex instead of com.mypackage.jaxws or c) something else.... Any help would be greatly appreciated. Thanks, Paul View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218530#4218530 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218530 From do-not-reply at jboss.com Tue Mar 17 09:44:52 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 17 Mar 2009 09:44:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: NullPointerException with jbossws 2.0.1 Message-ID: <2590870.1237297492639.JavaMail.jboss@colo-br-02.atl.jboss.com> The documentation fix mentioned in JBWS-1800 doesn't work on AS 5.x series. Related issue is: JBAS-6185. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218643#4218643 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218643 From do-not-reply at jboss.com Tue Mar 17 09:50:39 2009 From: do-not-reply at jboss.com (mounir-aboud) Date: Tue, 17 Mar 2009 09:50:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Urgent Exception Message-ID: <30670294.1237297839959.JavaMail.jboss@colo-br-02.atl.jboss.com> Please i need a help i have deployed a web service and it is running but in each time that i make a request i got this exception and the service keep running org.jboss.ws.WSException: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:640) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:153) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:135) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Caused by: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:636) ... 22 more Caused by: java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:761) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570) at org.apache.coyote.Response.doWrite(Response.java:560) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353) ... 27 more ERROR [http-127.0.0.1-9080-2] 09-03-17 15:29:53,875 [[Service]] : Servlet.service() for servlet Service threw exception java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:761) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570) at org.apache.coyote.Response.doWrite(Response.java:560) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:636) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:153) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:135) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) INFO [Thread-13] 09-03-17 15:31:58,515 [STDOUT] : 1818547 [Thread-13] DEBUG com.mobinets.mps.business.bo.message.impl.SRMessageSenderProxyImpl - execute(OTADCMUTL, [27022, 99282563, [Ljava.lang.Object;@16bf0e6]) ERROR [http-127.0.0.1-9080-1] 09-03-17 15:31:59,062 [RequestHandlerImpl] : Error processing web service request org.jboss.ws.WSException: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:640) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:153) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:135) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) Caused by: ClientAbortException: java.net.SocketException: Software caused connection abort: socket write error at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:358) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:636) ... 22 more Caused by: java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:761) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570) at org.apache.coyote.Response.doWrite(Response.java:560) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353) ... 27 more ERROR [http-127.0.0.1-9080-1] 09-03-17 15:31:59,062 [[Service]] : Servlet.service() for servlet Service threw exception java.net.SocketException: Software caused connection abort: socket write error at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at org.apache.coyote.http11.InternalOutputBuffer.realWriteBytes(InternalOutputBuffer.java:737) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.tomcat.util.buf.ByteChunk.append(ByteChunk.java:349) at org.apache.coyote.http11.InternalOutputBuffer$OutputStreamOutputBuffer.doWrite(InternalOutputBuffer.java:761) at org.apache.coyote.http11.filters.ChunkedOutputFilter.doWrite(ChunkedOutputFilter.java:124) at org.apache.coyote.http11.InternalOutputBuffer.doWrite(InternalOutputBuffer.java:570) at org.apache.coyote.Response.doWrite(Response.java:560) at org.apache.catalina.connector.OutputBuffer.realWriteBytes(OutputBuffer.java:353) at org.apache.tomcat.util.buf.ByteChunk.flushBuffer(ByteChunk.java:434) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:309) at org.apache.catalina.connector.OutputBuffer.close(OutputBuffer.java:273) at org.apache.catalina.connector.CoyoteOutputStream.close(CoyoteOutputStream.java:104) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleWSDLRequest(RequestHandlerImpl.java:636) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doGet(RequestHandlerImpl.java:153) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:135) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) So if anyone could help it is an urgent issue Thanks in advance View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218645#4218645 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218645 From do-not-reply at jboss.com Tue Mar 17 10:05:39 2009 From: do-not-reply at jboss.com (mahdesh) Date: Tue, 17 Mar 2009 10:05:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - java.lang.UnsupportedOperationException: setProperty must be Message-ID: <18940282.1237298739435.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am deploying my web service on JBossWS + jboss-5.0.1.GA + jdk1.6.0_12 I am following tutorial http://www.codeproject.com/KB/java/webservice-for-jboss.aspx and web service properly deployed. I also generated client stubs using wsdl2java and wrote a client of my own. In both cases, getting following error. 18:57:37,953 ERROR [[GreetingWebService]] Servlet.service() for servlet GreetingWebService threw exception java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage at javax.xml.soap.SOAPMessage.setProperty(SOAPMessage.java:441) at org.jboss.ws.core.soap.SOAPMessageImpl.(SOAPMessageImpl.java:82) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:169) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.createSOAPMessage(SOAPFaultHelperJAXWS.java:295) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:256) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:187) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:102) at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:496) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:295) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) at org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:85) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126 ) at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) I have gone through http://sourceforge.net/project/shownotes.php?release_id=645033&group_id=22866 and manually copied the following libraries from the JBOSS_HOME/client directory to the JBOSS_HOME/lib/endorsed * jbossws-native-saaj.jar * jbossws-native-jaxrpc.jar * jbossws-native-jaxws.jar * jbossws-native-jaxws-ext.jar Also I set -Dsun.lang.ClassLoader.allowArraySyntax=true to run.conf Still the problem persists.. .. .. Please let me know the fix. Thanks in advance. Thanks, Mahesh View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218654#4218654 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218654 From do-not-reply at jboss.com Tue Mar 17 11:07:11 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 17 Mar 2009 11:07:11 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Trying to use jboss.xml instead of @WebContext Message-ID: <11160568.1237302432075.JavaMail.jboss@colo-br-02.atl.jboss.com> Please read my last comments on JBWS-1309 issue on Jira. This should work since August 2008, on AS 5 or later only. I've added 2 testcases showing that: http://fisheye.jboss.org/changelog/JBossWS/?cs=9612 http://fisheye.jboss.org/changelog/JBossWS/?cs=9609 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218686#4218686 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218686 From do-not-reply at jboss.com Tue Mar 17 11:49:07 2009 From: do-not-reply at jboss.com (PeterJ) Date: Tue, 17 Mar 2009 11:49:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.UnsupportedOperationException: setProperty mus Message-ID: <13038752.1237304947996.JavaMail.jboss@colo-br-02.atl.jboss.com> Sounds like you downloaded the JDK5 variant of 5.0.1, and not the JDK6 variant. The error you got is a common one when using JDK 6 to run the JDK5 variant of JBoss AS. You can either download the jdk6 variant, or search the forums for setProperty to locate a workaround (which involves copying specific jar file to the endoresed directory). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218715#4218715 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218715 From do-not-reply at jboss.com Tue Mar 17 13:24:56 2009 From: do-not-reply at jboss.com (rakula) Date: Tue, 17 Mar 2009 13:24:56 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - ERROR [STDERR] javax.naming.NameNotFoundException: RuleEngin Message-ID: <31576395.1237310696829.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, Currently, my application is deployed on JBoss 4.x, I am in the process of migrating to Jboss 5.x. My application in suceesfully deployed in Jboss 5.0.1 GA using JDK 1.6 but i get the following error when the client is trying to lookup for an ejb. The client request is coming through a servlet. 09:28:59,606 ERROR [STDERR] javax.naming.NameNotFoundException: RuleEngineManager not bound 09:28:59,606 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(Naming Server.java:771) 09:28:59,606 ERROR [STDERR] at org.jnp.server.NamingServer.getBinding(Naming Server.java:779) 09:28:59,606 ERROR [STDERR] at org.jnp.server.NamingServer.getObject(NamingS erver.java:785) 09:28:59,731 ERROR [STDERR] at org.jnp.server.NamingServer.lookup(NamingServ er.java:443) 09:28:59,731 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0( Native Method) 09:28:59,731 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(N ativeMethodAccessorImpl.java:39) 09:28:59,731 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invo ke(DelegatingMethodAccessorImpl.java:25) 09:28:59,731 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:5 97) 09:28:59,731 ERROR [STDERR] at sun.rmi.server.UnicastServerRef.dispatch(Unic astServerRef.java:305) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.Transport$1.run(Transport.j ava:159) 09:28:59,731 ERROR [STDERR] at java.security.AccessController.doPrivileged(N ative Method) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.Transport.serviceCall(Trans port.java:155) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport.handleMess ages(TCPTransport.java:535) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$Connection Handler.run0(TCPTransport.java:790) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.tcp.TCPTransport$Connection Handler.run(TCPTransport.java:649) 09:28:59,731 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worke r.runTask(ThreadPoolExecutor.java:886) 09:28:59,731 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worke r.run(ThreadPoolExecutor.java:908) 09:28:59,731 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.exceptionR eceivedFromServer(StreamRemoteCall.java:255) 09:28:59,731 ERROR [STDERR] at sun.rmi.transport.StreamRemoteCall.executeCal l(StreamRemoteCall.java:233) 09:28:59,731 ERROR [STDERR] at sun.rmi.server.UnicastRef.invoke(UnicastRef.j ava:142) 09:28:59,747 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag= JBoss_5_0_1_GA date=200902231221)] Started in 3m:45s:522ms 09:28:59,747 ERROR [STDERR] at org.jnp.server.NamingServer_Stub.lookup(Unkno wn Source) 09:28:59,747 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(Namin gContext.java:722) 09:28:59,747 ERROR [STDERR] at org.jnp.interfaces.NamingContext.lookup(Namin gContext.java:682) 09:28:59,762 ERROR [STDERR] at javax.naming.InitialContext.lookup(InitialCon text.java:392) 09:28:59,762 ERROR [STDERR] at b2b.beans.EntityBeanLookup.getRuleEngineManag er(EntityBeanLookup.java:1941) 09:28:59,762 ERROR [STDERR] at b2b.beans.EntityBeanLookup.getRuleEngineManag er(EntityBeanLookup.java:1922) 09:28:59,762 ERROR [STDERR] at b2b.managers.system.EndOfDayMonitor.run(EndOf DayMonitor.java:78) 09:28:59,762 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:512 ) 09:28:59,762 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:462) 09:28:59,762 INFO [STDOUT] Got EJB context from JNDI javax.naming.InitialContex t at 1d673d3 My application is deployed as .ear file. This .ear contains different .jar files for each of the ejb's and a .war for a web application. Servlet is deployed in the .war file. Also, utility classes are bundled in a jar within this .ear file. This is the structure of .ear file .ear -META-INF -application.xmk -MANIFEST.mf -.jar for each of the ejbs -bean classes -META-INF -ejb-jar.xml -jboss.xml --MANIFEST.mf -.war -WEB-INF -servlet classes and other classes So far i did these to resolve this issue 1) Removed some of the duplicate ejb classes loaded in .war 2) deployment sequence Looks like ejb's are getting deployed before .war deployment. This is order i set up in server\default\conf\xmdesc\org.jboss.deployment.MainDeployer-xmbean.xml Statically set one or more enhanced suffix orders, independent of the value proposed by subdeployers. Some deployers may also allow the suffixes/orders to be set locally, so that's preferable too. For reference, this is the list of enhanced suffixes likely to be set by deployers (it may not be completely up-to-date, or there can be user-defined deployers). 050:.deployer,050:-deployer.xml,100:.aop,100:-aop.xml,150:.sar,150:-service.xml,200:.beans,250:.rar,300:-ds.xml,350:.har,400:.jar,400:.ejb3,400:.par,500:.war,600:.wsr,650:.ear,700:.jar,750:.zip,800:.bsh,900:.last Until we resolve some startup issues, we'll setup some static enhanced suffix orders bellow and leave the rest of the suffixes contributed dynamically by registering deployers. 3) Some of the class loading configuration like "java2ClassLoadingCompliance", "java2ParentDelegation" set to true Can somebody please help me to figure out the problem here? I am not sure if is a class loading issue or context issue or something else. This package(.ear) perfectly works in Jboss 4.x. I am having issues only in Jboss 5.0.1 GA One more thing, Initially, it was complaining(Class not found) about the claases located in utility/helper classes jar file. This jar file class path setup in the manifest file. To get rid of this error, i have copied this jar file in the jboss lib directory. After i copied this jar file, i didn't see this error. Thanks, Raj View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218776#4218776 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218776 From do-not-reply at jboss.com Tue Mar 17 19:40:07 2009 From: do-not-reply at jboss.com (mahdesh) Date: Tue, 17 Mar 2009 19:40:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.UnsupportedOperationException: setProperty mus Message-ID: <25694374.1237333207117.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks Peter for response but issue was altogether different. I got the solution as mentioned in release notes http://sourceforge.net/project/shownotes.php?release_id=645033&group_id=22866 We copy the few libraries from the JBOSS_HOME/client directory to the JBOSS_HOME/lib/endorsed directory That fixes it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218837#4218837 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218837 From do-not-reply at jboss.com Wed Mar 18 00:18:58 2009 From: do-not-reply at jboss.com (scottmh) Date: Wed, 18 Mar 2009 00:18:58 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Additional SOAP Header data. Message-ID: <4630259.1237349938463.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using jbossws 2.0.3 as a standalone client trying to call a https webservice (which is not mine). The wrinkle seems to be they want a custom security token placed in the SOAPHeader. This token then needs to be signed. So far... I have consumed the wsdl and generated the necessary objects. I think I have the certs, jboss-wsse-client.xml and standard-jaxws-client-config.xml correct, as the SSL handshake works and it generates SOAP. I then added a SOAPHandler to the binding which adds the content to the SOAPHeader...but no matter what I try I cannot get the added content to be signed. Can anyone give any guidance on how to accomplish this? Thanks in advance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218865#4218865 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218865 From do-not-reply at jboss.com Wed Mar 18 05:00:33 2009 From: do-not-reply at jboss.com (erahamim) Date: Wed, 18 Mar 2009 05:00:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain fault type for elemet Message-ID: <30505009.1237366833853.JavaMail.jboss@colo-br-02.atl.jboss.com> Adding more details: My exception is: | package com.company.Exceptions | public class TriggerException extends Exception{ | private String msgName; | public TriggerException() { | } | public String getMsgName() { | return msgName; | } | public void setMsgName(String msgName) { | this.msgName = msgName; | } | } | My endpoint service (ejb 2.1) | | package com.company.rundownEx.ejb; | | public interface RundownEx extends Remote{ | Data getData(long Id) throws TriggerException, RemoteException; | } | implementation | package com.company.rundownEx.ejb; | | public class RundownExBean implements SessionBean { | | public Data getData (long in) throws TriggerException{ | try{ | | // do something | } | // ENTRY_POINT_CATCH_START | catch(Exception rte){ | // ENTRY_POINT_CATCH_END | | throw new TriggerException (); } | } | } | My configuration xml for wstool: | | | | | | | | | When I try to generate client with eclipse I'm getting the following error: Error in generating Java from WSDL: java.io.IOException: Element {http://www.opentv.co.il}TriggerException is referenced but not defined. java.io.IOException: Element {http://www.opentv.co.il}TriggerException is referenced but not defined. Can anyone help? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218935#4218935 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218935 From do-not-reply at jboss.com Wed Mar 18 05:40:37 2009 From: do-not-reply at jboss.com (dhanushgopinath) Date: Wed, 18 Mar 2009 05:40:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WebServiceContext injection. Was it fixed or not? Message-ID: <14678394.1237369237070.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am using JBOSS 4.2.3 with JBOSS WS 3.1.0 and I am also getting the same problem. The web service context is getting null. Here is my service | | @WebService(serviceName = "AWFUtilityService", targetNamespace = "http://www.test.com/WF/Framework/AWFUtilityService", endpointInterface = "com.test.wf.framework.awfutilityservice.AWFUtilityServicePortType",portName="AWFUtilityServicePort",wsdlLocation="WEB-INF/wsdl/AWFUtilityService.wsdl") | public class AWFUtilityServiceImpl implements AWFUtilityServicePortType { | | @Resource | WebServiceContext context; | | @WebMethod | public String getCorrelationID(String CorrelationID) | throws GetCorrelationIDFault | { | SOAPMessageContext soapMsgContext = (SOAPMessageContext) context.getMessageContext(); | try { | boolean login = ParseAndValidateSoapHeader(soapMsgContext); | } catch (EPMAuthenticationFailureException e) { | // TODO Auto-generated catch block | e.printStackTrace(); | } | String strCorrValue = EPMUtils.GetGloballyUniqueID(); | return CorrelationID + "_" + strCorrValue; | } | Is this still a bug in JBOSS WS or am I doing some thing wrong. Thanks DHanush View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4218957#4218957 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4218957 From CHALASAA at bupa.com Wed Mar 18 10:22:36 2009 From: CHALASAA at bupa.com (CHALASANI, Aruna) Date: Wed, 18 Mar 2009 14:22:36 -0000 Subject: [jbossws-users] jbossws version for implementing username token Message-ID: <66FBC3F9485AB149B8DA52EB734276E503238292@GBMANVEX01.GB.BUPAGROUP.COM> Hello, I am working on jboss-4.0.4GA and jbossws1.0.4 to implement webservice security using username tokens. Is it possible to achieve this with jbossws1.0.4? Thanks. Regards, AC Our Story ... The Bupa Story Visit www.bupastory.com to find out who we are, where we've come from, what we're about and where we're going. Bupa House 15-19 Bloomsbury Way London WC1A 2BA Internet communications are not secure and therefore Bupa does not accept legal responsibility for the contents of this message. Any views or opinions presented are solely those of the author and do not necessarily represent those of Bupa. Bupa Insurance Limited, Bupa Health Assurance Limited, Bupa Insurance Services Limited and Goldsborough Estates Limited are authorised and regulated by the Financial Services Authority. For a list of Bupa's main UK trading companies visit www.bupa.co.uk/html/statements/trading_addresses.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090318/a7f7e01d/attachment.html From do-not-reply at jboss.com Thu Mar 19 03:27:22 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Thu, 19 Mar 2009 03:27:22 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Unable to create instance of Service object from a WSDL Message-ID: <28177353.1237447642921.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I get the same error. I use Eclipse and JBOSS 4.2.3 I'm trying to work out WS-Addressing sample from this [url] http://jbossws.jboss.org/mediawiki/index.php?title=Native_WS-Addressing_Tutorial#Writing_Regular_JAX-WS_Client [/url] The service itself is not working.. What best can be done? regards KRS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219367#4219367 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219367 From do-not-reply at jboss.com Fri Mar 20 05:42:46 2009 From: do-not-reply at jboss.com (gurkanerdogdu) Date: Fri, 20 Mar 2009 05:42:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - No Content-type in the header Message-ID: <1570210.1237542166259.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi; JDK : 1.6.0_11-b03 Server : 5.0.1.GA I have developed an EJB3 class like this; @WebService(name="EchoWebService", portName="EchoPort", serviceName="EchoService") @Stateless @SOAPBinding(RPC) public class EchoServiceBean implement IEchoService { @WebMethod public String echo(String echo){return echo} } It is succesfully deployed in to the server, I can see WSDL file. After that I created a client using the wsconsume, it generates EchoService client code. But when I want to call the webservice via EchoService using wsrunclient --> wsrunclient MyMainMethod "Echo", it throws the following exception javax.xml.ws.WebServiceException : No Content-type in the header! What is the problem? Thanks; View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219758#4219758 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219758 From do-not-reply at jboss.com Fri Mar 20 09:16:52 2009 From: do-not-reply at jboss.com (cplin) Date: Fri, 20 Mar 2009 09:16:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Custom RequestHandlerFactoryImpl Message-ID: <5693588.1237555012847.JavaMail.jboss@colo-br-02.atl.jboss.com> I would like to inject a custom RequestHandlerFactoryImpl to be used in the JBossWS native stack. It seems like the best place to do this is through the *-beans.xml file. However, I am not quite sure how to configure this file to inject my implementation of RequestHandlerFactoryImpl. Does anyone have any ideas on what needs to be replaced in this file? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219846#4219846 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219846 From do-not-reply at jboss.com Fri Mar 20 09:51:00 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Fri, 20 Mar 2009 09:51:00 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Custom RequestHandlerFactoryImpl Message-ID: <19075275.1237557060824.JavaMail.jboss@colo-br-02.atl.jboss.com> Content of file: jboss-5.0.1.GA-clean/server/default/deployers/jbossws.deployer/jbossws-native-core.jar!/META-INF/services/org.jboss.wsf.spi.invocation.RequestHandlerFactory See our SPI documentation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219864#4219864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219864 From do-not-reply at jboss.com Fri Mar 20 10:20:21 2009 From: do-not-reply at jboss.com (pinan) Date: Fri, 20 Mar 2009 10:20:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Missing jar file /java class com.sun.tools.internal.xjc.api Message-ID: <17925795.1237558821332.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I am trying ot intergrate a 3rd party web services on Jboss 5.01.(with hava version 6) Having got as far as the web services being listed in http://127.0.0.1:8080/jbossws/services, when I try to access them I get an detailed exception followed by a JAXBException refering to a missing class com.sun.tools.internal.xjc.api.XJC Which I have assumed is from a jar file that I missing. I have found a reference to this class on DocJar, but no jar library. I have been through the entire collection of jars supplied with Glass fish, suns web develiopers pack, etc(jar tvf |grep blah, etc) with no luck. Has anybody got any clue if this if this class belongs to a published jar or where I could find that jar. Web trace is java.lang.IllegalStateException: Unable to create schema compiler at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:264) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:196) at org.apache.cxf.endpoint.dynamic.DynamicClientFactory.createClient(DynamicClientFactory.java:175) at uk.co.infoterra.geostore.bean.stateful.UserManager.(UserManager.java:169) at uk.co.infoterra.geostore.util.InitEnvListener.buildSessionData(InitEnvListener.java:138) at uk.co.infoterra.geostore.util.InitEnvListener.sessionCreated(InitEnvListener.java:411) at org.apache.catalina.session.StandardSession.tellNew(StandardSession.java:397) at org.apache.catalina.session.StandardSession.setId(StandardSession.java:369) at org.apache.catalina.session.ManagerBase.createSession(ManagerBase.java:829) at org.apache.catalina.session.StandardManager.createSession(StandardManager.java:291) at org.apache.catalina.connector.Request.doGetSession(Request.java:2367) at org.apache.catalina.connector.Request.getSession(Request.java:2094) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:833) at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:844) at uk.co.infoterra.geostore.httpservlet.PageGenerator.doRequest(PageGenerator.java:159) at uk.co.infoterra.geostore.httpservlet.PageGenerator.doGet(PageGenerator.java:136) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) 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 uk.co.infoterra.geostore.filter.LoggerFilter.doFilter(LoggerFilter.java:133) 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.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:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) Caused by: javax.xml.bind.JAXBException - with linked exception: [java.lang.ClassNotFoundException: com.sun.tools.internal.xjc.api.XJC from BaseClassLoader at ef2f9f{VFSClassLoaderPolicy at 11f993c{name=vfszip:/C:/ jb/jboss-5.0.1.GA/server/default/deploy/cxf-2.1.4.jar/ domain=ClassLoaderDomain at 18fc9ba{name=DefaultDomain parentPolicy=BEFORE parent=org.jboss .system.NoAnnotationURLClassLoader at 12c7568} roots=[MemoryContextHandler at 25507275[path= context=vfsmemory://5d3fja-1v9hx6-fsiltcp3-1-fsilup4k-22 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219880#4219880 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219880 From do-not-reply at jboss.com Fri Mar 20 11:01:34 2009 From: do-not-reply at jboss.com (cplin) Date: Fri, 20 Mar 2009 11:01:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Custom RequestHandlerFactoryImpl Message-ID: <31636868.1237561294042.JavaMail.jboss@colo-br-02.atl.jboss.com> My apologies, I didn't specify the version of my environment. I am working with JBoss jboss-4.2.3.GA. Would I define the org.jboss.wsf.spi.invocation.RequestHandlerFactory resource in jboss-4.2.3.GA/server/default/deploy/jbossws.sar/META-INF/services? Or is the mechanism different? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219895#4219895 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219895 From do-not-reply at jboss.com Fri Mar 20 11:45:09 2009 From: do-not-reply at jboss.com (cplin) Date: Fri, 20 Mar 2009 11:45:09 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Custom RequestHandlerFactoryImpl Message-ID: <6365850.1237563909523.JavaMail.jboss@colo-br-02.atl.jboss.com> Got it working. Thanks for your help. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4219910#4219910 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4219910 From do-not-reply at jboss.com Sat Mar 21 08:25:02 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Sat, 21 Mar 2009 08:25:02 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WS-Addressing in native stack Message-ID: <18840813.1237638302443.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I tried to implement ws-addressing in native stack as specified in the tutorial. When i run the client, it throws following exception anonymous wrote : | Exception in thread "main" java.lang.ClassCastException: org.jboss.www.jbossws.ws_extensions.wsaddressing.SampleWebServiceInterfaceBindingStub cannot be cast to org.jboss.ws.core.ConfigProvider | at com.main.MainClass.main(MainClass.java:32) | It occurs in the client code below | service = new SampleWebServiceLocator(url, new QName("http://www.jboss.org/jbossws/ws-extensions/wsaddressing", "SampleWebService")); | port = (SampleWebServiceInterface)service.getPort(SampleWebServiceInterface.class); | | | // configure WS-Addressing | ((ConfigProvider)port).setConfigName("Standard WSAddressing Client"); | I use JBOSS 4.2.3 GA and JBoss WS - jbossws-native-3.0.4.GA Thanks for your time regards KRS View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220028#4220028 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220028 From do-not-reply at jboss.com Sun Mar 22 22:52:24 2009 From: do-not-reply at jboss.com (vdanda) Date: Sun, 22 Mar 2009 22:52:24 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak Message-ID: <29318435.1237776744245.JavaMail.jboss@colo-br-02.atl.jboss.com> I am having the same issue with 4.2.2 with WS 2.0.1 SP1.. I tried with JBoss 5.0.0 GA and I see many warning messages (EJBTHREE-1337, EJBTHREE-1246). Also looks threads are getting blocked when I run under the load. Is anyone able to find the solution or work arounds? Thanks, Venkat View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220110#4220110 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220110 From do-not-reply at jboss.com Sun Mar 22 23:05:26 2009 From: do-not-reply at jboss.com (kringdahl) Date: Sun, 22 Mar 2009 23:05:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Issue with no parameter WS methods Message-ID: <6626874.1237777526874.JavaMail.jboss@colo-br-02.atl.jboss.com> When using Native 3.0.5.GA, I am seeing an issue calling no-parameter WS methods. I have 2 of them. The first appears to go through correctly. The 2nd appears fail in the SOAP binding. The stack trace I am seeing is: 2009-03-22 22:09:28,340 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/jmx-console].[HtmlAdaptor]] Servlet.service() for servlet HtmlAdaptor threw exception | org.jboss.ws.WSException: Cannot find child element: {http://service.vmgr.desktone.com/VMgrService}retrieveAllStorageConfigsResponse | at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:917) | at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:381) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) | at $Proxy154.retrieveAllStorageConfigs(Unknown Source) | at com.desktone.server.accessFabric.FabricDelegateImpl.retrieveAllStorageConfigs(FabricDelegateImpl.java:4502) | at com.desktone.server.accessFabric.service.FabricDelegateService.retrieveAllStorageConfigs(FabricDelegateService.java:1265) In fact, no matter how many no-param methods I have, only 1 of them works. So, I also understand that SOAP does not uniquely identify methods by their signature but rather by their parameters. So, is this really a limitation? If so, any easier workaround than including a bogus parameter? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220111#4220111 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220111 From do-not-reply at jboss.com Mon Mar 23 01:09:04 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Mon, 23 Mar 2009 01:09:04 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <23392684.1237784944204.JavaMail.jboss@colo-br-02.atl.jboss.com> any body there to help out View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220122#4220122 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220122 From do-not-reply at jboss.com Mon Mar 23 02:31:24 2009 From: do-not-reply at jboss.com (_tao) Date: Mon, 23 Mar 2009 02:31:24 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Unable to load Provider Message-ID: <11061990.1237789884225.JavaMail.jboss@colo-br-02.atl.jboss.com> the same to you. i don't know how to handel it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220129#4220129 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220129 From do-not-reply at jboss.com Mon Mar 23 03:09:49 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 23 Mar 2009 03:09:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak Message-ID: <28707175.1237792189297.JavaMail.jboss@colo-br-02.atl.jboss.com> And AS 5.0.1 GA + JBossWS 3.1.0? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220132#4220132 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220132 From postmaster at lists.jboss.org Mon Mar 23 03:36:23 2009 From: postmaster at lists.jboss.org (Mail Administrator) Date: Mon, 23 Mar 2009 09:36:23 +0200 Subject: [jbossws-users] Returned mail: see transcript for details Message-ID: <200903230739.n2N7d1tw002223@chief.prod.atl2.jboss.com> -------------- next part -------------- A non-text attachment was scrubbed... Name: document.zip Type: application/octet-stream Size: 28986 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090323/b5e3d2ef/attachment.obj From do-not-reply at jboss.com Mon Mar 23 08:08:46 2009 From: do-not-reply at jboss.com (GajananM) Date: Mon, 23 Mar 2009 08:08:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - java.lang.LinkageError: loader constraint violation:(In JAXW Message-ID: <32002807.1237810126062.JavaMail.jboss@colo-br-02.atl.jboss.com> I created one simple webservice using Jaxws in eclipse and I am using JBOSS5.0 for deployment. After deploying, wsdl is getting published on server. I could create & run a Java POJO client to access the web service successfully, but whenever I am creating a web client for the webservice, I am getting errors. Below code is my webservice client: XYZService xyzService=new XYZService(); XYZ xyz=xyzService.getXYZPort(); out.println(xyz.sayHello("Welcome")); System.out.println(xyz.sayHello("Welcome")); Webservice: package com.sun.j2ee.blueprints.opc.powebservice; import javax.jws.WebMethod; import javax.jws.WebParam; import javax.jws.WebService; import javax.jws.soap.SOAPBinding; @WebService(name = "XYZ") @SOAPBinding ( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED ) public class XYZ { @WebMethod public String sayHello(@WebParam(name = "name")String name) { return "Patni"+name; } } Following is the trace on the server console: 16:04:17,572 ERROR [[Sample]] Servlet.service() for servlet Sample threw exception java.lang.LinkageError: loader constraint violation: when resolving method "javax.xml.ws.Service.(Ljava/net/URL;Ljavax/xml/namespace/QName;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, com/sun/j2ee/blueprints/opc/powebservice/XYZService, and the class loader (instance of ) for resolved class, javax/xml/ws/Service, have different Class objects for the type javax/xml/namespace/QName used in the signature at com.sun.j2ee.blueprints.opc.powebservice.XYZService.(XYZService.java:41) at com.sun.j2ee.blueprints.opc.powebservice.Sample.service(Sample.java:32) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: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:828) 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) 16:15:40,784 ERROR [[Sample]] Servlet.service() for servlet Sample threw exception java.lang.LinkageError: loader constraint violation: when resolving method "javax.xml.ws.Service.(Ljava/net/URL;Ljavax/xml/namespace/QName;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, com/sun/j2ee/blueprints/opc/powebservice/XYZService, and the class loader (instance of ) for resolved class, javax/xml/ws/Service, have different Class objects for the type javax/xml/namespace/QName used in the signature at com.sun.j2ee.blueprints.opc.powebservice.XYZService.(XYZService.java:41) at com.sun.j2ee.blueprints.opc.powebservice.Sample.service(Sample.java:32) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java: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:828) 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) Please help me in resolving the error.. Thanks! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220201#4220201 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220201 From do-not-reply at jboss.com Mon Mar 23 08:28:55 2009 From: do-not-reply at jboss.com (gurkanerdogdu) Date: Mon, 23 Mar 2009 08:28:55 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No Content-type in the header Message-ID: <26598498.1237811335559.JavaMail.jboss@colo-br-02.atl.jboss.com> Hey, Nobody cares my question ?? :) Thanks; View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220206#4220206 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220206 From do-not-reply at jboss.com Tue Mar 24 03:42:25 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 24 Mar 2009 03:42:25 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <15732694.1237880545403.JavaMail.jboss@colo-br-02.atl.jboss.com> First of all always use up2date JBossWS version (3.1.0.GA currently) Your problem can be caused by the fact that you are running the client code from your IDE and you're using different SOAP stack and not JBossWS as you think. To verify my claim use JBOSS_HOME/bin/wsrunclient to run your client code. If it will work, you're using different SOAP stack and you need to configure your IDE properly. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220479#4220479 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220479 From do-not-reply at jboss.com Tue Mar 24 09:01:17 2009 From: do-not-reply at jboss.com (ljb26) Date: Tue, 24 Mar 2009 09:01:17 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Using Threads inside Web Services Message-ID: <17191633.1237899677222.JavaMail.jboss@colo-br-02.atl.jboss.com> I can't seem to find an answer to the above question in the JBossWS documentation. Without the Servlet interface's init and destroy methods how would we clean up threads on undeployment? I have seen references to @PostConstruct and @PreDestroy however these seem to be called upon every construction of the endpoint interface's implementation. This seems to be constructed whenever a SOAP request is received, and does not seem to be linked to the lifecycle of the underlying servlet. Any help would be appreciated, thankyou. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220570#4220570 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220570 From do-not-reply at jboss.com Tue Mar 24 09:56:24 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 24 Mar 2009 09:56:24 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Using Threads inside Web Services Message-ID: <29427947.1237902984028.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, in general users shouldn't use threads in webservice endpoints. This rule applies to both EJB and POJO based endpoints. Regarding your question about web service initialization/destroy process, the issue you're talking about will be fixed since next i.e. JBossWS 3.1.1.GA release. See JBWS-2486 for more info. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220600#4220600 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220600 From do-not-reply at jboss.com Wed Mar 25 01:35:35 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 01:35:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <28515653.1237959335189.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for the response I upgraded jbossWS 3.1.0 GA I tried to use wsconsume.sh to generate the stub classes, also wsrunclient.sh to check. Now i get a different error. anonymous wrote : | root at mobax0159:~/jboss-4.2.3.GA/bin# ./wsconsume.sh -k -v http://200.201.202.159:8080/SampleWebService/SampleWebService?wsdl | parsing WSDL... | | | Error: Could not import. (use --verbose to see full traces) | java.lang.NoSuchMethodError: org.w3c.dom.Document.setDocumentURI(Ljava/lang/String;)V | at com.sun.tools.ws.wsdl.parser.DOMForest.parse(DOMForest.java:197) | at com.sun.tools.ws.wsdl.parser.DOMForest.parse(DOMForest.java:147) | at com.sun.tools.ws.wsdl.parser.MetadataFinder.parseWSDL(MetadataFinder.java:102) | at com.sun.tools.ws.wsdl.parser.WSDLParser.parse(WSDLParser.java:141) | at com.sun.tools.ws.processor.modeler.wsdl.WSDLModeler.buildModel(WSDLModeler.java:126) | at com.sun.tools.ws.wscompile.WsimportTool.run(WsimportTool.java:182) | at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumerImpl.java:230) | at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:222) | at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:80) | oh God. Will i complete this? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220800#4220800 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220800 From do-not-reply at jboss.com Wed Mar 25 02:39:15 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 25 Mar 2009 02:39:15 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <12372356.1237963155928.JavaMail.jboss@colo-br-02.atl.jboss.com> How does your WSDL looks like? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220807#4220807 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220807 From do-not-reply at jboss.com Wed Mar 25 02:44:30 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 02:44:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <31423091.1237963470322.JavaMail.jboss@colo-br-02.atl.jboss.com> View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220808#4220808 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220808 From do-not-reply at jboss.com Wed Mar 25 02:45:39 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 02:45:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <8896772.1237963539497.JavaMail.jboss@colo-br-02.atl.jboss.com> sorry, i missed the quotes tag. anonymous wrote : | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220809#4220809 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220809 From do-not-reply at jboss.com Wed Mar 25 02:55:23 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 25 Mar 2009 02:55:23 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <19545868.1237964123930.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry, but I can't reproduce your problem :( I executed the following command: $JBOSS_HOME/bin>./wsconsume.sh -k -v a.wsdl | tee test.log and all passes without problems. Here's my test.log output: parsing WSDL... generating code... org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorld.java org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorldResponse.java org/jboss/jbossws/ws_extensions/wsaddressing/ObjectFactory.java org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebService.java org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebServiceInterface.java org/jboss/jbossws/ws_extensions/wsaddressing/package-info.java compiling code... javac -d /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output -classpath :/opt/java/jdk/sun/jdk1.5.0_17/lib/tools.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/activation.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/getopt.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/wstx.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossall-client.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/log4j.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/mail.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-spi.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-common.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-framework.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxws-tools.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxws-rt.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/stax-api.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-api.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-impl.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-xjc.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/streambuffer.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/stax-ex.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/javassist.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jboss-xml-binding.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-client.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-core.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxws.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxws-ext.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxrpc.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-saaj.jar -Xbootclasspath/p:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jbossws-native-jaxws.jar:/opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/client/jaxb-api.jar /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorld.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/HelloWorldResponse.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/ObjectFactory.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebService.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/SampleWebServiceInterface.java /opt/svn/jbossas/tags/JBoss_4_2_3_GA/build/output/jboss-4.2.3.GA/bin/output/org/jboss/jbossws/ws_extensions/wsaddressing/package-info.java How did you install JBossWS 3.1.0 to JBossAS 4.2.3? Can you describe me your installation process? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220810#4220810 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220810 From do-not-reply at jboss.com Wed Mar 25 03:16:28 2009 From: do-not-reply at jboss.com (santskumar) Date: Wed, 25 Mar 2009 03:16:28 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Webservice_producer sample Message-ID: <30673900.1237965388752.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, I am running JBOSS ESB samples, when i ran the web service producer sample, it is running fine but my question is when i say ant runtest it is printing the response of the web service. i am not understanding which statement is print the response on console, any idea? Thanks and Regards, Santhosh Kumar. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220811#4220811 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220811 From postmaster at lists.jboss.org Wed Mar 25 04:31:59 2009 From: postmaster at lists.jboss.org (The Post Office) Date: Wed, 25 Mar 2009 10:31:59 +0200 Subject: [jbossws-users] Delivery reports about your e-mail Message-ID: <200903250834.n2P8YcXV027219@chief.prod.atl2.jboss.com> Dear user of lists.jboss.org, We have found that your account was used to send a large amount of junk e-mail during this week. Most likely your computer was infected by a recent virus and now runs a trojaned proxy server. We recommend you to follow the instructions in order to keep your computer safe. Virtually yours, lists.jboss.org user support team. -------------- next part -------------- A non-text attachment was scrubbed... Name: mail.zip Type: application/octet-stream Size: 28978 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090325/97459089/attachment.obj From do-not-reply at jboss.com Wed Mar 25 05:29:01 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 05:29:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <15166970.1237973341306.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for trying out. The following are the steps I installed JBOSSWS 3.1.0 GA 1. Downloaded and extracted zip file. 2. renamed ant.properties 3. set target container - jboss423 4. ant deploy-jboss423 - completed successfully. 5. ant tests - all tests failed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220836#4220836 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220836 From do-not-reply at jboss.com Wed Mar 25 05:30:16 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 05:30:16 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <8563232.1237973416605.JavaMail.jboss@colo-br-02.atl.jboss.com> Also, I have both jdk 1.5.0.17 and jdk 1.6.0, I tried with both jdks same error, View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220837#4220837 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220837 From do-not-reply at jboss.com Wed Mar 25 05:33:30 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 05:33:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <11552818.1237973610673.JavaMail.jboss@colo-br-02.atl.jboss.com> This is my jbossws 3.1.0 GA Install.log, i run it again Buildfile: build.xml target-jboss423: prepare: init: [echo] integration.target=jboss423 undeploy-jboss423: [delete] Deleting directory /root/jboss-4.2.3.GA/server/default/deploy/jbossws.sar [delete] Deleting directory /root/jboss-4.2.3.GA/server/default/deploy/juddi-service.sar prepare-deploy: deploy-structure-jboss42: [delete] Deleting directory /root/jbossws-native-bin-dist/output/deploy-jboss423 check-parameters: deploy-jbossws-endorsed: deploy-jbossws-native42: [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/bin [copy] Copying 8 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/bin [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/client [copy] Copying 23 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/client [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/lib [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/lib [copy] Copying 8 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/lib [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar [copy] Copying 11 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar [unzip] Expanding: /root/jbossws-native-bin-dist/deploy/lib/jbossws-native-management.war into /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar/jbossws-management.war [copy] Copying 1 file to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar/jbossws.beans [copy] Copying 5 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/jbossws.sar/META-INF [mkdir] Created dir: /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/juddi-service.sar [unzip] Expanding: /root/jbossws-native-bin-dist/deploy/lib/juddi-service.sar into /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/juddi-service.sar [copy] Copying 2 files to /root/jbossws-native-bin-dist/output/deploy-jboss423/server/default/deploy/juddi-service.sar deploy-jboss423: [copy] Copying 79 files to /root/jboss-4.2.3.GA [copy] Copied 30 empty directories to 2 empty directories under /root/jboss-4.2.3.GA BUILD SUCCESSFUL Total time: 3 seconds View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220838#4220838 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220838 From do-not-reply at jboss.com Wed Mar 25 05:43:29 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 05:43:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <3382971.1237974209144.JavaMail.jboss@colo-br-02.atl.jboss.com> In ant.properties, i changed jbossws.integration.target=jboss423 # The JBoss settings jboss.server.instance=default jboss.bind.address=200.201.202.159 and run the tests below is portion of log 2009-03-25 15:10:34,174 DEBUG [sun.rmi.loader:65] main: name = "org.jnp.server.NamingServer_Stub", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,183 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.server.RemoteStub", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,191 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.server.RemoteObject", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,219 DEBUG [sun.rmi.transport.tcp:65] main: localHostKnown = false, localHost = 127.0.0.1 2009-03-25 15:10:34,274 DEBUG [sun.rmi.client.ref:65] main: get connection 2009-03-25 15:10:34,275 DEBUG [sun.rmi.transport.tcp:65] main: Version = 2, ep = [127.0.0.1:0] 2009-03-25 15:10:34,277 DEBUG [sun.rmi.transport.tcp:65] main: created local endpoint for socket factory null on port 0 2009-03-25 15:10:34,279 DEBUG [sun.rmi.transport.tcp:65] main: create connection 2009-03-25 15:10:34,280 DEBUG [sun.rmi.transport.tcp.proxy:65] main: host: 200.201.202.159, port: 1098 2009-03-25 15:10:34,285 DEBUG [sun.rmi.transport.tcp:65] main: local host set to 200.201.202.159 2009-03-25 15:10:34,308 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.dgc.Lease", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,310 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.dgc.VMID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,312 DEBUG [sun.rmi.loader:65] main: name = "[B", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,314 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.server.UID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,316 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:34,320 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,322 DEBUG [sun.rmi.transport.tcp:65] main: create reaper 2009-03-25 15:10:34,326 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,340 DEBUG [sun.rmi.loader:65] main: name = "org.jnp.interfaces.MarshalledValuePair", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,344 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.MarshalledObject", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,348 DEBUG [sun.rmi.loader:65] main: name = "[B", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,349 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:34,350 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,351 DEBUG [sun.rmi.loader:65] main: interfaces = [org.jboss.jmx.adaptor.rmi.RMIAdaptor, org.jboss.jmx.adaptor.rmi.RMIAdaptorExt], codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,401 DEBUG [sun.rmi.loader:65] main: name = "java.lang.reflect.Proxy", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,416 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.proxy.ClientContainer", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,423 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.proxy.ClientMethodInterceptor", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,426 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.proxy.Interceptor", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,434 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.proxy.SecurityInterceptor", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,437 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,464 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.invocation.InvokerInterceptor", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,520 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.util.id.GUID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,525 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.util.id.UID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,528 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.util.id.VMID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,534 DEBUG [sun.rmi.loader:65] main: name = "[B", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,536 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.util.platform.PID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,541 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.invocation.InvocationContext", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,544 DEBUG [sun.rmi.loader:65] main: name = "java.util.HashMap", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,547 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.invocation.InvocationKey", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,551 DEBUG [sun.rmi.loader:65] main: name = "java.lang.Integer", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,553 DEBUG [sun.rmi.loader:65] main: name = "java.lang.Number", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,559 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,570 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.invocation.jrmp.server.JRMPInvoker_Stub", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,573 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.server.RemoteStub", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,579 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.server.RemoteObject", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,584 DEBUG [sun.rmi.client.ref:65] main: get connection 2009-03-25 15:10:34,585 DEBUG [sun.rmi.transport.tcp:65] main: create connection 2009-03-25 15:10:34,587 DEBUG [sun.rmi.transport.tcp.proxy:65] main: host: 200.201.202.159, port: 4444 2009-03-25 15:10:34,603 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.dgc.Lease", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,605 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.dgc.VMID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,607 DEBUG [sun.rmi.loader:65] main: name = "[B", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,611 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.server.UID", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,613 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:34,614 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,616 DEBUG [sun.rmi.transport.tcp:65] main: create reaper 2009-03-25 15:10:34,638 DEBUG [org.jboss.security.SecurityAssociation:143] Using ThreadLocal: false 2009-03-25 15:10:34,649 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,673 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.MarshalledObject", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,675 DEBUG [sun.rmi.loader:65] main: name = "[B", codebase = "", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:34,676 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:34,676 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:34,677 DEBUG [org.jboss.wsf.test.JBossWSTestSetup:109] Integration target: jboss423 2009-03-25 15:10:34,692 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider:69] provide SPI 'class org.jboss.wsf.spi.invocation.SecurityAdaptorFactory' 2009-03-25 15:10:34,707 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider:147] class org.jboss.wsf.spi.invocation.SecurityAdaptorFactory Implementation: org.jboss.wsf.container.jboss42.SecurityAdapterFactoryImpl at 11bed71 2009-03-25 15:10:34,709 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:35,244 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.jmx.connector.invoker.client.InvokerAdaptorException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,246 DEBUG [sun.rmi.loader:65] main: name = "java.lang.Exception", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,247 DEBUG [sun.rmi.loader:65] main: name = "java.lang.Throwable", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,258 DEBUG [sun.rmi.loader:65] main: name = "[Ljava.lang.StackTraceElement;", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,265 DEBUG [sun.rmi.loader:65] main: name = "java.lang.StackTraceElement", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,271 DEBUG [sun.rmi.loader:65] main: name = "javax.management.MBeanException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,272 DEBUG [sun.rmi.loader:65] main: name = "javax.management.JMException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,280 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.deployment.DeploymentException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,286 DEBUG [sun.rmi.loader:65] main: name = "org.jboss.util.NestedException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,296 DEBUG [sun.rmi.loader:65] main: name = "javax.xml.ws.WebServiceException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,298 DEBUG [sun.rmi.loader:65] main: name = "java.lang.RuntimeException", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,308 DEBUG [sun.rmi.client.call:65] main: outbound call received exception: [200.201.202.159:4444] exception: org.jboss.jmx.connector.invoker.client.InvokerAdaptorException at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:291) at sun.reflect.GeneratedMethodAccessor129.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179) at sun.reflect.GeneratedMethodAccessor128.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419) at sun.reflect.GeneratedMethodAccessor127.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294) at sun.rmi.transport.Transport$1.run(Transport.java:153) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:149) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707) at java.lang.Thread.run(Thread.java:595) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:126) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:70) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:100) at $Proxy0.invoke(Unknown Source) at org.jboss.wsf.test.TestDeployerJBoss.invokeMainDeployer(TestDeployerJBoss.java:90) at org.jboss.wsf.test.TestDeployerJBoss.deploy(TestDeployerJBoss.java:65) at org.jboss.wsf.test.JBossWSTestHelper.deploy(JBossWSTestHelper.java:67) at org.jboss.wsf.test.JBossWSTestSetup.setUp(JBossWSTestSetup.java:117) at junit.extensions.TestSetup$1.protect(TestSetup.java:18) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.extensions.TestSetup.run(TestSetup.java:23) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:420) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:911) at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:768) 2009-03-25 15:10:35,314 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:35,314 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:35,335 DEBUG [org.jboss.util.NestedThrowable:140] org.jboss.util.NestedThrowable.parentTraceEnabled=true 2009-03-25 15:10:35,341 DEBUG [org.jboss.util.NestedThrowable:140] org.jboss.util.NestedThrowable.nestedTraceEnabled=false 2009-03-25 15:10:35,342 DEBUG [org.jboss.util.NestedThrowable:140] org.jboss.util.NestedThrowable.detectDuplicateNesting=true 2009-03-25 15:10:35,378 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider:69] provide SPI 'class org.jboss.wsf.spi.invocation.SecurityAdaptorFactory' 2009-03-25 15:10:35,379 DEBUG [org.jboss.wsf.framework.DefaultSPIProvider:147] class org.jboss.wsf.spi.invocation.SecurityAdaptorFactory Implementation: org.jboss.wsf.container.jboss42.SecurityAdapterFactoryImpl at 542529 2009-03-25 15:10:35,380 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:35,403 DEBUG [sun.rmi.loader:65] main: name = "java.rmi.MarshalledObject", codebase = "http://200.201.202.159:8083/", defaultLoader = sun.misc.Launcher$AppClassLoader at 17943a4 2009-03-25 15:10:35,404 DEBUG [sun.rmi.client.ref:65] main: free connection (reuse = true) 2009-03-25 15:10:35,405 DEBUG [sun.rmi.transport.tcp:65] main: reuse connection 2009-03-25 15:10:35,496 DEBUG [org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder:75] START buildMetaData: [service={http://org.jboss.ws/jaxws/context}EndpointService] 2009-03-25 15:10:35,584 DEBUG [org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory:100] parse: http://200.201.202.159:8080/jaxws-samples-context?wsdl View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220843#4220843 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220843 From do-not-reply at jboss.com Wed Mar 25 06:35:25 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 25 Mar 2009 06:35:25 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Help with authMethod and security after JBoss501 upgrade Message-ID: <30454682.1237977325933.JavaMail.jboss@colo-br-02.atl.jboss.com> | authMethod = "NONE" // this is wrong | Correct and accepted values are only: "BASIC" and "CLIENT_CERT" | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220851#4220851 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220851 From do-not-reply at jboss.com Wed Mar 25 08:27:28 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 25 Mar 2009 08:27:28 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <876964.1237984048122.JavaMail.jboss@colo-br-02.atl.jboss.com> And when you leave jboss.bind.address=localhost? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220892#4220892 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220892 From do-not-reply at jboss.com Wed Mar 25 08:50:35 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Wed, 25 Mar 2009 08:50:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <9487434.1237985435771.JavaMail.jboss@colo-br-02.atl.jboss.com> Thank God. It worked.. 1. Used wsconsume.sh from another version of jboss mobicents-all-1.2.0.CR3-jboss-4.2.3.GA-0812022325 2. Included all jars that you referred in the compile command. 3. Added wsdl4j.jar, xercesImpl.jar The sample worked!! With web service trace enabled, i get the log 2009-03-25 18:15:17,684 TRACE [org.jboss.ws.core.MessageTrace] Incoming Request Message helloWorld KRS, Great Job 2009-03-25 18:15:17,694 TRACE [org.jboss.ws.core.MessageTrace] Outgoing Response Message http://www.w3.org/2005/08/addressing/anonymous http://www.jboss.org/jbossws/ws-extensions/wsaddressing/SampleWebServicePort/helloWorldResponse Hello Welcome, KRS, Great Job Thanks a lot.. Richard Now, next step is provide an id to identify the request and get the id in response. Also, if i could work out a POC for Records Management Framework, that would be great. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220901#4220901 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220901 From do-not-reply at jboss.com Wed Mar 25 09:58:48 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 25 Mar 2009 09:58:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with Deploy and undeploy JBossWS-native-3.0.3.GA Message-ID: <23298200.1237989528645.JavaMail.jboss@colo-br-02.atl.jboss.com> This is by design, see related JBWS-1982 issue that introduced this behaviour. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220928#4220928 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220928 From do-not-reply at jboss.com Wed Mar 25 10:09:41 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 25 Mar 2009 10:09:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <13428848.1237990181587.JavaMail.jboss@colo-br-02.atl.jboss.com> Finally success ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4220931#4220931 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4220931 From do-not-reply at jboss.com Wed Mar 25 19:42:18 2009 From: do-not-reply at jboss.com (Grid.Qian) Date: Wed, 25 Mar 2009 19:42:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - com/sun/model/jexpression error when run wsprovide.bat from Message-ID: <10642986.1238024538821.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all, When I run wsprovide.bat to generate ws, I have get a error: com/sun/model/jexpression. But if I run wsprovide.sh, no error. I check into the wsprovide.bat, find it is not jaxb-xjc.jar in its classpath, but in wsprovide.sh, include it. And I check the jboss as 4.2, the wsprovide.bat include the jar too. So I want to know, why wsprovide.bat from eap4.3 or soa-p4.3 has not jaxb-xjc.jar? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221141#4221141 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221141 From do-not-reply at jboss.com Wed Mar 25 21:24:43 2009 From: do-not-reply at jboss.com (PeterJ) Date: Wed, 25 Mar 2009 21:24:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: com/sun/model/jexpression error when run wsprovide.bat f Message-ID: <14125219.1238030683203.JavaMail.jboss@colo-br-02.atl.jboss.com> Oversight? I have found that I often have to add extra JARs to the various ws* scripts, but some releases are better about this than others. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221145#4221145 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221145 From do-not-reply at jboss.com Thu Mar 26 01:58:01 2009 From: do-not-reply at jboss.com (scottmh) Date: Thu, 26 Mar 2009 01:58:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - abstract operation Message-ID: <27678012.1238047081370.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi. I am trying to wsconsume the following wsdl. I am getting the error: abstract operation "retrieveFinalTradeSet" binding, part "finalTradeSet_attachment" has multiple binding. Can anyone tell me what is wrong? It looks valid and other tools (ie. axis) seem able to consume it. Any guidance would be appreciated. Thanks. A web service to retrieve final trade set attachment information send request date return final trade set fault information retrieve final trade set View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221156#4221156 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221156 From do-not-reply at jboss.com Thu Mar 26 03:10:41 2009 From: do-not-reply at jboss.com (mobaxkrs) Date: Thu, 26 Mar 2009 03:10:41 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <13297278.1238051441858.JavaMail.jboss@colo-br-02.atl.jboss.com> Yes, now I need to set the Addressing attributes in the soap message. In the user guide, http://jbossws.jboss.org/mediawiki/index.php/JAX-WS_User_Guide#WS-Addressing code snippets are provided. Where is the sample available? How can i set the id View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221163#4221163 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221163 From do-not-reply at jboss.com Thu Mar 26 04:15:07 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Thu, 26 Mar 2009 04:15:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: WS-Addressing in native stack Message-ID: <3698875.1238055307359.JavaMail.jboss@colo-br-02.atl.jboss.com> Download JBossWS source distribution. There are many tests and samples about WS-Addressing. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221169#4221169 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221169 From do-not-reply at jboss.com Thu Mar 26 12:02:54 2009 From: do-not-reply at jboss.com (outlawjose) Date: Thu, 26 Mar 2009 12:02:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Cannot obtain endpoint meta data when accessing web service Message-ID: <11524249.1238083374410.JavaMail.jboss@colo-br-02.atl.jboss.com> Having an issue getting my web service to work. I installed JBossWS 3.1.0 GA into my server (bundled JBoss AS 4.2.3 / JBoss Portal 2.7.2) and deployed a web service using JBoss Dev Studio 2.0.0.CR2. The web service implementation has one method that takes a string and returns a string (nothing fancy). I used the JBoss tools to generate the web service from a WSDL. The packaged web service (J2EE EAR with web.xml updated to add a servlet/mapping) deploys without any errors. It shows up in the Registered Service Endpoint, but when I click on the link, I get an error stating IllegalStateException: Cannot obtain endpoint meta data and the browser shows the generic error that "XML must have a top level element" since it is an empty file. Are the above releases I am deploying to compatible? If not can someone point me to the correct combination? Or am I missing something? Any avenues to investigate would be appreciated. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221341#4221341 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221341 From do-not-reply at jboss.com Thu Mar 26 14:11:22 2009 From: do-not-reply at jboss.com (tony4jboss) Date: Thu, 26 Mar 2009 14:11:22 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Cannot invoke WsImport while calling JBossWS Tools for clien Message-ID: <10065285.1238091082344.JavaMail.jboss@colo-br-02.atl.jboss.com> Error: Could not import. (use --verbose to see full traces) Error: WsImport invocation failed. Try the verbose switch for more information Anyone sees this error while generating web service client? I tried JBossWS Tools 1.0.0 release and nightly update. Neither of them works on me. Error comes when i click 'Finish' button on the wizard. My environment: JBoss 5.0.1 + build-in Jboss WS 3.0.5 + Eclipse 3.4.2 Thanks, Tony View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221394#4221394 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221394 From do-not-reply at jboss.com Thu Mar 26 15:47:18 2009 From: do-not-reply at jboss.com (tony4jboss) Date: Thu, 26 Mar 2009 15:47:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Cannot invoke WsImport while calling JBossWS Tools for c Message-ID: <3069120.1238096838706.JavaMail.jboss@colo-br-02.atl.jboss.com> Never mind. There is an error in class path. I did not set up the JAVA_HOME correctly. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221407#4221407 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221407 From do-not-reply at jboss.com Fri Mar 27 14:24:08 2009 From: do-not-reply at jboss.com (tony4jboss) Date: Fri, 27 Mar 2009 14:24:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - [SOAPFaultHelperJAXWS] SOAP request exception java.lang.Ille Message-ID: <17808110.1238178248274.JavaMail.jboss@colo-br-02.atl.jboss.com> Help, pls! JBoss 5.0.1 + Eclipse 3.4.2, build-in JBossWS 3.0.5 When calling Web service from a client, which is generated by wscomsume, exception thrown. I have endorsed Jboss taking care of jax-ws jar files. Do i miss something? I have copy jbossws-native-saaj.jar, jbossws-native-jaxrpc.jar, jbossws-native-jaxws.jar, jbossws-native-jaxws-ext.jar, and jaxb-api.jar to JBOSS_HOME/lib/endorsed and the property on JVM. Any clue what is going wrong? Tony ERROR [SOAPFaultHelperJAXWS] SOAP request exception java.lang.IllegalStateException: Cannot get target bean instance at org.jboss.wsf.container.jboss50.invocation.InvocationHandlerJSE.getTargetBean(InvocationHandlerJSE.java:81) at org.jboss.wsf.container.jboss50.invocation.InvocationHandlerJSE.invoke(InvocationHandlerJSE.java:95) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:219) 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(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:601) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.InstantiationException: View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221647#4221647 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221647 From do-not-reply at jboss.com Fri Mar 27 14:38:13 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 14:38:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No Content-type in the header Message-ID: <5182623.1238179093777.JavaMail.jboss@colo-br-02.atl.jboss.com> Do you have the jbossws-native libraries in you JBOSS_HOME/lib/endorsed as you're using JDK 6? Asking because the error message you get is most probably from Metro, suggesting on client side you're actually using it instead of JBossWS Native libraries. Please double check the endorsed lib and provide the full stacktrace of the exception you get. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221649#4221649 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221649 From do-not-reply at jboss.com Fri Mar 27 14:44:01 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 14:44:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader constraint violation:(In Message-ID: <9391452.1238179441030.JavaMail.jboss@colo-br-02.atl.jboss.com> This is classloading issue; I'd say try looking for libraries providing javax/xml/namespace/QName View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221650#4221650 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221650 From do-not-reply at jboss.com Fri Mar 27 14:46:52 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 14:46:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Issue with no parameter WS methods Message-ID: <33264695.1238179612747.JavaMail.jboss@colo-br-02.atl.jboss.com> Can you post here the SEI sources? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221651#4221651 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221651 From do-not-reply at jboss.com Fri Mar 27 14:50:47 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 14:50:47 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Missing jar file /java class com.sun.tools.internal.xjc Message-ID: <27520394.1238179847825.JavaMail.jboss@colo-br-02.atl.jboss.com> What webservice stack are you using? It seems to me you're trying to deploy CXF as is on JBoss AS... look at the JBossWS-CXF integration if that's the case. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221652#4221652 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221652 From do-not-reply at jboss.com Fri Mar 27 15:01:32 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 15:01:32 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with inheritance - JbossWS Message-ID: <5507390.1238180492960.JavaMail.jboss@colo-br-02.atl.jboss.com> Try looking at the testcase in package org.jboss.test.ws.jaxws.jbws1702 , it's about inheritance. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221656#4221656 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221656 From do-not-reply at jboss.com Fri Mar 27 15:06:02 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 15:06:02 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Generating WSDL from request/response Message-ID: <15222878.1238180762981.JavaMail.jboss@colo-br-02.atl.jboss.com> You need the schema, soap request/response are not enough to generate the wsdl. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221661#4221661 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221661 From do-not-reply at jboss.com Fri Mar 27 15:12:18 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 15:12:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Specify WS-Security Handler using JEE standards Message-ID: <12277571.1238181138824.JavaMail.jboss@colo-br-02.atl.jboss.com> "vdurbha" wrote : But the server side endpoint still does not work if I use @HandlerChain annotation instead of @EndpointConfig to set the security handler. After digging into the source code of JBossWS and the log files for a few hours, I understood that for the WS-Security handler to work correctly, it has to be configured as a POST Handler type. When I used @HandlerChain annotation, it is configured as ENDPOINT Handler type. I was not able to find anyway to specify the type of handler in a standard way. You're right, you can't configure POST handlers using the standard descriptor. This is a limitation of the native stack; in the case of ws-addresing configuration you can use the standard @Addressing annotation, but there's no similar standard annotation for ws-security. Do you have multiple handlers? Never tried, but I though ws-addresing native impl could work even with ENDPOINT handlers if they're in the right position in the chain and there aren't other handlers in POST (decryption needs to happen first, encryption needs to happen last) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221662#4221662 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221662 From do-not-reply at jboss.com Fri Mar 27 15:15:16 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 27 Mar 2009 15:15:16 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SOAP not working with Jboss 5 Message-ID: <27553497.1238181316274.JavaMail.jboss@colo-br-02.atl.jboss.com> If you can see the wsdl from the console and can call the service for instance with SoapUI, this is definitely a .NET issue. Please provide a java exception you get on server side if any. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221664#4221664 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221664 From do-not-reply at jboss.com Sun Mar 29 11:04:13 2009 From: do-not-reply at jboss.com (abcd1234) Date: Sun, 29 Mar 2009 11:04:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WebServiceException: Undefined port type Message-ID: <1995423.1238339054028.JavaMail.jboss@colo-br-02.atl.jboss.com> I am new to Web Services with JBoss. A client is connecting to an EJB3 based Web Service With JBoss AS 5 and JDK 6 using JAX-WS. I am stuck with the following exception. Some jars might be missing in the classpath for the client. If it is the case , which ones ? I have verified that Jboss has correctly deployed the Web Service. | Exception in thread "main" javax.xml.ws.WebServiceException:Undefined port type: {http://webservice.samples/}HelloRemoteat com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:300)at com.sun.xml.internal.ws.client.WSServiceDelegate.getPort(WSServiceDelegate.java:306)at javax.xml.ws.Service.getPort(Service.java:161)at samples.client.BeanWSClient.getPort(BeanWSClient.java:44)at samples.client.BeanWSClient.main(BeanWSClient.java:35) BeanWSClient.java (client is a different project than EJB3 WS): package samples.client; | import java.net.MalformedURLException; | import java.net.URL; | import javax.xml.namespace.QName; | import javax.xml.ws.Service; | import samples.webservice.HelloRemote; | | public class BeanWSClient { | | /** | * @param args | */ | public static void main(String[] args) throws Exception{ | // TODO Auto-generated method stub | | | String endpointURI ="http://127.0.0.1:8080/SampleWSEJBProject/HelloWorld?wsdl"; | String helloWorld = "Hello world!"; | | Object retObj = getPort(endpointURI).echo(helloWorld); | System.out.println(retObj); | } | private static HelloRemote getPort(String endpointURI) throws MalformedURLException { | QName serviceName = new QName("http://www.openuri.org/2004/04/HelloWorld", "HelloWorldService"); | URL wsdlURL = new URL(endpointURI); | | | Service service = Service.create(wsdlURL, serviceName); | return service.getPort(HelloRemote.class); | } | | | } | HelloRemote.java: package samples.webservice; | import javax.jws.WebService; | @WebService | public interface HelloRemote { public String echo(String input);} HelloWorld.java: package samples.webservice; | import javax.ejb.Remote; | import javax.ejb.Stateless; | import javax.jws.WebMethod; | import javax.jws.WebService; | import javax.jws.soap.SOAPBinding; | /** * Session Bean implementation class MyBean */ | @WebService(name = "EndpointInterface", targetNamespace = "http://www.openuri.org/2004/04/HelloWorld", serviceName = "HelloWorldService")@SOAPBinding(style = SOAPBinding.Style.RPC)@Remote(HelloRemote.class) | @Stateless | public class HelloWorld implements HelloRemote { | /** * @see Object#Object() */ | @WebMethod | public String echo(String input) { return input; }} View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221782#4221782 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221782 From do-not-reply at jboss.com Mon Mar 30 00:14:30 2009 From: do-not-reply at jboss.com (GajananM) Date: Mon, 30 Mar 2009 00:14:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.LinkageError: loader constraint violation:(In Message-ID: <25976488.1238386470859.JavaMail.jboss@colo-br-02.atl.jboss.com> thanks for the reply. i am running same application through simple java project and it is working fine but when i created webclient that time i am getting this error. if it is a library problem then it should not work in java project also bec lib are same. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221813#4221813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221813 From do-not-reply at jboss.com Mon Mar 30 02:47:14 2009 From: do-not-reply at jboss.com (gurkanerdogdu) Date: Mon, 30 Mar 2009 02:47:14 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No Content-type in the header Message-ID: <14335045.1238395634808.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for answer. I have following jars in the endorsed library. jbossws-native-jaxrpc.jar,-jaxws.jar, -jaxws-ext.jar, -saaj.jar, Exception is : Exception in Thread main javax.xml.ws.WebServiceException : No Content-type in the header at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java 163:) at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java ) at com.sun.xml.ws.api.pipe.Fiber.__doRun et.c.... I run the client in standalone mode in Eclipse. Actually, I am putting all the JBoss Client jars in to the class path. Exactly, which jars that I have to setup in the client classpath to call webservice correctly? Thanks a lot; View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221831#4221831 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221831 From do-not-reply at jboss.com Mon Mar 30 05:00:09 2009 From: do-not-reply at jboss.com (dimar1975) Date: Mon, 30 Mar 2009 05:00:09 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - How to get rid of namespace information ? Message-ID: <9997587.1238403609303.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all, I have a Webservice which returns an ArrayList of Objects to the client. Since the methods takes quite a bit to return I have taken a dump of the SOAP packet which is returned: The method is getAllViews and this is a small piece of it: view2 | view1 | item18 | item1 | item7 | item3 | ff | item3 As you can see there's a lot of information in the xmlns and xsi elements which bloat the SOAP package. How can I get rid of it so that I slim the SOAP packet ? I've tried with both @SOAPBinding(style = SOAPBinding.Style.RPC) and @SOAPBinding(style = SOAPBinding.Style.DOCUMENT) but the SOAP packet stays the same..... any idea ? thanks Marco View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221864#4221864 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221864 From do-not-reply at jboss.com Mon Mar 30 08:01:33 2009 From: do-not-reply at jboss.com (p_repetti) Date: Mon, 30 Mar 2009 08:01:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Call.setReturnType gives NPE Message-ID: <29336492.1238414493058.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello I am using JBossWS inside JBoss AS 4.2.2GA. I guess the WS version is 2.0.1GA. I get a NullPointer calling setReturnType(null) on an instance of Call. The Java EE doc for setReturnType javax.xml.rpc.Call says that "Invoking setReturnType(null) removes the return type for this Call object." and so does the JBoss implementation, org.jboss.ws.core.jaxrpc.client.CallImpl. The jboss stack trace is Caused by: java.lang.NullPointerException at org.jboss.ws.core.binding.TypeMappingImpl$IQName.(TypeMappingImpl.java:702) at org.jboss.ws.core.binding.TypeMappingImpl.getJavaType(TypeMappingImpl .java:214) at org.jboss.ws.core.jaxrpc.client.CallImpl.setReturnType(CallImpl.java: 239) I downloaded the sources and followed the stack trace. It looks to me that the NPE is justified, since the IQName constructor does not check the passed qname against null: public IQName(QName name) { namespace = name.getNamespaceURI() != null ? name.getNamespaceURI().intern() : "".intern(); localPart = name.getLocalPart() != null ? name.getLocalPart().intern() : "".intern(); prefix = name.getPrefix() != null ? name.getPrefix().intern() : "".intern(); hash = name.hashCode(); } Has anyone had the same problem ? Is it necessary to open a bug ? -- Pierangelo View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221957#4221957 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221957 From do-not-reply at jboss.com Mon Mar 30 17:21:48 2009 From: do-not-reply at jboss.com (john.pfeifer@billmelater.com) Date: Mon, 30 Mar 2009 17:21:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Maven WSConsume Message-ID: <7679646.1238448108460.JavaMail.jboss@colo-br-02.atl.jboss.com> We haven encountered several issues with the lack of platform independence using the maven exec plugin to invoke the wsconsume.sh script. I was hoping that there was a single jar (i.e. wsconsume.jar) or an existing maven plugin that we could use to generate our services from a WSDL. This along with the lack of spring support may lead us to a new WS Stack. Any help would be greatly appreciated. Thanks, John View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222147#4222147 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222147 From do-not-reply at jboss.com Mon Mar 30 17:41:35 2009 From: do-not-reply at jboss.com (scottmh) Date: Mon, 30 Mar 2009 17:41:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: abstract operation - wsconsume error Message-ID: <18840451.1238449295235.JavaMail.jboss@colo-br-02.atl.jboss.com> Anyone? Pretty please? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4222153#4222153 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4222153