From do-not-reply at jboss.com Sun Jan 4 07:02:17 2009 From: do-not-reply at jboss.com (rodosa) Date: Sun, 4 Jan 2009 07:02:17 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problem calling a ws in a servlet Message-ID: <24256454.1231070537300.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello!! Had you found the solution or the reason of this problem??? Thanks, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199396#4199396 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199396 From do-not-reply at jboss.com Sun Jan 4 19:16:39 2009 From: do-not-reply at jboss.com (rodosa) Date: Sun, 4 Jan 2009 19:16:39 -0500 (EST) Subject: [jbossws-users] [JBossWS] - java.lang.ClassCastException: org.jboss.ws.core.jaxws.spi.Se Message-ID: <27710960.1231114599408.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello! I've a problem. I've two jboss. Jboss 4.0.5 and Jboss jBPM 3.2.3. The Jboss 4.0.5 access to jBPM web services but .... when the session beans of jBPM try to access to WS of JBoss 4.0.4, the following exception it's thown: | 01:11:30,437 ERROR [STDERR] java.lang.ClassCastException: org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl cannot be cast to javax.xml.ws.spi.ServiceDelegate21 | 01:11:30,437 ERROR [STDERR] at javax.xml.ws.Service.(Service.java:82) | 01:11:30,437 ERROR [STDERR] at com.ideit.modules.cmmi.requirements.session.ProductWS_Service.(ProductWS_Service.java:40) | 01:11:30,437 ERROR [STDERR] at com.ideit.modules.cmmi.jbpm.requirements.session.JbpmSessionBean.createInstance(JbpmSessionBean.java:140) | 01:11:30,437 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 01:11:30,453 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) | 01:11:30,453 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) | 01:11:30,453 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) | 01:11:30,453 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) | 01:11:30,453 ERROR [STDERR] at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) | 01:11:30,468 ERROR [STDERR] at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) | 01:11:30,468 ERROR [STDERR] at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | 01:11:30,468 ERROR [STDERR] at org.jboss.wsf.container.jboss42.InvocationHandlerEJB3.invoke(InvocationHandlerEJB3.java:103) | 01:11:30,468 ERROR [STDERR] at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220) | 01:11:30,468 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:408) | 01:11:30,468 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:272) | 01:11:30,468 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:189) | 01:11:30,468 ERROR [STDERR] at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:122) | 01:11:30,468 ERROR [STDERR] at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) | 01:11:30,468 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | 01:11:30,468 ERROR [STDERR] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) | 01:11:30,468 ERROR [STDERR] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) | 01:11:30,468 ERROR [STDERR] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) | 01:11:30,468 ERROR [STDERR] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) | 01:11:30,468 ERROR [STDERR] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) | 01:11:30,468 ERROR [STDERR] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) | 01:11:30,468 ERROR [STDERR] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) | 01:11:30,468 ERROR [STDERR] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) | 01:11:30,468 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) | I build a junit class that acces to the WS deployed in jboss 4.0.5, and this work. I suposse that it could be a problem of libraries but I don't know how to fix it. Could someone help me?? Thank you very much View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199436#4199436 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199436 From do-not-reply at jboss.com Mon Jan 5 05:49:51 2009 From: do-not-reply at jboss.com (dbauched) Date: Mon, 5 Jan 2009 05:49:51 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Invoking Web service from in a JSP. Message-ID: <32169217.1231152591309.JavaMail.jboss@colo-br-02.atl.jboss.com> dd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199490#4199490 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199490 From do-not-reply at jboss.com Mon Jan 5 07:03:36 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 5 Jan 2009 07:03:36 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS 3.0.5 SFSB as a web service Message-ID: <4282139.1231157016775.JavaMail.jboss@colo-br-02.atl.jboss.com> No, you don't need to install Metro. Stateful EJBs won't work there too. Just FYI here's the stack compatibility matrix: http://jbossws.jboss.org/mediawiki/index.php?title=Supported_Target_Containers You need to play with WS-Addressing using any SOAP stack. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199521#4199521 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199521 From do-not-reply at jboss.com Mon Jan 5 08:31:15 2009 From: do-not-reply at jboss.com (RajaRamana) Date: Mon, 5 Jan 2009 08:31:15 -0500 (EST) Subject: [jbossws-users] [JBossWS] - J2EE Webservice and C lang - Message-ID: <33342161.1231162275044.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am looking for help to provide a service between J2EE and C lang. 1. I have created the following Web Service in J2EE /* * @WebService indicates that this is webservice interface and the name * indicates the webservice name. */ @WebService(name = "Hello") /* * @SOAPBinding indicates binding information of soap messages. Here we have * document-literal style of webservice and the parameter style is wrapped. */ @SOAPBinding ( style = SOAPBinding.Style.DOCUMENT, use = SOAPBinding.Use.LITERAL, parameterStyle = SOAPBinding.ParameterStyle.WRAPPED ) public class Hello { /** * This method takes a input parameter and appends "Hello" to it and * returns the same. * * @param name * @return */ @WebMethod public String greet( @WebParam(name = "name") String name ) { return "Hello " + name; } } 2. Configured in web.xml Hello com.carrefour.cmt.central.webservice.Hello 1 Hello /Hello 3. Started Jboss421. After that it created a wsdl file in DATA folder. 4 Now i want to write a Client to consume the service in 'C' LANG . Please Assist me. Thanks and Reg, Raja View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199536#4199536 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199536 From do-not-reply at jboss.com Mon Jan 5 12:27:28 2009 From: do-not-reply at jboss.com (skajotde) Date: Mon, 5 Jan 2009 12:27:28 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: NullPointerException with jbossws 2.0.1 Message-ID: <25178064.1231176448506.JavaMail.jboss@colo-br-02.atl.jboss.com> thanks guys for pointing solution. Exception is horrible unclear . Before Christmas vacation i had added jmx parameter to run.conf to monitor jboss. After vacation I did svn update and JBoss doesn't start. I forget about this parameter added 2 weeks ago. I thought it is from updating svn repo but it was my mistake. Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199595#4199595 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199595 From do-not-reply at jboss.com Tue Jan 6 05:52:06 2009 From: do-not-reply at jboss.com (sverker) Date: Tue, 6 Jan 2009 05:52:06 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Recomended way to build server and client with maven? Message-ID: <2577362.1231239126449.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I think this should be a FAQ as it's asked many times in the forum but I can't find any answers. What is the recommended way to build server and client side of a webservice for jbossws with maven2? To partly answer my own question, on the where I build my webservice with annotated classes, I added the following dependency to get it to work: | | org.jboss.ws | jbossws-framework | 3.0.4.GA | provided | | However, I have not found a clear answer on how to generate the client side stub. I found two possible solutions: * Use the jaxws:wsimport maven goal. This use the wsimport tool from Sun RI. Is this method fully functional with JbossWS? * Use the wsconsume ant task with maven-antrun-plugin. Should work fine but is not a very "elegant" solution. Which is the best way, or is there another recommended way? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199718#4199718 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199718 From do-not-reply at jboss.com Tue Jan 6 11:01:25 2009 From: do-not-reply at jboss.com (okiSM) Date: Tue, 6 Jan 2009 11:01:25 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Proper configuration of CXF web service Message-ID: <27079892.1231257685991.JavaMail.jboss@colo-br-02.atl.jboss.com> Anyone? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199830#4199830 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199830 From do-not-reply at jboss.com Tue Jan 6 14:46:56 2009 From: do-not-reply at jboss.com (rodosa) Date: Tue, 6 Jan 2009 14:46:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problem calling a ws in a servlet Message-ID: <18451060.1231271216348.JavaMail.jboss@colo-br-02.atl.jboss.com> After a bit of time I resolved my problem deleting all jboss-jaxws.jar of my JBoss Regards View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199889#4199889 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199889 From do-not-reply at jboss.com Tue Jan 6 21:51:13 2009 From: do-not-reply at jboss.com (taral) Date: Tue, 6 Jan 2009 21:51:13 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS 3.0.5 SFSB as a web service Message-ID: <15494959.1231296673963.JavaMail.jboss@colo-br-02.atl.jboss.com> thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199956#4199956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199956 From do-not-reply at jboss.com Wed Jan 7 03:04:19 2009 From: do-not-reply at jboss.com (mwittig) Date: Wed, 7 Jan 2009 03:04:19 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: setProperty must be overridden by all subclasses of SOAP Message-ID: <27886429.1231315459951.JavaMail.jboss@colo-br-02.atl.jboss.com> The problem was https://jira.jboss.org/jira/browse/JBWS-1439?focusedCommentId=12436397#action_12436397 thx. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199977#4199977 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199977 From do-not-reply at jboss.com Wed Jan 7 04:23:06 2009 From: do-not-reply at jboss.com (r12345_2003) Date: Wed, 7 Jan 2009 04:23:06 -0500 (EST) Subject: [jbossws-users] [JBossWS] - javax.xml.ws.soap.SOAPFaultException: Read timed out - Does Message-ID: <19229360.1231320186505.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am using jboss eap 4.3 and jboss-ws. My application exposes a web service implemented as a servlet. I also have a web service client that invokes the web service. So far everything works okay. I then started load testing the web service by submitting a number of simultaneously requests. (I wrote a standalone application to do this). I noticed that most of the times all the submitted requests are not processed by the web service. For ex. if I run the test with 25 simultaneous requests, only 22 get processed. The numbers are not consistent and vary on each run. I also noticed the following errors returned by the web service for some client requests: | javax.xml.ws.soap.SOAPFaultException: Read timed out | at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:69) | at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) | at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:553) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:371) | 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) | The following exception is also seen: | javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message | at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:317) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:255) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:164) | ........................ | | Caused by: java.io.IOException: Could not transmit message | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:204) | at org.jboss.ws.core.client.SOAPRemotingConnection.invoke(SOAPRemotingConnection.java:77) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:337) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:243) | ... 11 more | Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:333) | at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:135) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.ws.core.client.RemotingConnectionImpl.invoke(RemotingConnectionImpl.java:183) | ... 14 more | Caused by: java.io.IOException: Error writing to server | at sun.net.www.protocol.http.HttpURLConnection.writeRequests(Unknown Source) | at sun.net.www.protocol.http.HttpURLConnection.writeRequests(Unknown Source) | at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) | at java.net.HttpURLConnection.getResponseCode(Unknown Source) | at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:280) | ... 19 more | I was just wondering if the web service times out under load. If so, is there some way of increasing the timeout? Another point worth mentioning here is that the task performed by the web service is time consuming. So could it be the case that some time consuming web service calls cause a timeout? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200002#4200002 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200002 From postmaster at lists.jboss.org Wed Jan 7 05:31:00 2009 From: postmaster at lists.jboss.org (Automatic Email Delivery Software) Date: Wed, 7 Jan 2009 12:31:00 +0200 Subject: [jbossws-users] RETURNED MAIL: SEE TRANSCRIPT FOR DETAILS Message-ID: <200901071033.n07AXLNl006632@chief.prod.atl2.jboss.com> The original message was received at Wed, 7 Jan 2009 12:31:00 +0200 from 118.128.63.165 ----- The following addresses had permanent fatal errors ----- jbossws-users at lists.jboss.org -------------- next part -------------- A non-text attachment was scrubbed... Name: text.zip Type: application/octet-stream Size: 29182 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090107/98b8f585/attachment.obj From do-not-reply at jboss.com Wed Jan 7 09:43:01 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 7 Jan 2009 09:43:01 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: IllegalStateException Cannot find property Message-ID: <18310573.1231339381879.JavaMail.jboss@colo-br-02.atl.jboss.com> OK, I've patched the sources to log that exception (which btw you should have got in the soap fault anyway). This will be available in JBossWS 3.0.6. Did you find the reason of your issue in the mean time? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200103#4200103 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200103 From do-not-reply at jboss.com Wed Jan 7 17:52:41 2009 From: do-not-reply at jboss.com (tom.e.murphy) Date: Wed, 7 Jan 2009 17:52:41 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JBoss 5.0 fails in startup after applying JBossWS 3.0.5 Message-ID: <15577420.1231368761257.JavaMail.jboss@colo-br-02.atl.jboss.com> I installed JBoss-5.0.0.GA and it ran fine - my jre is a jdk6u10 version. I stopped the instance, then downloaded jbossws-native-3.0.5.GA, set the ant.properties per instructions, and ran ant deploy-jboss500. I then made sure that the jar files from the WS made it to the JBoss lib/endorsed folder, as discussed elsewhere in this forum. Now I'm getting failures during startup of JBoss. Numerous exceptions appear in the log, a portion of which follows. Any clues as to why the JBossWS build kills JBoss like this? Thanks in advance. LOG FRAGMENT: ... 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(remoting-jboss-beans.xml) with relative path: remoting-jboss-beans.xml-e4b4e38880aec6b7ccc5f95d211ae5db\ 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(ROOT.war) with relative path: ROOT.war-7aa373c31716b96f128bcc492afefb1b\ 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(security-jboss-beans.xml) with relative path: security-jboss-beans.xml-f0f673d27f3a8df2fa795ad4d7e63827\ 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(security-policies-jboss-beans.xml) with relative path: security-policies-jboss-beans.xml-c9c500f9d2cfbf66b8f8be49f0e351be\ 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(transaction-jboss-beans.xml) with relative path: transaction-jboss-beans.xml-08047d763ec4fd3cf83823e21ec475d8\ 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(transaction-service.xml) with relative path: transaction-service.xml-fe70a3fcddf5d1625851f8668d33772d\ 16:31:45,736 DEBUG [AbstractAttachmentStore] No persisted attachment found for deployment AbstractVFSDeployment(uuid-key-generator.sar) with relative path: uuid-key-generator.sar-5065595621f5861b2b3f476a27990d3e\ 16:31:45,736 INFO [ProfileServiceImpl] Loading profile: standard from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository at 151fe8a(root=C:\jboss_5_0_0_GA\server, key=org.jboss.profileservice.spi.ProfileKey at 664cb3f[domain=default,server=default,name=standard]) 16:31:45,736 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository at 151fe8a(root=C:\jboss_5_0_0_GA\server, key=org.jboss.profileservice.spi.ProfileKey at 664cb3f[domain=default,server=default,name=standard]) 16:31:45,736 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl at 1c160cb{key=org.jboss.profileservice.spi.ProfileKey at 664cb3f[domain=default,server=default,name=standard]} 16:31:45,752 DEBUG [ProfileServiceBootstrap] Using ProfileService: org.jboss.system.server.profileservice.repository.ProfileServiceImpl at 7b4ed7 16:31:45,752 DEBUG [ProfileServiceBootstrap] Using MainDeployer: org.jboss.deployers.plugins.main.MainDeployerImpl at 17535b6 16:31:45,752 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.kernel.plugins.deployment.AbstractKernelDeployment} 16:31:45,768 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.classloading.spi.metadata.ClassLoadingMetaData} 16:31:45,768 DEBUG [AbstractManagedObjectFactory] ICF returned null class: AbstractBeanMetaData at d0d843{name=topContextComparator bean=null properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 154ea79{parameters= factoryClass=org.jboss.system.deployers.LegacyDeploymentContextComparator factoryMethod=getInstance} autowireCandidate=true} 16:31:45,768 DEBUG [AbstractManagedObjectFactory] ICF returned null class: AbstractBeanMetaData at ed65e0{name=ManagedObjectFactory bean=null properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at d2b918{parameters= factoryClass=org.jboss.managed.api.factory.ManagedObjectFactory factoryMethod=getInstance} autowireCandidate=true installCallbacks=[method=addInstanceClassFactory, method=addManagedObjectDefinition] uninstallCallbacks=[method=removeInstanceClassFactory, method=removeManagedObjectDefinition]} 16:31:45,768 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1144823{name=ManagedObjectCreator bean=org.jboss.deployers.spi.deployer.helpers.DefaultManagedObjectCreator properties=[mof] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,768 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,768 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1144823{name=ManagedObjectCreator bean=org.jboss.deployers.spi.deployer.helpers.DefaultManagedObjectCreator properties=[mof] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,768 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1526e3{name=MainDeployer bean=org.jboss.deployers.plugins.main.MainDeployerImpl properties=[comparator, structuralDeployers, mgtDeploymentCreator, deployers] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1526e3{name=MainDeployer bean=org.jboss.deployers.plugins.main.MainDeployerImpl properties=[comparator, structuralDeployers, mgtDeploymentCreator, deployers] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1cdc190{name=ManagedDeploymentCreator bean=org.jboss.deployers.plugins.managed.TypedManagedDeploymentCreator properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1cdc190{name=ManagedDeploymentCreator bean=org.jboss.deployers.plugins.managed.TypedManagedDeploymentCreator properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 15ede11{name=StructuralDeployers bean=org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl properties=[structureBuilder] constructor=null autowireCandidate=true installCallbacks=[method=addDeployer] uninstallCallbacks=[method=removeDeployer]} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 15ede11{name=StructuralDeployers bean=org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl properties=[structureBuilder] constructor=null autowireCandidate=true installCallbacks=[method=addDeployer] uninstallCallbacks=[method=removeDeployer]} 16:31:45,783 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1ceebfa{name=Deployers bean=org.jboss.deployers.plugins.deployers.DeployersImpl properties=[mgtObjectCreator] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 1cee361{parameters=[null]} autowireCandidate=true annotations=[AbstractAnnotationMetaData at 1e6743e{expr={exposedInterface=interface org.jboss.deployers.plugins.deployers.DeployersImplMBean, name=jboss.deployment:service=DeployersImpl, registerDirectly=true}}] installCallbacks=[method=addDeployer] uninstallCallbacks=[method=removeDeployer]} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1ceebfa{name=Deployers bean=org.jboss.deployers.plugins.deployers.DeployersImpl properties=[mgtObjectCreator] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 1cee361{parameters=[null]} autowireCandidate=true annotations=[AbstractAnnotationMetaData at 1e6743e{expr={exposedInterface=interface org.jboss.deployers.plugins.deployers.DeployersImplMBean, name=jboss.deployment:service=DeployersImpl, registerDirectly=true}}] installCallbacks=[method=addDeployer] uninstallCallbacks=[method=removeDeployer]} 16:31:45,783 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 19f9c7a{name=DeclaredStructure bean=org.jboss.deployers.vfs.plugins.structure.explicit.DeclaredStructure properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 19f9c7a{name=DeclaredStructure bean=org.jboss.deployers.vfs.plugins.structure.explicit.DeclaredStructure properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1da366c{name=JARStructure bean=org.jboss.deployers.vfs.plugins.structure.jar.JARStructure properties=[candidateStructureVisitorFactory] constructor=AbstractConstructorMetaData at 8be9ef{parameters=[null]} autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 1da366c{name=JARStructure bean=org.jboss.deployers.vfs.plugins.structure.jar.JARStructure properties=[candidateStructureVisitorFactory] constructor=AbstractConstructorMetaData at 8be9ef{parameters=[null]} autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at cd927d{name=FileStructure bean=org.jboss.deployers.vfs.plugins.structure.file.FileStructure properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 16fdcc1{parameters=[null]} autowireCandidate=true installCallbacks=[method=addFileMatcher] uninstallCallbacks=[method=removeFileMatcher]} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at cd927d{name=FileStructure bean=org.jboss.deployers.vfs.plugins.structure.file.FileStructure properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 16fdcc1{parameters=[null]} autowireCandidate=true installCallbacks=[method=addFileMatcher] uninstallCallbacks=[method=removeFileMatcher]} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 4c562f{name=AOPXMLMetaDataParserDeployer bean=org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer properties=[suffix] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 9d5793{parameters=[null]} autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 4c562f{name=AOPXMLMetaDataParserDeployer bean=org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer properties=[suffix] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 9d5793{parameters=[null]} autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 3d511e{name=AOPAnnotationMetaDataParserDeployer bean=org.jboss.aop.asintegration.jboss5.AOPAnnotationMetaDataParserDeployer properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 189c12a{parameters=[null]} autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 3d511e{name=AOPAnnotationMetaDataParserDeployer bean=org.jboss.aop.asintegration.jboss5.AOPAnnotationMetaDataParserDeployer properties= classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=AbstractConstructorMetaData at 189c12a{parameters=[null]} autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 198a35d{name=AOPClassLoaderDeployer bean=org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer properties=[aspectManager] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [AbstractManagedObjectFactory] Created skeleton ManagedObject: ManagedObject{org.jboss.beans.metadata.plugins.AbstractBeanMetaData} 16:31:45,783 DEBUG [BeanMetaDataICF] Using bean class:, class org.jboss.beans.metadata.plugins.AbstractBeanMetaData for bean: AbstractBeanMetaData at 198a35d{name=AOPClassLoaderDeployer bean=org.jboss.aop.asintegration.jboss5.AOPClassLoaderDeployer properties=[aspectManager] classLoader=AbstractClassLoaderMetaData at 6a2f81{classloader=AbstractDependencyValueMetaData at 1263b07{value=deployers-classloader:0.0.0}} constructor=null autowireCandidate=true} 16:31:45,783 DEBUG [BeanMetaDataICF] Failed to get property value for bean: org.jboss.beans.metadata.plugins.AbstractBeanMetaData, property: properties java.lang.IllegalArgumentException: Property is not readable: propertyReplace for org.jboss.beans.metadata.plugins.AbstractPropertyMetaData at org.jboss.beans.info.plugins.DefaultPropertyInfo.get(DefaultPropertyInfo.java:131) at org.jboss.beans.info.plugins.BeanInfoUtil.getNestedTarget(BeanInfoUtil.java:78) at org.jboss.beans.info.plugins.BeanInfoUtil.get(BeanInfoUtil.java:142) at org.jboss.beans.info.plugins.AbstractBeanInfo.getProperty(AbstractBeanInfo.java:284) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCompositeValue(DefaultMetaValueFactory.java:471) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1023) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.createCollectionValue(DefaultMetaValueFactory.java:247) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.internalCreate(DefaultMetaValueFactory.java:1029) at org.jboss.metatype.plugins.values.DefaultMetaValueFactory.create(DefaultMetaValueFactory.java:542) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:165) at org.jboss.deployers.plugins.managed.BeanMetaDataICF.getValue(BeanMetaDataICF.java:48) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectValue(AbstractInstanceClassFactory.java:315) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getManagedObjectArray(AbstractInstanceClassFactory.java:331) at org.jboss.managed.plugins.factory.AbstractInstanceClassFactory.getValue(AbstractInstanceClassFactory.java:252) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateValues(AbstractManagedObjectPopulator.java:201) at org.jboss.managed.plugins.factory.AbstractManagedObjectPopulator.populateManagedObject(AbstractManagedObjectPopulator.java:130) at org.jboss.managed.plugins.factory.AbstractManagedObjectFactory.initManagedObject(AbstractManagedObjectFactory.java:364) at org.jboss.managed.api.factory.ManagedObjectFactory.initManagedObject(ManagedObjectFactory.java:77) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.initBootstrapMDs(ProfileServiceBootstrap.java:447) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:199) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405) at org.jboss.Main.boot(Main.java:209) at org.jboss.Main$1.run(Main.java:547) at java.lang.Thread.run(Thread.java:619) ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200196#4200196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200196 From do-not-reply at jboss.com Thu Jan 8 04:52:50 2009 From: do-not-reply at jboss.com (edaogut) Date: Thu, 8 Jan 2009 04:52:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Can JBoss set Username Token in SOAP header with authent Message-ID: <2465566.1231408370101.JavaMail.jboss@colo-br-02.atl.jboss.com> I'll call a web service by using Java , I need client code example to put username and password by using token message ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200276#4200276 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200276 From do-not-reply at jboss.com Thu Jan 8 07:59:26 2009 From: do-not-reply at jboss.com (giordano) Date: Thu, 8 Jan 2009 07:59:26 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Problems with EJB3 and JBossWS Message-ID: <8276725.1231419566793.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello everybody, I have the following problem: I developed a simple EJB application using JBoss 5.0.0.GA without any upgrading. The EJB application is made by 2 Entity with oneToMany bidirectional relation. I also developed a SLSB to create, delete, get the entity beans. Due to relation Entity Bean 1 contains a list of Entity Beans 2 and Entity Bean 2 contains a reference to Entity Bean 1. I also developed a simple external client. Through this client I call the SLSB to create some Entity Bean 1 and some Entity Beans 2 and the relationships. Thorough the same SLSB I get all Entity Bean 1 (with all the related Entity Bean 2) and I have no problems. Now I exposed all the methods of SLSB as WS and I created another client for WS. With this client I am able to call all methods except the method that get all Entity Bean 1. I have an error due to bidirectional relationship between the Entity Bean 1 and the Entity Bean 2. I modified the relationship from bidirectional to unidirectional and now I am able to call the method get all Entity Bean 1 from WS Client. Is there one able to explain me which is the problem and if I can solve it? Thank you very much and bye, Giordano View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200330#4200330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200330 From do-not-reply at jboss.com Thu Jan 8 12:42:50 2009 From: do-not-reply at jboss.com (justin_sane) Date: Thu, 8 Jan 2009 12:42:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Exceptions thrown to the client without logging Message-ID: <18775752.1231436570345.JavaMail.jboss@colo-br-02.atl.jboss.com> I have some custom exceptions created in my web service. When the client calls that web service within jboss, when it fails with a custom exception I want it to return to the client the exception. All fine, except for one little thing. The JAXWS that handles the request, before sending the exception to the client, calls logger.error on that exception! I can configure the log4j or some other logger to avoid this, but is there some nice solution, like configuring jax to only stacktrace the exceptions that aren't defined in the web service interface. Thank You View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200405#4200405 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200405 From do-not-reply at jboss.com Thu Jan 8 22:50:19 2009 From: do-not-reply at jboss.com (sakura_tom) Date: Thu, 8 Jan 2009 22:50:19 -0500 (EST) Subject: [jbossws-users] [JBossWS] - How to resolved this problem. Message-ID: <7770255.1231473019751.JavaMail.jboss@colo-br-02.atl.jboss.com> 11:35:11,487 ERROR [MainDeployer] Could not start deployment: file:/C:/jboss-4.2.2.GA/server/default/deploy/commonAPI.jar java.lang.IllegalStateException: Cannot build JAXB context at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:925) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:146) at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50) at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderEJB3.buildMetaData(JAXWSMetaDataBuilderEJB3.java:78) at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:71) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:115) at org.jboss.wsf.container.jboss42.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:97) at org.jboss.wsf.container.jboss42.DeployerInterceptor.start(DeployerInterceptor.java:90) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy34.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy9.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:508) at java.lang.Thread.run(Thread.java:595) Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 2 counts of IllegalAnnotationExceptions java.io.Serializable is an interface, and JAXB can't handle interfaces. this problem is related to the following location: at java.io.Serializable at private java.util.List ims.vi.common.service.jaxws.SearchByCriteriaResponse._return at ims.vi.common.service.jaxws.SearchByCriteriaResponse java.io.Serializable does not have a no-arg default constructor. this problem is related to the following location: at java.io.Serializable at private java.util.List ims.vi.common.service.jaxws.SearchByCriteriaResponse._return at ims.vi.common.service.jaxws.SearchByCriteriaResponse at com.sun.xml.bind.v2.runtime.IllegalAnnotationsException$Builder.check(IllegalAnnotationsException.java:102) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.getTypeInfoSet(JAXBContextImpl.java:438) at com.sun.xml.bind.v2.runtime.JAXBContextImpl.(JAXBContextImpl.java:286) at com.sun.xml.bind.v2.ContextFactory.createContext(ContextFactory.java:139) at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:105) at com.sun.xml.bind.api.JAXBRIContext.newInstance(JAXBRIContext.java:116) at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBContext(JAXWSMetaDataBuilder.java:921) ... 81 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200481#4200481 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200481 From do-not-reply at jboss.com Fri Jan 9 04:13:49 2009 From: do-not-reply at jboss.com (r12345_2003) Date: Fri, 9 Jan 2009 04:13:49 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.soap.SOAPFaultException: Read timed out - D Message-ID: <18204248.1231492429757.JavaMail.jboss@colo-br-02.atl.jboss.com> Any ideas anyone? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200512#4200512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200512 From do-not-reply at jboss.com Fri Jan 9 09:29:03 2009 From: do-not-reply at jboss.com (narensb) Date: Fri, 9 Jan 2009 09:29:03 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Thread pool error Message-ID: <10289202.1231511343339.JavaMail.jboss@colo-br-02.atl.jboss.com> I have created a event source.when subscription request is coming i am passing the subscription info to lower layer where events are generated. After getting the subscription status at lower layer level i am subscribing the subscription in jboss eventing module. The events are being generated in the lower layer creating a new thread which is calling a dispatch method of Dispatch service(where actual dispatching is done using delegate.dispatch() as specified in the user guide chapter 16 of jbossws). I am getting this error 19:44:26,433 ERROR [STDERR] Exception in thread "pool-1-thread-2" 19:44:26,433 ERROR [STDERR] java.lang.NullPointerException 19:44:26,433 ERROR [STDERR] at org.jboss.ws.extensions.eventing.mgmt.DispatchJob.run(DispatchJob.java:51) 19:44:26,433 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) 19:44:26,433 ERROR [STDERR] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) 19:44:26,433 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595) any clue plzz help!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200581#4200581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200581 From do-not-reply at jboss.com Fri Jan 9 10:24:56 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 9 Jan 2009 10:24:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problems accessing SSL webservice Message-ID: <23057926.1231514696670.JavaMail.jboss@colo-br-02.atl.jboss.com> First of all take a look at this if you didn't already: http://jbossws.jboss.org/mediawiki/index.php?title=Secure_transport Then look at the following testcase: org.jboss.test.ws.interop.nov2007.wsse.UsernameTokenHTTPSTestCase This said, you can specify the target endpoint address using something like: ((BindingProvider)port).getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, targetEndpoint); View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200612#4200612 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200612 From do-not-reply at jboss.com Fri Jan 9 14:04:14 2009 From: do-not-reply at jboss.com (srinijb) Date: Fri, 9 Jan 2009 14:04:14 -0500 (EST) Subject: [jbossws-users] [JBossWS] - DOM parser performance issue Message-ID: <23599794.1231527854182.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, We are running into OutOfMemory issues when testing the service that returns large results. Web service libraries are relying on DOM to serialize the DTO, it appears that DOM does this very inefficiently. I am wondering if there is a way to replace DOM with SAX/other parser to increase efficiency? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200687#4200687 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200687 From snow8261 at gmail.com Sun Jan 11 02:38:48 2009 From: snow8261 at gmail.com (Tongjie Li) Date: Sun, 11 Jan 2009 15:38:48 +0800 Subject: [jbossws-users] WS-eventing sample Message-ID: <6054b7290901102338q3ebbe578idf4c0896d11747a4@mail.gmail.com> hello everyone i found JBossWS support ws-eventing, it there any sample of ws-eventing shipped with JBossWS? thank you for information! -- All the Best! Li Tongjie -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/jbossws-users/attachments/20090111/61f213de/attachment.html From ropalka at redhat.com Mon Jan 12 03:09:00 2009 From: ropalka at redhat.com (Richard Opalka) Date: Mon, 12 Jan 2009 09:09:00 +0100 Subject: [jbossws-users] WS-eventing sample In-Reply-To: <6054b7290901102338q3ebbe578idf4c0896d11747a4@mail.gmail.com> References: <6054b7290901102338q3ebbe578idf4c0896d11747a4@mail.gmail.com> Message-ID: <496AFA9C.4050602@redhat.com> Download JBossWS 3.0.5 source distribution. Richard Tongjie Li wrote: > hello everyone > > i found JBossWS support ws-eventing, it there any sample of > ws-eventing shipped with JBossWS? > > thank you for information! > -- > All the Best! > Li Tongjie > ------------------------------------------------------------------------ > > _______________________________________________ > 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 Mon Jan 12 06:54:37 2009 From: do-not-reply at jboss.com (adinn) Date: Mon, 12 Jan 2009 06:54:37 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Class Cast Exception under Endpoint.publish() Message-ID: <27530940.1231761277523.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using JBossAS 5.0.0.GA with JBossWS 3.0.4 and I am trying to publish an endpoint using | Endpoint publish(String address, Object implementor) | I supply the call with an instance of my endpoint class which is annotated with the appropriate WebService, SOAPBinding, WebMethod, etc annotations. During deployment of the endpoint I get a Class Cast Exception as follows | 11:40:51,731 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=/xtsservicetests1 state=ClassLoader mode=Manual requiredState=PostClassLoader | org.jboss.deployers.spi.DeploymentException: Error during deploy: /xtsservicetests1 | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:177) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781) | at org.jboss.deployers.plugins.main.MainDeployerImpl.deploy(MainDeployerImpl.java:418) | at org.jboss.wsf.container.jboss50.transport.EndpointAPIHttpTransportManager.deploy(EndpointAPIHttpTransportManager.java:169) | at org.jboss.wsf.container.jboss50.transport.EndpointAPIHttpTransportManager.createListener(EndpointAPIHttpTransportManager.java:85) | at org.jboss.wsf.framework.deployment.HttpTransportDeploymentAspect.create(HttpTransportDeploymentAspect.java:76) | at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.create(DeploymentAspectManagerImpl.java:121) | at org.jboss.wsf.container.jboss50.BareWSFRuntime.create(BareWSFRuntime.java:61) | at org.jboss.wsf.container.jboss50.transport.WSFRuntimeDelegateHttpServer.publish(WSFRuntimeDelegateHttpServer.java:96) | at org.jboss.ws.core.jaxws.spi.EndpointImpl.publish(EndpointImpl.java:172) | at org.jboss.ws.core.jaxws.spi.EndpointImpl.publish(EndpointImpl.java:129) | at org.jboss.ws.core.jaxws.spi.ProviderImpl.createAndPublishEndpoint(ProviderImpl.java:83) | at javax.xml.ws.Endpoint.publish(Endpoint.java:184) | at org.jboss.jbossts.xts.servicetests.service.XTSServiceTestServiceManager.publish(XTSServiceTestServiceManager.java:19) | at org.jboss.jbossts.xts.servicetests.test.XTSPublishAndInvokeTest.run(XTSPublishAndInvokeTest.java:20) | at org.jboss.jbossts.xts.servicetests.bean.XTSServiceTestRunnerBean$1.run(XTSServiceTestRunnerBean.java:74) | Caused by: java.lang.ClassCastException: org.jboss.deployers.structure.spi.helpers.AbstractDeploymentUnit | at org.jboss.deployment.security.AbstractSecurityDeployer.deploy(AbstractSecurityDeployer.java:148) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171) | ... 25 more | The problem is that AbstractSecurityDeployer.deploy is invoked with an AbstractDeploymentUnit as argument. However, at line 148 it tries to cast its argument to a VFSDeploymentUnit. Any ideas why this is happening? Has anyone successfully managed to use Endpoint.publish previously? If so what did you do to avoid running up against this exception? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200960#4200960 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200960 From do-not-reply at jboss.com Mon Jan 12 07:13:49 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 12 Jan 2009 07:13:49 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception under Endpoint.publish() Message-ID: <32800867.1231762429640.JavaMail.jboss@colo-br-02.atl.jboss.com> Endpoint.publish() isn't supported on AS 5.x, see (JBWS-1967) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200966#4200966 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200966 From do-not-reply at jboss.com Mon Jan 12 08:32:56 2009 From: do-not-reply at jboss.com (adinn) Date: Mon, 12 Jan 2009 08:32:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception under Endpoint.publish() Message-ID: <6821232.1231767176495.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for the quick response, Richard. anonymous wrote : | Endpoint.publish(), Endpoint.unpublish() is faulty by design IMHO. | It doesn't make sense to be able to publish POJOs to different web contexts. | | Here are top two reasons why I think it is broken and hence excluded from TCK5 tests: | * security issue (how to configure java security for such ugly published endpoints where e.g. Security Manager is turned on)? | * design problem (why web archive should be able to publish another web/ejb archive)? | I'm not sure exactly why you think this makes it either undesirable or impossible to implement the Endpoint API as defined in the JaxWS spec. Let's go through these in turn: 1) It definitely makes sense to publish a specific POJO to a specific web context. Firstly, this API is simpler to use than providing a war with web.xml config. Secondly, it is dynamic, which allows all sorts of options not available using fixed web.xml config. For example, the endpoint implementation class might be loaded (or even generated) dynamically by the application. And, actually, if you want to use the same POJO to masquerade behind two (or more) different URLs what is wrong with that? I can imagine good reasons for presenting a single service via multiple URLs and iIt's quite straightforward to deal with any threading issues this might imply. 2) The JaxWS spec does talk about security (Subsection 5.2.3 of the 21. spec) and, indeed, the Security permission it defines is checked by the current implementation of class EndpointImpl. Why can this implementation not be retro-fitted to conform to the JBoss Security Manager requirements? 3) I don't want a web archive to publish another web/ejb archive. In my case I have a test runner program for the XTS (Web Services Transactions) implementation. I deploy the test runner as a POJO via a jboss-beans.xml file. The test runner dynamically loads and executes different tests on different runs. Depending upon the specifics of the test, it needs to be able to install 0 or more POJOs as web service endpoints during test bootstrap. I could, of course, deploy my test runner inside a war which statically deploys N endpoints via a web.xml config file. At present, I only use a single POJO service implementation but I don't always need the same value of N. In fact, for some runs (more precisely, on some of the AS instances employed in some of the runs -- the tests employ more than one AS) I don't even need to deploy a web service to complete the test. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4200991#4200991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4200991 From do-not-reply at jboss.com Mon Jan 12 09:03:17 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 12 Jan 2009 09:03:17 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception under Endpoint.publish() Message-ID: <22769745.1231768997734.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for your valuable feedback Andrew. I reopened the aforementioned issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201005#4201005 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201005 From do-not-reply at jboss.com Mon Jan 12 09:30:50 2009 From: do-not-reply at jboss.com (adinn) Date: Mon, 12 Jan 2009 09:30:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception under Endpoint.publish() Message-ID: <19631777.1231770650058.JavaMail.jboss@colo-br-02.atl.jboss.com> Wow, that's certainly what I call quality service! I'm not 100% sure why you immediately reopened it though. I was posting more to discuss the reasons for excluding it than to state an absolute requirement :-) Well, ok, I actually saw that Alessio told you to do it on the assumption that eventually the TCK tests will be reinstated. However, I noticed that the JaxWS spec doesn't actually include a Conformance note indicating that the Endpoint API must be implemented. Maybe this is why the TCK tests are commented out? I would still like to be able to use the Endpoint API but as it is not available now I am going to have to go ahead with static configured endpoints. So, although this feature would be nice to have don't prioritise it before other important customer-driven features on my account. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201019#4201019 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201019 From do-not-reply at jboss.com Mon Jan 12 11:37:40 2009 From: do-not-reply at jboss.com (srinijb) Date: Mon, 12 Jan 2009 11:37:40 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: DOM parser performance issue Message-ID: <4729991.1231778261002.JavaMail.jboss@colo-br-02.atl.jboss.com> Any ideas friends? How can I replace underlying parsing engine to SAX from DOM ? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201075#4201075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201075 From do-not-reply at jboss.com Tue Jan 13 01:31:46 2009 From: do-not-reply at jboss.com (okiSM) Date: Tue, 13 Jan 2009 01:31:46 -0500 (EST) Subject: [jbossws-users] [JBossWS] - SLSB exposed as WS security issue Message-ID: <7204024.1231828306489.JavaMail.jboss@colo-br-02.atl.jboss.com> I have SLSB exposed as WS. I tried to add security. WS is deployed as jar. I've placed jboss-wsse-server and keystore files into META-INF (together with persistence.xml). | | META-INF/wsse.keystore | jbossws | META-INF/wsse.truststore | jbossws | | | | | | | | | | This configuration is read during deployment (if I put wrong locations of keystores, jar deployment breaks). However, when I try to access this WS with an unsecured client (generated using wsconsume) it responds normally (as if there is no security). Endpoint interface: import javax.ejb.Remote; | import javax.jws.WebMethod; | import javax.jws.WebService; | import javax.jws.soap.SOAPBinding; | | @WebService(name = "CityFacadeProxy", targetNamespace="http://gint_scm_ws") | @SOAPBinding(style=SOAPBinding.Style.DOCUMENT, use=SOAPBinding.Use.LITERAL, parameterStyle=SOAPBinding.ParameterStyle.WRAPPED) | @Remote | public interface CityFacadeSEI { | @WebMethod | public City createCity(String cityName) throws RemoteException; | } | Implemetation bean: import gint.scm.ws.entity.City; | | import javax.ejb.Remote; | import javax.ejb.Stateless; | import javax.jws.WebService; | import javax.persistence.EntityManager; | import javax.persistence.PersistenceContext; | import javax.xml.ws.BindingType; | | import org.jboss.ws.annotation.EndpointConfig; | import org.jboss.wsf.spi.annotation.WebContext; | | @Stateless | @WebService(endpointInterface = "gint.scm.ws.session.CityFacadeSEI", | serviceName = "CityFacadeServis", targetNamespace="http://gint_scm_ws") | @WebContext(contextRoot="/SCM", urlPattern="/*") | @BindingType(value = "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true") | @EndpointConfig(configName = "Standard WSSecurity Endpoint") | @Remote(CityFacadeSEI.class) | public class CityFacadeBean implements CityFacadeSEI { | | @PersistenceContext(name = "scm") | EntityManager em; | | public City createCity(String cityName) { | em.persist(new City(cityName.hashCode(), cityName)); | return new City(cityName.hashCode(), cityName); | } | | } What's wrong here? There are no examples for security for SLSB WS (or I couldn't find them in last 4 weeks). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201217#4201217 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201217 From do-not-reply at jboss.com Tue Jan 13 01:42:52 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 13 Jan 2009 01:42:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception under Endpoint.publish() Message-ID: <16447185.1231828972483.JavaMail.jboss@colo-br-02.atl.jboss.com> "adinn" wrote : Well, ok, I actually saw that Alessio told you to do it on the assumption that eventually the TCK tests will be reinstated. Yes, this was the reason of reopening it. (We were discussing this issue on IRC with Alessio) "adinn" wrote : However, I noticed that the JaxWS spec doesn't actually include a Conformance note indicating that the Endpoint API must be implemented. Maybe this is why the TCK tests are commented out? Maybe, but we see Sun folks are working on these TCK5 excluded tests at the moment. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201218#4201218 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201218 From do-not-reply at jboss.com Tue Jan 13 01:45:52 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 13 Jan 2009 01:45:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Class Cast Exception under Endpoint.publish() Message-ID: <4489539.1231829152417.JavaMail.jboss@colo-br-02.atl.jboss.com> "adinn" wrote : So, although this feature would be nice to have don't prioritise it before other important customer-driven features on my account. Don't worry, we'll start working on it once it will be available in TCK5 test suite again ;) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201219#4201219 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201219 From do-not-reply at jboss.com Tue Jan 13 02:09:13 2009 From: do-not-reply at jboss.com (narensb) Date: Tue, 13 Jan 2009 02:09:13 -0500 (EST) Subject: [jbossws-users] [JBossWS] - unsubscibing for an event Message-ID: <25274049.1231830553824.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using soapUI 2.5 to subscribe and unsubscribe for events in jboss eventing module.Already deployed the event source and manager endpoint. This is the subscription request (Raw xml) User-Agent: Jakarta Commons-HttpClient/3.1 | Host: localhost:8080 | Content-Length: 1612 | | | | http://schemas.xmlsoap.org/ws/2004/08/eventing/Subscribehttp://www.w3.org/2005/08/addressing/anonymoushttp://www.w3.org/2005/08/addressing/anonymoushttp://www.w3.org/2005/08/addressing/anonymous73e0832e-50e3-48aa-9eed-675b50b2b42chttp://com.temp/ServiceEventInfo | | | | http://localhost:8080/EventSink/EventSink | | | | | http://localhost:8080/EventSink/EventSink | | | | | | | This is the subscription response | | | http://www.w3.org/2005/08/addressing/anonymous | http://schemas.xmlsoap.org/ws/2004/08/eventing/SubscribeResponse | 73e0832e-50e3-48aa-9eed-675b50b2b42c | | | | |
http://localhost:8080/eventing123/ServiceManagementEndpoint
| | urn:jbwse:4533e47c-a0f-4790-a499-f2b4788b62a2 | |
| 2009-01-13T11:30:08.899+05:30 |
|
|
| this is the unsubscribe request(raw xml) POST http://localhost:8080/eventing123/ServiceManagementEndpoint HTTP/1.1 | Content-Type: text/xml;charset=UTF-8 | SOAPAction: "" | User-Agent: Jakarta Commons-HttpClient/3.1 | Host: localhost:8080 | Content-Length: 1039 | | | | | urn:jbwse:4533e47c-a0f-4790-a499-f2b4788b62a2 | | http://schemas.xmlsoap.org/ws/2004/08/eventing/Unsubscribehttp://www.w3.org/2005/08/addressing/anonymoushttp://www.w3.org/2005/08/addressing/anonymoushttp://www.w3.org/2005/08/addressing/anonymous7c5478bc-cd83-41c9-8d10-40ac896b2f7ehttp://localhost:8080/eventing123/ServiceManagementEndpoint | | | | | | | This is the unsubscribe response | | http://www.w3.org/2005/08/addressing/anonymous | http://www.w3.org/2005/08/addressing/fault | 7c5478bc-cd83-41c9-8d10-40ac896b2f7e | | | | env:Server | The message is not valid and cannot be processed: Cannot obtain subscription id. | | | | I have specified the subscription id in unsubscribe request but still it gives cannot obtain subscription id plz help!!! wt am i missing here? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201226#4201226 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201226 From postmaster at lists.jboss.org Tue Jan 13 04:10:51 2009 From: postmaster at lists.jboss.org (Mail Administrator) Date: Tue, 13 Jan 2009 11:10:51 +0200 Subject: [jbossws-users] Report Message-ID: <200901130913.n0D9DDci026183@chief.prod.atl2.jboss.com> The message was undeliverable due to the following reason(s): Your message was not delivered because the destination computer was not reachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely there is a network problem that prevented delivery, but it is also possible that the computer is turned off, or does not have a mail system running right now. Your message was not delivered within 7 days: Host 218.14.49.184 is not responding. The following recipients could not receive this message: Please reply to postmaster at lists.jboss.org if you feel this message to be in error. -------------- next part -------------- A non-text attachment was scrubbed... Name: message.zip Type: application/octet-stream Size: 28984 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090113/86d1389d/attachment.obj From do-not-reply at jboss.com Tue Jan 13 05:08:16 2009 From: do-not-reply at jboss.com (okiSM) Date: Tue, 13 Jan 2009 05:08:16 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: SLSB exposed as WS security issue Message-ID: <22206214.1231841296509.JavaMail.jboss@colo-br-02.atl.jboss.com> When I set treshhold to ALL in jboss-log4j.xml, there are several ClassNotFoundExceptions: org.springframework.scripting.config.LangNamespaceHandler org.springframework.ejb.config.JeeNamespaceHandler org.springframework.transaction.config.TxNamespaceHandler org.springframework.aop.config.AopNamespaceHandler Does this matter? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201284#4201284 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201284 From do-not-reply at jboss.com Tue Jan 13 07:57:18 2009 From: do-not-reply at jboss.com (okiSM) Date: Tue, 13 Jan 2009 07:57:18 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: SLSB exposed as WS security issue Message-ID: <11129281.1231851438815.JavaMail.jboss@colo-br-02.atl.jboss.com> Why no one told that it has to be deployed on 'all' configuration (4.2.3)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201363#4201363 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201363 From do-not-reply at jboss.com Tue Jan 13 08:42:35 2009 From: do-not-reply at jboss.com (rijkr) Date: Tue, 13 Jan 2009 08:42:35 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JBoss 5.0.0.GA: WebCtxLoader - RuntimeException: mapped-name Message-ID: <26003413.1231854155910.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using jboss-5.0.0.GA to deploy a web service. This service uses a WebService Context. In jboss-web.xml the following tags are present: MyWebService/wsc javax.xml.ws.WebServiceContext Container Shareable MyWebService wsc When starting jboss (run.sh) MyWebService fails to start, due to this error (server.log): 2009-01-13 11:39:37,772 DEBUG [org.jboss.web.tomcat.service.WebCtxLoader] (main) injectionContainer enabled and processing beginning with JBoss WebCtxLoader 2009-01-13 11:39:37,857 ERROR [org.apache.catalina.core.StandardContext] (main) Context [/MyWebApplication] startup failed due to previous errors java.lang.RuntimeException: mapped-name is required for MyWebService/wsc of deployment MyWebApplication.war I saw some posts regarding this issue but am not sure if this is a known issue for the 5.0.0.GA release, or that there is a solution available? Can anyone help me with a solution? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201381#4201381 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201381 From do-not-reply at jboss.com Tue Jan 13 14:17:51 2009 From: do-not-reply at jboss.com (sstaible) Date: Tue, 13 Jan 2009 14:17:51 -0500 (EST) Subject: [jbossws-users] [JBossWS] - XML signatures as WS payload? Message-ID: <15633502.1231874271761.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, we've implemented a web service that receives a xml structure as input, signs it (with XML-D-Sig) and returns it to the client. We found out however that during transport of the xml structure from the client to server (and also back), the whitespaces in the XML data partially stripped from the XML data. This of course makes the XML signature completely unusable. To embed the unsigned and signed XML structures into the SOAP-request/response we use the XmlAnyElement annotation (auto-generated JAX-WS2.0 class from the WSDL). So the XML structures are embedded directly as a sub node into the SOAP structure. We use JBoss 4.2.3.GA on the server and the respective JBoss client libraries on the client-side. Is this behaviour of JBoss normal? I'm quite new to web services, JAXB, JAX-WS and the like but I would expect embedded xml to be transported unmodified over the SOAP channel. Any help or explanation of this behaviour is highly appreciated. Regards, Sven www.keyon.ch View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201493#4201493 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201493 From do-not-reply at jboss.com Tue Jan 13 21:31:34 2009 From: do-not-reply at jboss.com (nogamejoe) Date: Tue, 13 Jan 2009 21:31:34 -0500 (EST) Subject: [jbossws-users] [JBossWS] - How do I determine which version of JBossWS is being used? Message-ID: <2094250.1231900294890.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am reviewing JBoss Portal and JBossWS support. I currently installed JBossWS 3.05 into JBoss Portal 2.6.7 which is using JBoss AS 4.2.3. I am testing portlets. So far my portlet examples work. However they had also worked prior to installing JBossWS 3.0.5. How do I find out what version of the WS Stack my JBoss Portal environment is executing with, upon startup. I checked the boot.log, and found no mention of JBossWS 3.0.5. I tried following the install instructions (JBossWS 3.0.5 native GA) which instructed that I navigate to http://localhost:8080/jbossws. The page is displayed, however, if I do the same within the old environment, the same page is displayed - without any version specification made regarding JBossWS. So after all the above, the basic question at hand is: How do I determine which specific version my JBoss Portal environment is executing with? If you need any more information to help with this request, please let me know. Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201552#4201552 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201552 From do-not-reply at jboss.com Tue Jan 13 23:19:39 2009 From: do-not-reply at jboss.com (nogamejoe) Date: Tue, 13 Jan 2009 23:19:39 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: How do I determine which version of JBossWS is being use Message-ID: <17838607.1231906779756.JavaMail.jboss@colo-br-02.atl.jboss.com> I found the answer. I missed the reference several times. Found it in console and then the server.log. I missed original references before posting. Damn...always seems to be the way, now if I can only find my glasses...oh there they are...right on top of my head ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201567#4201567 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201567 From do-not-reply at jboss.com Wed Jan 14 01:19:52 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 14 Jan 2009 01:19:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: XML signatures as WS payload? Message-ID: <31350236.1231913992236.JavaMail.jboss@colo-br-02.atl.jboss.com> "sstaible" wrote : Hi, | Any help or explanation of this behaviour is highly appreciated. | I suggest you to call Node.normalize() method before calling XML digital signature API. You can't rely on the precondition SOAP message will be unmodified (regarding the whitespaces) on other side. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201582#4201582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201582 From do-not-reply at jboss.com Wed Jan 14 02:34:09 2009 From: do-not-reply at jboss.com (mikaeljl) Date: Wed, 14 Jan 2009 02:34:09 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <31842345.1231918449513.JavaMail.jboss@colo-br-02.atl.jboss.com> For anyone watching/tracking this thread: Looks like JBWS-1999 has been implemented and is now scheduled for the 3.0.6 release. Docs updated at: http://jbossws.jboss.org/mediawiki/index.php?title=WS-Security_options look for POJO endpoint. This seems to be exactly what I was looking for when I initially started this thread, looking forward to try this out! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201597#4201597 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201597 From do-not-reply at jboss.com Wed Jan 14 02:53:27 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 02:53:27 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <11368154.1231919607244.JavaMail.jboss@colo-br-02.atl.jboss.com> Yes, that has just been implemented on trunk and we'll included in the next release. Getting the sources from svn, giving it a try and providing feedback now could be usefu if you have some spare time. Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201601#4201601 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201601 From do-not-reply at jboss.com Wed Jan 14 03:03:29 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:03:29 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: XML signatures as WS payload? Message-ID: <30578198.1231920209183.JavaMail.jboss@colo-br-02.atl.jboss.com> Is there a reason why you're not using the WS-Security implementation provided by jbossws (which of course offers signing functionalities) ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201606#4201606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201606 From do-not-reply at jboss.com Wed Jan 14 03:08:50 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:08:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBoss WS 3.0.5 SFSB as a web service Message-ID: <27561032.1231920530633.JavaMail.jboss@colo-br-02.atl.jboss.com> "taral" wrote : i tried with jboss ws metro 3.2.2. | after installation it was giving me error jaxb-xjc.jar is alredy registered. | can any body comment pl? | Btw this will be solved, but it's actually not a blocking issue, it doesn't hurt. https://jira.jboss.org/jira/browse/JBWS-2385 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201607#4201607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201607 From do-not-reply at jboss.com Wed Jan 14 03:27:50 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:27:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Recomended way to build server and client with maven? Message-ID: <29443275.1231921670259.JavaMail.jboss@colo-br-02.atl.jboss.com> "sverker" wrote : | * Use the wsconsume ant task with maven-antrun-plugin. Should work fine but is not a very "elegant" solution. | I'd saying this is the way to go giving what we have now. In general, also consider including the jbossws native artifact instead of the framework one, to be sure you don't miss anything. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201615#4201615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201615 From do-not-reply at jboss.com Wed Jan 14 03:29:09 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:29:09 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problems with EJB3 and JBossWS Message-ID: <14518196.1231921749425.JavaMail.jboss@colo-br-02.atl.jboss.com> To better understand, could you please post the exception you're getting please? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201616#4201616 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201616 From do-not-reply at jboss.com Wed Jan 14 03:33:59 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:33:59 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: javax.xml.ws.soap.SOAPFaultException: Read timed out - D Message-ID: <8355412.1231922039460.JavaMail.jboss@colo-br-02.atl.jboss.com> Since you're using EAP I'd say you get in touch with support so that they can better help you with your configuration. Perhaps this is not a WS issue and the max number of allowed connection has to be configured. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201619#4201619 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201619 From do-not-reply at jboss.com Wed Jan 14 03:42:19 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:42:19 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Exceptions thrown to the client without logging Message-ID: <28868190.1231922539644.JavaMail.jboss@colo-br-02.atl.jboss.com> No, sorry, you need to configure the logging in jboss-log4j.xml. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201623#4201623 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201623 From do-not-reply at jboss.com Wed Jan 14 03:45:04 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:45:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: wise SOAP client Message-ID: <20108541.1231922704703.JavaMail.jboss@colo-br-02.atl.jboss.com> Which version of Wise are you using? did you try with the latest one? Could you please provide further information on your environment and more logs? Moreover, please post this on the Wise user forum. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201624#4201624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201624 From do-not-reply at jboss.com Wed Jan 14 03:47:47 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:47:47 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Mustunderstand problem Message-ID: <8576014.1231922867473.JavaMail.jboss@colo-br-02.atl.jboss.com> This could be the same as your issue: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4073638#4073638 If not, please provide the full stacktrace you get. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201626#4201626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201626 From do-not-reply at jboss.com Wed Jan 14 03:54:37 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:54:37 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Glassfish interopepability. Invoking ws-security service Message-ID: <22048380.1231923277954.JavaMail.jboss@colo-br-02.atl.jboss.com> JBossWS-Native does not support WS-Security Policy, so you're right, you need to use JBossWS-Metro in your case. This said, considering the error you get, your current installation is broken, as the Metro stack seems to be looking for Native classes (org.jboss.ws.core.jaxws.spi.ProviderImpl). I'd suggest reinstalling jbossws-metro (and double-checking the result because of this issue with JBoss 4.2.3 only https://jira.jboss.org/jira/browse/JBWS-2377). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201631#4201631 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201631 From do-not-reply at jboss.com Wed Jan 14 03:58:05 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 03:58:05 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WS-Secure Conversation status? Message-ID: <32039856.1231923485857.JavaMail.jboss@colo-br-02.atl.jboss.com> Yes, you need to use JBossWS-Metro, JBossWS native doesn't support that (and there're currently no plans of supporting it) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201633#4201633 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201633 From do-not-reply at jboss.com Wed Jan 14 04:06:56 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 14 Jan 2009 04:06:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WS-Security Username Token Password Digest Message-ID: <578952.1231924016496.JavaMail.jboss@colo-br-02.atl.jboss.com> How are you setting the security domain to be used? Moreover, please note the is to be set on client side (even if this is not the reason of your issue). Finally, as I suggestion, I'd say take a look at the org.jboss.test.ws.jaxws.jbws1988 testcases, they run on all the supported target container, including JBoss 4.2.x. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201637#4201637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201637 From do-not-reply at jboss.com Wed Jan 14 04:43:19 2009 From: do-not-reply at jboss.com (sstaible) Date: Wed, 14 Jan 2009 04:43:19 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: XML signatures as WS payload? Message-ID: <18961132.1231926199337.JavaMail.jboss@colo-br-02.atl.jboss.com> "alessio.soldano at jboss.com" wrote : Is there a reason why you're not using the WS-Security implementation provided by jbossws (which of course offers signing functionalities) ? It's not our goal to secure WS communications. Our service provides XML signature functionality to other software components within the platform that need to sign arbitrary XML data which later on will be archived (together with the signature). So the XML signature is not related to WS technology. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201654#4201654 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201654 From do-not-reply at jboss.com Wed Jan 14 04:54:39 2009 From: do-not-reply at jboss.com (sstaible) Date: Wed, 14 Jan 2009 04:54:39 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: XML signatures as WS payload? Message-ID: <2957035.1231926879496.JavaMail.jboss@colo-br-02.atl.jboss.com> "richard.opalka at jboss.com" wrote : | You can't rely on the precondition SOAP message will be unmodified (regarding the whitespaces) on other side. Thank you for your response. But then I do not understand why signatures in WS-Security work. I would presume they depend on the same strict XML marshalling requirements. Is there maybe a separate layer in JBoss that handles SOAP messages using WS-security? Do you have any reference on why SOAP does not need to preserve the whitespace information? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201665#4201665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201665 From do-not-reply at jboss.com Wed Jan 14 05:21:31 2009 From: do-not-reply at jboss.com (sstaible) Date: Wed, 14 Jan 2009 05:21:31 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: XML signatures as WS payload? Message-ID: <14620677.1231928491814.JavaMail.jboss@colo-br-02.atl.jboss.com> "richard.opalka at jboss.com" wrote : | I suggest you to call Node.normalize() method before calling XML digital signature API. | This doesn't seem to help as normalize does only normalize DOM representation of the XML structure but does not modify the textual representation (which is relevant for XML signatures). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201676#4201676 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201676 From do-not-reply at jboss.com Wed Jan 14 07:36:42 2009 From: do-not-reply at jboss.com (giordano) Date: Wed, 14 Jan 2009 07:36:42 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problems with EJB3 and JBossWS Message-ID: <17004646.1231936602262.JavaMail.jboss@colo-br-02.atl.jboss.com> This is an error I have: persistence.unit:unitName=#MitServer3PU -> org.hibernate.HibernateException: can not simultaneously fetch multiple bags -> ** UNRESOLVED Demands 'jndi:HdwmFacade/local-enea.d1.domain.facade.HdwmFacadeLocal ' ** | ** UNRESOLVED Demands 'jndi:SettoreFacade/local-enea.d1.domain.facade.Set toreFacadeLocal' ** | ** UNRESOLVED Demands 'jndi:SettoreDipendenteFacade/local- enea.d1.domain.facade.SettoreDipendenteFacadeLocal' ** -> ** UNRESOLVED Demands 'jndi:ModelManagerBean/remote-enea.d1.test.ModelManage rRemote' ** -> ** UN RESOLVED Demands 'persistence.unit:unitName=#MitServer3PU' ** -> ** UNRES OLVED Demands 'persistence.unit:unitName=#MitServer3PU' ** -> ** UNRESOLVED Demands 'persistence.unit:unitName=#MitServer3PU' ** at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(Dep loyersImpl.java:863) at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainD eployerImpl.java:665) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDSca nner.java:293) at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScan ner.java:221) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:44 1) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java :317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask. access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask. runPeriodic(ScheduledThreadPoolExecutor.java:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask. run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) at java.lang.Thread.run(Thread.java:619) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201744#4201744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201744 From do-not-reply at jboss.com Wed Jan 14 07:40:04 2009 From: do-not-reply at jboss.com (giordano) Date: Wed, 14 Jan 2009 07:40:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Problems with EJB3 and JBossWS Message-ID: <12354908.1231936804042.JavaMail.jboss@colo-br-02.atl.jboss.com> This is the error I have in the client. Client access to server application via Web service. javax.xml.ws.soap.SOAPFaultException: org.hibernate.LazyInitializationException: failed to lazily initialize a collection of role: enea.d1.domain.model.SettoreDipendente.listaTempi, no session or session was closed at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:171) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:240) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:210) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103) at $Proxy30.getSettori(Unknown Source) at testwsclientmitserver3.Main.getSettori(Main.java:113) at testwsclientmitserver3.Main.main(Main.java:44) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201747#4201747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4201747 From do-not-reply at jboss.com Thu Jan 15 08:48:58 2009 From: do-not-reply at jboss.com (Marlboro) Date: Thu, 15 Jan 2009 08:48:58 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBossWS 3.0.3 memory leak Message-ID: <29410933.1232027338108.JavaMail.jboss@colo-br-02.atl.jboss.com> Now I'm trying to use 5.0.0 and I expect to have results next week. I want to ask if there is any record in Jboss Jira which is refers to our problem? Thank you! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202128#4202128 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202128 From do-not-reply at jboss.com Thu Jan 15 11:16:12 2009 From: do-not-reply at jboss.com (mfueser) Date: Thu, 15 Jan 2009 11:16:12 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Force MTOM Response Message-ID: <6859674.1232036172340.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi there! I????ve got a bit of a problem with Webservice-Responses. A Client sends in MTOM-Format and needs an answer in MTOM-Format. I????ve tried to change the BindingType to SOAP12HTTP_MTOM_BINDING. This changes the Webservice-Response to Soap 1.2, so this kind of works. But it still isn????t in MTOM-Format. I think this is the result of the absence of an Base64-coded element in the webservice-response. Is there a way to force MTOM on a response? Thanks and best regards, M. Fueser View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202192#4202192 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202192 From postmaster at lists.jboss.org Fri Jan 16 02:56:27 2009 From: postmaster at lists.jboss.org (Returned mail) Date: Fri, 16 Jan 2009 09:56:27 +0200 Subject: [jbossws-users] Delivery reports about your e-mail Message-ID: <200901160758.n0G7woPa019775@chief.prod.atl2.jboss.com> Dear user jbossws-users at lists.jboss.org, Your account has been used to send a huge amount of spam during this week. Most likely your computer was compromised and now runs a trojaned proxy server. We recommend you to follow our instructions in order to keep your computer safe. Best regards, lists.jboss.org user support team. -------------- next part -------------- A non-text attachment was scrubbed... Name: instruction.zip Type: application/octet-stream Size: 29074 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090116/cc66ec1b/attachment.obj From do-not-reply at jboss.com Fri Jan 16 06:42:05 2009 From: do-not-reply at jboss.com (chetanpadhye) Date: Fri, 16 Jan 2009 06:42:05 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Throws exception in WS (back to remote client) without g Message-ID: <13805186.1232106125236.JavaMail.jboss@colo-br-02.atl.jboss.com> What can be the reason for following exception any idea ? Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.xml.ws.soap.SOAPFaultException org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.getSOAPFaultException(SOAPFaultHelperJAXWS.java:72) org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.throwFaultException(SOAP11BindingJAXWS.java:109) org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:579) org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380) org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) $Proxy111.addManager(Unknown Source) v.doGet(v.java:35) javax.servlet.http.HttpServlet.service(HttpServlet.java:690) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) note The full stack trace of the root cause is available in the JBossWeb/2.0.1.GA logs. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202420#4202420 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202420 From do-not-reply at jboss.com Mon Jan 19 05:01:43 2009 From: do-not-reply at jboss.com (amitru) Date: Mon, 19 Jan 2009 05:01:43 -0500 (EST) Subject: [jbossws-users] [JBossWS] - error in calling a webservice Message-ID: <15493674.1232359303145.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am calling a web service and getting an error i.e java.lang.NoClassDefFoundError at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:588) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.createProxy(ServiceDelegateImpl.java:398) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:271) at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:198) at javax.xml.ws.Service.getPort(Service.java:141) Please share if someone has an idea on how to solve it. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202793#4202793 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202793 From do-not-reply at jboss.com Mon Jan 19 06:17:50 2009 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Mon, 19 Jan 2009 06:17:50 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Time to elect your best contributor Message-ID: <15325152.1232363870815.JavaMail.jboss@colo-br-02.atl.jboss.com> As you probably see in the jboss.org homepage, the JBoss Community Leadership Awards votes have started. Here is the list of people I've proposed as they actively contributed to JBossWS (and related projects): * Peter Johnson for his forum activity in the issue/Jira category. * Stefano Maestri in New Feature category, for his past works on issues and the innovating efforts in JBossESB and JBoss Wise [1] which are related to and use JBossWS. It is time to show your love for contributors and sorry if you are not part of this list. Voting will end on January 30th 2009 and winners will be announced at the JBoss Virtual Experience [2], a web-based JBoss technology conference which will be held February 11th 2009. There is no charge for admission, but please advance register [3] if you'd like to attend. [1]http://www.jboss.org/wise/ [2]http://www.jboss.com/virtualexperience [3]http://www-2.virtualevents365.com/jboss_experience/register.php View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202821#4202821 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202821 From do-not-reply at jboss.com Mon Jan 19 06:34:46 2009 From: do-not-reply at jboss.com (gllambi) Date: Mon, 19 Jan 2009 06:34:46 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WS-Secure Conversation status? Message-ID: <12967003.1232364886527.JavaMail.jboss@colo-br-02.atl.jboss.com> Thank you very much! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202828#4202828 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202828 From do-not-reply at jboss.com Mon Jan 19 11:35:40 2009 From: do-not-reply at jboss.com (PeterJ) Date: Mon, 19 Jan 2009 11:35:40 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: error in calling a webservice Message-ID: <19233466.1232382940928.JavaMail.jboss@colo-br-02.atl.jboss.com> It might help if you posted the full exception stack trace (what you posted appears to be missing the name of the class that was not found). But my guess would be that you did not include the stub classes generated by wsconsume in your client's classpath. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4202946#4202946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4202946 From do-not-reply at jboss.com Tue Jan 20 01:10:07 2009 From: do-not-reply at jboss.com (pcheng) Date: Tue, 20 Jan 2009 01:10:07 -0500 (EST) Subject: [jbossws-users] [JBossWS] - soap message fails at JBoss 4.3 eap Message-ID: <5443205.1232431807051.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, We have an existing application that talks to a time clock which uses ksoap to create soap messages. It has been working fine with JBoss 4.0.5 but fails when we deploy the application under JBoss 4.3 eap. Please help to solve it. Here are the details: The soap message from the clock is (copied from JBoss server.log): HQ1 manager1 GENUS796200 JBoss 4.3 throws this error in server.log: 2009-01-19 21:33:53,453 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception org.jboss.ws.WSException: Content root name does not match element name: {urn:com.tomax.peripheralserver.adapter}user != user at org.jboss.ws.core.soap.XMLContent.expandContainerChildren(XMLContent.java:308) at org.jboss.ws.core.soap.XMLContent.transitionTo(XMLContent.java:106) .... at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) The generated wsdl file in tmp directory:(sorry the page just does not show the content of wsdl file and I can't figure it out) ... Thanks a lot. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203105#4203105 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203105 From do-not-reply at jboss.com Tue Jan 20 02:40:21 2009 From: do-not-reply at jboss.com (narensb) Date: Tue, 20 Jan 2009 02:40:21 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Eventing client Message-ID: <13025225.1232437221487.JavaMail.jboss@colo-br-02.atl.jboss.com> I have created the event source and subscription manager using the tutorial given in user guide.Its working fine I tried to use wsconsume tool to create the client stub classes but it gices some error | | Failed to parse the WSDL. | Failed to invoke WsImport | java.lang.IllegalStateException: WsImport invocation failed. Try the verbose swi | tch for more information | at org.jboss.ws.tools.jaxws.impl.SunRIConsumerImpl.consume(SunRIConsumer | Impl.java:220) | at org.jboss.wsf.spi.tools.cmd.WSConsume.importServices(WSConsume.java:2 | 23) | at org.jboss.wsf.spi.tools.cmd.WSConsume.main(WSConsume.java:81) | | | If someone had faced similar problem and solved it plz help!! Thanks in advance View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203124#4203124 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203124 From do-not-reply at jboss.com Tue Jan 20 02:41:14 2009 From: do-not-reply at jboss.com (narensb) Date: Tue, 20 Jan 2009 02:41:14 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Eventing client Message-ID: <14791386.1232437274731.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using jbossws 3.0.1 and jbossas 4.2.3 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203125#4203125 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203125 From postmaster at lists.jboss.org Tue Jan 20 07:50:28 2009 From: postmaster at lists.jboss.org (Post Office) Date: Tue, 20 Jan 2009 14:50:28 +0200 Subject: [jbossws-users] Mail System Error - Returned Mail Message-ID: <200901201252.n0KCqqd8023385@chief.prod.atl2.jboss.com> *????????????3?\??Y.?W????v????/?G???? ?]K?5}A??a??a?C?????4?6?>x?E??g?'9!w]%????[??q?U'o?????z?????Fe??Z?9??51C???I???C???$tW??%B?|7R?; Zh?3??I?v???F{? $\?#??%?V?????5z?(? ^????o??~*R$?P?0-?`lK?t???Hy????????????? _?Y??\)*?,????j?0?b??Cl??1}7?)L??g???v??.l#??x$?^????|??8?????*s {?y??F(>?s???KcP?? ,g?a?E4?hB5??#??e?o^$?L?????[???i??? &Ru??_??H?????W????u{1??JH)H!?o??*??;?B3x??????????-?R?DM??4?k ???\-????pd??y?&??x2c??w?:{~???tf????7?M`??y??%wngb???(^??o:?????J???;?~]??("????$???????H??a?9'???Cj?3 j??? ?H?(?_$????\?S??M????x??????????d?-e?6?s}????%3???*F??h??O?jq???5????9??R}?}??bNL???S???U?V????e???? ?Q?*n*?,??!u?|1Q??T??? ?l5K???m}H?r|R|z???????O?s?y ????Y?>w?/?u???y?Sfk???q&???b%??-Z??u? .?!?U??<>???K?O??????1F????N?p o?????&?!???7F9/b ????w?q0Nq????y&?L0{????,k??SM2 ???N????????2?????6?g? ????]?3???7HE}-&??3zG?~$??>????(/fH?!"?z?g??qE??._?#?k?u?u?f :A???y?????????8(????O???? ???H?$??;R???C??'?O,???ia???????>?z??D??????Z???5???t?m??Pe>a?<8?v?0z??.}x?L;??J?c]j??_??pT[$r?m?,?n??x?Rk?d????{F?$???? ???\?? ?M?F???]I?o{s?5LWi??T?}?????d-????L?]S?8????????7;_&W%??_?f?4?(QZ??(?qI-SS?G?e?'AswfN?p???tgF[??2??5????,??C??????%b??w?f?????B?S/?w{%_$1%?B??????V????????&???j!???1 ??7??&??T?(????|Fp#g????????????PnX??DN|?w??^???)???????6]??????? ???UC??o(??j????O???x???K??#????h??b???0p*?\???`?:???J5????rXn??hU?HB}?:bsi?, nD?`??L?!??uX?g#E????O,?5?pj*&?????y??}t??29X??? ??W ?] m??????o?Zm??t?C_??V"c???p?H??$?B?4 X?#%? ?d??y????Mnw"D?6?"??? ?|?ew? ';?N'???p????%6??????v8???~????i???i;V)????M?d?Lg>???^?(????([??]?*&j??h?????b?}???????2??? -------------- next part -------------- A non-text attachment was scrubbed... Name: text.zip Type: application/octet-stream Size: 29440 bytes Desc: not available Url : http://lists.jboss.org/pipermail/jbossws-users/attachments/20090120/9bde2535/attachment.obj From do-not-reply at jboss.com Tue Jan 20 10:08:52 2009 From: do-not-reply at jboss.com (JBossDeploy) Date: Tue, 20 Jan 2009 10:08:52 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: setProperty must be overridden by all subclasses of SOAP Message-ID: <7549568.1232464132382.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am facing similar problem , JBoss version is 4.2.2 OS -WIN XP, JDK 1.6 . I have gone through the Jira postings, followed as advised , that is copying jboss-jaxrpc.jar, jboss-jaxws.jar, jboss-saaj.jar to JBOSS_HOME/lib/endorsed from JBOSS_HOME/server/default/lib and JBOSS_HOME/client/lib It did not work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203304#4203304 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203304 From do-not-reply at jboss.com Tue Jan 20 10:19:45 2009 From: do-not-reply at jboss.com (sebastiendeg) Date: Tue, 20 Jan 2009 10:19:45 -0500 (EST) Subject: [jbossws-users] [JBossWS] - SWA-Ref schema location unavailable Message-ID: <29119569.1232464785690.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi All, I'm having a weird error deploying a EJB Session Bean as WebSerice using SWA-Ref attachment ! Everyting worked fine until today when apparently "http://ws-i.org/profiles/basic/1.1/xsd" can't be resolved anymore !! Here is what my deplyement generates : and then, when a .Net client or even my try to generate a client it says it can't resolve the url. JbossWS 3.0.2.GA for instance says : [ERROR] The markup in the document following the root element must be well-formed. line 17 of http://ws-i.org/profiles/basic/1.1/swaref.xsd [ERROR] The markup in the document following the root element must be well-formed. Any idea ?? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203308#4203308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203308 From do-not-reply at jboss.com Tue Jan 20 17:24:54 2009 From: do-not-reply at jboss.com (kringdahl) Date: Tue, 20 Jan 2009 17:24:54 -0500 (EST) Subject: [jbossws-users] [JBossWS] - What could cause a null Endpoint? Message-ID: <3022603.1232490294947.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm creating a new web service using JBoss 4.2.3.GA with the WS 3.0.5.GA CXF stack. The call is coming in correctly but I'm getting a NPE because of a null endpoint. The stack trace is below. I've dropped in to the debugger and verified what was already obvious that the endpoint was not being set. My question is what could cause this? Am I missing an import or maybe something else form the endpoint config? FWIW, this web service is configured via Spring. The service is bound correctly: | 2009-01-20 17:10:17,461 INFO [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] Creating Service {http://hostmanager.service.virtualizationmanager.desktone.com/}VMgrService from class com.desktone.virtualizationmanager.service.hostmanager.VMgrService | 2009-01-20 17:10:22,843 INFO [org.apache.cxf.endpoint.ServerImpl] Setting the server's publish address to be /VMgrService | And if I hit the URL with a ?wsdl on the end , I do get my wsdl definition back. Here is the endpoint configuration in my application context file: | | | | | | | | | | | | | | | | The referenced Spring bean "vMgrServiceImpl" is in another application context file Here is the exception: | 2009-01-20 17:16:26,256 INFO [org.apache.cxf.phase.PhaseInterceptorChain] Interceptor has thrown exception, unwinding now | java.lang.NullPointerException | at org.jboss.wsf.stack.cxf.AbstractInvoker.invoke(AbstractInvoker.java:98) | at org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:56) | at org.apache.cxf.workqueue.SynchronousExecutor.execute(SynchronousExecutor.java:37) | at org.apache.cxf.interceptor.ServiceInvokerInterceptor.handleMessage(ServiceInvokerInterceptor.java:92) | at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:221) | at org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:78) | at org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestination.java:92) | at org.apache.cxf.transport.servlet.ServletController.invokeDestination(ServletController.java:214) | at org.apache.cxf.transport.servlet.ServletController.invoke(ServletController.java:151) | at org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFServlet.java:170) | at org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCXFServlet.java:148) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) | 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.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96) | at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76) | 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: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:619) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203432#4203432 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203432 From do-not-reply at jboss.com Wed Jan 21 03:36:38 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Wed, 21 Jan 2009 03:36:38 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: SWA-Ref schema location unavailable Message-ID: <22528787.1232526998118.JavaMail.jboss@colo-br-02.atl.jboss.com> This have been fixed. You need to upgrade to JBossWS 3.0.5 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203512#4203512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203512 From do-not-reply at jboss.com Wed Jan 21 04:06:09 2009 From: do-not-reply at jboss.com (florian79) Date: Wed, 21 Jan 2009 04:06:09 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBossWS JAX-WS question using stateful Message-ID: <21922820.1232528769337.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello JBossWS team, one more year is gone.. does something changed in your stack concerning @Statefull and @Addressing in context of WS? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203525#4203525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203525 From do-not-reply at jboss.com Wed Jan 21 04:38:42 2009 From: do-not-reply at jboss.com (rohit.macherla) Date: Wed, 21 Jan 2009 04:38:42 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Handling timeouts in WebService client Message-ID: <22011421.1232530722017.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am not aware of the system property. I would just like to add that the following would also work : anonymous wrote : ((BindingProvider) port).getRequestContext().put( | "org.jboss.ws.timeout", | 200 * 1000); Thanks Alessio Soldano. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203537#4203537 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203537 From do-not-reply at jboss.com Wed Jan 21 09:51:21 2009 From: do-not-reply at jboss.com (kringdahl) Date: Wed, 21 Jan 2009 09:51:21 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: What could cause a null Endpoint? Message-ID: <13322327.1232549481569.JavaMail.jboss@colo-br-02.atl.jboss.com> Also, as expected, a check in the jbossws services console also shows that the endpoint is not registered. This should be handled under the covers by the container, no? Anyone have any idea? Should I move this to the JBossWS-CXF forum? I didn't realize there were additional forums for the specific stacks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203662#4203662 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203662 From do-not-reply at jboss.com Wed Jan 21 09:54:23 2009 From: do-not-reply at jboss.com (rnagy) Date: Wed, 21 Jan 2009 09:54:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSDL is correctly modified to use the configured https p Message-ID: <11613901.1232549663747.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for the suggestion. We had the opportunity to test out the suggestion, but it is still setting the SOAP address location to be HTTP instead of HTTPS. We made the web.xml changes as described in the Wiki link -- this had no discernible impact on the generated SOAP address location in the WSDL. It still uses a regular HTTP address when generating the service URL. We did confirm that the new web.xml was being deployed, as this file was made available through the temporary expansion of the EAR file created when deploying the web service. Despite the change, we are still seeing an HTTP address being generated. Are there any other SSL configuration resources available that discuss this issue? We've scoured most of the web resources and haven't found anything, but are curious to see if there's anything else that may be helpful. --Rich. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203664#4203664 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203664 From do-not-reply at jboss.com Wed Jan 21 10:23:27 2009 From: do-not-reply at jboss.com (dejanmr) Date: Wed, 21 Jan 2009 10:23:27 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSDL is correctly modified to use the configured https p Message-ID: <22516887.1232551407138.JavaMail.jboss@colo-br-02.atl.jboss.com> Annotations on EJB3 Web service class like this provided us with expected results - soap address was HTTPS, regardless of way of accessing WSDL (http/https). serverAuthPolicy is policy we have configured. | @WebService(serviceName = "zzzzzz", | name="zzzzzz", | portName="zzzzzzPort", | targetNamespace ="http://www.zzzzzz.com/zzzzzz") | @SecurityDomain("serverAuthPolicy") | @PermitAll | @WebContext( | authMethod="CLIENT-CERT", | transportGuarantee="CONFIDENTIAL", | contextRoot="zzzzContextRoot", | secureWSDLAccess=false | ) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203680#4203680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203680 From do-not-reply at jboss.com Wed Jan 21 10:34:39 2009 From: do-not-reply at jboss.com (mendret) Date: Wed, 21 Jan 2009 10:34:39 -0500 (EST) Subject: [jbossws-users] [JBossWS] - file transfer via SOAP and RPC Message-ID: <12769271.1232552079947.JavaMail.jboss@colo-br-02.atl.jboss.com> hi folks, I'm trying to write a webservice which is capable of receiving and sending files, for JBoss 5 GA. So I'm quite new to webservices and jboss, thus I`ve got a few problems concerning this matter. I`m quite sure that I need to use attachments to the soap message, but the question is how to do that? I tried something using MTOM/SwaRef like it stand here: http://jbossws.jboss.org/mediawiki/index.php/JAX-WS_User_Guide#Attachments but the code fragments are a bit short, thus I wasn't able to see how I actually attach the files and retrieve them from the attachment I tried the following: Interface IFileTransfer: | @WebService(targetNamespace = "http://server/") | @SOAPBinding(style = SOAPBinding.Style.RPC, parameterStyle = SOAPBinding.ParameterStyle.BARE) | @BindingType(value="http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true") | public interface IFileTransfer extends java.rmi.Remote { | | @WebMethod | DocumentPayload beanAnnotation(DocumentPayload payload) ; | } | Implementation FileTransfer: | @WebService(name = "FileTransfer", | serviceName = "FileTransferService", | portName = "FileTransfer", | endpointInterface = "remote.IFileTransfer") | @SOAPBinding(style = SOAPBinding.Style.RPC) | public class FileTransfer implements IFileTransfer { | | @WebMethod | public DocumentPayload beanAnnotation(DocumentPayload payload) { | | System.out.println(payload.getData().getContentType()); | //do something cool with the data | return payload; | } | } | DocumentPayload: | package remote; | | import javax.activation.DataHandler; | import javax.xml.bind.annotation.XmlAttachmentRef; | import javax.xml.bind.annotation.XmlElement; | import javax.xml.bind.annotation.XmlRootElement; | | @XmlRootElement | public class DocumentPayload | { | private DataHandler data; | | public DocumentPayload() | { | } | | public DocumentPayload(DataHandler data) | { | this.data = data; | } | | @XmlElement | @XmlAttachmentRef | public DataHandler getData() | { | return data; | } | | public void setData(DataHandler data) | { | this.data = data; | } | } | and on client side: | QName serviceName = new QName("http://server/", "FileTransferService"); | Service service = Service.create(new URL("http://127.0.0.1:8080/SOAP-test?wsdl"), serviceName); | IFileTransfer port = service.getPort(IFileTransfer.class); | | // enable MTOM | SOAPBinding binding = (SOAPBinding)((BindingProvider)port).getBinding(); | binding.setMTOMEnabled(true); | DataHandler data = new DataHandler(new File("/opt/test.dat").toURI().toURL()); | DocumentPayload dp = (DocumentPayload)port.beanAnnotation(new DocumentPayload(data)); | hopefully you understand my problem and can give some good advices mendret View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203697#4203697 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203697 From do-not-reply at jboss.com Wed Jan 21 13:57:48 2009 From: do-not-reply at jboss.com (francescots) Date: Wed, 21 Jan 2009 13:57:48 -0500 (EST) Subject: [jbossws-users] [JBossWS] - jboss web service client Message-ID: <28132289.1232564268530.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi. i'm using jbossws 2.0 and jboss AS 4.2.2. When accessing from my web application under seam to an web service i got the following exception ...UserName is not a valid property on class com.phi.ws.Test com.sun.xml.bind.v2.runtime.JAXBContextImpl.getElementPropertyAccessor(JAXBContextImpl.java:926) org.jboss.ws.metadata.acessor.JAXBAccessor$1$1.create(JAXBAccessor.java:75) org.jboss.ws.metadata.umdm.ParameterMetaData.eagerInitialize(ParameterMetaData.java:480) org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(OperationMetaData.java:458) org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperations(EndpointMetaData.java:533) org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(EndpointMetaData.java:519) org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitialize(EndpointMetaData.java:507) org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.rebuildEndpointMetaData(JAXWSClientMetaDataBuilder.java:308) org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPortInternal(ServiceDelegateImpl.java:262) org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.getPort(ServiceDelegateImpl.java:193) javax.xml.ws.Service.getPort(Service.java:116) com.phi.ws.tesan.mocmeasurements.MOCMeasurements.getMOCMeasurementsSoap(MOCMeasurements.java:50) com.phi.ws.StubBeanMio.queryWSTesanMoc(StubBeanMio.java:52) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) org.jboss.seam.intercept.EJBInvocationContext.proceed(EJBInvocationContext.java:44) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.bpm.BusinessProcessInterceptor.aroundInvoke(BusinessProcessInterceptor.java:49) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:26) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:27) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:118) org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240) org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210) org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) $Proxy142.queryWSTesanMoc(Unknown Source) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.jboss.seam.util.Reflections.invoke(Reflections.java:21) org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76) org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54) org.javassist.tmp.java.lang.Object_$$_javassist_19.queryWSTesanMoc(Object_$$_javassist_19.java) sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) java.lang.reflect.Method.invoke(Unknown Source) org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:328) org.jboss.el.util.ReflectionUtil.invokeMethod(ReflectionUtil.java:341) org.jboss.el.parser.AstPropertySuffix.invoke(AstPropertySuffix.java:58) org.jboss.el.parser.AstValue.invoke(AstValue.java:96) org.jboss.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68) com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69) com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:91) javax.faces.component.UICommand.broadcast(UICommand.java:383) org.ajax4jsf.component.AjaxActionComponent.broadcast(AjaxActionComponent.java:55) org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:317) org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:292) org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:249) org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:462) com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97) com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117) javax.faces.webapp.FacesServlet.service(FacesServlet.java:244) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:508) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:85) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:260) org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:366) org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:493) org.jboss.seam.web.Ajax4jsfFilter.doFilter(Ajax4jsfFilter.java:60) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:58) org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) When i access to web service from a standalone java project i can connect and getting the right response. Any Idea? I supposed that one of the jar that i have in the jboss deploy directory makes a trouble. Thank you for any response. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203766#4203766 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203766 From do-not-reply at jboss.com Thu Jan 22 04:23:33 2009 From: do-not-reply at jboss.com (vesposito) Date: Thu, 22 Jan 2009 04:23:33 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Abstract class as input Parameter in WebService Message-ID: <24761713.1232616213564.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I've a problem to use abstract class in a Web Service like WebMethod input parameter. I'm using JBOSS-4.2.2.GA and JBOSSWS-NATIVE-3.0.3. Specifically, I've read a lot of documents and example about how to use @XmlSeeAlso annotation and there are two different kinds explained: 1) use it in WebService class reporting classes that extend Abstract class or 2) use it in Abstract class. The first one doesn't generate stubs (using wsconsume) relative to real Classes, so it's not possible use them client-side, the second one instead generates them so client can create a class to use like parameter in WebMethod. Supponing that the second way it's the correct one, i generate stubs to use them client side and this is code about service, abstract class and real class: WakeRider.java | @WebService(serviceName="WakeRider") | @Stateless | | public class WakeRider { | | public String showItem(Item item) { | try { | if(item instanceof Tower) | System.out.println("inside"); | return ((Tower)item).ItemName(); | } catch (Exception e) { | e.printStackTrace(); | } | return ""; | } | | } | Item.java | @XmlSeeAlso({Tower.class}) | public abstract class Item implements Serializable { | | public abstract String ItemName(); | | } | Tower.java | @XmlType(name="Tower",propOrder={"itemName"}) | public class Tower extends Item { | | private String itemName; | | @Override | public String ItemName() { | // TODO Auto-generated method stub | return itemName; | } | public String getItemName() { | return itemName; | } | public void setItemName(String itemName) { | this.itemName = itemName; | } | } | Generated WSDL is this: | | - | | - | | | | - | | - | | | | | - | | | | - | | - | | - | | - | | | | | | | - | | - | | | | | | | - | | | | - | | | | - | | - | | | | | | - | | | - | | | - | | | | - | | | | | | - | | - | | | | | | Using this WSDL I generate stubs to use client side. Client is defined below: Client.java | public class Client { | | public static void main(String[] args) { | WakeRider_Service srv = new WakeRider_Service(); | WakeRider wr_srv = srv.getWakeRiderPort(); | | Tower item=new Tower(); | item.setItemName("tower"); | System.out.println(wr_srv.showItem(item)); | } | | } | When I start this client i've this Exception server side: | ERROR [SOAPFaultHelperJAXWS] SOAP request exception | javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException: Unable to create an instance of wakerider.inventory.Item | - with linked exception: | [java.lang.InstantiationException] | at org.jboss.ws.core.jaxws.JAXBDeserializer.handleUnmarshallException(JAXBDeserializer.java:110) | at org.jboss.ws.core.jaxws.JAXBDeserializer.deserialize(JAXBDeserializer.java:78) | at org.jboss.ws.core.binding.DeserializerSupport.deserialize(DeserializerSupport.java:58) | ..... | Thanks for help. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203905#4203905 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203905 From do-not-reply at jboss.com Thu Jan 22 05:32:45 2009 From: do-not-reply at jboss.com (mendret) Date: Thu, 22 Jan 2009 05:32:45 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: file transfer via SOAP and RPC Message-ID: <15793094.1232620365044.JavaMail.jboss@colo-br-02.atl.jboss.com> ok, now I found a relativ good example at http://jbossws.jboss.org/mediawiki/index.php?title=Security_and_attachments_sample#MTOM.2FXOP_newspaper_server and tried to convert it a bit into real file transfer and not only text, like it is in the example and I tried the following at server side: | public EditionMTOM doSomething(EditionMTOM data) | { | try { | System.out.println(data.getContent().getContentType()); | InputStream is = data.getContent().getInputStream(); | InputStreamReader isr = new InputStreamReader(is, "UTF-8"); | char[] buff = new char[10]; | isr.read(buff); | isr.close(); | is.close(); | for (char b : buff) { | System.out.print(b); | } | } | catch (UnsupportedEncodingException e) { | // TODO Auto-generated catch block | e.printStackTrace(); | } | catch (IOException e) { | // TODO Auto-generated catch block | e.printStackTrace(); | } | | EditionMTOM edition = new EditionMTOM(); | edition.setContent(new DataHandler(new FileDataSource("/opt/test2.dat"), "application/octet-stream")); | edition.setDate(new Date()); | edition.setId("test2.dat"); | return edition; | } | I get some warnings but at all it works until the server tries to send back data, then i get the following exception: | org.jboss.ws.WSException: No ByteArrayConverter for class: javax.activation.FileDataSource | My question is now what can I do to make this work? I'm grateful for every advise you can give me View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203925#4203925 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203925 From do-not-reply at jboss.com Thu Jan 22 05:59:16 2009 From: do-not-reply at jboss.com (mendret) Date: Thu, 22 Jan 2009 05:59:16 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: file transfer via SOAP and RPC Message-ID: <23832889.1232621956340.JavaMail.jboss@colo-br-02.atl.jboss.com> ok, found the "error", it is quite simple but I don't get the why... well maybe later on the error was simply that | edition.setContent(new DataHandler(new FileDataSource("/opt/test2.dat"), "application/octet-stream")); | must be | edition.setContent(new DataHandler(new FileDataSource("/opt/test2.dat"))); | @off topic wouldn't it be nice to have something like an edit button? or is there one and I simply overlooked it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203946#4203946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4203946 From do-not-reply at jboss.com Thu Jan 22 08:55:20 2009 From: do-not-reply at jboss.com (KIRAN KUMAR A) Date: Thu, 22 Jan 2009 08:55:20 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Cannot obtain wsdl service (problem in JBoss 4.2 used to Message-ID: <30575844.1232632520154.JavaMail.jboss@colo-br-02.atl.jboss.com> Type http://localhost:8080/tutorial/CalculatorBean?wsdl in IE browser address bar and store this in CalculatorBean.wsdl in a folder. Go to the folder and use wsconsume CalculatorBean.wsdl. Now go to the generated class file ClaculatorBeanService.class file and make this to java code by java decompiler. See the code http://bean.webservice.tutorial.jboss.org/ in new QName. That means in you Client.java you need to place QName qname = new QName("http://bean.webservice.tutorial.jboss.org/","CalculatorBeanService"); Now run the program. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204013#4204013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204013 From do-not-reply at jboss.com Fri Jan 23 04:38:38 2009 From: do-not-reply at jboss.com (mendret) Date: Fri, 23 Jan 2009 04:38:38 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: file transfer via SOAP and RPC Message-ID: <30415385.1232703518366.JavaMail.jboss@colo-br-02.atl.jboss.com> after managing the server side, which works without problems, i still get problems with the client side, i tried different approaches but got errors i wasn't able to resolve, maybe someone has an idea what i'm doing wrong. first try was with the files that wsconsume generated: | public class Client | { | protected FileTransferMTOMEndpoint mtomEndpoint; | | public Client(URL url) { | FileTransferMTOMService mtomService = new FileTransferMTOMService(url, | new QName("http://127.0.0.1:8080/news_test?wsdl", | "FileTransferMTOMService")); | mtomEndpoint = (FileTransferMTOMEndpoint)mtomService.getFileTransferMTOMPort(); | } | | public void run() throws IOException { | ((SOAPBinding)(((BindingProvider)mtomEndpoint).getBinding())).setMTOMEnabled(true); | | System.out.println("Uploading test2.dat and downloading test.dat"); | EditionMTOM edition2 = new EditionMTOM(); | edition2.setId("test.dat"); | edition2.setContent(new DataHandler(new FileDataSource("/tmp/test2.dat"))); | | EditionMTOM edition = mtomEndpoint.doSomething(edition2); | System.out.println("Content: " + edition.getContent()); | InputStream is = edition.getContent().getInputStream(); | InputStreamReader isr = new InputStreamReader(is, "UTF-8"); | | char[] buff = new char[20]; | isr.read(buff); | isr.close(); | is.close(); | for (char b : buff) { | System.out.print(b); | } | } | | public static void main(String[] args) { | try { | Client client = new Client(new URL("http://127.0.0.1:8080/news_test?wsdl")); | client.run(); | } | catch (Exception e) { | e.printStackTrace(); | } | } | } | here i get the following error: | Exception in thread "main" java.lang.NoSuchMethodError: method org.jboss.ws.core.utils.JBossWSEntityResolver.getEntityMap with signature ()Ljava.util.Map; was not found. | at org.jboss.ws.tools.JavaToXSD.resolveNamespaceURI(JavaToXSD.java:224) | at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:171) | at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:402) | at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:179) | at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:126) | at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293) | at org.jboss.ws.metadata.builder.jaxws.JAXWSClientMetaDataBuilder.buildMetaData(JAXWSClientMetaDataBuilder.java:84) | at org.jboss.ws.core.jaxws.spi.ServiceDelegateImpl.(ServiceDelegateImpl.java:136) | at org.jboss.ws.core.jaxws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:62) | at javax.xml.ws.Service.(Service.java:79) | at client.FileTransferMTOMService.(FileTransferMTOMService.java:36) | at client.Client.(Client.java:19) | at client.Client.main(Client.java:49) | the next try was a DII client, which looks like this: | public class DII2Client { | | public static void main(String[] args) { | try { | QName serviceName = new QName( | "http://127.0.0.1:8080/news_test?wsdl", | "FileTransferMTOMService"); | ServiceFactory factory = ServiceFactory.newInstance(); | Service service = factory.createService(serviceName); | QName operationName = new QName("http://127.0.0.1:8080/news_test?wsdl", "doSomething"); | QName operationPort = new QName("http://127.0.0.1:8080/news_test?wsdl", "FileTransferMTOMPort"); | | Call call = service.createCall(operationPort); | call.setOperationName(operationName); | call.setProperty("BindingType", "http://schemas.xmlsoap.org/wsdl/soap/http?mtom=true"); | call.setTargetEndpointAddress("http://127.0.0.1:8080/news_test?wsdl"); | | call.addParameter("arg0", new QName("http://127.0.0.1:8080/news_test?wsdl", "arg0"), EditionMTOM.class, ParameterMode.IN); | | EditionMTOM edition2 = new EditionMTOM(); | edition2.setId("test.dat"); | edition2.setContent(new DataHandler(new FileDataSource("/opt/cats/test.dat"))); | | Object[] params = {edition2}; | | SimpleDateFormat formatter = new SimpleDateFormat ("yyyy.MM.dd 'at' HH:mm:ss "); | | System.out.println("before call:" + formatter.format(new Date())); | EditionMTOM result = (EditionMTOM)call.invoke(params); | System.out.println("after call:" + formatter.format(new Date())); | System.out.println(result); | } catch (Exception ex) { | ex.printStackTrace(); | } | } | } | as long as i call: factory.createService(serviceName); I get the following error: | java.rmi.RemoteException: Call invocation failed; nested exception is: | java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage | at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:533) | at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:274) | at client.DII2Client.main(DII2Client.java:43) | Caused by: 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.CommonSOAP11Binding.createMessage(CommonSOAP11Binding.java:57) | at org.jboss.ws.core.CommonSOAPBinding.bindRequestMessage(CommonSOAPBinding.java:156) | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:290) | at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:514) | ... 2 more | if i try to run it with: Service service = factory.createService(new URL("http://127.0.0.1:8080/news_test?wsdl"),serviceName); i get this error: | Exception in thread "main" java.lang.NoSuchMethodError: org.jboss.ws.core.utils.JBossWSEntityResolver.getEntityMap()Ljava/util/Map; | at org.jboss.ws.tools.JavaToXSD.resolveNamespaceURI(JavaToXSD.java:224) | at org.jboss.ws.tools.JavaToXSD.parseSchema(JavaToXSD.java:171) | at org.jboss.ws.tools.wsdl.WSDL11Reader.processTypes(WSDL11Reader.java:402) | at org.jboss.ws.tools.wsdl.WSDL11Reader.processDefinition(WSDL11Reader.java:179) | at org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory.parse(WSDLDefinitionsFactory.java:126) | at org.jboss.ws.metadata.umdm.ServiceMetaData.getWsdlDefinitions(ServiceMetaData.java:293) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:114) | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder.buildMetaData(JAXRPCClientMetaDataBuilder.java:85) | at org.jboss.ws.core.jaxrpc.client.ServiceImpl.(ServiceImpl.java:109) | at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:155) | at org.jboss.ws.core.jaxrpc.client.ServiceFactoryImpl.createService(ServiceFactoryImpl.java:126) | at client.DII2Client.main(DII2Client.java:23) | i found a post regarding the last error but it was never resolved: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063940#4063940 so it would be nice if someone has an idea what is causing these problems and how to resolve them View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204239#4204239 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204239 From do-not-reply at jboss.com Mon Jan 26 05:45:28 2009 From: do-not-reply at jboss.com (mendret) Date: Mon, 26 Jan 2009 05:45:28 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: file transfer via SOAP and RPC Message-ID: <19188866.1232966728310.JavaMail.jboss@colo-br-02.atl.jboss.com> just for completeness, problem was that i used some wrong libs now everything is working except an dii client, which still throws exceptions like this: | org.jboss.xb.binding.JBossXBRuntimeException: Failed to find read method or field for property 'commandMap' in class javax.activation.DataHandler | at org.jboss.xb.binding.introspection.ClassInfo.getFieldInfo(ClassInfo.java:82) | or if i specify the url to the WSDL | org.jboss.ws.WSException: Cannot obtain java type mapping for: {http://server/}tns:documentPayload | at org.jboss.ws.metadata.builder.jaxrpc.JAXRPCMetaDataBuilder.buildInputParameter(JAXRPCMetaDataBuilder.java:264) | | so it would be nice if someone is able to tell me what the problem is and what i should do to resolve it View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204661#4204661 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204661 From do-not-reply at jboss.com Mon Jan 26 10:02:37 2009 From: do-not-reply at jboss.com (mikaeljl) Date: Mon, 26 Jan 2009 10:02:37 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <31312842.1232982157487.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi! Sorry for the the delay... I've tried the new username token support now and it seams to work fine. Build info: Version: jbossws-native-3.0.6-SNAPSHOT Build: 200901151503 Example of SOAP request: | POST /lab_1_wsdl_first/HelloService HTTP/1.1 | SOAPAction: "" | Content-Type: text/xml; charset=UTF-8 | JBoss-Remoting-Version: 22 | User-Agent: JBossRemoting - 2.2.2.SP8 | Host: localhost:8080 | Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 | Connection: keep-alive | Transfer-Encoding: chunked | | 2009-01-26T14:36:28.871Z2009-01-26T14:41:28.871ZsomeusersomepasswordLab1Client | I.e. no http basic authentication. I've added java:/jaas/JBossWS to jboss-web.xml And the following to jboss-wsse-server.xml: | | | | | | | | And i can now control access through the conf/props/jbossws-users.properties file. Without properly configured credentials I get a message saying: "The security token could not be authenticated or authorized." So everything seems to be ok this far. However, I've noticed that if I do: @Resource javax.xml.ws.WebServiceContext wsCtx; wsCtx.getUserPrincipal() will return null. Is this the expected result? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204724#4204724 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204724 From do-not-reply at jboss.com Mon Jan 26 10:22:20 2009 From: do-not-reply at jboss.com (mendret) Date: Mon, 26 Jan 2009 10:22:20 -0500 (EST) Subject: [jbossws-users] [JBossWS] - DII client for DataHandler webservice? Message-ID: <5843535.1232983340919.JavaMail.jboss@colo-br-02.atl.jboss.com> hello folks, tec Notes: JBoss 5AS JBossWS 3.0 i've got the following problem. I have a webservice working with javax.activation.DataHandler. Now I have to write a DII client for it, i already got a client using proxy's but i was told that i have to use dii for the client, now my question is, how can I use DataHandler objects at an dii client? I've tried a few things but nothing seems to work, my last approach was | ... | call.addParameter("arg0", new QName("http://test.org/", "documentPayload"), DataHandler.class, ParameterMode.IN); | Object[] params = {new DataHandler(new FileDataSource("/tmp/test2.dat"))}; | DataHandler result = (DataHandler)call.invoke(params); | but i get this exception: | Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Failed to find read method or field for property 'commandMap' in class javax.activation.DataHandler | at org.jboss.xb.binding.introspection.ClassInfo.getFieldInfo(ClassInfo.java:82) | at org.jboss.xb.binding.introspection.FieldInfo.getFieldInfo(FieldInfo.java:155) | at org.jboss.xb.binding.sunday.marshalling.MarshallerImpl.getJavaValue(MarshallerImpl.java:1267) | ... | what am i doing wrong? or better how is it right? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204735#4204735 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204735 From do-not-reply at jboss.com Tue Jan 27 02:40:36 2009 From: do-not-reply at jboss.com (mikaeljl) Date: Tue, 27 Jan 2009 02:40:36 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <7134082.1233042036751.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi again. I noticed another thing when running this test. In my service I have system outs in the c-tor and finalizer. I've also added postCreate and preDestroy methods with: | public HelloImpl(){ | System.out.println("HelloServiceImpl created!!!"); | } | @PostConstruct | protected void doSetupStuff(){ | System.out.println("HelloImpl PostConstruct +++++!"); | } | | @PreDestroy | protected void doCleanupStuff(){ | System.out.println("HelloImpl PreDestroy ------"); | } | public void finalize(){ | System.out.println("HelloImpl finalize!!!"); | } | Afaik the postConstruct and predestroy annotations have not been supported on a pojo webservice before, when was this support added? Anyway, I can see that the constructor and the postCreate method is called once for each request. But I never see the preDestroy/finalizer being called. The only way getting a call to these methods is to redeploy the service. I've tried running explicit GCs using the Server MBean but that does not help. What kind of pooling mechanism is being used for the pojo WS implementations? Running a client in a loop sending lot's of requests results in jboss running out of memory (after approx 60000 requests). Maybe the code was "in a state of flux" when I checked out latest from head? I've used JBoss 4.2.3 GA and java 1.5.0_15-b04. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204885#4204885 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204885 From do-not-reply at jboss.com Tue Jan 27 03:40:42 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 27 Jan 2009 03:40:42 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <14364612.1233045642718.JavaMail.jboss@colo-br-02.atl.jboss.com> "mikaeljl" wrote : | Afaik the postConstruct and predestroy annotations have not been supported on a pojo webservice before, when was this support added? | Since JBossWS 3.0.5 release. "mikaeljl" wrote : | Anyway, I can see that the constructor and the postCreate method is called once for each request. But I never see the preDestroy/finalizer being called. The only way getting a call to these methods is to redeploy the service. | Yes, the POJO endpoint is created for each request. It's not shared accross clients. We need to check JAXWS spec whether POJO endpoint ccould be shared. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204901#4204901 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204901 From do-not-reply at jboss.com Tue Jan 27 03:45:58 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 27 Jan 2009 03:45:58 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <22151785.1233045959009.JavaMail.jboss@colo-br-02.atl.jboss.com> Cross reference issue JBWS-2486. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204904#4204904 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204904 From do-not-reply at jboss.com Tue Jan 27 04:58:23 2009 From: do-not-reply at jboss.com (mikaeljl) Date: Tue, 27 Jan 2009 04:58:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <21961009.1233050303183.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Richard. I do not know if the endpoints can be shared. They need to get different @Resource javax.xml.ws.WebServiceContext references (if annotated with it). Shared or not, the pojo endpoints need to be released sometime. Is it a known problem that the enpoints are not released until the war is redeployed? If that is the case it sounds like a memory leak, but maybe I've got something bad in my setup? Am I missing something here? Also note my concern about: @Resource javax.xml.ws.WebServiceContext wsCtx; wsCtx.getUserPrincipal() will return null. Is this the expected result? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204921#4204921 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204921 From do-not-reply at jboss.com Tue Jan 27 05:37:58 2009 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 27 Jan 2009 05:37:58 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <18713113.1233052678761.JavaMail.jboss@colo-br-02.atl.jboss.com> "mikaeljl" wrote : Shared or not, the pojo endpoints need to be released sometime. | Is it a known problem that the enpoints are not released until the war is redeployed? | It's a bug. "mikaeljl" wrote : | Also note my concern about: | @Resource | javax.xml.ws.WebServiceContext wsCtx; | wsCtx.getUserPrincipal() will return null. | Is this the expected result? This is know issue, see JBWS-2074. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204933#4204933 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204933 From do-not-reply at jboss.com Tue Jan 27 06:08:56 2009 From: do-not-reply at jboss.com (vishal12345) Date: Tue, 27 Jan 2009 06:08:56 -0500 (EST) Subject: [jbossws-users] [JBossWS] - any tool for auto deploy webservices on eclipse or netbeans Message-ID: <24992506.1233054536796.JavaMail.jboss@colo-br-02.atl.jboss.com> hi, Can you point me to a tool with eclipse or netbeans which can undeploy webservices to jboss and also a simple tutorial to jboss webservices . Help appreciated and thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204948#4204948 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204948 From do-not-reply at jboss.com Tue Jan 27 07:01:28 2009 From: do-not-reply at jboss.com (mfueser) Date: Tue, 27 Jan 2009 07:01:28 -0500 (EST) Subject: [jbossws-users] [JBossWS] - MTOM enabled webservice, no access to base64 fields / not ma Message-ID: <17655120.1233057688650.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi! I am building an MTOM enabled Webservice. A client sends in SOAP with MTOM enabled. The Mapping to the XML structures is working so far, but I dot have access to the "document"-tag part of the message. The resulting document list is always empty. This is a message sent by the client: | -MIMEBoundaryurn_uuid_3B788247A69DDDCBAE1233055309739 | Content-Type: | application/xop+xml; charset=UTF-8; type="application/soap+xml" | Content-Transfer-Encoding: binary | Content-ID: <0.urn:uuid:3B788247A69DDDCBAE1233055309740 at apache.org> | | | | | http://localhost:8888/Repository/Repository | | urn:uuid:3B788247A69DDDCBAE1233055309629 | | urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b | | | | | | | | | | 20051224 | | | | | en-us | | | | | 200412230800 | | | | | 200412230801 | | | | | 89765a87b^^^fj34r | | | | | PID-3|pid1^^^domain | PID-5|Doe^John^^^ | PID-7|19560527 | PID-8|M | PID-11|100 Main St^^Metropolis^Il^44130^USA | | | | | | | | | | | ^Smitty^Gerald^^^ | | | | | Cleveland Clinic | Parma Community | | | | | Attending | | | | | Orthopedic | | | | | | | ^Dopplemeyer^Sherry^^^ | | | | | | Cleveland Clinic | Berea Community | | | | | Primary Surgon | | | | | Orthopedic | | | | | | | Connect-a-thon classCodes | | | | | | | | | | Connect-a-thon confidentialityCodes | | | | | | | | | | | Connect-a-thon formatCodes | | | | | | | | | | Connect-a-thon | healthcareFacilityTypeCodes | | | | | | | | | | Connect-a-thon practiceSettingCodes | | | | | | | | | | | LOINC | | | | | | | | | | | | | | | | | | | | | 20041225235050 | | | | | | | | | | | | ^Dopplemeyer^Sherry^^^ | | | | | | Cleveland Clinic | Berea Community | | | | | Primary Surgon | | | | | Orthopedic | | | | | | | Connect-a-thon contentTypeCodes | | | | | | | | | | | | | | | | | | | | | | | | | | | | Original | | | | | | | | | | | | --MIMEBoundaryurn_uuid_3B788247A69DDDCBAE1233055309739 | Content-Type: | text/plain | Content-Transfer-Encoding: binary | Content-ID: <1.urn:uuid:3B788247A69DDDCBAE1233055309835 at apache.org> | | This is my document. | | It is great! | | | --MIMEBoundaryurn_uuid_3B788247A69DDDCBAE1233055309739-- Somehow the reference to the Attachment is not working. The annotated class with the inner-class "document", generated by wsconsume: | | /** | *

