[JBossWS] - Single Client, Multiple Service Endpoints
by elcapitan
G'day all,
This is probably quite straightforward, but I've been unable to turn much up about it. I'm deploying a reasonably complicated EJB3 application in an AS, and I've got four different stateless beans that I'd like to expose as webservices, to be consumed by a single client. I can't work out a tidy way to create and provide the client-side artefacts - at the moment, I can expose all the services, but I'm having problems generating mapping files and setting them up on the client side.
In order of preference, here's what I'd like to be able to do:
1. Instruct wstools to include information from more than a single WSDL file, and produce a single jaxrpc-mapping.xml file. At present, my wstools-config.xml looks like:
<configuration xmlns="http://www.jboss.org/jbossws-tools">
| <wsdl-java file="http://localhost:8080/crawler/WatchListManager?wsdl" unwrap="false">
| <mapping file="META-INF/jaxrpc-mapping.xml"/>
| </wsdl-java>
| </configuration>
If I could get this to include multiple WSDLs, that would solve all my problems pretty neatly, I think.
2. If that's not possible, can I instruct the client to read mapping information from multiple files? As such, they won't all be named jaxrpc-mapping.xml, so how can I tell the client where to look?
3. If all else fails, I could always create a facade service interface, but for reasons of modularity I'd really like to avoid this.
Cheers, thanks in advance,
James
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994532#3994532
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994532
19 years, 4 months
[JBoss Seam] - Conversation Timeout and time of conversation destruction
by ccurban
I need to change the status of an entity at the end of a conversation (even a timed out one).
Here is the SFSB that should do that:
@Stateful
| @Scope(ScopeType.CONVERSATION)
| @Name("callCenterAddressAction")
| public class CallCenterAddressAction implements CallCenterAddressLocal
| {
| @Out(required = false, scope = ScopeType.CONVERSATION)
| private Distribution currentDistribution;
| .
| .
| .
| @Destroy
| @Remove
| public void destroy() {
| if (currentDistribution != null) {
| Distribution distribution = inaEntityManager.merge(currentDistribution);
| if (distribution.getStatus().equals(Distribution.STATUS_IN_PROCESS)) {
| distribution.setStatus(Distribution.STATUS_PRE_PROCESS);
| }
| }
| }
| }
|
To test the behaviour I set the conversation timeout to 10 secs in components.xml
<component name="org.jboss.seam.core.manager">
| <property name="conversationTimeout">10000</property>
| </component>
I expected that the conversation will be destroyed after 10 secs (or some time in the near surrounding of 10 secs).
Unfortunately it seams only to be destroyed when I navigate to another page in the browser.
Did I make a mistake or is this behaviour only occuring in my single-place-test-environment (and the context cleanup is started on every servlet call)?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994531#3994531
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994531
19 years, 4 months
[JBoss Seam] - ICEFaces example for Glassfish
by alexg79
Could someone make a deployable Glassfish version of the Seam ICEFaces example? I can't get it to work on Glassfish. It deploys fine (after creating the datasource and modifying its JNDI pattern), but trying to load the front page gives:
| Servlet.service() for servlet Persistent Faces Servlet threw exception
| javax.faces.FacesException: java.lang.NullPointerException
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:305)
| at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:113)
| at com.icesoft.faces.webapp.xmlhttp.PersistentFacesServlet.service(PersistentFacesServlet.java:389)
| at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
| at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
| at org.jboss.seam.servlet.SeamExceptionFilter.doFilter(SeamExceptionFilter.java:46)
| at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:216)
| at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:184)
| at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
| at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
| at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
| at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240)
| at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179)
| at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
| at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73)
| at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182)
| at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
| at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120)
| at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
| at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137)
| at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566)
| at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536)
| at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939)
| at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:239)
| at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667)
| at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574)
| at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844)
| at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287)
| at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212)
| at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252)
| at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75)
| Caused by: java.lang.NullPointerException
| at com.icesoft.faces.application.D2DViewHandler.calculateRenderKitId(D2DViewHandler.java:696)
| at com.sun.faces.lifecycle.RestoreViewPhase.isPostback(RestoreViewPhase.java:241)
| at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:170)
| at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:244)
| ... 32 more
|
I'm running it on the Sun RI.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994530#3994530
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994530
19 years, 4 months
[JBoss Seam] - Re: action=
by koatto
this is my faces-config :
<faces-config>
|
| <application>
| <view-handler>org.jboss.seam.ui.facelet.SeamFaceletViewHandler</view-handler>
| </application>
|
| <application>
| <message-bundle>messages</message-bundle>
| <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
| </application>
|
| <!-- Seam transaction management -->
| <lifecycle>
| <phase-listener>org.jboss.seam.jsf.TransactionalSeamPhaseListener</phase-listener>
| </lifecycle>
|
| <!-- No Seam transaction management -->
| <!--
| <lifecycle>
| <phase-listener>org.jboss.seam.jsf.SeamPhaseListener</phase-listener>
| </lifecycle>
| -->
|
| </faces-config>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994529#3994529
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994529
19 years, 4 months
[JBoss Seam] - Re: Request for feedback
by norman.richards＠jboss.com
I don't know how other people's taste in XML goes, but the following reads really well to me:
<page view-id="/getDocument.jsp">
| <on action="#{documentHome.get}">
| <redirect to-view-id="/editDocument.jsp" when="#{documentHome.document!=null}">
| <param name="documentId" value="#{documentHome.document.id}"/>
| </redirect>
|
| <redirect to-view-id="/404.jsp" when="#{documentHome.document==null}" />
| </on>
|
|
| <on action="#{logout.logout}">
| <redirect to-view-id="/login.jsp" />
| </on>
| </page>
Or, with explicit outcome declaration:
<page view-id="/getDocument.jsp">
| <on action="#{documentHome.get}">
| <outcome value="#{documentHome.document!=null}" />
|
| <redirect to-view-id="/editDocument.jsp" when-outcome="true">
| <param name="documentId" value="#{documentHome.document.id}"/>
| </redirect>
|
| <redirect to-view-id="/404.jsp" when-outcome="false" />
| </on>
|
| <on action="#{logout.logout}">
| <redirect view-id="/login.jsp" when-null-outcome="true" />
| </on>
| </on>
Although, I think it might be even better if outcome were just a variable:
| <redirect to-view-id="/editDocument.jsp" when="#{outcome==true}">
| ...
| <redirect to-view-id="/404.jsp" when="#{outcome==null}">
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994525#3994525
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994525
19 years, 4 months