[JBoss Seam] - Re: Deployment: Where to put richfaces-*.jar for rich:tree?!
by Kruno
You need richfaces-3.0.1-SNAPSHOT.jar in WEB-INF/lib and you have to change
in jboss-4.0.5.GA/server/default/deploy/jbossweb-tomcat55.sar/META-INF/jboss-service.xml
from false to true
| <attribute name="Java2ClassLoadingCompliance">true</attribute>
| <!-- A flag indicating if the JBoss Loader should be used. This loader
| uses a unified class loader as the class loader rather than the tomcat
| specific class loader.
| The default is false to ensure that wars have isolated class loading
| for duplicate jars and jsp files.
| -->
| <attribute name="UseJBossWebLoader">true</attribute>
| <!-- The list of package names that should not be loaded without
| delegating to the parent class loader before trying the web app
| class loader. The packages listed here are those tha are used by
| the web container implementation and cannot be overriden.
| This only applies when UseJBossWebLoader=false.
| -->
|
for jboss4.2.0 is the same just jboss-service.xml has a different path.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060792#4060792
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060792
18Â years, 9Â months
[JBoss Seam] - Re: Nested conversations - potential bug in Manager.beginNes
by wschwendt
"hkarapuu" wrote : anonymous wrote : IllegalStateException should be thrown if @Begin(nested=true) is encountered and there is no long-running conversation active.
|
|
| I think that might cause some difficulties with reuse and recursive use.
|
| I.e. In crud application i can start creation of a new object from a master list (=starting new conversation), OR from within the creation of another object (=starting nested conversation). In both cases the same @Begin method would be called, and the callee should not concern itself who called it or why.
hkarapuu, do I understand you correctly that you want the following behavior? (The following is the behavior I'd prefer to see if I could choose...)
When @Begin(nested=true) is encountered and there is already a long-running conversation active, a new nested conversation (which is also long-running) gets created.
When @Begin(nested=true) is encountered and there is NO long-running conversation active, a nested conversation does NOT get created. Instead, the temporary conversation being active gets promoted to a long-running conversation. So we get the same behavior in this case as would happen if @Begin (without nested=true) was encountered.
The thing quoted above with the IllegalStateException is not my proposal. Rather, it is my interpretation based on the code of
org.jboss.seam.core.Manager.beginNestedConversation() what the intented behavior probably is.
If I could vote for a behavior, I wouldn't choose the one with the IllegalStateException either. I'd choose the one described in this post.
But clearly, the present behavior where a nested (but temporary instead of long-running) conversation gets created when @Begin(nested=true) gets encountered and there is no long-running conversation active, looks not like intended to me.
anonymous wrote :
| Disclaimer; i'm only evaluating Seam so i might have understood things wrong.
Me too.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4060784#4060784
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4060784
18Â years, 9Â months