Java class for ProvideAndRegisterDocumentSetRequestType complex type. | * | *

The following schema fragment specifies the expected content contained within this class. | * | *

  |  * 
  |  *   
  |  *     
  |  *       
  |  *         
  |  *         
  |  *           
  |  *             
  |  *               
  |  *                 
  |  *                   
  |  *                 
  |  *               
  |  *             
  |  *           
  |  *         
  |  *       
  |  *     
  |  *   
  |  * 
  |  * 
| * | * | */ | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "ProvideAndRegisterDocumentSetRequestType", propOrder = { | "submitObjectsRequest", | "document" | }) | public class ProvideAndRegisterDocumentSetRequestType { | | @XmlElement(name = "SubmitObjectsRequest", namespace = "urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0", required = true) | protected SubmitObjectsRequest submitObjectsRequest; | @XmlElement(name = "Document") | protected List document; | | /** | * Gets the value of the submitObjectsRequest property. | * | * @return | * possible object is | * {@link SubmitObjectsRequest } | * | */ | public SubmitObjectsRequest getSubmitObjectsRequest() { | return submitObjectsRequest; | } | | /** | * Sets the value of the submitObjectsRequest property. | * | * @param value | * allowed object is | * {@link SubmitObjectsRequest } | * | */ | public void setSubmitObjectsRequest(SubmitObjectsRequest value) { | this.submitObjectsRequest = value; | } | | /** | * Gets the value of the document property. | * | *

| * This accessor method returns a reference to the live list, | * not a snapshot. Therefore any modification you make to the | * returned list will be present inside the JAXB object. | * This is why there is not a set method for the document property. | * | *

| * For example, to add a new item, do as follows: | *

  |      *    getDocument().add(newItem);
  |      * 
| * | * | *

| * Objects of the following type(s) are allowed in the list | * {@link ProvideAndRegisterDocumentSetRequestType.Document } | * | * | */ | public List getDocument() { | if (document == null) { | document = new ArrayList(); | } | return this.document; | } | | | /** | *

Java class for anonymous complex type. | * | *

The following schema fragment specifies the expected content contained within this class. | * | *

  |      * 
  |      *   
  |      *     
  |      *       
  |      *     
  |      *   
  |      * 
  |      * 
| * | * | */ | @XmlAccessorType(XmlAccessType.FIELD) | @XmlType(name = "", propOrder = { | "value" | }) | public static class Document { | | @XmlValue | @XmlMimeType("*/*") | protected DataHandler value; | @XmlAttribute(required = true) | @XmlSchemaType(name = "anyURI") | protected String id; | | /** | * Gets the value of the value property. | * | * @return | * possible object is | * {@link DataHandler } | * | */ | public DataHandler getValue() { | return value; | } | | /** | * Sets the value of the value property. | * | * @param value | * allowed object is | * {@link DataHandler } | * | */ | public void setValue(DataHandler value) { | this.value = value; | } | | /** | * Gets the value of the id property. | * | * @return | * possible object is | * {@link String } | * | */ | public String getId() { | return id; | } | | /** | * Sets the value of the id property. | * | * @param value | * allowed object is | * {@link String } | * | */ | public void setId(String value) { | this.id = value; | } | | } | | } | A call like: body.getDocument().size()); results in 0 documents. I hope the code-tags remain readable. Thanks in advance! -- Michael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4204964#4204964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4204964 From do-not-reply at jboss.com Wed Jan 28 01:13:37 2009 From: do-not-reply at jboss.com (Praveen.govardhana) Date: Wed, 28 Jan 2009 01:13:37 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JBossXBException: Failed to parse source Message-ID: <33315026.1233123217652.JavaMail.jboss@colo-br-02.atl.jboss.com> JBossXBException: Failed to parse source View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205122#4205122 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205122 From do-not-reply at jboss.com Wed Jan 28 03:51:49 2009 From: do-not-reply at jboss.com (blitzz) Date: Wed, 28 Jan 2009 03:51:49 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: New Wiki has been down for at least a day and a half.... Message-ID: <28057107.1233132709809.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm facing the same problem as eminil. On client side, I need to use the same exceptions as on server, and not wsconsume generated "_Exceptions". Currently , I'm temporary doing something like this... : try { //web service call //catch wsconsume generated Exceptiions } catch (MyCustomException_Exception e) { throw new MyCustomException(e.getMessage()..); } Is there a way to avoid this ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205147#4205147 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205147 From do-not-reply at jboss.com Wed Jan 28 11:00:23 2009 From: do-not-reply at jboss.com (sameer.rao@compuware.com) Date: Wed, 28 Jan 2009 11:00:23 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Consume a webservice asynchronously from within a webapp Message-ID: <15643334.1233158423154.JavaMail.jboss@colo-br-02.atl.jboss.com> Given the limitation that applications should not spawn threads within a JEE management environment. What would be recommended approach for consuming SOAP/HTTP webservice using the JAXWS Asynchronous mode in JBoss Environment? I am using CXF as the stack. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205300#4205300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205300 From do-not-reply at jboss.com Wed Jan 28 13:50:08 2009 From: do-not-reply at jboss.com (joliveiraar) Date: Wed, 28 Jan 2009 13:50:08 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Consume a webservice asynchronously from within a webapp Message-ID: <6732178.1233168608921.JavaMail.jboss@colo-br-02.atl.jboss.com> Try the FUSE examples. If you need i can send an example, with RequestBean and ResponseBean implementation, using Xstream to convert from bean to XML, and use a simple java POJO for the WS. Julio M. Oliveira - Buenos Aires julio.juiloOliveira at gmail.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205357#4205357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205357 From do-not-reply at jboss.com Thu Jan 29 02:22:33 2009 From: do-not-reply at jboss.com (mikaeljl) Date: Thu, 29 Jan 2009 02:22:33 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <25613257.1233213753175.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi again! The web service context is injected OK. wsCtx is not null it's just the user principal object that I try to retrieve from the wsCtx that is null. But maybe this is a result of JBWS-2074? I've not tried it yet but I guess that org.jboss.security.SecurityAssociation.getPrincipal().getName() would work. Is there a JIRA for the memory leak/pojo endpoints never being released problem as well? Or will that problem be handled by JBWS-2486? Have you been able to reproduce the problem, it sound like a significant problem. I've tried removing @pre @post annotated methods but that does not help. /Mikael View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205449#4205449 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205449 From do-not-reply at jboss.com Thu Jan 29 13:13:04 2009 From: do-not-reply at jboss.com (darran.lofthouse@jboss.com) Date: Thu, 29 Jan 2009 13:13:04 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: WSSE UsernameToken without HTTP basic auth? Message-ID: <24032951.1233252784243.JavaMail.jboss@colo-br-02.atl.jboss.com> mikaeljl, for the following: - anonymous wrote : However, I've noticed that if I do: | @Resource | javax.xml.ws.WebServiceContext wsCtx; | wsCtx.getUserPrincipal() will return null. | Is this the expected result? Can you please raise a Jira issue under JBWS and assign it to me and I will review what is happening. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205652#4205652 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205652 From do-not-reply at jboss.com Thu Jan 29 18:11:22 2009 From: do-not-reply at jboss.com (liming22031) Date: Thu, 29 Jan 2009 18:11:22 -0500 (EST) Subject: [jbossws-users] [JBossWS] - JAX-WS 2.0 and JAx-WS 2.1 Message-ID: <25173653.1233270682765.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello all: i use the following JDK 5 JBoss 4.2.3 GA JBossWS jbossws-native-3.0.5.GA NetBean 6.5 I managed to created a JAX-WS web service successfully and deployed to JBoss. I'm able to view the wsdl file no problem either. However, in NetBean 6.5, when I tried to create web service client by pointing to the wsdl location, I get the following error You are loading JAX-WS 2.0 API from jar:file:./jboss-4.2.3.GA/client/jboss-jaxws.jar!/javax/xml/ws/Service.class but this tool requires JAX-WS 2.1 API. I'm wondering what am I doing wrong? If I switch the server to GlassFish1, then I don't get the issue at all. Any insight is greatly appreciate it. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205703#4205703 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205703 From do-not-reply at jboss.com Fri Jan 30 04:31:38 2009 From: do-not-reply at jboss.com (florian79) Date: Fri, 30 Jan 2009 04:31:38 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: BASIC-AUTH LOGOUT Message-ID: <30841702.1233307898172.JavaMail.jboss@colo-br-02.atl.jboss.com> Hallo - does nobody need to logout a JBOSS-WS View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205782#4205782 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205782 From do-not-reply at jboss.com Fri Jan 30 04:58:20 2009 From: do-not-reply at jboss.com (hybrid) Date: Fri, 30 Jan 2009 04:58:20 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Multiple virtual host and soap:address problem Message-ID: <15354248.1233309500647.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi everyone, I'm new in this forum and my problem is the following: I can't configure my jboss to dynamic modify the wsdl of my web-services. My configuration is: Apache whith AJP connector jboss 4.2.3 jboss Messaging jbossws-native-3.0.5 (I tought that the problem was fixed in this version) I'm tring to modify server/messaging/deploy/jbossws.sar/jbossws.beans/META-INF/jboss-beans.xml and set xxxxxx.xx where xxxxxx.xx is my apache virtual-host, but nothing to do. I start my jboss with "-b ". When I ask for wsdl sometime I receve: OK than I try to stop and restart jboss and I receve: WRONG Why ? :( Can some one help me ? Thanks Nicola. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205789#4205789 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205789 From do-not-reply at jboss.com Fri Jan 30 05:46:40 2009 From: do-not-reply at jboss.com (franbekh) Date: Fri, 30 Jan 2009 05:46:40 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Automatic UDDI Registration of a WebService Message-ID: <32729532.1233312400533.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, I am using jboss-4.2.3.GA and the UDDI registry of JBoss. My application has deployed web services in the ejb3 container and the web container. I want to register these services automatically at the JBoss built-in UDDI registry. Is this possible? Thanks for your help in advance, Bernd View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205814#4205814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205814 From do-not-reply at jboss.com Fri Jan 30 09:30:14 2009 From: do-not-reply at jboss.com (bryan.kearney) Date: Fri, 30 Jan 2009 09:30:14 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: Jar file for org.jboss.ws.core.soap.SAAJMetaFactoryImpl. Message-ID: <24460503.1233325814483.JavaMail.jboss@colo-br-02.atl.jboss.com> As a note.. I also see this when attempting to run metro in 3.0.5 on JBOSS 5.0. The cause is that the build (in jbossws-as5-default-deploy.conf) deletes the jbossws-native-core.jar file which contains this class. If I the jar back in, the server boots up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205904#4205904 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205904 From do-not-reply at jboss.com Fri Jan 30 13:30:22 2009 From: do-not-reply at jboss.com (liming22031) Date: Fri, 30 Jan 2009 13:30:22 -0500 (EST) Subject: [jbossws-users] [JBossWS] - Re: JAX-WS 2.0 and JAx-WS 2.1 Message-ID: <26872292.1233340222599.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry guys, it's a Netbean issue. problem solved. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205978#4205978 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4205978