[JBossWS] - Multiple Bindings not Supported
by jesse_sweetland
Hello,
I'm trying to consume a web service with multiple ports and I receive the error "Multiple bindings not supported." I'm using an IDE-generated static stub built with NetBeans 5.0 (rpcliteral, wsi). I've added an application-client.xml and jboss-client.xml in the JAR META-INF directory to bind the client to JNDI. I have specified a port-component-ref in both, but I still receive the same error. I'm using JBoss 4.0.3SP1.
Here is an example of how my application-client.xml:
| <application-client xmlns="http://java.sun.com/xml/ns/j2ee"
| xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
| xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
| http://java.sun.com/xml/ns/j2ee/application-client_1_4.xsd"
| version="1.4">
|
| <display-name>MyWSClient</display-name>
| <service-ref>
| <service-ref-name>MyWSClient</service-ref-name>
| <service-interface>mypkg.MyWSSEI</service-interface>
| <wsdl-file>META-INF/wsdl/MyWS.wsdl</wsdl-file>
| <jaxrpc-mapping-file>META-INF/MyWS-mapping.xml</jaxrpc-mapping-file>
| <port-component-ref>
| <service-endpoint-interface>mypkg.MyPort</service-endpoint-interface>
| </port-component-ref>
| </service-ref>
| </application-client>
|
Where mypkg.MyWSSEI is a generated interface that extends javax.xml.rpc.Service and mypkg.MyPort is a generated interface extends java.rmi.Remote. Names have been changed to protect the innocent. I receive no errors other than the "Multiple bindinds not supported". Is there anything I'm doing wrong?
I've tried upgrading to JBoss 4.0.5, but I receive many other errors with my other JAX-RPC web service clients. I receive the same errors even after upgrading to JBossWS 1.0.4 and 1.2.0.
Can someone provide an example of an application-client.xml or jboss-client.xml with a port-component-ref that will enable me to build a client for JBoss 4.0.3? Is there a document that explains a what steps are necessary to migrate JAX-RPC clients from 4.0.3 to 4.0.5?
Is there a preferred or recommended platform? (JBoss 4.0.5 + wstools, JBoss 4.0.3 + wscompile, etc?) We have a lot of existing web services and clients and I would like to minimize migration effort.
Thanks,
Jesse
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038057#4038057
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038057
19 years, 1 month
[JBoss Seam] - Deploying seam app along side standard jsf app problem
by leman_1
Hello,
App Server: 4.0.5GA
Seam version: 1.2.0 Patch 1
I am trying to deploy a single ear file with a seam app inside it and a JSF app. The ear file deploys but as soon as I try to hit a page in the JSF app the JSF code tries to load some objects into the application scope but fails with the following error:
| 17:49:39,168 ERROR [[Faces Servlet]] Servlet.service() for servlet Faces Servlet threw exception
| java.lang.IllegalStateException: No active application scope
| at org.jboss.seam.core.Init.instance(Init.java:78)
| at org.jboss.seam.jsf.SeamNavigationHandler.handleNavigation(SeamNavigationHandler.java:28)
| at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:84)
| at javax.faces.component.UICommand.broadcast(UICommand.java:106)
| at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:94)
| at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:168)
| at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:343)
| at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
| at javax.faces.webapp.FacesServlet.service(FacesServlet.java:137)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.myfaces.webapp.filter.ExtensionsFilter.doFilter(ExtensionsFilter.java:144)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java
| :664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
The stack trace contains seam classes in it. The war file containing the JSF code doesn't have any references to any Seam classes or jars. I was hoping the two would be able to run independently of each other.
Has anyone already done this?
I would appreciate any help.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038053#4038053
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038053
19 years, 1 month
[JBoss Seam] - Re: Problems Starting Page Flows
by petemuir
"Delphi's Ghost" wrote : I have test.xml that contains a bunch of test links with the different ways of starting page flows :
FYI, you can also use pages.xml to start pageflows (my favourite ;)
anonymous wrote : I would have thought that if you click a link, button, or call a method that starts a pageflow, then you would automatically end up on the view-id referenced by the start-page definition (in this case testpage1).
No. You use start-page when you are:
anonymous wrote : already at the page being rendered
If you want to navigate to a new view as a result of starting the pageflow, use a start-state node.
anonymous wrote : But if the pageflow is begun as the result of an action listener invocation, the outcome of the action listener determines which is the first page to be rendered. In this case, we use a <start-state> as the first node in the pageflow, and declare a transition for each possible outcome:
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038050#4038050
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038050
19 years, 1 month
[JBossWS] - setProperty must be overridden by all subclasses of SOAPMesa
by cjunge
Hi, I have created (using Netbeans) a JAX-WS client to invoke a web service. I've copied the JAX-WS jars to the deafult/lib directory of the AS including saaj-api.jar and saaj-impl.jar.
I'm using jboss-4.0.5.GA and jdk1.5.0_09.
The server boots without errors but when I invoke the client I get the following error in the console.
| 2007-04-13 15:07:41,937 ERROR [org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper] SOAP request exception
| java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
| at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
| at org.jboss.ws.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:65)
| at org.jboss.ws.soap.MessageFactoryImpl.createMessageInternal(MessageFactoryImpl.java:209)
| at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:142)
| at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:190)
| at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355)
| at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
|
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11Base
| Protocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
| 2007-04-13 15:07:41,937 ERROR [org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper] Error creating SOAPFault message java.lang.UnsupportedOperationException: setProperty must be overridden by all subclasses of SOAPMessage
| at javax.xml.soap.SOAPMessage.setProperty(Unknown Source)
| at org.jboss.ws.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:65)
| at org.jboss.ws.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:115)
| at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.toSOAPMessage(SOAPFaultExceptionHelper.java:203)
| at org.jboss.ws.jaxrpc.SOAPFaultExceptionHelper.exceptionToFaultMessage(SOAPFaultExceptionHelper.java:188)
| at org.jboss.ws.server.ServiceEndpoint.handleRequest(ServiceEndpoint.java:223)
| at org.jboss.ws.server.ServiceEndpointManager.processSOAPRequest(ServiceEndpointManager.java:355)
| at org.jboss.ws.server.StandardEndpointServlet.doPost(StandardEndpointServlet.java:115)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
| at org.jboss.ws.server.StandardEndpointServlet.service(StandardEndpointServlet.java:76)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
| at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
|
| at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
| at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
| at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
| at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
| at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
| at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11Base
| Protocol.java:664)
| at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
| at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
| at java.lang.Thread.run(Thread.java:595)
|
>From what I've been able to find out in the forums the problem is that I have two saaj.jar in the classpath and I should tell JBoss to use it's own verson (jboss-saaj.jar) over the other.
Removing the other version generates other errors so I need to know how to make sure that I'm using jboss-saaj.jar in execution time.
Whould someone please tell me how to do this or maybe give a different solution to my problem?
Thanks in advance,
Cristian
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038048#4038048
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038048
19 years, 1 month