[JBoss Seam] - Re: conversations, propagations etc ... - need explanation
by amashtakov
anonymous wrote :
| Which version of Seam are you using? conversation-is-long-running-parameter is not included in latest (Seam 2.0.0.CR2) due to the addition of conversation-required.
|
I'm using 1.2.1GA
anonymous wrote :
| The key to understanding conversations is the conversationId sent with the request. The conversationId is maintained along with the view (as you've discovered) and indicates to Seam what the foreground long-running conversation is.
|
I noticed two GET parameters [cid] and [clr] and it seems that the second
one is used in order to check whether the conversation is long running or not. But I do not understand how does the postback work - tried to
print out the request parameters but nothing about cid/clr:
| <c:forEach var="n" items="#{facesContext.externalContext.requestParameterMap}">
| #{n.key} = #{n.value}<br/>
| </c:forEach>
|
anonymous wrote :
| This is why the back-button just seems to work. If the user goes back to a previous view, the conversationId will be sent with that view in the request so our conversation context is restored (if it exists otherwise redirect to no-conversation-view-id).
|
How does the conversationId sent with that view ?
I checked seam-booking demo with back button - the page is restored, but
seems it's from browser's cache - server.log didn't included an extra request trace.
anonymous wrote :
| Understanding the semantics is the key. As long as the appropriate conversationId is sent with the request, your conversation state will be restored.
|
As a GET parameter ?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096140#4096140
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096140
18Â years, 9Â months
[Installation, Configuration & DEPLOYMENT] - Re: Creating a secure development environment
by PeterJ
I do not see how a worm could propagate through the JBoss app servers if those app server are not opening ports accessible by remote hosts. You cannot get at the app server if it does not provide you with an opening. By binding to localhost, the app server could be considered just another desktop application. Heck, any application can send traffic out to the network, that's what outbound firewalls are for (and why Windows Firewall is a joke), to stop such traffic.
I do not see why they could not shutdown and patch your desktops if the JBoss app server is running. I think they are confusing production machines with desktop development machines. If your desktop reboots to apply a patch, who cares that the app server is down? Only you. But then your whole desktop rebooted so it is not like you could do anything anyway.
One solution that we implemented was to take offending machines and place then on a private network. Several of our machines could not be upgraded to meet corporate security requirements for various reasons, so we placed them all on a separate network with their own routers, etc. We then took a "corporate approved" machine on the corporate network, added in a second NIC and connected that NIC to the private network. To gain remote access to a machine on the private network, we remote desktop (or VNC) to the "bridge" machine, and from there remote desktop (or VNC) to the desired machine.
I think in your situation I would ask for a second desktop (most places have older PCs sitting around), hook the second desktop to the corporate network to do email, etc. Then take my primary desktop off the network and do my development work in peace. If several people in your group are in the same situation, you could network all of the development PCs and perhaps get another PC to host the database. You could even use that PC as the "bridge" to the corporate network.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096139#4096139
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096139
18Â years, 9Â months
[JCA/JBoss] - Re: RA deployment in JBoss
by jeff.yuchang
Back to the problem.
As I said before, the error that I had firstly is due to the older version (xmlapi.jar and resolver.jar) in the my RAR than the $JBoss/lib, So I remove these two jars to use the jars that JBoss had.
But then I restart it again, it complains the ClassCastException,,, the error stack is:
-------------------------
23:00:59,248 ERROR [STDERR] java.lang.ClassCastException: $Proxy63
23:00:59,248 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.annotationForMap(Annotati
onParser.java:239)
23:00:59,248 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseAnnotation(Annotatio
nParser.java:229)
23:00:59,248 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseAnnotations2(Annotat
ionParser.java:69)
23:00:59,248 ERROR [STDERR] at sun.reflect.annotation.AnnotationParser.parseAnnotations(Annotati
onParser.java:52)
23:00:59,248 ERROR [STDERR] at java.lang.Class.initAnnotationsIfNecessary(Class.java:3031)
23:00:59,248 ERROR [STDERR] at java.lang.Class.getAnnotation(Class.java:2989)
23:00:59,248 ERROR [STDERR] at org.apache.cxf.jca.servant.EJBEndpoint.isJaxWsServiceInterface(EJ
BEndpoint.java:159)
23:00:59,279 ERROR [STDERR] at org.apache.cxf.jca.servant.EJBEndpoint.publish(EJBEndpoint.java:7
6)
23:00:59,279 ERROR [STDERR] at org.apache.cxf.jca.cxf.JCABusFactory.initializeServantsFromProper
ties(JCABusFactory.java:128)
23:00:59,279 ERROR [STDERR] at org.apache.cxf.jca.cxf.JCABusFactory.access$200(JCABusFactory.jav
a:49)
23:00:59,279 ERROR [STDERR] at org.apache.cxf.jca.cxf.JCABusFactory$EJBServicePropertiesMonitorW
orker.run(JCABusFactory.java:269)
23:00:59,279 ERROR [STDERR] at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
23:00:59,279 ERROR [STDERR] at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.j
ava:275)
23:00:59,279 ERROR [STDERR] at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Pooled
Executor.java:743)
23:00:59,279 ERROR [STDERR] at java.lang.Thread.run(Thread.java:595)
The code is:
------------------------
Class<?> interfaceClass = Class.forName(this.getServiceClassName());
if (cls == null) {
return false;
}
if (null != cls.getAnnotation(WebService.class)) {
return true;
}
return true;
So, I suspect that in this situation, it might used the different classloader...
Any thoughts?
Thanks
Jeff
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096137#4096137
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096137
18Â years, 9Â months
[JBoss Seam] - Re: conversations, propagations etc ... - need explanation
by jacob.orshalick
Which version of Seam are you using? conversation-is-long-running-parameter is not included in latest (Seam 2.0.0.CR2) due to the addition of conversation-required.
The key to understanding conversations is the conversationId sent with the request. The conversationId is maintained along with the view (as you've discovered) and indicates to Seam what the foreground long-running conversation is. This is why the back-button just seems to work. If the user goes back to a previous view, the conversationId will be sent with that view in the request so our conversation context is restored (if it exists otherwise redirect to no-conversation-view-id).
Feel free to parse the code but the details of how this works should really be transparent if you use the methods of propagation provided i.e. @Begin, s:link, s:conversationPropagation, etc). Understanding the semantics is the key. As long as the appropriate conversationId is sent with the request, your conversation state will be restored.
Hope that helps.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096132#4096132
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096132
18Â years, 9Â months
[JCA/JBoss] - Re: RA deployment in JBoss
by jeff.yuchang
A little story about my situation:
Before I pack the rar file in an ear, I use the cxf-ds.xml and cxf.rar to do the deployment.
Because the cxf uses some jars which JBoss used its older version, to make it cxf based RA works, I need to endorse a bunch of jars in the $JBoss/lib/endorsed.
* geronimo-activation_1.1_spec-1.0-M1.jar
* geronimo-annotation_1.0_spec-1.1.jar
* geronimo-ws-metadata_2.0_spec-1.1.1.jar
* jaxb-api-2.1.jar
* jaxb-impl-2.1.4.jar
* jaxb-xjc-2.1.4.jar
* jsr181-api-1.0-MR1.jar
* saaj-api-1.3.jar
* saaj-impl-1.3.jar
* stax-api-1.0.1.jar
* stax-utils-20060502.jar
and it can start successfully, however, I am looking for an elegant way to do this instead of using endorsed.
So I know I need to use the scoped classloader, and in order to do that, it needs me to pack the RAR to an EAR, and then adding the jboss-app.xml to configure.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096131#4096131
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4096131
18Â years, 9Â months