From do-not-reply at jboss.com Mon Sep 1 03:55:44 2008 From: do-not-reply at jboss.com (jimpo) Date: Mon, 1 Sep 2008 03:55:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Getting handle of the original XML message in JAX-WS Message-ID: <32978301.1220255744269.JavaMail.jboss@colo-br-02.atl.jboss.com> Also, binding to a String is not a necessity. I could bind to a Document or an Element as well. As long as I can extract the xml easily, ie. not binding into a group of java objects. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173517#4173517 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173517 From do-not-reply at jboss.com Mon Sep 1 09:19:11 2008 From: do-not-reply at jboss.com (PatrickMadden) Date: Mon, 1 Sep 2008 09:19:11 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Cannot find service endpoint target Message-ID: <31549526.1220275151477.JavaMail.jboss@colo-br-02.atl.jboss.com> I know this is asking a lot but it would be amazing if the the error that stated that it couldn't find the service endpoint target also put a warning in the log that said "make sure your persistence.xml jta-data-source element matches your ${foo}-ds.xml's jndi-name element". Otherwise it is very difficult to track down. Thanks, PVM View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173612#4173612 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173612 From do-not-reply at jboss.com Mon Sep 1 12:34:24 2008 From: do-not-reply at jboss.com (dtagjmh) Date: Mon, 1 Sep 2008 12:34:24 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBOSS Portal 2.6.4. Error on Startup Message-ID: <4437504.1220286864065.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I'm getting an [org.jboss.ws.metadata.wsdl.xmlschema.JBossXSErrorHandler] on startup which looks like this: It was detected that '<....>' is in namespace '<....>', but components from this namespace are not referenceable from schema document 'file:<....>.xsd'. If this is the incorrect namespace, perhaps the prefix of '<....>' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:<....>.xsd'. Real names are replaced. My question is, can I configure JBoss to keep the generated XSDs so that I can examine them. Regards View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173630#4173630 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173630 From do-not-reply at jboss.com Mon Sep 1 14:21:53 2008 From: do-not-reply at jboss.com (SagarD) Date: Mon, 1 Sep 2008 14:21:53 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Exception Deploying JAX-WS on JBoss4.2.2GA with JDK1.5 Message-ID: <29364244.1220293313776.JavaMail.jboss@colo-br-02.atl.jboss.com> java.lang.ClassCastException: com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.toSOAPMessage(SOAPFaultHelperJAXWS.java:245) at org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS.exceptionToFaultMessage(SOAPFaultHelperJAXWS.java:174) at org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS.createFaultMessageFromException(SOAP11BindingJAXWS.java:104) at org.jboss.ws.core.CommonSOAPBinding.bindFaultMessage(CommonSOAPBinding.java:671) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:440) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:274) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:191) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:124) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173637#4173637 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173637 From do-not-reply at jboss.com Tue Sep 2 17:20:34 2008 From: do-not-reply at jboss.com (ashwinbijani) Date: Tue, 2 Sep 2008 17:20:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Strange java.lang.ClassCastException: org.jboss.axis.Mes Message-ID: <13100603.1220390434320.JavaMail.jboss@colo-br-02.atl.jboss.com> Did you get the solution to this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173806#4173806 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173806 From do-not-reply at jboss.com Tue Sep 2 17:22:59 2008 From: do-not-reply at jboss.com (mmeola) Date: Tue, 2 Sep 2008 17:22:59 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Trying to use jboss.xml instead of @WebContext Message-ID: <24900682.1220390579428.JavaMail.jboss@colo-br-02.atl.jboss.com> Have you been able to get this working at all? I, too, cannot get JBoss to recognize the webservices/context-root element of jboss.xml. Since we won't do container-specific code, it means that EJB-based web services are a no go. I've tested this on JBoss AS 4.2.2.GA, 4.2.3.GA and 5.0.0.CR1; all no joy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173808#4173808 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173808 From do-not-reply at jboss.com Wed Sep 3 04:26:44 2008 From: do-not-reply at jboss.com (karypid) Date: Wed, 3 Sep 2008 04:26:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Trying to use jboss.xml instead of @WebContext Message-ID: <13136750.1220430404320.JavaMail.jboss@colo-br-02.atl.jboss.com> Sorry, still no joy. Since there is a valid interest in this, I suggest we open a feature request in JIRA. I have located http://jira.jboss.org/jira/browse/JBWS-1309 which seems relevant, but was closed as "outdated". If you need this as well, please watch that issue and comment to support having it re-opened. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173872#4173872 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173872 From do-not-reply at jboss.com Wed Sep 3 05:56:12 2008 From: do-not-reply at jboss.com (ljgp) Date: Wed, 3 Sep 2008 05:56:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation annotation in 3.0.1 ? Message-ID: <25319927.1220435772068.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Ana, It worked now, thanks again ! I had to flatten my WSDL (copy the XSD that I imported into the file itself) and rename the class that implemented the endpoint to make jbossws understand it, but now I end up in the errorhandler on schema validation errors. A remaining problem, that for now makes the feature not so useful: if I throw an exception in my handler, nothing happens. As in: the client gets back nothing (nope, nada, zero bytes) instead of a SOAP fault I was expecting. Cheers, Luc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173896#4173896 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173896 From do-not-reply at jboss.com Wed Sep 3 06:10:02 2008 From: do-not-reply at jboss.com (ljgp) Date: Wed, 3 Sep 2008 06:10:02 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - schemavalidation: fault not returned to calling client Message-ID: <18946438.1220436602660.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I am using JBoss 4.2.2 and I was expecting that a schemavalidation error would by default be passed on to the client as a SOAP fault. I am observing that the exceptions show up in the app server logs, but that the client does not get any response (except for the header). I tried both without a custom error handler, and with my own handler, throwing an exception from handleError(). Both gave the same result: no output sent to the client. I must be missing something here, any help is appreciated. Cheers, Luc. The header is: HTTP/1.1 200 OK Date: Wed, 03 Sep 2008 10:03:33 GMT Content-Length: 0 Content-Type: text/xml;charset=UTF-8 X-Powered-By: Servlet 2.4; JBoss-4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)/Tomcat-5.5 Server: Apache-Coyote/1.1 In the logs it says: 12:03:33,416 INFO [SOAPBodyElementDoc] Validating: XML_VALID 12:03:33,447 ERROR [StrictlyValidErrorHandler] org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'Service'. One of '{Schema}' is expected. 12:03:33,462 ERROR [RequestHandlerImpl] Error processing web service request org.jboss.ws.WSException: org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'Service'. One of '{Schema}' is expected. at org.jboss.ws.WSException.rethrow(WSException.java:68) at org.jboss.ws.core.soap.SOAPBodyElementDoc.validatePayload(SOAPBodyElementDoc.java:130) at org.jboss.ws.core.soap.SOAPBodyElementDoc.transitionTo(SOAPBodyElementDoc.java:90) at org.jboss.ws.core.soap.SOAPContentElement.writeElement(SOAPContentElement.java:547) at org.jboss.ws.core.soap.SOAPElementImpl.writeElementContent(SOAPElementImpl.java:840) at org.jboss.ws.core.soap.SOAPElementImpl.writeElement(SOAPElementImpl.java:825) at org.jboss.ws.core.soap.SOAPElementImpl.writeElementContent(SOAPElementImpl.java:840) at org.jboss.ws.core.soap.SOAPElementImpl.writeElement(SOAPElementImpl.java:825) at org.jboss.ws.core.soap.SOAPElementWriter.writeElementInternal(SOAPElementWriter.java:149) at org.jboss.ws.core.soap.SOAPElementWriter.writeElement(SOAPElementWriter.java:130) at org.jboss.ws.core.soap.SOAPMessageImpl.writeTo(SOAPMessageImpl.java:326) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.sendResponse(RequestHandlerImpl.java:392) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:321) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173905#4173905 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4173905 From do-not-reply at jboss.com Wed Sep 3 11:59:29 2008 From: do-not-reply at jboss.com (dtagjmh) Date: Wed, 3 Sep 2008 11:59:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Configuring JBossWS behaviour when deploying EAR file Message-ID: <10109006.1220457569882.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, when I deploy my EAR file to JBOSS, it processes the JAX-WS annotated classes and produces WSDL files. So far so good. However JBOSS also produces temporary XSD files (via JavaToXSD) and then proceeds to validate them (via JBossWSEntityResolver). In my case it throws an error here because it cannot handle an embedded complex type. That however is another issue. What I would like to know is, can I configure JBoss to stop producing and validation XSD files? Alternatively, if I supplied the WSDL files myself, would JBoss not try to produce them. I am using JBOSS-WS 2.0 and JBoss Portal 2.6.4 I have spent the last two days on this problem and would greatly appreciate any pointers here. I cannot find any useful documentation on the EAR deployment process. Regards jmh View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174012#4174012 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174012 From do-not-reply at jboss.com Wed Sep 3 14:44:36 2008 From: do-not-reply at jboss.com (anaholzbach) Date: Wed, 3 Sep 2008 14:44:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation annotation in 3.0.1 ? Message-ID: <22750879.1220467476350.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Luc, Were you able to deploy the demo application ? The demo application clearly returns a SOAP Fault to the client. I'm not sure what the issue is. Did you try calling the web service with Oxygen XML, for example ? Thanks, Ana View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174071#4174071 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174071 From do-not-reply at jboss.com Wed Sep 3 15:36:07 2008 From: do-not-reply at jboss.com (lall2) Date: Wed, 3 Sep 2008 15:36:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Error SAP WS-Security client calling JBoss Security WS Message-ID: <32369766.1220470567743.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi enpasos, thanks for your reply. I did a further test. Taking the request from the SAP system, see a) of my first post, I manually added ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3' to the element of | ... | | | | | | ... | | -----> | | ... | | | | | | ... | Using my sniffer tool, I resubmitted this modified request to JBoss and the WSSecurityException("Inavliad message, Reference element is missing a ValueType") of org.jboss.ws.extensions.security.element.DirectReference was gone. But unfortunately, I faced the next exeption: WSSecurityException("Invalid message, BinarySecurityToken is missing an id") of org.jboss.ws.extensions.security.element.X509Token So I modified and resent the same request again by adding xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='sap-18' to the line | ... | | ... | | -----> | | ... | | ... | Again, after resubmitting the modified request to JBoss, the exception did not occur any more. However, using this resubmitting method resulted in an expired message error/exception. I am running out of ideas. The only two things that remain is trying out the latest releases of JBoss and JBossWS native 3.0.3 or rebuilding JBossWS 3.0.x from the source after commenting out the "Reference element is missing a ValueType" check of org.jboss.ws.extensions.security.element.DirectReference and the "Invalid message, BinarySecurityToken is missing an id" check of org.jboss.ws.extensions.security.element.X509Token to see what is happening then. Unfortunately, I have no time to do that at the moment :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174088#4174088 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174088 From do-not-reply at jboss.com Thu Sep 4 06:53:00 2008 From: do-not-reply at jboss.com (ljgp) Date: Thu, 4 Sep 2008 06:53:00 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation annotation in 3.0.1 ? Message-ID: <19888065.1220525580125.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Ana, I did not deploy the demo app, as far as I can remember, just tried to mimick as much as I could your approach. I tried calling my app with SoapUI, which shows HTTP headers are returned but nothing else. The Sax exceptions simply end up in the app server log. I am suspecting the problem might have something to do with the webservice being generated top-down from the WSDL, but this is just a guess. I hope to have some time soon to do some more experiments: deploying your demo app and also trying to run the JBoss testcase. Cheers, Luc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174253#4174253 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174253 From do-not-reply at jboss.com Thu Sep 4 10:29:36 2008 From: do-not-reply at jboss.com (huberth) Date: Thu, 4 Sep 2008 10:29:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Cannot find service endpoint target Message-ID: <30504129.1220538576263.JavaMail.jboss@colo-br-02.atl.jboss.com> I get this error as well with AS4.2.1 and WS2.0.3, as well as with AS4.2.3. I get it on 3 out of 8 web services. All 8 are simple JSR-181 web services and SLSBs - the 3 that fail have @Depends annotations, that being the only commonality I can find. One of the 3 failing ones doesn't even have injected resources. JBWS-1822 has been closed-won't-fix but I'm not sure how the cross-module ordering workaround in there applies to this case... especially as the service it can't find is the SLSB itself. It seems to be timing related (race condition?) as, if I remove the @Depends annotations on those 3, 2 of them start up. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174312#4174312 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174312 From do-not-reply at jboss.com Thu Sep 4 10:37:51 2008 From: do-not-reply at jboss.com (Vitor Isaia) Date: Thu, 4 Sep 2008 10:37:51 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Problems accessing SSL webservice Message-ID: <11896387.1220539071320.JavaMail.jboss@colo-br-02.atl.jboss.com> Greetings, I have a working jax-ws webservice deployed, wich I access it through a java standalone client. Now I need to enable SSL on it. I've configured jboss-web.deployer/server.xml to create the SSL connection, and now I have my webservice successfully deployed in the following URL: https://localhost:8443/abc/deteccaopcws?wsdl with: ... | | | | | | ... and in the webservice class: ... | @WebService(targetNamespace = "xyz.abc.deteccaoPC") | @WebContext(contextRoot = "/abc", urlPattern = "/deteccaopcws", transportGuarantee="CONFIDENTIAL") | @Stateless | @HandlerChain(file = "deteccaopc-handler.xml") | public class DeteccaoPCWS | ... The problem is, since I've turned on SSL, my client doesn't work anymore... I always get a "Target endpoint no set" exception: Exception in thread "main" javax.xml.ws.WebServiceException: org.jboss.ws.WSException: Target endpoint address not set | at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:410) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:316) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) | at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) | at $Proxy16.processarDeteccao(Unknown Source) | at deteccaopc.abc.xyz.client.SingleClient.main(SingleClient.java:70) | Caused by: org.jboss.ws.WSException: Target endpoint address not set | at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:334) | at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:304) | ... 4 more Here is my client service: @WebServiceClient(name = "DeteccaoPCWSService", | targetNamespace = "xyz.abc.deteccaoPC", wsdlLocation = "https://localhost:8443/abc/deteccaopcws?wsdl") | public class DeteccaoPCWSService | extends Service | { | | private final static URL DETECCAOPCWSSERVICE_WSDL_LOCATION; | private final static Logger logger = Logger.getLogger(deteccaopc.abc.xyz.DeteccaoPCWSService.class.getName()); | | static { | URL url = null; | try { | URL baseUrl; | baseUrl = deteccaopc.abc.xyz.DeteccaoPCWSService.class.getResource("."); | url = new URL(baseUrl, "https://localhost:8443/abc/deteccaopcws?wsdl"); | } catch (MalformedURLException e) { | logger.warning("Failed to create URL for the wsdl Location: 'https://localhost:8443/abc/deteccaopcws?wsdl', retrying as a local file"); | logger.warning(e.getMessage()); | } | DETECCAOPCWSSERVICE_WSDL_LOCATION = url; | } | public DeteccaoPCWSService(URL wsdlLocation, QName serviceName) { | super(wsdlLocation, serviceName); | } | public DeteccaoPCWSService() { | super(DETECCAOPCWSSERVICE_WSDL_LOCATION, new QName("xyz.abc.deteccaoPC", "DeteccaoPCWSService")); | } | @WebEndpoint(name = "DeteccaoPCWSPort") | public DeteccaoPCWS getDeteccaoPCWSPort() { | return super.getPort(new QName("xyz.abc.deteccaoPC", "DeteccaoPCWSPort"), DeteccaoPCWS.class); | } | } And in the client, I'm setting theseVM properties : -Djavax.net.ssl.trustStore=/home/vitor/Desktop/wsse.truststore | -Djavax.net.ssl.trustStorePassword=jbossws So, the hole code I've show you was working without SSL, in the URL http://localhost:9090/abc/deteccaopcws?wsdl Even having that exception (Target endpoint no set) I know the webservice is deployed because I can successfully access it in my browser... One thing I suspect is: Since the certificate is a self-signed certficate, when I acess it in the browser it alerts me about it, asking for the confirmation. I guess that's what is causing the error. I appreciate any help, thanks. Vitor Isaia View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174316#4174316 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174316 From do-not-reply at jboss.com Thu Sep 4 10:53:11 2008 From: do-not-reply at jboss.com (Vitor Isaia) Date: Thu, 4 Sep 2008 10:53:11 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problems accessing SSL webservice Message-ID: <7699675.1220539991483.JavaMail.jboss@colo-br-02.atl.jboss.com> "Vitor Isaia" wrote : | So, the hole code I've show you was working without SSL, in the URL http://localhost:9090/abc/deteccaopcws?wsdl | I mean the whole code... In the client, I just instantiate the client service (DeteccaoPCWSService) and call It's method. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174328#4174328 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174328 From do-not-reply at jboss.com Thu Sep 4 20:53:54 2008 From: do-not-reply at jboss.com (jstewart66061) Date: Thu, 4 Sep 2008 20:53:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Consuming a secure web service as standalone app using jboss Message-ID: <30793731.1220576034778.JavaMail.jboss@colo-br-02.atl.jboss.com> I need to consume a third=party web service (that is over SSL and requires WS-Security username/password authentication) from both a standalone app (running outside of an app server environment) and from within a web app (a WAR in JBoss 4.2.1+). Is this possible using JBossWS? I have a completely working WS client built using CXF, but can't get anything to work inside JBoss. I'm willing to get rid of CXF if I can get JBossWS native working both inside and outside of the container. I've already done a nice wsconsume and got the required artifacts. I just can't figure out how to setup the WS-Sec stuff, the SSL stuff, or the WAR's classpath to allow this all to work. If I can get all of that working, I can hopefully figure out the standalone stuff using just a ton of the JBossWS JARs in a really huge classpath. Any help is greatly appreciated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174445#4174445 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174445 From do-not-reply at jboss.com Fri Sep 5 03:30:54 2008 From: do-not-reply at jboss.com (ljgp) Date: Fri, 5 Sep 2008 03:30:54 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - No sources for post 3.0.1 releases ? Message-ID: <5928350.1220599854245.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, In the download area I cannot find any source for the 3.0.2 and 3.0.3 releases. Are they available elsewhere ? Regards, Luc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174485#4174485 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174485 From do-not-reply at jboss.com Fri Sep 5 03:31:06 2008 From: do-not-reply at jboss.com (skajotde) Date: Fri, 5 Sep 2008 03:31:06 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with Deploy and undeploy JBossWS-native-3.0.3.GA Message-ID: <22003986.1220599866660.JavaMail.jboss@colo-br-02.atl.jboss.com> It is not important for JBossWS distribution ? Should I report Jira bug ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174486#4174486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174486 From do-not-reply at jboss.com Fri Sep 5 03:32:29 2008 From: do-not-reply at jboss.com (skajotde) Date: Fri, 5 Sep 2008 03:32:29 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Missing jbossws.integration.target in ant.properties in Message-ID: <29491346.1220599949449.JavaMail.jboss@colo-br-02.atl.jboss.com> I know it is not much important but I dont want to lost this issue (nobody reply from developer ;>) Should I report Jira bug ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174487#4174487 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174487 From do-not-reply at jboss.com Fri Sep 5 03:35:19 2008 From: do-not-reply at jboss.com (skajotde) Date: Fri, 5 Sep 2008 03:35:19 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No sources for post 3.0.1 releases ? Message-ID: <24282605.1220600119605.JavaMail.jboss@colo-br-02.atl.jboss.com> Look at http://repository.jboss.com/maven2/org/jboss/ws/native/jbossws-native-core/3.0.3.GA/ View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174490#4174490 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174490 From do-not-reply at jboss.com Fri Sep 5 05:43:52 2008 From: do-not-reply at jboss.com (ljgp) Date: Fri, 5 Sep 2008 05:43:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: schemavalidation: fault not returned to calling client Message-ID: <20084567.1220607832966.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I think I understand now what is happening. When a schema validation occurs on an input message, the client that sent the incorrect message _does_ get the Soap fault. When the service itself constructs an XML reply that does not meet the schema requirements, the SaxException only ends up in the log and the client is left in the dark. Is this working as designed ? Cheers, Luc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174527#4174527 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174527 From do-not-reply at jboss.com Fri Sep 5 05:46:21 2008 From: do-not-reply at jboss.com (ljgp) Date: Fri, 5 Sep 2008 05:46:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No tests for @SchemaValidation annotation in 3.0.1 ? Message-ID: <20229568.1220607981069.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Ana, I got your sample to deploy and it works as expected (i.e. exceptions returned to client). Comparing with my project, I think I know now what is the problem. See http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141744 for further discussion / questions. Cheers, Luc. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174529#4174529 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174529 From do-not-reply at jboss.com Fri Sep 5 06:48:07 2008 From: do-not-reply at jboss.com (powerOn) Date: Fri, 5 Sep 2008 06:48:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: error when using wsgen to generet wsdl Message-ID: <3116455.1220611687694.JavaMail.jboss@colo-br-02.atl.jboss.com> I have got the same issue. Have anybody found a solution? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174543#4174543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174543 From do-not-reply at jboss.com Mon Sep 8 02:50:43 2008 From: do-not-reply at jboss.com (skajotde) Date: Mon, 8 Sep 2008 02:50:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Missing jbossws.integration.target in ant.properties in Message-ID: <10217122.1220856643924.JavaMail.jboss@colo-br-02.atl.jboss.com> I reported Jira. https://jira.jboss.org/jira/browse/JBWS-2290 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174888#4174888 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174888 From do-not-reply at jboss.com Mon Sep 8 02:54:18 2008 From: do-not-reply at jboss.com (skajotde) Date: Mon, 8 Sep 2008 02:54:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with Deploy and undeploy JBossWS-native-3.0.3.GA Message-ID: <19677961.1220856858491.JavaMail.jboss@colo-br-02.atl.jboss.com> I reported Jira https://jira.jboss.org/jira/browse/JBWS-2291 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174890#4174890 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174890 From do-not-reply at jboss.com Mon Sep 8 04:06:20 2008 From: do-not-reply at jboss.com (jkla) Date: Mon, 8 Sep 2008 04:06:20 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - webservice jaxb and custom accessor Message-ID: <13702752.1220861180699.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, in our company we use Hibernate/JPA + JbossWS to host create web services (beans annotated with @WebService). Now we get a lot of lazy loading exceptions when the Hibernate entity is serialized, because the persistence context is not any longer available when this takes place. Someone had the same problems and found a solution : http://forums.java.net/jive/message.jspa?messageID=174549 https://jaxb.dev.java.net/issues/show_bug.cgi?id=280 Only I have problems to apply this, because I do not find the correct places to configure JAXB in JBossWS. So two things have to be done 1. set the JAXB marshaller property, only how? marshaller.setProperty("com.sun.xml.bind.XmlAccessorFactory", true); 2. Set a JAXB property like below, but how can I pass JAXB properties in JbossWS? properties.put(JAXBRIContext.XMLACCESSORFACTORY_SUPPORT, true); | context = JAXBContext.newInstance(new Class[] { ....}, properties); | Would be great if someone could help Jan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174907#4174907 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174907 From do-not-reply at jboss.com Mon Sep 8 05:35:30 2008 From: do-not-reply at jboss.com (thorstenschmid) Date: Mon, 8 Sep 2008 05:35:30 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Jar file for org.jboss.ws.core.soap.SAAJMetaFactoryImpl.clas Message-ID: <6016371.1220866531015.JavaMail.jboss@colo-br-02.atl.jboss.com> The class org.jboss.ws.core.soap.SAAJMetaFactoryImpl.class is declared in the file META-INF/services/javax.xml.soap.MetaFactory in jboss-saaj.jar. Unfortunately I cannot find any jar file where org.jboss.ws.core.soap.SAAJMetaFactoryImpl.class is included. Does anyone know which jar file or maven artifact includes this class? Without it I get the following exception when starting a web application using JAX-WS on JBoss 4.3: Caused by: java.lang.IllegalStateException: Failed to load javax.xml.soap.MetaFactory: org.jboss.ws.core.soap.SAAJMetaFactoryImpl | at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:131) | at javax.xml.soap.SAAJMetaFactory.getInstance(SAAJMetaFactory.java:60) | at javax.xml.soap.MessageFactory.newInstance(MessageFactory.java:106) | at com.sun.xml.ws.api.SOAPVersion.(SOAPVersion.java:178) | at com.sun.xml.ws.api.SOAPVersion.(SOAPVersion.java:83) | ... 140 more | Caused by: java.lang.ClassNotFoundException: org.jboss.ws.core.soap.SAAJMetaFactoryImpl | at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358) | at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204) | at javax.xml.soap.SAAJFactoryLoader.loadFactory(SAAJFactoryLoader.java:125) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4174938#4174938 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4174938 From do-not-reply at jboss.com Mon Sep 8 10:23:19 2008 From: do-not-reply at jboss.com (Vitor Isaia) Date: Mon, 8 Sep 2008 10:23:19 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problems accessing SSL webservice Message-ID: <2549621.1220883799926.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello folks! I didn't find a solution for this yet. Any tip? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175059#4175059 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175059 From do-not-reply at jboss.com Mon Sep 8 17:02:12 2008 From: do-not-reply at jboss.com (bob.lynch) Date: Mon, 8 Sep 2008 17:02:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - problems with mtom and soap version 1.2 Message-ID: <18336765.1220907732316.JavaMail.jboss@colo-br-02.atl.jboss.com> I've created a simple pojo ws and it works fine as long as the client sends requests using a SOAP 1.1 envelope, but if I use SOAP 1.2 I get this error back in a soap fault: S:VersionMissmatch Couldn't create SOAP message. Expecting Envelope in namespace http://schemas.xmlsoap.org/soap/envelope/, but got http://www.w3.org/2003/05/soap-envelope Does mtom work with soap version 1.2? Thanks, Bob View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175170#4175170 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175170 From do-not-reply at jboss.com Mon Sep 8 17:09:14 2008 From: do-not-reply at jboss.com (longbeach) Date: Mon, 8 Sep 2008 17:09:14 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - java.lang.NullPointerException with EJB 3 stateless web ser Message-ID: <22342487.1220908154584.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I get an error while deploying a Stateless session bean defined as a web service on JBoss 5 CR1. It seems to be a problem of version of JRE since it works with JRE 5 but does not work with JRE 6. I am using Eclipse 3.4 My interface looks like this : @WebService @SOAPBinding(style = Style.RPC) public interface Test extends Remote { ... } My bean looks like this : @Stateless @WebService(endpointInterface ="Test") @Remote(Test.class) public class TestBean { ... } It deploys with jre 1.5 but it fails miserably using jre 1.6. Here is the stack trace (the web services are developped inside the VenteEnLigneEJB project, with Eclipse 3.4): | 2:18:19,835 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/D:/EJB3/jboss-5.0.0.CR1/server/default/deploy/VenteEnLigne.ear state=PreReal mode=Manual requiredState=Real | org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/D:/DeveloppementEJB3/jboss-5.0.0.CR1/server/default/deploy/VenteEnLigne.ear/VenteEnLigneEJB.jar | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:180) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:257) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:135) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409) | at org.jboss.Main.boot(Main.java:209) | at org.jboss.Main$1.run(Main.java:544) | at java.lang.Thread.run(Unknown Source) | Caused by: java.lang.NullPointerException | at org.jboss.wsf.common.KernelAwareSPIFactory.getKernelProvidedSPI(KernelAwareSPIFactory.java:40) | at org.jboss.wsf.framework.DefaultWSFRuntimeLocator.locateRuntime(DefaultWSFRuntimeLocator.java:36) | at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHook.getWsfRuntime(AbstractDeployerHook.java:59) | at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:86) | at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:43) | at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:62) | at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:95) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174) | ... 18 more | 22:18:19,899 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core | 22:18:19,899 INFO [NativeServerConfig] 3.0.2.GA | And the version of java that i use : | 22:17:15,871 INFO [CopyMechanism] VFS temp dir: D:\EJB3\jboss-5.0.0.CR1\server\default\tmp | 22:17:15,885 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled. | 22:17:16,787 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc. | 22:17:16,787 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 10.0-b23,Sun Microsystems Inc. | 22:17:16,787 INFO [ServerInfo] OS-System: Windows Vista 6.0,x86 | If i comment out the annotations @Webservice on the class AND the interface, it deploys correctly, no error. Does anyone know what is wrong here ? Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175171#4175171 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175171 From do-not-reply at jboss.com Tue Sep 9 04:50:56 2008 From: do-not-reply at jboss.com (jaikiran) Date: Tue, 9 Sep 2008 04:50:56 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.NullPointerException with EJB 3 stateless web Message-ID: <8996189.1220950256721.JavaMail.jboss@colo-br-02.atl.jboss.com> "longbeach" wrote : | It deploys with jre 1.5 but it fails miserably using jre 1.6. I don't know how you got this working on jre 1.5. I tried out a simple example in my application: package org.myapp.webservice; | | import javax.jws.WebService; | import javax.jws.soap.SOAPBinding; | import javax.jws.soap.SOAPBinding.Style; | | @WebService | @SOAPBinding(style = Style.RPC) | public interface AppService { | | void sayHello(String user); | | } | | package org.myapp.webservice; | | import javax.jws.WebService; | | @WebService (endpointInterface="org.myapp.webservice.AppService") | public class AppServiceImpl implements AppService { | | public void sayHello(String user) { | System.out.println("Hello " + user); | | } | | | } | Packaged this in a EAR file and placed it in deploy folder of JBoss-5 CR1 with JDK 1.5 13:54:30,148 INFO [ServerInfo] Java version: 1.5.0_10,Sun Microsystems Inc. | 13:54:30,257 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_10-b03,Sun Microsystems Inc. | 13:54:30,257 INFO [ServerInfo] OS-System: Windows 2003 5.2,x86 | Started JBoss. But the startup failed with the same exception as what you see: | 13:55:52,195 ERROR [AbstractKernelController] Error installing to Real: name=vfsfile:/D:/jboss-5.0.0.CR1/server/jaikiran/deploy/ZEJB3Persistence.ear/ state=PreReal mode=Manual requiredState=Real | org.jboss.deployers.spi.DeploymentException: Error during deploy: vfsfile:/D:/jboss-5.0.0.CR1/server/jaikiran/deploy/ZEJB3Persistence.ear/myapp_ejb3.jar/ | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:180) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:970) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1023) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:911) | at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) | at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1392) | at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:784) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:912) | at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:834) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:672) | at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:455) | at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:594) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:257) | at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:135) | at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:409) | at org.jboss.Main.boot(Main.java:209) | at org.jboss.Main$1.run(Main.java:544) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.NullPointerException | at org.jboss.wsf.common.KernelAwareSPIFactory.getKernelProvidedSPI(KernelAwareSPIFactory.java:40) | at org.jboss.wsf.framework.DefaultWSFRuntimeLocator.locateRuntime(DefaultWSFRuntimeLocator.java:36) | at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHook.getWsfRuntime(AbstractDeployerHook.java:59) | at org.jboss.wsf.container.jboss50.deployer.ArchiveDeployerHook.deploy(ArchiveDeployerHook.java:86) | at org.jboss.wsf.container.jboss50.deployer.AbstractDeployerHookEJB.deploy(AbstractDeployerHookEJB.java:43) | at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:62) | at org.jboss.wsf.container.jboss50.deployer.WebServiceDeployerEJB.internalDeploy(WebServiceDeployerEJB.java:95) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:174) | ... 18 more | 13:55:52,305 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core | 13:55:52,305 INFO [NativeServerConfig] 3.0.2.GA | Going by the logs, this looks like deployment ordering issue in CR1. As a workaround, i stopped JBoss. Removed the EAR from the deploy folder of JBoss. Then started JBoss (without the EAR file). Once the server had started successfully, i copied the EAR containing this webservice to the deploy folder. The hot deployer picked up the deployment and successfully deployed the applicaiton. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175234#4175234 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175234 From do-not-reply at jboss.com Tue Sep 9 05:03:55 2008 From: do-not-reply at jboss.com (jaikiran) Date: Tue, 9 Sep 2008 05:03:55 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.NullPointerException with EJB 3 stateless web Message-ID: <8063022.1220951035731.JavaMail.jboss@colo-br-02.atl.jboss.com> "jaikiran" wrote : | As a workaround, i stopped JBoss. Removed the EAR from the deploy folder of JBoss. Then started JBoss (without the EAR file). Once the server had started successfully, i copied the EAR containing this webservice to the deploy folder. The hot deployer picked up the deployment and successfully deployed the applicaiton. Another workaround is to create a folder named "deploy.last" in %JBOSS_HOME%/server/default/deploy and place your application in that folder and start JBoss. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175238#4175238 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175238 From do-not-reply at jboss.com Tue Sep 9 05:50:32 2008 From: do-not-reply at jboss.com (jaikiran) Date: Tue, 9 Sep 2008 05:50:32 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.NullPointerException with EJB 3 stateless web Message-ID: <9710285.1220953832508.JavaMail.jboss@colo-br-02.atl.jboss.com> Just found this JIRA https://jira.jboss.org/jira/browse/JBWS-2246 which talks about a SAR deployment failure. Seems applicable to EAR deployment too. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175249#4175249 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175249 From do-not-reply at jboss.com Tue Sep 9 11:23:37 2008 From: do-not-reply at jboss.com (KickMeToAndy) Date: Tue, 9 Sep 2008 11:23:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - wssecurity client threadsafety question Message-ID: <14047469.1220973817044.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, we are using ws security (UsernameTokenProfile) with our JBoss server. The Client is a multithreaded web application. For each web service call we have to add the logged in users credentials to the webservice so we can pass the authentication at the server. The client code looks like : | TestWebservice_Service service = new TestWebservice_Service(); | TestWebservice port = service.getPort(TestWebservice.class); | | ((StubExt) port).setConfigName("Standard WSSecurity Client"); | ((StubExt) port).setSecurityConfig("jboss-wsse-client.xml"); | | ((BindingProvider) port).getRequestContext().put(StubExt.PROPERTY_AUTH_TYPE, StubExt.PROPERTY_AUTH_TYPE_WSSE); | ((BindingProvider) port).getRequestContext().put(BindingProvider.USERNAME_PROPERTY, "user"); | ((BindingProvider) port).getRequestContext().put(BindingProvider.PASSWORD_PROPERTY, | "pwd"); | I was wondering i a have to create a new port for each client call or if it is possible to share one for all the thread, because the creation of the port is quite expensive (and we are using spring to create the client service class). the only difference between the calls is the different content in the RequestContext map, due to the differen users. As far as i can tell the RequestContext is not ThreadSafe thus i have to create a new Port for each call. can anybody confirm this ? thanks in advance, cheers, andy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175343#4175343 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175343 From do-not-reply at jboss.com Tue Sep 9 16:03:24 2008 From: do-not-reply at jboss.com (longbeach) Date: Tue, 9 Sep 2008 16:03:24 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: java.lang.NullPointerException with EJB 3 stateless web Message-ID: <21865194.1220990604459.JavaMail.jboss@colo-br-02.atl.jboss.com> hi, i tried what you did, using JRE 1.6 I removed the ear, started JBoss 5, then i copied the ear file and the deployment works. Thanks. That seems to help. I have not tested it yet though. Hope there is no problem. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175398#4175398 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175398 From do-not-reply at jboss.com Wed Sep 10 05:23:49 2008 From: do-not-reply at jboss.com (iloveyou0222) Date: Wed, 10 Sep 2008 05:23:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - hlep me: Authorization EJB3 webservice client Message-ID: <8690077.1221038629771.JavaMail.jboss@colo-br-02.atl.jboss.com> How to join the authorized client information | @Stateless | @WebService | @RolesAllowed({"AdminUser"}) | public class SupportInterfaceBean implements SupportInterfaceBeanRemote { | | @EJB(beanName = "ChatContentFacade") ChatContentFacadeLocal chatContentFacadeLocal;//?? ??????Bean???????????????,????????????????????? | @EJB(beanName = "ChatFacade") ChatFacadeLocal chatFacadeLocal; | | @WebMethod(operationName="sendMessage") | public Boolean sendMessage(@WebParam(name="chatId") Integer chatId, at WebParam(name="content") String content, at WebParam(name="sndObject") String sndObject) { | LogUtil.log("?????????????? ?????????", Level.INFO, null); | ChatContent chatContent = new ChatContent(); | chatContent.setChat(chatFacadeLocal.findById(chatId)); | chatContent.setContent(content); | chatContent.setIsRead(false); | chatContent.setSndObject(Short.parseShort(sndObject)); | return chatContentFacadeLocal.save(chatContent); | } | | @WebMethod(operationName="accessMessage") | public List accessMessage(@WebParam(name="chatId") Integer chatId, at WebParam(name="sndObject") String sndObject) { | LogUtil.log("????????????????????????????? ???", Level.INFO, null); | String sqlString = "select * from ChatContent model where model.isRead=0 and model.ChatID=" + chatId + " and model.sndObject='" + sndObject + "'"; | List list = chatContentFacadeLocal.query(sqlString, null, null); | List results = new ArrayList(); | for(ChatContent chatContent : list){ | WsChatContent wsObj = new WsChatContent(); | wsObj.setChatContentId(chatContent.getChatContentId()); | wsObj.setContent(chatContent.getContent()); | wsObj.setIsRead(chatContent.getIsRead()); | wsObj.setSndObject(chatContent.getSndObject().toString()); | results.add(wsObj); | chatContent.setIsRead(true); | chatContentFacadeLocal.update(chatContent); | } | return results; | } | | } | | // TODO Auto-generated method stub | SupportInterfaceBean proxy = new SupportInterfaceBeanService().getSupportInterfaceBeanPort(); | BindingProvider bindProvider = (BindingProvider) proxy; | Map reqCtx = bindProvider.getRequestContext(); | | //reqCtx.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "/SupportInterfaceBeanService/SupportInterfaceBean"); | reqCtx.put(BindingProvider.USERNAME_PROPERTY, "lihuoming"); | reqCtx.put(BindingProvider.PASSWORD_PROPERTY, "123456"); | reqCtx.put(BindingProvider.SESSION_MAINTAIN_PROPERTY, true); | System.out.println(proxy.accessMessage(1, "1")); | | xception in thread "main" javax.xml.ws.soap.SOAPFaultException: Authorization failure | at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:188) | at com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:108) | at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:119) | at com.sun.xml.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:89) | at com.sun.xml.ws.client.sei.SEIStub.invoke(SEIStub.java:118) | at $Proxy34.accessMessage(Unknown Source) | at com.ewke.ejb.ws.Test.main(Test.java:25) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175519#4175519 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175519 From do-not-reply at jboss.com Wed Sep 10 11:48:35 2008 From: do-not-reply at jboss.com (TonyR) Date: Wed, 10 Sep 2008 11:48:35 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: jbossws first steps Message-ID: <17209077.1221061717921.JavaMail.jboss@colo-br-02.atl.jboss.com> Finally found this! (took awhile to get the right keywords in search) I'm using jboss-4.2.3.GA and when I start my server I found these lines: 0:19:57,234 INFO [NativeServerConfig] JBoss Web Services - Native | 10:19:57,234 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044) However when I check the http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers, the matrix implies that only jbossws-native-3.0.3 is compatible with the application server 4.2.3. So does that mean, I should download the 3.0.3 stack and install it? Or should I just take the 'easy way' out and just use the 4.2.2 version of the server. Another question I had is how can I run the http://jbws.dyndns.org/mediawiki/index.php?title=Samples_testsuite (via 'ant tests') without deploying it to my server; since the JBossWS stack is already installed? I don't want to break anything if it's already installed correctly. Thanks for your time. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175624#4175624 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175624 From do-not-reply at jboss.com Wed Sep 10 16:21:48 2008 From: do-not-reply at jboss.com (sr_ren) Date: Wed, 10 Sep 2008 16:21:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Webservice impl from WSDL Message-ID: <97866.1221078108159.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a JBoss 4.3 with "[NativeServerConfig] jbossws-native-2.0.1.SP2 (build=200710210837)". I am trying to implement the WSDL using "start from WSDL" approach to implement server side webservice. First I tried using Eclipse 3.4 plugin that can generate server side code, however the deployment fails with "application.xml" not found. Also I found eclipse 3.4 webservice plugin generates buggy jaxb classes and it is unusable for complex types that uses derived types. I abandoned using Eclipse for webservice dev. Then I restored to using "wsconsume" to do service side webservice development. "wsconsume" generated interface and I wrote the implementation for the interface. However I have no idea what are the things that are needed to be in the war/ear to package and in what structure (e.g META-INF/application.xml, META-INF/manifest.mf, WEB-INF/wsdl/mywsdl.wsdl). I could not get information about what all things need to be put for packaging if I want to manually package and deploy, could anyone help? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175689#4175689 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175689 From do-not-reply at jboss.com Wed Sep 10 17:22:59 2008 From: do-not-reply at jboss.com (PeterJ) Date: Wed, 10 Sep 2008 17:22:59 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Webservice impl from WSDL Message-ID: <6332871.1221081779434.JavaMail.jboss@colo-br-02.atl.jboss.com> Are you doing a POJO web service or an EJB3 web service? They are slightly different. For a simple pojo 'hello world' service, you need: WEB-INF/web.xml WEB-INF/classes/pojo/ws/*.class (the wsconsume-generated classes) WEB-INF/classes/pojo/ws/HelloImpl.class (the class you coded) WEB-INF/wsdl/hello.wsdl this layout assume this annotation on the HelloImpl class: @WebService(.., wsdlLocation="WEB-INF/wsdl/hello.wsdl") View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175708#4175708 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175708 From do-not-reply at jboss.com Thu Sep 11 02:11:10 2008 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Thu, 11 Sep 2008 02:11:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: jbossws first steps Message-ID: <16390402.1221113470729.JavaMail.jboss@colo-br-02.atl.jboss.com> "TonyR" wrote : | However when I check the http://jbws.dyndns.org/mediawiki/index.php?title=Supported_Target_Containers, the matrix implies that only jbossws-native-3.0.3 is compatible with the application server 4.2.3. So does that mean, I should download the 3.0.3 stack and install it? Or should I just take the 'easy way' out and just use the 4.2.2 version of the server. Download JBossWS 3.0.3 if you want to run Web Services stack on AS 4.2.3. "TonyR" wrote : | Another question I had is how can I run the http://jbws.dyndns.org/mediawiki/index.php?title=Samples_testsuite (via 'ant tests') without deploying it to my server; since the JBossWS stack is already installed? I don't want to break anything if it's already installed correctly. | Yes, you should be able to run the tests even if you don't upgrade the SOAP stack. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175759#4175759 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175759 From do-not-reply at jboss.com Thu Sep 11 12:44:01 2008 From: do-not-reply at jboss.com (amashtakov) Date: Thu, 11 Sep 2008 12:44:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - websphere swaRef/MIME interop. issue Message-ID: <23398634.1221151441054.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi Everybody, I spent several hours while fighting with the following issue, but with no luck: I have to access a web service, running on websphere v6. The web service itself uses swaRef and MIME for attachments. Both, JBossWS and WebSphere v6 claim support for WS-I Attachment Profile 1.0, but running wsconsume tool against wsdl file raises the folowing error: | [ERROR] invalid extension element: "mime:part" (in namespace http://schemas.xmlsoap.org/wsdl/mime/") unknown location | I tested this with jboss 4.2.2.GA, 4.2.3.GA and jbossws-3.0.3-native, but the error remains. Seems, that problem is with wsdl file, but I cannot figure out why due my limited experience with web services. Can anybody help me this ? Any pointers will be highly appreciated. Thank you in advance, /Alexander PS: WeatherAttachment.wsdl (an example from websphere web services handbook v6) | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | swaref.xsd | | | | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175922#4175922 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175922 From do-not-reply at jboss.com Thu Sep 11 13:29:27 2008 From: do-not-reply at jboss.com (sr_ren) Date: Thu, 11 Sep 2008 13:29:27 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of the generated one. Message-ID: <30557659.1221154167680.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using JBoss 4.3. I followed the exact steps I just got this 10:25:45,013 INFO [DefaultEndpointRegistry] register: jboss.ws:context=EchoTest,endpoint=echo 10:25:45,075 INFO [TomcatDeployer] deploy, ctxPath=/EchoTest, warUrl=.../tmp/deploy/tmp53925EchoTest-exp.war/ 10:25:45,401 INFO [WSDLFilePublisher] WSDL published to: file:/C:/Program Files/JBoss/server/default/data/wsdl/EchoTest.war/EchoService.wsdl I did not get the message regarding "ServiceEndpointDeployer". When I test my web service I got exception 10:27:07,011 ERROR [SOAPFaultHelperJAXWS] SOAP request exception java.lang.IllegalStateException: Canot get target bean instance at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.getTargetBean(DefaultInvocationHandler.java:80) at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.invoke(DefaultInvocationHandler.java:90) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:220) ... Caused by: java.lang.InstantiationException: echo.Echo at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.jboss.wsf.container.jboss42.DefaultInvocationHandler.getTargetBean(DefaultInvocationHandler.java:75) I don't understand who creates this echo.Echo servlet which is mentioned in the web.xml. Any help View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175930#4175930 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175930 From do-not-reply at jboss.com Thu Sep 11 15:07:48 2008 From: do-not-reply at jboss.com (davidm2005) Date: Thu, 11 Sep 2008 15:07:48 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SOAPElementImpl cast excepion (JBoss 4.2 + Axis2 + JDK1. Message-ID: <22694233.1221160068516.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, Did you (or anyone else) ever figure out this problem? I have almost the same error message trying to do use WS-Security for encrypting and signing messages: 2008-09-11 15:02:45,968 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] SOAP request exception java.lang.ClassCastException: org.jboss.ws.core.soap.SOAPElementImpl at org.jboss.ws.core.soap.SOAPEnvelopeImpl.(SOAPEnvelopeImpl.java:60) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:124) at org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:96) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:280) at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:195) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:447) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:284) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:201) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:134) at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446) at java.lang.Thread.run(Thread.java:595) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175964#4175964 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175964 From do-not-reply at jboss.com Thu Sep 11 15:09:07 2008 From: do-not-reply at jboss.com (davidm2005) Date: Thu, 11 Sep 2008 15:09:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SOAPElementImpl cast excepion (JBoss 4.2) Message-ID: <22092663.1221160147193.JavaMail.jboss@colo-br-02.atl.jboss.com> P.S. I'm using neither axis nor jdk 1.6, but rather jboss-4.2.3.GA, JAX-WS SLSB EJB Webservices, and JDK 1.5.0_16 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175965#4175965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175965 From do-not-reply at jboss.com Thu Sep 11 16:13:02 2008 From: do-not-reply at jboss.com (sr_ren) Date: Thu, 11 Sep 2008 16:13:02 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Providing your own wsdl instead of the generated one. Message-ID: <21953754.1221163982667.JavaMail.jboss@colo-br-02.atl.jboss.com> I followed the posting below and I could get EchoTest to work by doing the following (adding portName which is in bold) @javax.jws.WebService(endpointInterface="echo.Echo", portName="EchoPort") public class EchoImpl implements Echo{ ... } It looks like the name should match WSL port which is defined as I am surprised why some instructions are not available in the product manual or part of WSCONSUME intructions. I don't understand why it should be so difficult to do a simple hello world web service when I start from WSDL first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175975#4175975 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175975 From do-not-reply at jboss.com Thu Sep 11 16:16:12 2008 From: do-not-reply at jboss.com (sr_ren) Date: Thu, 11 Sep 2008 16:16:12 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Webservice impl from WSDL Message-ID: <31474733.1221164172441.JavaMail.jboss@colo-br-02.atl.jboss.com> This helped. I was able to resolve further by going through http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142165 Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175976#4175976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175976 From do-not-reply at jboss.com Thu Sep 11 16:44:31 2008 From: do-not-reply at jboss.com (PeterJ) Date: Thu, 11 Sep 2008 16:44:31 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: SOAPElementImpl cast excepion (JBoss 4.2 + Axis2 + JDK1. Message-ID: <17760876.1221165871568.JavaMail.jboss@colo-br-02.atl.jboss.com> There was a discussion on WS-Secuiryt a while back, see if this helps: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127824 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175983#4175983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175983 From do-not-reply at jboss.com Thu Sep 11 17:13:58 2008 From: do-not-reply at jboss.com (JBossWS_NewBee) Date: Thu, 11 Sep 2008 17:13:58 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Validation of input Message-ID: <445145.1221167638819.JavaMail.jboss@colo-br-02.atl.jboss.com> I had a similar question: I have a WSDL operation which is based on a XML schema with the following info: CheckInDate: YYMMDD Couple of questions around this schema: 1. Does JBossWS framework understand the xml schema constraints of xs:minLength, xs:maxLength and xs:pattern, if specified? 2. What kind of error (Soap or otherwise) does the JBossWS framework throw or report to the WS-Client, if minLength, maxLength and pattern constraints are violated.? 3. If not, do I need to do a validation around these constraints in my code and throw a wsdl 'validation error' fault. Thanks in Advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175988#4175988 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175988 From do-not-reply at jboss.com Thu Sep 11 18:45:34 2008 From: do-not-reply at jboss.com (sr_ren) Date: Thu, 11 Sep 2008 18:45:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - org.jboss.ws.WSException: Cannot find port in wsdl: Message-ID: <24955956.1221173135087.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using standard WSDL packaged with jaxws-ri AddNumbers.wsdl. I am following wsdl first approach to design my Java implementation. I followed the steps given in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=104843 I was able to make Echo service work fine, however I could not do AddNumbers which is as given below | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I ran wsconsume on this and wrote my impl class AddNumbersImp.java @javax.jws.WebService(endpointInterface="org.example.duke.AddNumbersPortType", portName="AddNumbersPort") public class AddNumbersImpl implements AddNumbersPortType { public int addNumbers(int arg0, int arg1)throws AddNumbersFault_Exception { return 10; } } After building AddNumbers.war file at deployment time I get the following error 15:27:46,185 INFO [DefaultEndpointRegistry] register: jboss.ws:context=AddNumbers,endpoint=AddNumbers 15:27:46,200 INFO [TomcatDeployer] deploy, ctxPath=/AddNumbers, warUrl=.../tmp/deploy/tmp53972AddNumbers-exp.war/ 15:27:46,482 WARN [PolicyMetaDataBuilder] Cannot get service '{http://duke.example.org/}AddNumbersImplService' from the given wsdl definitions! Eventual policies attached to this service won't be considered. 15:27:46,560 ERROR [MainDeployer] Could not start deployment: file:/C:/Program Files/JBoss/server/default/deploy/AddNumbers.war org.jboss.ws.WSException: Cannot find port in wsdl: {http://duke.example.org/}AddNumbersPort at org.jboss.ws.metadata.builder.MetaDataBuilder.replaceAddressLocation(MetaDataBuilder.java:338) at org.jboss.ws.metadata.builder.jaxws.JAXWSWebServiceMetaDataBuilder.buildWebServiceMetaData(JAXWSWebServiceMetaDataBuilder.java:192) at org.jboss.ws.metadata.builder.jaxws.JAXWSServerMetaDataBuilder.setupProviderOrWebService(JAXWSServerMetaDataBuilder.java:50) at org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilderJSE.buildMetaData(JAXWSMetaDataBuilderJSE.java:63) at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.create(UnifiedMetaDataDeploymentAspect.java:66) at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.deploy(Unknown Source) 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 $Proxy45.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.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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:610) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.loop(AbstractDeploymentScanner.java:274) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.run(AbstractDeploymentScanner.java:225) I tried several ways to tweak the PortName, but I don't have any success. Appreciate any help View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4175997#4175997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4175997 From do-not-reply at jboss.com Fri Sep 12 12:01:04 2008 From: do-not-reply at jboss.com (JBossWS_NewBee) Date: Fri, 12 Sep 2008 12:01:04 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Validation of XSD (minLength, maxLength and pattern) Message-ID: <26394101.1221235264063.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a WSDL operation which is based on a XML schema with the following info: CheckInDate: YYMMDD Couple of questions around this schema: 1. Does JBossWS framework understand the xml schema constraints of xs:minLength, xs:maxLength and xs:pattern, if specified? 2. What kind of error (Soap or otherwise) does the JBossWS framework throw or report to the WS-Client, if minLength, maxLength and pattern constraints are violated.? 3. If not, do I need to do a validation around these constraints in my code and throw a wsdl 'validation error' fault. Thanks in Advance! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176196#4176196 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176196 From do-not-reply at jboss.com Fri Sep 12 16:15:03 2008 From: do-not-reply at jboss.com (zaiwengong) Date: Fri, 12 Sep 2008 16:15:03 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Jbossws Sample build failed Message-ID: <28380402.1221250503526.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I downloaded jbossws-1.2.1.GA.zip and installed it to jboss-4.0.5GA using JDK 1.5.0_06 on Windows 2003. Start jboss and I can access http://localhost:8080/jbossws. To build the samples I dis the following: - unzip jbossws-samples-1.2.1.GA.zip - cd jbossws-samples-1.2.1.GA - cp ant.properties.example as ant.properties - in the ant.properties file: - set jboss40.home - set jbossws.integration.target=jboss40 I then ran ant, but received error: thirdparty-get: [get] Error getting http://repository.jboss.org/apache-collections/3.1/lib /commons-collections.jar to D:\jbossws-samples-1.2.1.GA\thirdparty\commons-collections.jar Do I need to set proxy anywhere? My machine itself has no problem access http://repository.jboss.org. Then I tried to manually download the commons-collections.jar and placed it in the ..\thirdparty directory and run ant again, but received another error: D:\jbossws-samples-1.2.1.GA\build.xml:249: java.lang.IllegalStateException: Could not load provider:org.jboss.ws.tools.jaxws.impl.WSContractConsumerFactoryImpl Any clue? I appreciate your help greatly! I am now being blocked :( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176257#4176257 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176257 From do-not-reply at jboss.com Sat Sep 13 02:04:11 2008 From: do-not-reply at jboss.com (sr_ren) Date: Sat, 13 Sep 2008 02:04:11 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: org.jboss.ws.WSException: Cannot find port in wsdl: Message-ID: <32261317.1221285851892.JavaMail.jboss@colo-br-02.atl.jboss.com> Since I did not get reply and I had to work on the problem, we figured out what is JBoss requirement to fix the problem @javax.jws.WebService(endpointInterface="org.example.duke.AddNumbersPortType", targetNamespace = "http://duke.example.org", portName="AddNumbersPort") It seems targetNamespace is required in the implementation class. This is not documented anywhere in the wsconsume wiki. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176291#4176291 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176291 From do-not-reply at jboss.com Mon Sep 15 05:51:01 2008 From: do-not-reply at jboss.com (AgainC) Date: Mon, 15 Sep 2008 05:51:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Double ws request using jbossws client Message-ID: <15929947.1221472261523.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi all, I have a problem using WebServices proxy clients generated with wsconsume. Looks the the exposed ws is called 3 times 1 to download the wsdl(OK) and 2 consecutive calls to the the exposed method. the implemented code it's right as you can see following: URL webServiceURL = null; Vector beanList = null; ConfigurationWrapper conf = ConfigurationWrapper.getInstance(); try { webServiceURL = new URL(conf.getVehicleCountServiceEndPoint()); } catch (MalformedURLException e) { e.printStackTrace(); log(e); } ObjectFactory of = new ObjectFactory(); GetCountProxyService service = new GetCountProxyService(webServiceURL, new QName("http://www.infomobility.com/IB", "getCountProxyService")); try { GetCountProxyPortType port = service.getGetCountProxyPort(); GetCountProxyReq req = of.createGetCountProxyReq(); req.setHEADER(beanHeader); req.setCUSTOMER(beanBodyCustomer); req.setSERVICE(beanBodyService); GetCountProxyRes result = port.getCountProxy(req); logger.info("############# STA WA CALL IB VehicleCount "+System.currentTimeMillis()+" #############"); result = port.getCountProxy(req); logger.info("############# END WA CALL IB VehicleCount "+System.currentTimeMillis()+" #############"); if (null != result) { beanBodyResult = result.getMESSAGERESULT(); beanHeaderResult = result.getHEADER(); beanIndexResult = result.getINDEX(); beanList = new Vector(); beanList.add(beanHeaderResult); beanList.add(beanBodyResult); beanList.add(beanIndexResult); } } catch (Exception e) { error("", e); } return beanList; The logs that you can see in the code are printed just 1 time a call in the log files. the Log: 2008-09-15 11:16:23,864 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml; charset=utf-8] 2008-09-15 11:16:23,866 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.http.HTTPClientInvoker at 7b28dc from registry 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 42058f (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 17accc9 (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindResponseMessage: {http://www.infomobility.com/IB}getCountProxy 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: org.jboss.ws.core.soap.SOAPBodyElementDoc 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.CommonClient] Handler modified body payload, unbind message again 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindResponseMessage: {http://www.infomobility.com/IB}getCountProxy 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: org.jboss.ws.core.soap.SOAPBodyElementDoc 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.EndpointInvocation] getReturnValue 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from XML_VALID to OBJECT_VALID 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue [xmlType={http://www.infomobility.com/IB}>getCountProxy_Res,javaType=class it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes] 2008-09-15 11:16:23,866 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialize: [xmlName={http://www.infomobility.com/IB}getCountProxy_Res,xmlType={http://www.infomobility.com/IB}>getCountProxy_Res] 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialized: it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.soap.XMLContent] objectValue: it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: org.jboss.ws.core.soap.SOAPBodyElementDoc -> it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close 2008-09-15 11:16:23,901 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close 2008-09-15 11:16:23,902 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 17accc9 (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:16:23,902 INFO [it.telecomitalia.vt.wa.log.GenericLogInterface] ############# STA WA CALL IB VehicleCount 1221470183902 ############# 2008-09-15 11:16:23,903 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at c3455c (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:16:23,903 DEBUG [org.jboss.ws.core.EndpointInvocation] setRequestParamValue: [name={http://www.infomobility.com/IB}getCountProxy_Req,value=it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyReq] 2008-09-15 11:16:23,903 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] bindRequestMessage: {http://www.infomobility.com/IB}getCountProxy 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.EndpointInvocation] getRequestParamValue: {http://www.infomobility.com/IB}getCountProxy_Req 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyReq -> it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyReq 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [] 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [] 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] Create a handler executor: [] 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.client.RemotingConnectionImpl] Get locator for: [addr=http://ip-fe-alsb-ms-01-1:8101/getCountProxy,props={javax.xml.ws.service.endpoint.address=http://ip-fe-alsb-ms-01-1:8101/getCountProxy}] 2008-09-15 11:16:23,904 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.HTTPClientInvoker at 1feaee5 connecting 2008-09-15 11:16:23,904 DEBUG [org.jboss.remoting.MicroRemoteClientInvoker] org.jboss.remoting.transport.http.HTTPClientInvoker at 1feaee5 connected 2008-09-15 11:16:23,904 DEBUG [org.jboss.ws.core.client.RemotingConnectionImpl] Remoting metadata: {HEADER={SOAPAction="soapgetCountProxy", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true} 2008-09-15 11:16:23,905 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with SOAPAction : "soapgetCountProxy" 2008-09-15 11:16:23,905 DEBUG [org.jboss.remoting.transport.http.HTTPClientInvoker] Setting request header with Content-Type : text/xml; charset=UTF-8 2008-09-15 11:16:23,905 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- 2008-09-15 11:16:23,905 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from OBJECT_VALID to XML_VALID 2008-09-15 11:16:23,905 DEBUG [org.jboss.ws.core.soap.ObjectContent] getXMLFragment from Object [xmlType={http://www.infomobility.com/IB}>getCountProxy_Req,javaType=class it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyReq] 2008-09-15 11:16:23,905 DEBUG [org.jboss.ws.core.jaxws.JAXBSerializer] serialize: [xmlName={http://www.infomobility.com/IB}getCountProxy_Req,xmlType={http://www.infomobility.com/IB}>getCountProxy_Req] 2008-09-15 11:16:23,906 DEBUG [org.jboss.ws.core.jaxws.JAXBSerializer] serialized: WAIB85VTT 2008-09-15 11:16:23,906 DEBUG [org.jboss.ws.core.soap.ObjectContent] xmlFragment: [source=WAIB85VTT] 2008-09-15 11:16:23,906 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- 2008-09-15 11:16:25,628 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - first pass 2008-09-15 11:16:25,628 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] StatusModule: first pass 2008-09-15 11:16:25,629 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_3] - TORecoveryModule - first pass 2008-09-15 11:16:25,629 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass 2008-09-15 11:16:35,639 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] Periodic recovery - second pass 2008-09-15 11:16:35,639 DEBUG [com.arjuna.ats.arjuna.logging.arjLogger] AtomicActionRecoveryModule: Second pass 2008-09-15 11:16:35,639 DEBUG [com.arjuna.ats.txoj.logging.txojLoggerI18N] [com.arjuna.ats.internal.txoj.recovery.TORecoveryModule_6] - TORecoveryModule - second pass 2008-09-15 11:16:35,639 DEBUG [com.arjuna.ats.jta.logging.loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass 2008-09-15 11:17:19,736 DEBUG [org.jboss.ws.core.soap.SOAPMessageUnMarshaller] getMimeHeaders from: {X-Powered-By=[Servlet/2.4 JSP/2.0], Content-Length=[1114], ResponseCodeMessage=OK, Date=[Mon, 15 Sep 2008 09:16:30 GMT], Content-Type=[text/xml; charset=utf-8], HEADER={SOAPAction="soapgetCountProxy", Content-Type=text/xml; charset=UTF-8}, NoThrowOnError=true, ResponseCode=200} 2008-09-15 11:17:19,738 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl] createMessage: [contentType=text/xml; charset=utf-8] 2008-09-15 11:17:19,739 DEBUG [org.jboss.remoting.InvokerRegistry] removed org.jboss.remoting.transport.http.HTTPClientInvoker at 1feaee5 from registry 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.jaxws.handler.MessageContextJAXWS] Begin response processing 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at c3455c (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] pushMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 18c6c98 (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindResponseMessage: {http://www.infomobility.com/IB}getCountProxy 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: org.jboss.ws.core.soap.SOAPBodyElementDoc 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.CommonClient] Handler modified body payload, unbind message again 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS] unbindResponseMessage: {http://www.infomobility.com/IB}getCountProxy 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue: org.jboss.ws.core.soap.SOAPBodyElementDoc 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.EndpointInvocation] getReturnValue 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] Transitioning from XML_VALID to OBJECT_VALID 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue [xmlType={http://www.infomobility.com/IB}>getCountProxy_Res,javaType=class it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes] 2008-09-15 11:17:19,740 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialize: [xmlName={http://www.infomobility.com/IB}getCountProxy_Res,xmlType={http://www.infomobility.com/IB}>getCountProxy_Res] 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialized: it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.soap.XMLContent] objectValue: it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.soap.SOAPContentElement] ----------------------------------- 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.EndpointInvocation] transformPayloadValue: org.jboss.ws.core.soap.SOAPBodyElementDoc -> it.telecomitalia.vt.wa.ws.proxyclient.vehiclecount.GetCountProxyRes 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close 2008-09-15 11:17:19,741 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor] close 2008-09-15 11:17:19,742 DEBUG [org.jboss.ws.core.soap.MessageContextAssociation] popMessageContext: org.jboss.ws.core.jaxws.handler.SOAPMessageContextJAXWS at 18c6c98 (Thread ajp-10.35.67.68-8009-2) 2008-09-15 11:17:19,742 INFO [it.telecomitalia.vt.wa.log.GenericLogInterface] ############# END WA CALL IB VehicleCount 1221470239742 ############# 2008-09-15 11:17:19,743 INFO [it.telecomitalia.vt.wa.action.common.CommonAbstractAction] ############################## END IB CALL VehicleCount 1221470239743 ############################## I accept any ideas. Thanks. Carlo View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176452#4176452 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176452 From do-not-reply at jboss.com Mon Sep 15 08:22:59 2008 From: do-not-reply at jboss.com (sachinverma) Date: Mon, 15 Sep 2008 08:22:59 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - can anyone help me in achieving this below mentioned goal Message-ID: <16181661.1221481379831.JavaMail.jboss@colo-br-02.atl.jboss.com> anonymous wrote : I wanted to show a specific html page on portal; can anyone help me in achieving this goal of mine. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4176496#4176496 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4176496 From do-not-reply at jboss.com Wed Sep 17 06:56:05 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 17 Sep 2008 06:56:05 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Problem with Deploy and undeploy JBossWS-native-3.0.3.GA Message-ID: <20200141.1221648965581.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks for pointing this out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177071#4177071 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177071 From do-not-reply at jboss.com Wed Sep 17 11:45:43 2008 From: do-not-reply at jboss.com (ahmedmhyd) Date: Wed, 17 Sep 2008 11:45:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: When JbossWS Wiki will be online Message-ID: <2091162.1221666343709.JavaMail.jboss@colo-br-02.atl.jboss.com> I know this is old thread..But still dydns url is down.is there any plan to bring it up.if not can please update the wiki link on jboss for ws documentation which points to "DEAD URL". Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177181#4177181 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177181 From do-not-reply at jboss.com Wed Sep 17 12:33:57 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Wed, 17 Sep 2008 12:33:57 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: When JbossWS Wiki will be online Message-ID: <26488492.1221669237187.JavaMail.jboss@colo-br-02.atl.jboss.com> I know this is quite embarrassing, anyway the system is being moved under the jboss.org domain these days. Currently pushing for having this done as fast as possible. Sorry View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177195#4177195 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177195 From do-not-reply at jboss.com Thu Sep 18 02:59:05 2008 From: do-not-reply at jboss.com (lordjoker) Date: Thu, 18 Sep 2008 02:59:05 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Invalid default namespace: null Message-ID: <23591856.1221721145750.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a big problem with Webservice. I have a webservice client installed on jboss-4.2.2.GA and webservice installed on Tomcat. When I want to invoke webservice method a receive a following error: Jboss: org.jboss.ws.metadata.wsdl.WSDLException: Invalid default namespace: null Tomcat: Unsupported Content-Type: application/soap+xml Supported ones are: [text/xml] My webservice code is: @WebService(serviceName = "mySyncC1", portName = "WSService", targetNamespace = "http://servicemix.org/cheese/") @SOAPBinding(parameterStyle = SOAPBinding.ParameterStyle.BARE) public class WSService {..... and my client code is: @WebServiceClient(name = "mySyncC1", targetNamespace = "http://servicemix.org/cheese/", wsdlLocation = WSDL_PATH) public class MySyncC1 extends Service {....... The same client application deployed on glassfish does not cause any problems. Is there any extra jboss configuration required. Help.....!!!! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177300#4177300 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177300 From do-not-reply at jboss.com Thu Sep 18 06:03:42 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Thu, 18 Sep 2008 06:03:42 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - New JBossWS QA box Message-ID: <31517628.1221732222767.JavaMail.jboss@colo-br-02.atl.jboss.com> The documentation and Hudson instances have been moved to another server. The new URL is: http://jbossws.jboss.org In particular, the documentation is available at http://jbossws.jboss.org/mediawiki. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177348#4177348 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177348 From do-not-reply at jboss.com Thu Sep 18 06:07:59 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Thu, 18 Sep 2008 06:07:59 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: When JbossWS Wiki will be online Message-ID: <32542303.1221732479293.JavaMail.jboss@colo-br-02.atl.jboss.com> http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177348 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177350#4177350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177350 From do-not-reply at jboss.com Thu Sep 18 17:12:25 2008 From: do-not-reply at jboss.com (jstewart66061) Date: Thu, 18 Sep 2008 17:12:25 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Username Token Profile URIs in SOAP header not compatible? Message-ID: <27439545.1221772345425.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm writing a client to chat with a service written in .NET that utilizes Username Token Profile 1.0. I'm using JBossWS for my side of the pond. I have everything working, but when it creates the SOAP header that contains the password, it sets Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0#PasswordText". The .NET service seems to be looking for Type='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText', which is from the Username Token Profile 1.0 spec. Why is JBossWS putting this URI on the node of the header? Shouldn't it be conforming to the Username Token Profile 1.0 spec that is part of the WS-Security 1.0 spec? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177536#4177536 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177536 From do-not-reply at jboss.com Fri Sep 19 01:45:16 2008 From: do-not-reply at jboss.com (yaragalla_murali) Date: Fri, 19 Sep 2008 01:45:16 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - some problem with MBeans Message-ID: <24919614.1221803116697.JavaMail.jboss@colo-br-02.atl.jboss.com> I have implemented the webservices for the first time in JBoss. After implementation I am getting the following error. please kindly help me in this. MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=DeliverableReleaseWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=DeliverableWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=InputDependsOnWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=InputWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=MilestoneWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PoPWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 Depends On Me: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PublishRuleWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 Depends On Me: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=DeliverableReleaseWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=DeliverableWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=InputDependsOnWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=InputWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=MilestoneWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PoPWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PublishRuleWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=UserWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=WaterholeWorkflowImpl,service=EJB3 ObjectName: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PublishRuleWorkflowImpl,service=EJB3 State: NOTYETINSTALLED I Depend On: jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PoPWorkflowImpl,service=EJB3 jboss.j2ee:ear=mypopprojectEAR.ear,jar=mypopprojectEJB.jar,name=PrivilegeWorkflowImpl,service=EJB3 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177562#4177562 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177562 From do-not-reply at jboss.com Fri Sep 19 02:35:56 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Fri, 19 Sep 2008 02:35:56 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Username Token Profile URIs in SOAP header not compatibl Message-ID: <24603758.1221806156286.JavaMail.jboss@colo-br-02.atl.jboss.com> The username token profile specs are not really clear about this, anyway this was not addressed the proper way when working on JBWS-2265. It's a bug, I've created an issue for it: https://jira.jboss.org/jira/browse/JBWS-2309. This will go in the first release coming out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177569#4177569 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177569 From do-not-reply at jboss.com Fri Sep 19 04:18:15 2008 From: do-not-reply at jboss.com (sekobey) Date: Fri, 19 Sep 2008 04:18:15 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBOSS WS and SOAP element expected problem... Message-ID: <21647748.1221812295530.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I was using JBOSS 4.2.1 GA with Java 6 successfully. Now I've started to use JBOSS 4.2.3 with JAVA 6. I use a WS by a calling an ejb method. Firstly i got an exception as in: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=117274 Then i solved it. But now i get a new exception: java.lang.IllegalArgumentException: SOAPElement expected at org.jboss.ws.core.soap.SOAPHeaderImpl.convertToHeaderElement(SOAPHeaderImpl.java:286) at org.jboss.ws.core.soap.SOAPHeaderImpl.insertBefore(SOAPHeaderImpl.java:204) at com.sun.xml.wss.impl.XMLUtil.prependChildElement(XMLUtil.java:300) at com.sun.xml.wss.impl.XMLUtil.prependChildElement(XMLUtil.java:307) at com.sun.xml.wss.impl.SecurableSoapMessage.findWsseSecurityHeaderBlock(SecurableSoapMessage.java:197) at com.sun.xml.wss.impl.SecurableSoapMessage.findOrCreateSecurityHeader(SecurableSoapMessage.java:225) at com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.addUserNameTokenToMessage(AuthenticationTokenFilter.java:429) at com.sun.xml.wss.impl.filter.AuthenticationTokenFilter.processUserNameToken(AuthenticationTokenFilter.java:81) at com.sun.xml.wss.impl.HarnessUtil.processWSSPolicy(HarnessUtil.java:72) at com.sun.xml.wss.impl.HarnessUtil.processDeep(HarnessUtil.java:218) at com.sun.xml.wss.impl.SecurityAnnotator.processMessagePolicy(SecurityAnnotator.java:143) at com.sun.xml.wss.impl.SecurityAnnotator.secureMessage(SecurityAnnotator.java:118) at com.sun.xml.rpc.security.SecurityPluginUtil._preRequestSendingHook(SecurityPluginUtil.java:215) at tr.gov.nvi.kps.ws.client.KPSSoap_Stub._preRequestSendingHook(KPSSoap_Stub.java:2294) at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:87) at tr.gov.nvi.kps.ws.client.KPSSoap_Stub.nufusCuzdaniDogrulama(KPSSoap_Stub.java:579) at gov.tubitak.uekae.ydys.kym.eao.KartEAOImpl.getKPSNufusBilgisi(KartEAOImpl.java:1816) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:240) at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:210) at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:84) at $Proxy103.getKPSNufusBilgisi(Unknown Source) at gov.tubitak.uekae.ydys.kym.kyb.ejb.KYBIslemleriBean.getKPSNufusBilgisi(KYBIslemleriBean.java:609) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:166) at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptor.invoke(RoleBasedAuthorizationInterceptor.java:115) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:304) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:106) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:809) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:406) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) Important: In JBOSS 4.2.1 everything was fine. In JBOSS 4.2.3 i got this exception. Is there any library problem? Please help, thanks... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177584#4177584 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177584 From do-not-reply at jboss.com Fri Sep 19 05:24:43 2008 From: do-not-reply at jboss.com (kaviarasan) Date: Fri, 19 Sep 2008 05:24:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - javax.xml.rpc.ServiceException: Cannot create proxy Message-ID: <1273725.1221816283848.JavaMail.jboss@colo-br-02.atl.jboss.com> anonymous wrote : | I am facing the following issue. kindly help me in this issue. | Any help is appreciated.. Thanks in advance.. | | We have used wstools to generate the wsdl, jaxrpc-mapping and webservices file | | When calling the webservice we get this exception | the line that throws the exception is | statusListener = (StatusListener) service.getPort(StatusListener.class); anonymous wrote : Exception: | | 12:35:16,515 INFO [ReplicationConfigParser] getInstance serviceUtility::null | 12:35:17,171 WARN [EndpointMetaData] Loading SEI after eager initialization | 12:35:17,171 ERROR [STDERR] javax.xml.rpc.ServiceException: Cannot create proxy | 12:35:17,187 ERROR [STDERR] at org.jboss.ws.core.jaxrpc.client.ServiceImpl.getPort(ServiceImpl.j | ava:361) | 12:35:17,187 ERROR [STDERR] at com.iqs.sos.server.business.ejb.QueueProcessor.Service.ServiceUti | lity.getService(ServiceUtility.java:208) | 12:35:17,187 ERROR [STDERR] at com.iqs.sos.server.business.ejb.QueueProcessor.Service.ServiceUti | lity.(ServiceUtility.java:69) | 12:35:17,187 ERROR [STDERR] at com.iqs.sos.server.business.ejb.QueueProcessor.Service.ServiceUti | lity.getInstance(ServiceUtility.java:41) | 12:35:17,203 ERROR [STDERR] at com.iqs.sos.server.business.ejb.QueueProcessor.QueueProcessorMDB. | onMessage(QueueProcessorMDB.java:92) | 12:35:17,203 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) | 12:35:17,203 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorI | mpl.java:39) | 12:35:17,203 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA | ccessorImpl.java:25) | 12:35:17,218 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:597) | 12:35:17,218 ERROR [STDERR] at org.jboss.invocation.Invocation.performCall(Invocation.java:359) | 12:35:17,218 ERROR [STDERR] at org.jboss.ejb.MessageDrivenContainer$ContainerInterceptor.invoke( | MessageDrivenContainer.java:495) | 12:35:17,218 ERROR [STDERR] at org.jboss.resource.connectionmanager.CachedConnectionInterceptor. | invoke(CachedConnectionInterceptor.java:158) | 12:35:17,218 ERROR [STDERR] at org.jboss.ejb.plugins.MessageDrivenInstanceInterceptor.invoke(Mes | sageDrivenInstanceInterceptor.java:116) | 12:35:17,234 ERROR [STDERR] at org.jboss.ejb.plugins.CallValidationInterceptor.invoke(CallValida | tionInterceptor.java:63) | 12:35:17,234 ERROR [STDERR] at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTx | Interceptor.java:121) | 12:35:17,234 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInte | rceptorCMT.java:350) | 12:35:17,234 ERROR [STDERR] at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.ja | va:181) | 12:35:17,250 ERROR [STDERR] at org.jboss.ejb.plugins.RunAsSecurityInterceptor.invoke(RunAsSecuri | tyInterceptor.java:109) | 12:35:17,250 ERROR [STDERR] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:2 | 05) | 12:35:17,250 ERROR [STDERR] at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyF | actoryFinderInterceptor.java:138) | 12:35:17,250 ERROR [STDERR] at org.jboss.ejb.MessageDrivenContainer.internalInvoke(MessageDriven | Container.java:402) | 12:35:17,265 ERROR [STDERR] at org.jboss.ejb.Container.invoke(Container.java:960) | 12:35:17,265 ERROR [STDERR] at org.jboss.ejb.plugins.jms.JMSContainerInvoker.invoke(JMSContainer | Invoker.java:1092) | 12:35:17,265 ERROR [STDERR] at org.jboss.ejb.plugins.jms.JMSContainerInvoker$MessageListenerImpl | .onMessage(JMSContainerInvoker.java:1392) | 12:35:17,265 ERROR [STDERR] at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.jav | a:266) | 12:35:17,281 ERROR [STDERR] at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(Spy | MessageConsumer.java:906) | 12:35:17,281 ERROR [STDERR] at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.jav | a:170) | 12:35:17,281 ERROR [STDERR] at org.jboss.mq.SpySession.run(SpySession.java:323) | 12:35:17,281 ERROR [STDERR] at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194) | | 12:35:17,312 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Pooled | Executor.java:756) | 12:35:17,312 ERROR [STDERR] at java.lang.Thread.run(Thread.java:619) | 12:35:17,359 ERROR [STDERR] Caused by: java.lang.IllegalStateException: Cannot synchronize to any of | these methods: | public abstract void com.iqs.sos.queueserver.serviceengine.StatusListener.setSyslogStatus(java.util. | ArrayList) throws java.rmi.RemoteException,javax.naming.NamingException | | OperationMetaData: | qname={http://serviceengine.agentservice.iqs.com/}setSyslogStatus | javaName=setSyslogStatus | style=rpc/literal | oneWay=false | soapAction= | ParameterMetaData: | xmlName=SyslogMessageVO_1 | partName=SyslogMessageVO_1 | xmlType={http://serviceengine.agentservice.iqs.com/types}SyslogMessageVO | javaType=com.iqs.syslog.SyslogMessageVO | mode=IN | inHeader=false | index=0 | 12:35:17,406 ERROR [STDERR] at org.jboss.ws.metadata.umdm.OperationMetaData.eagerInitialize(Oper | ationMetaData.java:493) | 12:35:17,421 ERROR [STDERR] at org.jboss.ws.metadata.umdm.EndpointMetaData.eagerInitializeOperat | ions(EndpointMetaData.java:580) | 12:35:17,421 ERROR [STDERR] at org.jboss.ws.metadata.umdm.EndpointMetaData.initializeInternal(En | dpointMetaData.java:565) | 12:35:17,421 ERROR [STDERR] at org.jboss.ws.metadata.umdm.EndpointMetaData.setServiceEndpointInt | erfaceName(EndpointMetaData.java:231) | 12:35:17,421 ERROR [STDERR] at org.jboss.ws.core.jaxrpc.client.ServiceImpl.getPort(ServiceImpl.j | ava:347) | anonymous wrote : WSDL file: | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | anonymous wrote : Jaxrpc-mapping.xml: | | | | com.iqs.syslog | http://syslog.iqs.com/ | | | com.iqs.sos.queueserver.serviceengine.service.statusmessage | http://serviceengine.agentservice.iqs.com/types | | | com.iqs.syslog.CiscoDO | typeNS:CiscoDO | complexType | | action | action | | | ciscoFirewallType | ciscoFirewallType | | | createDate | createDate | | | destinationIP | destinationIP | | | intrface | intrface | | | messageID | messageID | | | msgType | msgType | | | protocol | protocol | | | rawMessage | rawMessage | | | sensor | sensor | | | severityLevel | severityLevel | | | sourceIP | sourceIP | | | | com.iqs.syslog.FortinetDO | typeNS:FortinetDO | complexType | | SN | SN | | | appType | appType | | | clusterId | clusterId | | | date | date | | | destinationIP | destinationIP | | | destinationInterface | destinationInterface | | | destinationName | destinationName | | | destinationPort | destinationPort | | | deviceId | deviceId | | | deviceName | deviceName | | | dirDisp | dirDisp | | | duration | duration | | | group | group | | | itime | itime | | | logId | logId | | | message | message | | | msgDate | msgDate | | | msgIP | msgIP | | | policyId | policyId | | | priority | priority | | | protocol | protocol | | | rawMessage | rawMessage | | | received | received | | | receivedPackets | receivedPackets | | | rule | rule | | | sent | sent | | | sentPackets | sentPackets | | | service | service | | | sourceIP | sourceIP | | | sourceInterface | sourceInterface | | | sourceName | sourceName | | | sourcePort | sourcePort | | | status | status | | | subType | subType | | | time | time | | | translatedDisp | translatedDisp | | | translatedIP | translatedIP | | | translatedPort | translatedPort | | | type | type | | | user | user | | | vd | vd | | | vpn | vpn | | | | com.iqs.syslog.SyslogMessageVO | typeNS:SyslogMessageVO | complexType | | ciscoMsgArray | ciscoMsgArray | | | fortinetMsgArray | fortinetMsgArray | | | | com.iqs.sos.queueserver.serviceengine.service.statusmessage.CMD-webservice | serviceNS:CMD-webservice | | StatusMessageServicePort | StatusMessageServicePort | | | | com.iqs.sos.queueserver.serviceengine.service.statusmessage.StatusMessageService | portTypeNS:StatusMessageService | bindingNS:StatusMessageServiceBinding | | setStatus | setStatus | | 0 | java.lang.String | | wsdlMsgNS:StatusMessageService_setStatus | String_1 | IN | | | | | setSyslogStatus | setSyslogStatus | | 0 | com.iqs.syslog.SyslogMessageVO | | wsdlMsgNS:StatusMessageService_setSyslogStatus | SyslogMessageVO_1 | IN | | | | | | anonymous wrote : webservices.xml: | | CMD-webservice | META-INF/wsdl/CMD-webservice.wsdl | META-INF/jaxrpc-mapping.xml | | StatusMessageServicePort | portNS:StatusMessageServicePort | com.iqs.sos.queueserver.serviceengine.service.statusmessage.StatusMessageService | | CMD-Agent-Status-Service | | | | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177602#4177602 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177602 From do-not-reply at jboss.com Fri Sep 19 12:24:04 2008 From: do-not-reply at jboss.com (mjremijan) Date: Fri, 19 Sep 2008 12:24:04 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Please help, cannot get @RolesAllowed to work. Message-ID: <26659718.1221841444666.JavaMail.jboss@colo-br-02.atl.jboss.com> I am trying to get @RolesAllowed to work but despite setting a user which does NOT have the role "JournalAccountLogin" the web service method is allowed to be called anyway. See below for what I have configured. From the client I use a user which has the role "Journal JWS" so I can get past the definition in the web.xml, however this user does NOT have the "JournalAccountLogin" role so when I try to call the login(...) method I was expecting the call to not work but it does. Can anyone help with this? WEB SERVICE | @WebMethod | @RolesAllowed("JournalAccountLogin") | public Account login(...) { ... } | FILE web.xml | | AccountJws | /bin/account.jws | | . | . | . | | secure and confidential | | All | /bin/* | | | Only Journal JWS role has access | Journal JWS | | | Only HTTPS | CONFIDENTIAL | | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177719#4177719 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177719 From do-not-reply at jboss.com Fri Sep 19 16:46:19 2008 From: do-not-reply at jboss.com (mjremijan) Date: Fri, 19 Sep 2008 16:46:19 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - jboss-portal-2.7.0.CR1 CMS main.jsp fails to compile? Message-ID: <29195915.1221857179681.JavaMail.jboss@colo-br-02.atl.jboss.com> I downloaded jboss-portal-2.7.0.CR1.zip and dropped /jboss-portal.sar into my JBoss 4.2.1 instance. I've tried running my JBoss instance with Java 1.5 and Java 1.6. In both cases when I login as "admin" the click the "CMS" tab I get a stack trace which basically is telling me that the generics code and the autoboxing code cannot be compiled almost as if a 1.4 jvm is being used to try the do the compiling. The stack trace is below. If I use "jboss-portal-2.7.0.CR1-bundled.zip" I don't see this problem. Any ideas how to fix this? I'd rather not have to reconfigure a new server. | Cause: javax.portlet.PortletException: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 45 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 42: 43: 44: <% 45: for (String message : messages) 46: { 47: %> 48: An error occurred at line: 142 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Type mismatch: cannot convert from Boolean to boolean 139: 140: ">${n:i18n("CMS_SECURE")} 141: <% 142: if (manageWorkflowAccessible) 143: { 144: %> 145: An error occurred at line: 270 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 267: <% 268: if (files.size() > 0) 269: { 270: for (File file : files) 271: { 272: %> 273: Stacktrace: | Message: org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 45 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 42: | ${n:i18n("CMS_MESSAGES")}: | 43: 44: <% 45: for (String message : messages) 46: { 47: %> 48: An error occurred at line: 142 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Type mismatch: cannot convert from Boolean to boolean 139: 140: ">${n:i18n("CMS_SECURE")} 141: <% 142: if (manageWorkflowAccessible) 143: { 144: %> 145: An error occurred at line: 270 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 267: <% 268: if (files.size() > 0) 269: { 270: for (File file : files) 271: { 272: %> 273: Stacktrace: | StackTrace: | | javax.portlet.PortletException: org.apache.jasper.JasperException: Unable to compile class for JSP: | | An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | The type List is not generic; it cannot be parameterized with arguments | 16: <% | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | | | An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | Syntax error, parameterized types are only available if source level is 5.0 | 16: <% | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | | | An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | The type List is not generic; it cannot be parameterized with arguments | 16: <% | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | | | An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | Syntax error, parameterized types are only available if source level is 5.0 | 16: <% | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | | | An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | The type List is not generic; it cannot be parameterized with arguments | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); | | | An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | Syntax error, parameterized types are only available if source level is 5.0 | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); | | | An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | The type List is not generic; it cannot be parameterized with arguments | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); | | | An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | Syntax error, parameterized types are only available if source level is 5.0 | 17: String sConfirm = renderRequest.getParameter("confirm"); | 18: String sCurrPath = (String)request.getAttribute("currpath"); | 19: List folders = (List)request.getAttribute("folders"); | 20: List files = (List)request.getAttribute("files"); | 21: String createDate = ""; | 22: String modifiedDate = ""; | 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); | | | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp | The type List is not generic; it cannot be parameterized with arguments | 21: String createDate = ""; | 22: String modifiedDate = ""; | 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); | 24: List messages = (List)request.getAttribute("messages"); | 25: %> | 26: | 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 45 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 42: | | ${n:i18n("CMS_MESSAGES")}: | 43: 44: <% 45: for (String message : messages) 46: { 47: %> 48: An error occurred at line: 142 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Type mismatch: cannot convert from Boolean to boolean 139: 140: ">${n:i18n("CMS_SECURE")} 141: <% 142: if (manageWorkflowAccessible) 143: { 144: %> 145: An error occurred at line: 270 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 267: <% 268: if (files.size() > 0) 269: { 270: for (File file : files) 271: { 272: %> 273: Stacktrace: at org.jboss.portal.portlet.impl.jsr168.api.PortletRequestDispatcherImpl.dispatch(PortletRequestDispatcherImpl.java:168) at org.jboss.portal.portlet.impl.jsr168.api.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:78) at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.internalDoView(CMSAdminPortlet.java:274) at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.doView(CMSAdminPortlet.java:184) at org.jboss.portlet.JBossPortlet.doDispatch(JBossPortlet.java:258) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:245) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:399) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:568) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:159) at org.jboss.portlet.filter.JBossPortletFilter.doFilter(JBossPortletFilter.java:79) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:159) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:80) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:505) at org.jboss.portal.portlet.container.ContainerPortletDispatcher.invoke(ContainerPortletDispatcher.java:42) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:117) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N7979132061380150447.invokeNext(TransactionInterceptor$invokeRequired_N7979132061380150447.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N7979132061380150447.invokeNext(TransactionInterceptor$invokeRequired_N7979132061380150447.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N7979132061380150447.invokeNext(TransactionInterceptor$invokeRequired_N7979132061380150447.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeRequired(TransactionInterceptor.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:74) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:49) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.SignOutInterceptor.invoke(SignOutInterceptor.java:43) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.AjaxInterceptor.invoke(AjaxInterceptor.java:49) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.BackwardCompatibilityInterceptor.invoke(BackwardCompatibilityInterceptor.java:46) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:49) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.PortletSessionSynchronizationInterceptor.invoke(PortletSessionSynchronizationInterceptor.java:82) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:48) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor.access$001(ContextDispatcherInterceptor.java:49) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor$1.doCallback(ContextDispatcherInterceptor.java:123) at org.jboss.portal.web.command.CommandDispatcher$CallbackCommand.execute(CommandDispatcher.java:74) 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.portal.web.command.CommandServlet.doGet(CommandServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505) at org.jboss.portal.web.command.CommandServlet.include(CommandServlet.java:79) at org.jboss.portal.web.command.CommandDispatcher.include(CommandDispatcher.java:50) at org.jboss.portal.web.jboss.JBossWebContext.include(JBossWebContext.java:66) at org.jboss.portal.web.impl.DefaultServletContainer.include(DefaultServletContainer.java:190) at org.jboss.portal.portlet.impl.spi.AbstractServerContext.dispatch(AbstractServerContext.java:69) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:77) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.SecureTransportInterceptor.invoke(SecureTransportInterceptor.java:69) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ValveInterceptor.invoke(ValveInterceptor.java:75) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.container.ContainerPortletInvoker.invoke(ContainerPortletInvoker.java:116) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.state.producer.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java:219) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker.org$jboss$portal$core$impl$portlet$state$ProducerPortletInvoker$invoke$aop(ProducerPortletInvoker.java:53) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java) at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerService.invoke(FederatedPortletInvokerService.java:145) at org.jboss.portal.portlet.federation.impl.FederatingPortletInvokerService.invoke(FederatingPortletInvokerService.java:149) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$1.invoke(InstanceContainerImpl.java:93) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.management.PortletContainerManagementInterceptorImpl.invoke(PortletContainerManagementInterceptorImpl.java:59) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor.invoke(PortalSessionSynchronizationInterceptor.java:93) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.model.instance.InstanceSecurityInterceptor.invoke(InstanceSecurityInterceptor.java:93) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ConsumerCacheInterceptor.invoke(ConsumerCacheInterceptor.java:162) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl.org$jboss$portal$core$impl$model$instance$InstanceContainerImpl$invoke$aop(InstanceContainerImpl.java:418) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl.invoke(InstanceContainerImpl.java) at org.jboss.portal.core.impl.model.instance.AbstractInstance.invoke(AbstractInstance.java:231) at org.jboss.portal.core.impl.model.content.InternalContentProvider.renderWindow(InternalContentProvider.java:345) at org.jboss.portal.core.model.portal.command.render.RenderWindowCommand.execute(RenderWindowCommand.java:100) at org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:124) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:134) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.BackwardCompatibilityInterceptor.invoke(BackwardCompatibilityInterceptor.java:48) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.ControlInterceptor.invoke(ControlInterceptor.java:56) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:55) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) at org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:134) at org.jboss.portal.core.model.portal.command.render.RenderWindowCommand.render(RenderWindowCommand.java:80) at org.jboss.portal.core.model.portal.command.render.RenderPageCommand.execute(RenderPageCommand.java:222) at org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:124) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:134) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.BackwardCompatibilityInterceptor.invoke(BackwardCompatibilityInterceptor.java:48) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.ControlInterceptor.invoke(ControlInterceptor.java:56) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:55) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) at org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:134) at org.jboss.portal.core.model.portal.PortalObjectResponseHandler.processCommandResponse(PortalObjectResponseHandler.java:81) at org.jboss.portal.core.controller.classic.ClassicResponseHandler.processHandlers(ClassicResponseHandler.java:79) at org.jboss.portal.core.controller.classic.ClassicResponseHandler.processCommandResponse(ClassicResponseHandler.java:53) at org.jboss.portal.core.controller.handler.ResponseHandlerSelector.processCommandResponse(ResponseHandlerSelector.java:70) at org.jboss.portal.core.controller.Controller.processCommandResponse(Controller.java:315) at org.jboss.portal.core.controller.Controller.processCommand(Controller.java:303) at org.jboss.portal.core.controller.Controller.handle(Controller.java:261) at org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:193) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.server.IdentityCacheInterceptor.invoke(IdentityCacheInterceptor.java:68) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49) at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:253) at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262) at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java) at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:69) at org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:130) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) at org.jboss.portal.server.servlet.PortalServlet.service(PortalServlet.java:252) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) org.apache.jasper.JasperException: Unable to compile class for JSP: An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 19 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 16: <% 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 20 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 17: String sConfirm = renderRequest.getParameter("confirm"); 18: String sCurrPath = (String)request.getAttribute("currpath"); 19: List folders = (List)request.getAttribute("folders"); 20: List files = (List)request.getAttribute("files"); 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp The type List is not generic; it cannot be parameterized with arguments 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 24 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, parameterized types are only available if source level is 5.0 21: String createDate = ""; 22: String modifiedDate = ""; 23: Boolean manageWorkflowAccessible = (Boolean)request.getAttribute("manageWorkflowAccessible"); 24: List messages = (List)request.getAttribute("messages"); 25: %> 26: 27: | An error occurred at line: 45 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 42: | ${n:i18n("CMS_MESSAGES")}: | 43: 44: <% 45: for (String message : messages) 46: { 47: %> 48: An error occurred at line: 142 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Type mismatch: cannot convert from Boolean to boolean 139: 140: ">${n:i18n("CMS_SECURE")} 141: <% 142: if (manageWorkflowAccessible) 143: { 144: %> 145: An error occurred at line: 270 in the jsp file: /WEB-INF/jsp/cms/admin/main.jsp Syntax error, 'for each' statements are only available if source level is 5.0 267: <% 268: if (files.size() > 0) 269: { 270: for (File file : files) 271: { 272: %> 273: Stacktrace: at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:92) at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:330) at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:415) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:308) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:286) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:273) at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:566) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505) at org.jboss.portal.portlet.impl.jsr168.api.PortletRequestDispatcherImpl.dispatch(PortletRequestDispatcherImpl.java:141) at org.jboss.portal.portlet.impl.jsr168.api.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:78) at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.internalDoView(CMSAdminPortlet.java:274) at org.jboss.portal.core.cms.ui.admin.CMSAdminPortlet.doView(CMSAdminPortlet.java:184) at org.jboss.portlet.JBossPortlet.doDispatch(JBossPortlet.java:258) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:245) at org.jboss.portlet.JBossPortlet.render(JBossPortlet.java:399) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:568) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:159) at org.jboss.portlet.filter.JBossPortletFilter.doFilter(JBossPortletFilter.java:79) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:159) at org.jboss.portal.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:80) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java:505) at org.jboss.portal.portlet.container.ContainerPortletDispatcher.invoke(ContainerPortletDispatcher.java:42) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.org$jboss$portal$core$aspects$portlet$TransactionInterceptor$invokeRequired$aop(TransactionInterceptor.java:117) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N7979132061380150447.invokeNext(TransactionInterceptor$invokeRequired_N7979132061380150447.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N7979132061380150447.invokeNext(TransactionInterceptor$invokeRequired_N7979132061380150447.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor$invokeRequired_N7979132061380150447.invokeNext(TransactionInterceptor$invokeRequired_N7979132061380150447.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invokeRequired(TransactionInterceptor.java) at org.jboss.portal.core.aspects.portlet.TransactionInterceptor.invoke(TransactionInterceptor.java:74) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.HeaderInterceptor.invoke(HeaderInterceptor.java:49) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.SignOutInterceptor.invoke(SignOutInterceptor.java:43) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.AjaxInterceptor.invoke(AjaxInterceptor.java:49) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.aspects.portlet.BackwardCompatibilityInterceptor.invoke(BackwardCompatibilityInterceptor.java:46) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.bridge.BridgeInterceptor.invoke(BridgeInterceptor.java:49) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.PortletSessionSynchronizationInterceptor.invoke(PortletSessionSynchronizationInterceptor.java:82) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ContextTrackerInterceptor.invoke(ContextTrackerInterceptor.java:48) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor.access$001(ContextDispatcherInterceptor.java:49) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor$1.doCallback(ContextDispatcherInterceptor.java:123) at org.jboss.portal.web.command.CommandDispatcher$CallbackCommand.execute(CommandDispatcher.java:74) 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.portal.web.command.CommandServlet.doGet(CommandServlet.java:130) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) 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.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:687) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:590) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:505) at org.jboss.portal.web.command.CommandServlet.include(CommandServlet.java:79) at org.jboss.portal.web.command.CommandDispatcher.include(CommandDispatcher.java:50) at org.jboss.portal.web.jboss.JBossWebContext.include(JBossWebContext.java:66) at org.jboss.portal.web.impl.DefaultServletContainer.include(DefaultServletContainer.java:190) at org.jboss.portal.portlet.impl.spi.AbstractServerContext.dispatch(AbstractServerContext.java:69) at org.jboss.portal.portlet.aspects.portlet.ContextDispatcherInterceptor.invoke(ContextDispatcherInterceptor.java:77) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.SecureTransportInterceptor.invoke(SecureTransportInterceptor.java:69) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ValveInterceptor.invoke(ValveInterceptor.java:75) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.container.ContainerPortletInvoker.invoke(ContainerPortletInvoker.java:116) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.state.producer.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java:219) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker.org$jboss$portal$core$impl$portlet$state$ProducerPortletInvoker$invoke$aop(ProducerPortletInvoker.java:53) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker$invoke_N8654503705355129869.invokeNext(ProducerPortletInvoker$invoke_N8654503705355129869.java) at org.jboss.portal.core.impl.portlet.state.ProducerPortletInvoker.invoke(ProducerPortletInvoker.java) at org.jboss.portal.portlet.federation.impl.FederatedPortletInvokerService.invoke(FederatedPortletInvokerService.java:145) at org.jboss.portal.portlet.federation.impl.FederatingPortletInvokerService.invoke(FederatingPortletInvokerService.java:149) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$1.invoke(InstanceContainerImpl.java:93) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.management.PortletContainerManagementInterceptorImpl.invoke(PortletContainerManagementInterceptorImpl.java:59) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.PortalSessionSynchronizationInterceptor.invoke(PortalSessionSynchronizationInterceptor.java:93) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.core.model.instance.InstanceSecurityInterceptor.invoke(InstanceSecurityInterceptor.java:93) at org.jboss.portal.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:82) at org.jboss.portal.portlet.aspects.portlet.ConsumerCacheInterceptor.invoke(ConsumerCacheInterceptor.java:162) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl.org$jboss$portal$core$impl$model$instance$InstanceContainerImpl$invoke$aop(InstanceContainerImpl.java:418) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl$invoke_N8654503705355129869.invokeNext(InstanceContainerImpl$invoke_N8654503705355129869.java) at org.jboss.portal.core.impl.model.instance.InstanceContainerImpl.invoke(InstanceContainerImpl.java) at org.jboss.portal.core.impl.model.instance.AbstractInstance.invoke(AbstractInstance.java:231) at org.jboss.portal.core.impl.model.content.InternalContentProvider.renderWindow(InternalContentProvider.java:345) at org.jboss.portal.core.model.portal.command.render.RenderWindowCommand.execute(RenderWindowCommand.java:100) at org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:124) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:134) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.BackwardCompatibilityInterceptor.invoke(BackwardCompatibilityInterceptor.java:48) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.ControlInterceptor.invoke(ControlInterceptor.java:56) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:55) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157) at org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:134) at org.jboss.portal.core.model.portal.command.render.RenderWindowCommand.render(RenderWindowCommand.java:80) at org.jboss.portal.core.model.portal.command.render.RenderPageCommand.execute(RenderPageCommand.java:222) at org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131) at org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:124) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:134) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78) at org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40) at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115) at org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81) at org.jboss.portal.core.con View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177751#4177751 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177751 From do-not-reply at jboss.com Sat Sep 20 06:37:08 2008 From: do-not-reply at jboss.com (leno681) Date: Sat, 20 Sep 2008 06:37:08 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - jbossws remote ws Message-ID: <7094471.1221907028582.JavaMail.jboss@colo-br-02.atl.jboss.com> We use jbossws for connecting to remote web service. Remote servise use ssl an client certificate for auth. When we try connecting to web service everytime recieve this error: 2008-09-20 11:43:23,765 ERROR [si.banka_koper.edokumenti.jobs.ArchiveDocumentJob] Error archiving document: java.io.IOException: Could not transmit message 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) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy232.initSaveDocument(Unknown Source) at si.banka_koper.edokumenti.mikrocop.MikrocopArchiveClient.archive(MikrocopArchiveClient.java:194) at si.banka_koper.edokumenti.jobs.ArchiveDocumentJob.archive(ArchiveDocumentJob.java:258) at si.banka_koper.edokumenti.jobs.ArchiveDocumentJob.archive(ArchiveDocumentJob.java:137) 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:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) at org.jboss.seam.transaction.RollbackInterceptor.aroundInvoke(RollbackInterceptor.java:31) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:46) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.async.AsynchronousInterceptor.aroundInvoke(AsynchronousInterceptor.java:50) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) at org.jboss.seam.intercept.JavaBeanInterceptor.interceptInvocation(JavaBeanInterceptor.java:166) at org.jboss.seam.intercept.JavaBeanInterceptor.invoke(JavaBeanInterceptor.java:102) at si.banka_koper.edokumenti.jobs.ArchiveDocumentJob_$$_javassist_6.archive(ArchiveDocumentJob_$$_javassist_6.java) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:125) at org.jboss.seam.async.AsynchronousInvocation.call(AsynchronousInvocation.java:52) at org.jboss.seam.async.Asynchronous.executeInContexts(Asynchronous.java:76) at org.jboss.seam.async.Asynchronous.execute(Asynchronous.java:45) at org.jboss.seam.async.QuartzDispatcher$QuartzJob.execute(QuartzDispatcher.java:240) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:529) 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) ... 37 more Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:334) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:136) 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) ... 40 more Caused by: org.jboss.ws.WSException: Invalid HTTP server response [403] - Forbidden at org.jboss.ws.core.soap.SOAPMessageUnMarshaller.read(SOAPMessageUnMarshaller.java:77) at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:502) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:306) ... 45 more Anybody know how to resolve this error? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177796#4177796 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177796 From do-not-reply at jboss.com Sat Sep 20 16:48:33 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Sat, 20 Sep 2008 16:48:33 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: problems with mtom and soap version 1.2 Message-ID: <24036007.1221943713607.JavaMail.jboss@colo-br-02.atl.jboss.com> Are you using the http://www.w3.org/2003/05/soap/bindings/HTTP/?mtom=true binding ID in the @BindingType ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177842#4177842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177842 From do-not-reply at jboss.com Sat Sep 20 16:54:18 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Sat, 20 Sep 2008 16:54:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: No sources for post 3.0.1 releases ? Message-ID: <5518060.1221944058348.JavaMail.jboss@colo-br-02.atl.jboss.com> https://jira.jboss.org/jira/browse/JBWS-2286 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177843#4177843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177843 From do-not-reply at jboss.com Sat Sep 20 18:15:13 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Sat, 20 Sep 2008 18:15:13 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Confused by JBossWS versioning Message-ID: <13548552.1221948913811.JavaMail.jboss@colo-br-02.atl.jboss.com> When we started releasing jbossws integration with Metro and CXF, the release major number was increased, thus we had 3.0.1. The native stack was previously meant to be named 2.0.4, so we used the double naming. We later decided to drop the double naming because it seemed too confusing and went on using the same name versioning for each stack integration. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177845#4177845 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177845 From do-not-reply at jboss.com Mon Sep 22 05:18:52 2008 From: do-not-reply at jboss.com (Vishnu1789) Date: Mon, 22 Sep 2008 05:18:52 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - How to send multiple attachments in a single web service cal Message-ID: <11053585.1222075132621.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, I had a requirement to send multiple documents in a single web service call . this is the web service i am trying to expose @WebMethod sendDocuments(String xmlStr, javax.activation.DataHandler[] documentData) or @WebMethod sendDocuments(String xmlStr,List documentData) I am able to attach multiple documents from client side and those attachments are reaching server side also. but in both cases documentData.inputStream has zero bytes of data. can any one help me to send multi documents Regards, Vishnu View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177965#4177965 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177965 From do-not-reply at jboss.com Mon Sep 22 06:50:10 2008 From: do-not-reply at jboss.com (anatolyg) Date: Mon, 22 Sep 2008 06:50:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - jbosws integration layers for JBoss application server 4.3.G Message-ID: <4452643.1222080610661.JavaMail.jboss@colo-br-02.atl.jboss.com> 1) You wrote: "Currently, we have integration layers for the JBoss application server 4.2 and 5.0." We are using JBoss application server 4.3.GA Is it a way to get it working with Jboss 4.3.GA? 2) Second question, Can you clarify: After installation of Jboss 4.3. i have JBoss-4.3.GA_Stargate\server\default\deploy\jbossws.sar What is difference between this framework and JBoss Web Services framework that is not part of installation of Jboss? Isn't is conflicts? Can i disable jbossws.sar in some way? Regards Anatoly View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178000#4178000 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178000 From do-not-reply at jboss.com Mon Sep 22 08:12:26 2008 From: do-not-reply at jboss.com (Marlboro) Date: Mon, 22 Sep 2008 08:12:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JBossWS 3.0.3 with heavy load Message-ID: <11540102.1222085546505.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello I have troubles with JBossWS 3.0.3 with heavy load. Our application which uses JBossWS can run with heavy load approximately 3 minutes but after that server throws BindException. Have somebody any idea or same experience? Thanks. Configuration: JBoss 4.2.2 GA + JBossWS 3.0.3 + JDK 1.5 also tested on JDK 1.6 Windows server 2003, 4 GB ram, 2x quad core Intel Xeon Stacktrace follows: 2008-09-18 12:34:36,546 ERROR [com.upek.services.web.AuthSvcServlet] Exception encountered invoking sendReceivePacket java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1205.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.upek.services.web.AuthSvcServlet.doPost(AuthSvcServlet.java:135) 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 com.upek.services.exceptions.ErrorObfuscationFilter.doFilter(ErrorObfuscationFilter.java:52) 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:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) 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) Caused by: com.upek.services.exceptions.ServiceException: java.io.IOException: Could not transmit message at com.upek.services.beans.EnrollerBean.sendReceivePacket(EnrollerBean.java:496) at sun.reflect.GeneratedMethodAccessor755.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.ExtendedPersistenceContextPropagationInterceptor.invoke(ExtendedPersistenceContextPropagationInterceptor.java:57) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateful.StatefulInstanceInterceptor.invoke(StatefulInstanceInterceptor.java:83) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:110) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:206) at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:119) at $Proxy107.sendReceivePacket(Unknown Source) at com.upek.services.web.AuthSvcServlet.sendReceivePacket(AuthSvcServlet.java:552) ... 28 more Caused by: javax.xml.ws.WebServiceException: java.io.IOException: Could not transmit message at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:397) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:303) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150) at $Proxy202.keyProvision(Unknown Source) at com.upek.services.beans.EnrollerBean.sendReceivePacket(EnrollerBean.java:492) ... 59 more Caused by: java.io.IOException: Could not transmit message at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:264) at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:340) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:291) ... 63 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.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:242) ... 66 more Caused by: java.net.BindException: Address already in use: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:519) at sun.net.NetworkClient.doConnect(NetworkClient.java:152) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:788) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:729) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:654) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:275) ... 71 more View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178030#4178030 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178030 From do-not-reply at jboss.com Mon Sep 22 08:59:47 2008 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 22 Sep 2008 08:59:47 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: jbosws integration layers for JBoss application server 4 Message-ID: <33169570.1222088387696.JavaMail.jboss@colo-br-02.atl.jboss.com> "anatolyg" wrote : 1) | | You wrote: | "Currently, we have integration layers for the JBoss application server 4.2 and 5.0." | | We are using JBoss application server 4.3.GA | | Is it a way to get it working with Jboss 4.3.GA? Yes, you have to download JBossWS 3.0.3 release and install it separately to AS 4.3 "anatolyg" wrote : | 2) Second question, | | Can you clarify: | | After installation of Jboss 4.3. i have | JBoss-4.3.GA_Stargate\server\default\deploy\jbossws.sar | | What is difference between this framework and JBoss Web Services framework that is not part of installation of Jboss? | | Isn't is conflicts? | Can i disable jbossws.sar in some way? | Sorry, I don't understand your 2-nd question. AFAIK jbossws.sar is part of AS 4.2.3 installation and when you upgrade to JBossWS 3.0.3, there still will be jbossws.sar directory in deploy directory. JBossWS 3.0.3 upgrade is always correct, just follow installation intructions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178041#4178041 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178041 From do-not-reply at jboss.com Mon Sep 22 13:57:26 2008 From: do-not-reply at jboss.com (jorgemoralespou_2) Date: Mon, 22 Sep 2008 13:57:26 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Open file descriptors to wsdl Message-ID: <7715619.1222106246488.JavaMail.jboss@colo-br-02.atl.jboss.com> I'm using JBossAS 4.2.2 with jbossws-native-3.0.2.GA. I have deployed a service and it is leaving file descriptors open for the wsdl. I was using jbossws-native 2.0.3 and I didn have this problem, but I have recently upgraded to 3.0.2 and this problem arrised. I haven't changed this service, but some other services (so the upgrade). I'm running on a HP-UX 11.23, and when see open file descriptors, I see an increassing number for a .wsdl, like the following line: | som at mymachine: lsof -usom | grep wsdl | | java 8640 som 965u REG 64,0x9 5638 29804 /core/server/som/data/wsdl/100persa-ws.ear/persa-ws-1.3.2.war/SpiPersa1478.wsdl | java 8640 som 967u REG 64,0x9 5638 29804 /core/server/som/data/wsdl/100persa-ws.ear/persa-ws-1.3.2.war/SpiPersa1478.wsdl | java 8640 som 970u REG 64,0x9 5638 29804 /core/server/som/data/wsdl/100persa-ws.ear/persa-ws-1.3.2.war/SpiPersa1478.wsdl | Has anyone had a similar problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178130#4178130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178130 From do-not-reply at jboss.com Tue Sep 23 10:33:18 2008 From: do-not-reply at jboss.com (zaiwengong) Date: Tue, 23 Sep 2008 10:33:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Jbossws Sample build failed Message-ID: <20311694.1222180398215.JavaMail.jboss@colo-br-02.atl.jboss.com> Any one help me? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178345#4178345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178345 From do-not-reply at jboss.com Tue Sep 23 11:03:11 2008 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Tue, 23 Sep 2008 11:03:11 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Jbossws Sample build failed Message-ID: <11898417.1222182191344.JavaMail.jboss@colo-br-02.atl.jboss.com> AFAIK jbossws-1.2.1.GA isn't supported on JBoss 4.0.5.GA. Here's the link of supported AS versions: http://jbossws.jboss.org/mediawi/index.php?title=Supported_Target_Containers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178358#4178358 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178358 From do-not-reply at jboss.com Tue Sep 23 11:27:21 2008 From: do-not-reply at jboss.com (asos) Date: Tue, 23 Sep 2008 11:27:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Porting Weblogic 8.x web services to JBoss 4.2.3 Message-ID: <4579299.1222183641587.JavaMail.jboss@colo-br-02.atl.jboss.com> I'd like to know if anyone has had to port Weblogic web services over to a JBoss environment? The web services I'm dealing with appear to be a specific Weblogic implementation. The source modules have a ".jws" extension and contain annotations through out. Is there a utility that can be used to convert the module over to a more standard Java Web Service? If not, can anyone recommend a procedure for converting such a module? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178363#4178363 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178363 From do-not-reply at jboss.com Tue Sep 23 13:29:43 2008 From: do-not-reply at jboss.com (alessio.soldano@jboss.com) Date: Tue, 23 Sep 2008 13:29:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Username Token Profile URIs in SOAP header not compatibl Message-ID: <16876633.1222190983890.JavaMail.jboss@colo-br-02.atl.jboss.com> This issue is fixed on trunk now. It would be great if you could build from sources and give it a try and see if you can correctly talk with the .NET impl now. Thanks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178388#4178388 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178388 From do-not-reply at jboss.com Wed Sep 24 02:22:18 2008 From: do-not-reply at jboss.com (alllle) Date: Wed, 24 Sep 2008 02:22:18 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Logging the soap messages before and after applying ws-secur Message-ID: <10078444.1222237338982.JavaMail.jboss@colo-br-02.atl.jboss.com> I have tried enable TRACE logging as well as using the JBossWS records discussed http://jbossws.jboss.org/mediawiki/index.php?title=Records_management, both of them only show the message with the encryption / signing, not the decrypted message. I wonder if there is any logging from the WS-Security handlers that can be turned on to show the decrypted messages so I can verify if the message content is correct or not? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178461#4178461 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178461 From do-not-reply at jboss.com Wed Sep 24 09:56:43 2008 From: do-not-reply at jboss.com (gressho) Date: Wed, 24 Sep 2008 09:56:43 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - timestamp and WS-Security Message-ID: <30002188.1222264603564.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, since JBossWS 3.0.2 a timestamp-verification tag is available. So I've deployed a server configuration file like the following: | | META-INF/ikmapp.jks | xxx | jks | META-INF/wsse10.truststore | xxx | | | | | | | | | | | The result is questionable. I'm calling a service and get an exception. The log claims the message is from the future. When I update the time of my system by ntp I receive normally a variance of about -0.052230 sec and fewer! I even tried to deactivate timestamps on my client but with no result. Our server is a cluster based on JBoss 4.2.3 (JDK 6) with JBossWS 3.0.3 installed. Has anybody a solution for this? Best wishes Werner View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178580#4178580 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178580 From do-not-reply at jboss.com Wed Sep 24 12:22:49 2008 From: do-not-reply at jboss.com (sr_ren) Date: Wed, 24 Sep 2008 12:22:49 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: consume WS error after update to JBossWS 2.0 Message-ID: <31641838.1222273369132.JavaMail.jboss@colo-br-02.atl.jboss.com> I followed this thread and removed jaxws-rt.jar and jaxws-tool.jar from JBOSS_HOME/client and copied xercesImpl.jar from JBOSS_HOME/lib/endorsed and it solve the problem for me. BTW, what are the minimum jars needed on the client to run a webservice? Thanks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178609#4178609 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178609 From do-not-reply at jboss.com Wed Sep 24 22:47:40 2008 From: do-not-reply at jboss.com (alllle) Date: Wed, 24 Sep 2008 22:47:40 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: timestamp and WS-Security Message-ID: <19544737.1222310860707.JavaMail.jboss@colo-br-02.atl.jboss.com> I think the timestamp-verification tag is out side of the config tag. Something like this: | META-INF/ikmapp.jks | xxx | jks | META-INF/wsse10.truststore | xxx | | | | | | | | | | The setting works as we just deployed a soap service and using this setting to avoid the "future timestamp" exception. Not sure if the existing is still needed or not but we removed it. It would be nice to have the XSD published... the schema location given is not valid. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178667#4178667 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178667 From do-not-reply at jboss.com Wed Sep 24 23:35:37 2008 From: do-not-reply at jboss.com (alllle) Date: Wed, 24 Sep 2008 23:35:37 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - WS client uses password from WSDL, ignoring client side sett Message-ID: <32625551.1222313737073.JavaMail.jboss@colo-br-02.atl.jboss.com> I am using JBossWS WS-Security. Server side has settings like this: jboss-wsse-server.xml | | /etc/security/wsse.keystore | | {CLASS}org.jboss.security.plugins.FilePassword:/etc/security/wsse-keystore.password | | /etc/security/wsse.truststore | | {CLASS}org.jboss.security.plugins.FilePassword:/etc/security/wsse-truststore.password | | | | | | | | | | | | As you can see, the password is not stored as clear text for enhanced security. It uses FilePassword, which is a utility class provided by JBoss. This security setting is published in the service wsdl file and all above settings are visible to the clients: Segment of the published wsdl file: | | | | /etc/security/wsse.keystore | | {CLASS}org.jboss.security.plugins.FilePassword:/etc/security/wsse-keystore.password | | /etc/security/wsse.truststore | | {CLASS}org.jboss.security.plugins.FilePassword:/etc/security/wsse-truststore.password | | | | | | | | | | | | | | | At the client side, we set the wsse system properties like this: | System.setProperty("org.jboss.ws.wsse.keyStore", "c:/wsse/wsse.keystore" ) | System.setProperty("org.jboss.ws.wsse.keyStorePassword", "{CLASS}org.jboss.security.plugins.FilePassword:c:/wsse/wsse-keystore.password" ) | System.setProperty("org.jboss.ws.wsse.keyStoreType", "jks" ) | System.setProperty("org.jboss.ws.wsse.trustStore", "c:/wsse/wsse.truststore" ) | System.setProperty("org.jboss.ws.wsse.trustStorePassword", "{CLASS}org.jboss.security.plugins.FilePassword:c:/wsse/wsse-truststore.password" ) | System.setProperty("org.jboss.ws.wsse.trustStoreType", "jks" ) | What happened was that the client side system property is partially used. It picked up the store locations, however, it uses the serverside store password settings obtained from the wsdl. In other words, it tries to lookup the password file at /etc/security/wsse-keystore.password and /etc/security/wsse-truststore.password instead of the local c:/wsse folder. When I trace into the code, it looks like the class WSSecurityHandler.handleOutboundSecurity() uses the msgContext to create a WSSecurityConfiguration object. This object has the server security settings published in the wsdl. The local settings (from the system property) are not used unless the setting is not set by the server wsdl. In my specific case, because the server uses the and tag, it sets the keyStoreFile and trustStoreFile properties of the configuration object, and left the keyStoreUrl and trustStoreUrl properties of the configuration object null. And later on, it tries to use the configuration object's keyStoreUrl and trustStoreUrl properties, which are null, so it thinks it's not set by the server and then looked up the keystore file locations from the local system properties. But for the keyStorePassword and trustStorePassword properties of the configuration object, since they are not null (set to the server settings from the wsdl), it completely ignores the local system property settings and use those values from server at the client side. Because the password files are stored in different folders at the client side, it errors out due to FileNotFoundException. Part of the above mentioned logics are in the SecurityStore class. I think this is a serious bug, as one can not dictates that the client must store the key store files and password files at the same folder as the server. At the client side, it needs to pick up the security settings from the system properties instead of looking them up from the wsdl first. If someone from JBoss team can validate what I described, can we open an issue ticket for this? Thanks! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178669#4178669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178669 From do-not-reply at jboss.com Thu Sep 25 02:06:21 2008 From: do-not-reply at jboss.com (gressho) Date: Thu, 25 Sep 2008 02:06:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: timestamp and WS-Security Message-ID: <32801273.1222322781288.JavaMail.jboss@colo-br-02.atl.jboss.com> Oh, great, it works now as expected!!! Think you're right, the XSD should be published. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178683#4178683 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178683 From do-not-reply at jboss.com Thu Sep 25 03:51:32 2008 From: do-not-reply at jboss.com (KickMeToAndy) Date: Thu, 25 Sep 2008 03:51:32 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - how to pass data from a GenericSOAPHandler to a LoginModule Message-ID: <27198360.1222329092084.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello, i was wondering if it is possible to pass information (username, password) from a custom GenericSOAPHandler to a JBoss LoginModule. In our SOAP Handler we extract the username, password from the wssecurity header in the soap message. We want the username and password to be validated by the LoginModule configured for the security Domain in the login-config.xml. So is it possible to pass the username/password information from the SoapHandler to the LoginModule ? And how can it be done ? thanks in advance, cheers, andy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178699#4178699 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178699 From do-not-reply at jboss.com Thu Sep 25 08:11:34 2008 From: do-not-reply at jboss.com (anatolyg) Date: Thu, 25 Sep 2008 08:11:34 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: jbosws integration layers for JBoss application server 4 Message-ID: <5326429.1222344694456.JavaMail.jboss@colo-br-02.atl.jboss.com> 1) Is it a way to get it working with Jboss 4.3.GA? 2) We integrated CXF webservice with Jboss 4.3.GA very easy. What is motivation to install additional framework JBossWS 3.0.3 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178779#4178779 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178779 From do-not-reply at jboss.com Thu Sep 25 11:12:07 2008 From: do-not-reply at jboss.com (adinn) Date: Thu, 25 Sep 2008 11:12:07 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Race Condition in WS Endpoint Startup Message-ID: <20075577.1222355527763.JavaMail.jboss@colo-br-02.atl.jboss.com> I have a crash recovery test which employs two JBoss AS instances, call them A and B each running a JaxWS app, call them AppA and AppB. I arrange for a crash to happen in B when AppA first tries to invoke JaxWS service SB published by AppB. AppA makes repeated attempts to invoke a service SB, resending a request about once every 5 seconds. When B reboots the WS code deploys endpoints for service SB plus several other services SB1, SB2 etc. Some of these other endpoints are deployed before SB. So, an endpoint for SB (instance of class DefaultEndpoint) exists in state CREATED while SB1, SB2, etc are being transitioned from CREATED to STARTED by class UnifiedMetaDataDeploymentAspect. When a request comes in from AppA the request handling code calls startEndpoint and SB transitions to state STARTED even though UnifiedMetaDataDeploymentAspect has not initialised the endpoint. The requests fail initially with this error | 15:35:53,470 ERROR [[Participant]] Servlet.service() for servlet Participant threw exception | java.lang.IllegalStateException: Deployment has no classloader associated | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:197) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:91) | at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:92) | 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:325) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) | This eventually gets resolved (not sure exactly how but it doesn't help :-). Subsequent requests fail with a different error because the endpoint has no associated metadata (UnifiedMetaDataDeploymentAspect has not yet added it as an attachment) | 15:36:03,752 ERROR [RequestHandlerImpl] Error processing web service request | java.lang.IllegalStateException: Cannot obtain endpoint meta data | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:240) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:205) | at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:131) | at org.jboss.wsf.stack.jbws.EndpointServlet.service(EndpointServlet.java:81) | at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) | at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) | at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) | at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235) | at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) | at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:189) | at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:91) | at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:92) | 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:325) | at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:828) | at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:601) | at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) | at java.lang.Thread.run(Thread.java:595) | Finally, UnifiedMetaDataDeploymentAspect gets round to initialising the endpoint for SB and calls addAttachment(). This throws up because the endpoint is already in state STARTED and it expects it to be in state CREATED so it asserts. | 15:36:10,623 ERROR [AbstractKernelController] Error installing to Real: name=vfszip:/home/adinn/jboss/jbossas/JBoss_5_0_0_CR2/build/output/jboss-5.0.0.CR2/server/default2/deploy/jbossxts.sar state=PreReal mode=Manual requiredState=Real | org.jboss.deployers.spi.DeploymentException: Error during deploy: vfszip:/home/adinn/jboss/jbossas/JBoss_5_0_0_CR2/build/output/jboss-5.0.0.CR2/server/default2/deploy/jbossxts.sar/ws-t11.war | at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:175) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1285) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1003) | at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1056) | at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:944) | 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:627) | at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:541) | at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:290) | at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221) | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417) | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:280) | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:135) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:65) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:142) | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:166) | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) | at java.lang.Thread.run(Thread.java:595) | Caused by: java.lang.IllegalStateException: Cannot modify endpoint properties in state: STARTED | at org.jboss.wsf.framework.deployment.DefaultEndpoint.assertEndpointSetterAccess(DefaultEndpoint.java:269) | at org.jboss.wsf.framework.deployment.DefaultEndpoint.addAttachment(DefaultEndpoint.java:241) | at org.jboss.wsf.stack.jbws.UnifiedMetaDataDeploymentAspect.start(UnifiedMetaDataDeploymentAspect.java:88) | at org.jboss.wsf.framework.deployment.DeploymentAspectManagerImpl.start(DeploymentAspectManagerImpl.java:144) | at org.jboss.wsf.container.jboss50.BareWSFRuntime.start(BareWSFRuntime.java:66) | at org.jboss.wsf.container.jboss50.deployer.JAXWSDeployerHookPostJSE.deploy(JAXWSDeployerHookPostJSE.java:51) | at org.jboss.wsf.container.jboss50.deployer.AbstractWebServiceDeployer.internalDeploy(AbstractWebServiceDeployer.java:60) | at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50) | at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169) | ... 24 more | At this point the deployment backs out all of AppB's services. So, the problem is that the endpoint has been made visible as a target for requests when it is not yet fully configured. This will not normaly show up because it requires a request to arrive between publishing the CREATED endpoint and setting its WS metadat. This could be solved by adding a state between CREATED and STARTED called, for example, READY. State READY would only be transitioned to by UnifiedMetaDataDeploymentAspect once it had called addAttachment to complete initialisaton of the endpoint. If a request finds a READY endpoint it can start it. If it finds a CREATED endpoint it should throw an error to ensure that the request is rejected. Another alternative is to avoid exposing the CREATED endpoint until it is fully initialised (I assume the reason for exposing endpoints at all when they are in this state is to cater for the web.xml setting load-on-startup=0). This may be feasible but appears like it would require more rework. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178852#4178852 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178852 From do-not-reply at jboss.com Fri Sep 26 04:14:55 2008 From: do-not-reply at jboss.com (ajayks) Date: Fri, 26 Sep 2008 04:14:55 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Unable to connect webservice deployed on JBOSS AS version 4. Message-ID: <25350548.1222416895623.JavaMail.jboss@colo-br-02.atl.jboss.com> Hello all, I have created EJB3.0 stateteless session bean named "Greeting" as a webservice using JAX-WS specifcation. This web service simply returning the parameter what is sent to it. I am successfully able to deploy the created web service on JBOSS application server 4.2.2 and the WSDL file is successfully created by the application server. When I tred to invoke the the deployed webservice from java client ,I am not gettig reference of Service object. I am using following code to get reference of Service object :- String url="http://dlhlx09.dlh.st.com:20120/mywebservice/Greeting?wsdl"; URL wsdlLocation=new URL(url); QName serviceName = new QName("http://ccc/", "GreetingService"); Service service = Service.create(wsdlLocation, serviceName); The Service.create call is returning null reference. The following is the content of the WSDL file created by the JBOSS :- can any one help me out what is going wrong here.How can I invoke webservice deployed on JBOSS from a java client. with best regards, Ajay kumar View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178988#4178988 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4178988 From do-not-reply at jboss.com Fri Sep 26 06:09:39 2008 From: do-not-reply at jboss.com (bortx) Date: Fri, 26 Sep 2008 06:09:39 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Open file descriptors to wsdl Message-ID: <12696023.1222423779074.JavaMail.jboss@colo-br-02.atl.jboss.com> Tested on jbossws 3.0.3 and had the same problem. Each request results on a file descriptor open. For this reason application reaches maximum file descriptors allowed and fails every request. Any suggestion on where should we have a look in order to solve this problem will be very appreciated. Thanks a lot! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179026#4179026 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179026 From do-not-reply at jboss.com Sat Sep 27 14:14:09 2008 From: do-not-reply at jboss.com (ajayks) Date: Sat, 27 Sep 2008 14:14:09 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Not getting instance of Service object from a WSDL file. Message-ID: <9787103.1222539249078.JavaMail.jboss@colo-br-02.atl.jboss.com> I exposed a stateless EJB3.0 as a web service as per JAX-WS specification. I deployed the web service on JBOSS 4.2.2 Application server which created the corresponding WSDL file successfully .I can see the produced WSDL file for the deployed Web service. I tried to consume the deployed web service from a java client using following steps :- String url="http://dlhlx09.dlh.st.com:20120/mywebservice/Greeting?wsdl"; URL wsdlLocation=new URL(url); QName serviceName = new QName("http://ccc/", "GreetingService"); Service service = Service.create(wsdlLocation, serviceName); But I am getting the static create method of Service class returning null instance of Service object. I do not understand why the create method returning null instance of Service object. Should I need to install some patch JAX-WS implementation of JBOSS? Can any one help me out waht is the problem why I am getting null value for instance of Service object. best regards, Ajay Kumar, ST Microelectronics Ltd. Noida,India. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179204#4179204 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179204 From do-not-reply at jboss.com Sun Sep 28 13:32:21 2008 From: do-not-reply at jboss.com (PeterJ) Date: Sun, 28 Sep 2008 13:32:21 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service object from a WSDL file. Message-ID: <6016303.1222623141359.JavaMail.jboss@colo-br-02.atl.jboss.com> It is easier if you use wsconsume to generate the client stubs. Then your client code would be something like: GreetingService svc = new GreetingService(); Greeting g = svc.getGreetingPort(); I was going to dig through the source code generated by wsconsume to correct your code, but you can do that just as easily so I will leave it as an exercise for you. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179237#4179237 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179237 From do-not-reply at jboss.com Mon Sep 29 00:54:46 2008 From: do-not-reply at jboss.com (ajayks) Date: Mon, 29 Sep 2008 00:54:46 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service object from a WSDL file. Message-ID: <10426736.1222664086461.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks a lot peter for the reply. I created the client stub for the my deployed web service and I called the webservice with the help following code :- GreetingService greetingSrv = new GreetingService(); Greeting greeting =greetingSrv.getGreetingPort(); But I am getting following run time exeception :- Unable to load Provider: Failed to load javax.xml.ws.spi.Provider: com.sun.xml.ws.spi.ProviderImpl Could please help me to know how can I load provider as specified in the above exeception.I have included all the jars in the client application and there is no compilation error. best regards, Ajay Kumar, ST Microelectronics Ltd, Noida,India. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179259#4179259 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179259 From do-not-reply at jboss.com Mon Sep 29 07:40:10 2008 From: do-not-reply at jboss.com (jimpo) Date: Mon, 29 Sep 2008 07:40:10 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - jboss.xml wsdl-override works with one JBoss version, but no Message-ID: <21828231.1222688410498.JavaMail.jboss@colo-br-02.atl.jboss.com> I try to override my @WebServiceRef wsdl location using jboss.xml and wsdl-location. This works fine with portal 2.6.4 which is deployed on JBossAS 4.2.1GA but override is not being done with bundled portal 2.6.6 (JBossAS 4.2.3GA). One of my EJBs: | @WebServiceRef(com.fooz.baz.webservice.vacationrequest.VacationRequestService_Service.class) | private transient VacationRequestService vacationRequestService; | | @WebServiceRef(com.fooz.baz.webservice.employee.EmployeeService_Service.class) | private transient EmployeeService employeeService; jboss.xml excerpt: | ApplicationListingAction | | com.fooz.baz.portlet.searchandapply.ApplicationListingAction/vacationRequestService | http://remoteserver:8080/service/vacation?wsdl | | | com.fooz.baz.portlet.searchandapply.ApplicationListingAction/employeeService | http://remoteserver:8080/employee-service/employee?wsdl | | | | When this is deployed on JBoss4.2.1GA I see what name the servicerefs get, and am able to use the same name in jboss.xml service-ref-name: | 14:14:13,722 INFO [EJBContainer] STARTED EJB: com.fooz.baz.portlet.freetextsearch.SearchAction ejbName: SearchAction | 14:14:13,725 INFO [JmxKernelAbstraction] creating wrapper delegate for: org.jboss.ejb3.stateful.StatefulContainer | 14:14:13,726 INFO [JmxKernelAbstraction] installing MBean: jboss.j2ee:ear=portlets.ear,jar=ejb.jar,name=ManagerApplicationEditAction,service=EJB3 with dependen | cies: | 14:14:13,739 INFO [ServiceRefHandlerJAXWS] setupServiceRef [jndi=/env/com.fooz.baz.portlet.manager.ManagerApplicationEditAction/vacationRequestProcess,tar | get=com.fooz.baz.webservice.vacationrequestprocess.VacationRequestProcess] | 14:14:13,742 INFO [ServiceRefHandlerJAXWS] setupServiceRef [jndi=/env/com.fooz.baz.portlet.manager.ManagerApplicationEditAction/employeeService,target=com | .fooz.baz.webservice.employee.EmployeeService] | 14:14:13,743 INFO [ServiceRefHandlerJAXWS] setupServiceRef [jndi=/env/com.fooz.baz.portlet.manager.ManagerApplicationEditAction/fortimeVacationService,tar But none of that is displayed when I deploy on JBoss 4.2.3 GA. When I ttry to use the EJB I see that the override ("remoteserver") is not working and instead the original wsdl ("localhost") location is used: | 14:25:38,497 INFO [STDOUT] DEBUG ApplicationListingAction.create(108) | Creating | 14:25:38,642 WARN [ServiceDelegateImpl] Cannot access wsdlURL: http://localhost:8080/employee-service/employee?wsdl | 14:25:38,644 WARN [ServiceDelegateImpl] Cannot get port meta data for: {http://www.ugu.fi/soa-poc/EmployeeServiceWSDL}EmployeeServiceSOAP | 14:25:38,749 WARN [ServiceDelegateImpl] Cannot access wsdlURL: http://localhost:8080/service/vacation?wsdl | 14:25:38,751 WARN [ServiceDelegateImpl] Cannot get port meta data for: {http://www.ugu.fi/soa-poc/VacationRequestServiceWSDL}VacationRequestServiceSOAP | 14:25:38,917 INFO [STDOUT] DEBUG ApplicationListingAction.create(108) | Creating | 14:25:39,001 ERROR [STDERR] 29.9.2008 14:25:38 com.sun.facelets.FaceletViewHandler handleRenderException | SEVERE: Error Rendering View[/pages/apply/applicationList.xhtml] | javax.ejb.EJBTransactionRolledbackException: org.jboss.ws.WSException: Target endpoint address not set | at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) | at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) | at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) Also I think I should be able to see the webservice-ref in the JNDI using JMXConsole -> JNDIView, but neither server displays the webservice-refs there, why? How could I see which JNDI name the webservice-refs are bound to? I have also tried adding "name" and "mappedName" attributes to the WebServiceRef annotation and using the same value as service-ref-name, without success. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179336#4179336 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179336 From do-not-reply at jboss.com Mon Sep 29 07:57:58 2008 From: do-not-reply at jboss.com (richard.opalka@jboss.com) Date: Mon, 29 Sep 2008 07:57:58 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Open file descriptors to wsdl Message-ID: <5474058.1222689478204.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi guys, thank you for pointing that out. This will be fixed with 3.0.4 release, see: JBWS-2325. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179339#4179339 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179339 From do-not-reply at jboss.com Mon Sep 29 08:52:20 2008 From: do-not-reply at jboss.com (jimpo) Date: Mon, 29 Sep 2008 08:52:20 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: jboss.xml wsdl-override works with one JBoss version, bu Message-ID: <12928338.1222692740987.JavaMail.jboss@colo-br-02.atl.jboss.com> It looks to me as if the wsdl-override would be completely disregarded from jboss.xml. I looked at the logs and it seems the webservice-refs are bound to same names as before. But the override just does not seem to be happening at all. Any ideas why this is? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179359#4179359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179359 From do-not-reply at jboss.com Mon Sep 29 11:11:47 2008 From: do-not-reply at jboss.com (PeterJ) Date: Mon, 29 Sep 2008 11:11:47 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service object from a WSDL file. Message-ID: <33241986.1222701107622.JavaMail.jboss@colo-br-02.atl.jboss.com> Are you using wsrunclient to run your client? I have found that the wsrunclient script does not include all of the JARs needed to run a web services client. Here is how I set the classpath (this is for JBoss AS 5.0.0.CR2, the actual list might be different for 4.2.2): ## Initialize the environment: | CLASSPATH=myclient.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossall-client.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-native-jaxws.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-native-core.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-native-jaxws-ext.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-spi.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-common.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/wsdl4j.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jboss-xml-binding.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-native-jaxrpc.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/activation.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jbossws-native-saaj.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/mail.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/policy.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jaxb-api.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/javassist.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/jaxb-impl.jar | CLASSPATH=$CLASSPATH:$JBOSS_HOME/client/stax-api.jar | | ## Invoke the application, letting the user know what is being run: | APP="$JBOSS_HOME/bin/wsrunclient.sh -classpath $CLASSPATH my.package.name.Client $*" | echo $APP | $APP View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179404#4179404 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179404 From do-not-reply at jboss.com Tue Sep 30 00:15:38 2008 From: do-not-reply at jboss.com (ajayks) Date: Tue, 30 Sep 2008 00:15:38 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service object from a WSDL file. Message-ID: <20734650.1222748138723.JavaMail.jboss@colo-br-02.atl.jboss.com> Thanks a lot peter for the reply. I am new in JbossWS and I am evaluating it for the use in our organization. 1.I did not call the web service using wsrunclient.I called it from simple java program. I found some of the the jars specified by you like jbossws-native-jaxws.jar is not available in my $JBOSS_HOME/client directory. I using JBOSS-4.2.2 application server. Should I need to install jobss JAX-WS patch for the JBOSS- 4.2.2 application server in order to run the web service.If yes, which version of jobss JAX-WS I need to install. 2.Normally a web service would be called from any environment and platform.I want to call it by using WSDL generated.Why I am getting null Service object when I tried to call the web service from its WSDL file using below code ? -- String url="http://dlhlx09.dlh.st.com:20120/mywebservice/Greeting?wsdl"; URL wsdlLocation=new URL(url); QName serviceName = new QName("http://ccc/", "GreetingService"); Service service = Service.create(wsdlLocation, serviceName); Is it only issue of JAX-WS patch which need to be installed.? best regards, Ajay kumar, ST Microleectronics Ltd., Noida,India. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179466#4179466 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179466 From do-not-reply at jboss.com Tue Sep 30 00:40:15 2008 From: do-not-reply at jboss.com (maffeis) Date: Tue, 30 Sep 2008 00:40:15 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - SOAP calls done with native stack blocked by SmartDefense fi Message-ID: <31463391.1222749615300.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi I would like to inform you of an issue I encountered while deploying JBoss and JBossWS (native) at a bank. The bank uses the SmartDefense intrusion detection system, and SmartDefense blocks SOAP calls done via the JBossWS native stack because of a "non-compliant HTTP header". The only details we could get from the intrusion detection system is that a header contains non-ascii data (our URLs, headers, payload does not contain any funny characters). Sorry but I have no further details nor dumps. Of course that could also be a bug in the intrusion detection system, but it was not possible to overcome the issue. So I replaced the native stack by metro and the issue went away. Not sure whether my input is valuable to the JBossWS team but I felt I should let you know of this issue, as other deployments might be affected as well. Silvano View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179469#4179469 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179469 From do-not-reply at jboss.com Tue Sep 30 10:45:44 2008 From: do-not-reply at jboss.com (jopersson) Date: Tue, 30 Sep 2008 10:45:44 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - JbossWS from ip address to host name Message-ID: <19407639.1222785945006.JavaMail.jboss@colo-br-02.atl.jboss.com> Hi, Running Swing client endorsed from Jboss-4.2.3-GA release with JbossWS (native) it works fine when using server ip adderss : POST /KService HTTP/1.1 SOAPAction: "" Content-Type: text/xml; charset=UTF-8 JBoss-Remoting-Version: 22 User-Agent: JBossRemoting - 2.2.2.SP8 Host: 192.168.0.1:8080 Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 Connection: keep-alive Content-Length: 749 0121020USR 12345 0121020USR 12345aa When trying to switch to host name getting Exception: 2008-09-30 16:07:42,682 WARN [org.jboss.ws.core.client.HTTPRemotingConnection] - Ignore 'javax.xml.ws.security.auth.password' with auth typy: org.jboss.ws.authType.wsse 2008-09-30 16:07:42,682 WARN [org.jboss.ws.core.client.HTTPRemotingConnection] - Ignore 'javax.xml.ws.security.auth.username' with auth typy: org.jboss.ws.authType.wsse 2008-09-30 16:07:47,823 ERROR [org.jboss.ws.core.jaxws.SOAPFaultHelperJAXWS] - SOAP request exception java.io.IOException: Could not transmit message at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:255) at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:73) at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:339) at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172) at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152) at $Proxy18.login(Unknown Source) at se.k.client.delegate.services.kiservice.KWS.login(KIServiceWS.java:112) at se.k.client.controller.LoginController.verifyLogin(LoginController.java:49) at se.k.client.main.Login$2.actionPerformed(Login.java:118) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242) at javax.swing.AbstractButton.doClick(AbstractButton.java:357) at javax.swing.plaf.basic.BasicRootPaneUI$Actions.actionPerformed(BasicRootPaneUI.java:191) at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1636) at javax.swing.JComponent.processKeyBinding(JComponent.java:2849) at javax.swing.KeyboardManager.fireBinding(KeyboardManager.java:267) at javax.swing.KeyboardManager.fireKeyboardAction(KeyboardManager.java:216) at javax.swing.JComponent.processKeyBindingsForAllComponents(JComponent.java:2926) at javax.swing.JComponent.processKeyBindings(JComponent.java:2918) at javax.swing.JComponent.processKeyEvent(JComponent.java:2812) at java.awt.Component.processEvent(Component.java:5818) at java.awt.Container.processEvent(Container.java:2058) at java.awt.Component.dispatchEventImpl(Component.java:4413) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4243) at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1848) at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:697) at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:962) at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:834) at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:661) at java.awt.Component.dispatchEventImpl(Component.java:4285) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Window.dispatchEventImpl(Window.java:2440) at java.awt.Component.dispatchEvent(Component.java:4243) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:177) at java.awt.Dialog$1.run(Dialog.java:1045) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121) Caused by: org.jboss.remoting.CannotConnectException: Can not connect http client invoker. Connection refused: connect. at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:348) at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:137) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.Client.invoke(Client.java:1634) at org.jboss.remoting.Client.invoke(Client.java:548) at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:233) ... 49 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.Socket.connect(Socket.java:519) at sun.net.NetworkClient.doConnect(NetworkClient.java:152) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:788) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:729) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:654) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:832) at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:277) ... 54 more Host can be ping, DNS lookup is fine and we also edited host file in Windows system32...quite sure host name can be resolved. Any ideas? tia johan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179593#4179593 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179593 From do-not-reply at jboss.com Tue Sep 30 11:26:01 2008 From: do-not-reply at jboss.com (PeterJ) Date: Tue, 30 Sep 2008 11:26:01 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: Not getting instance of Service object from a WSDL file. Message-ID: <26633020.1222788361265.JavaMail.jboss@colo-br-02.atl.jboss.com> 1) As I indicated, the list of JARs I gave is for 5.0 CR2. I provided the list mainly to say that you will probably need to add a lot of JARs and your list will most likely be different from mine. What I did was used wsrunclient and when it gave a ClassNotFoundEsxception, I found the JAR containing that class, added it to my classpath, and then ran it again. I did this about a dozen times to find all of the required JARs. You can do the same. You do not need to install anything different, the JBossWS provided with 4.2.x will work just fine. (Actually, what I cannot figure out is why wsrunclient does not already include all of the necessary JAR files - that was what the whole point of that script was.) 2) Most likely you are using the wrong names or making the wrong calls. Use wsconsume to generate the stubs and examine the source for the stubs. That should tell you what names you should be using or calls you should be making. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179600#4179600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179600 From do-not-reply at jboss.com Tue Sep 30 19:30:36 2008 From: do-not-reply at jboss.com (rishabh2u) Date: Tue, 30 Sep 2008 19:30:36 -0400 (EDT) Subject: [jbossws-users] [JBossWS] - Re: consume WS error after update to JBossWS 2.0 Message-ID: <22883211.1222817436485.JavaMail.jboss@colo-br-02.atl.jboss.com> did u mean what is the minimum jar to consume a ws ? if yes then : jaxb-api.jar jaxb-impl.jar jboss-common-client.jar jboss-jaxws.jar jbossws-client.jar xercesImpl.jar As a client generates soap messages etc we still need the some of the jbossws stack. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179670#4179670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179670