[JBossWS] - Re: Providing your own wsdl instead of the generated one.
by ngtdave
Alright, I got it working.
First I changed my web.xml to use the impl bean:
<servlet-class>echo.EchoImpl</servlet-class>
per this discussion:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70837
where Diesler says:
anonymous wrote : So this is trying to instanciate an interface. Your web.xml should contain the endpoint impl bean not the SEI. Is that the case?
but then I got this error:
9:55:24,824 ERROR [ServiceEndpointDeployer] Cannot create service endpoint
| rg.jboss.ws.WSException: Cannot find port in wsdl: {http://echo/}EchoImplPort
So then I remembered:
https://jax-ws.dev.java.net/jax-ws-ea3/docs/annotations.html#2.1%20javax....
specifies:
anonymous wrote : javax.jws.WebService.portName - The wsdl:portName
So I tried to change Echo.java to declare the port, but I got an error:
09:56:05,683 ERROR [MainDeployer] Could not create deployment: file:/D:/jboss/jboss-4.2.0.CR1/server/default/deploy/echo.war
| org.jboss.deployment.DeploymentException: Cannot create service endpoint; - nested throwable: (org.jboss.ws.WSException: @WebService[portName,serviceName,endpoi
| ntInterface] MUST NOT be defined on: echo.Echo)
So I changed EchoImple.java:
@javax.jws.WebService(endpointInterface="echo.Echo",portName="EchoPort")
| public class EchoImpl implements Echo
| ....
|
Now it works and it still serves out my wsdl.
I'm not sure if this is a bug or not because the docs here https://jax-ws.dev.java.net/jax-ws-ea3/docs/annotations.html#2.1%20javax....
say:
anonymous wrote : endpointInterface - The qualified name of the service endpoint interface. This annotation allows the separation of interface contract from implementation. If this property is specified, all other WebService properties are ignored as are all other 181 annotations. Only the annotations on the service endpoint interface will be taken into consideration. The endpoint implementation class is not required to implement the endpointInterface.
Which I take to mean the other parameters (portName) should be ignored if endpointInterface is specified.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031115#4031115
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031115
19Â years, 1Â month
[JBoss Seam] - Could not instantiate Seam component - Hibernate Session Err
by MightyDuck
Hi, i'm using Jboss-4.2.0 and Seam 1.2, get this error, can somebody help me
11:54:10,312 WARN [lifecycle] Could not instantiate Seam component: searchContractFrontController
org.jboss.seam.InstantiationException: Could not instantiate Seam component: searchContractFrontController
at org.jboss.seam.Component.newInstance(Component.java:1708)
at org.jboss.seam.Component.getInstance(Component.java:1611)
at org.jboss.seam.Component.getInstance(Component.java:1578)
at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:53)
at com.sun.faces.el.VariableResolverChainWrapper.getValue(VariableResolverChainWrapper.java:100)
at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:64)
at org.apache.el.parser.AstIdentifier.getValue(AstIdentifier.java:45)
at org.apache.el.parser.AstValue.getTarget(AstValue.java:42)
at org.apache.el.parser.AstValue.invoke(AstValue.java:127)
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:77)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:95)
at javax.faces.component.UICommand.broadcast(UICommand.java:383)
at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:448)
at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:752)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:97)
at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:248)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:117)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:244)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:57)
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:228)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
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.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:216)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:624)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:445)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.NamingException: Could not dereference object [Root exception is javax.ejb.EJBException: java.lang.RuntimeException: java.lang.ClassCastException: org.jboss.ejb3.entity.ExtendedHibernateSession]
at org.jnp.interfaces.NamingContext.getObjectInstanceWrapFailure(NamingContext.java:1150)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:705)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.seam.Component.instantiateSessionBean(Component.java:1075)
at org.jboss.seam.Component.instantiate(Component.java:1061)
at org.jboss.seam.Component.newInstance(Component.java:1704)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031112#4031112
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031112
19Â years, 1Â month
[JBoss Seam] - s:link bug?
by waynebagguley
I've got a <h:datatable> like this:
| <h:dataTable value="#{jobListHandler.jobList}" var="jobStore">
|
Nested inside are some <h:column> elements as you'd expect.
I want to include an <s:link> in one of the columns but before I did that I noticed that 'jobListHandler.jobList' was getting called twice to render the table only once. As it's making a database call I'm not happy about this, but it gets worse.
If I add this code inside one of the <h:column> tags then 'jobListHandler.jobList' gets called twice (as before) and once for each and every table row displayed (a total of 13 times in this case):
| <s:link action="#{jobHandler.reprint}" value="Reprint">
| <f:param value="#{jobStore.id}" name="jobStoreId"/>
| </s:link>
|
Why is this happening? Am I misunderstanding the usage of <h:dataTable> and/or <s:link>?
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4031102#4031102
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4031102
19Â years, 1Â month