hmm... strange... then you should have no visual layout... well, I already got 'something' that looks kind of useful.
You should really look into your fork.join constructs. Most are not correct. Things like having one transition of a fork going to the node before (propose adjustments) is not correct. That can lead to a lot of problems if the wrong transition is taken (propose is e.g. not allowed here since the original token will *never* get to the correct *instance* of the join, and neither the cancel-fork1 is valid then for the same reason)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236087#4236087
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236087
I posted in both places since I had read a message on that board that said a different poster's question belonged on this board since it was dealing with the connection-factories.
For the archives: I was able to get it to work once I moved the mbean description into its own file and out of the jms-ds.xml file. I was told it should work in either place, but I ran out of time trying to figure out why it wasn't working for me to combine them. Besides, having a separate file makes it easier to deploy and manage, so it is a better solution anyway.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236083#4236083
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236083
I encounter the same restriction. My use case is that I'm building an application composed by a few modules (each modules comes as a portlet package in a war).
I use some page spaces in order to compose different views of my application (base on the role or the application context (summary page, detail page)).
I can pass from one page to another but I need to instruct the target page (in fact the target portlets) for some params. So I build a sort of session Handler (DB storage) on top of synchronized by the sessionID.
I don't like that to much (should not work on distributed applications), but I don't know how to do that differently. I regret the lake of a Portal Scope variable.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236078#4236078
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236078
