[Design of JBoss Remoting, Unified Invokers] - StatefulHandleImpl in 4.x
by Frito
When migrating a huge application from JBoss 3.2.7 to JBoss 4.0 (and then to JBoss 4.2), I found some strange behaviour which I filed as a bug (http://jira.jboss.org/jira/browse/JBAS-5302) and some implementation details which I wanted to discuss here (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=123553), probably the wrong forum... many views, no comment ;-)
Reading the sources and the EJB spec lead me to these questions:
1.)
Why has the 3.2.7 compatibility not been implemented, using the invokerProxyBinding instead of doing a fresh lookup? The StatefulHandleImpl stores the "old" values when the property "org.jboss.ejb.sfsb.handle.V327" is set, but it doesn't use them.
I tried to port the 3.2.7 implementation to the getEJBObject method, evaluating the property, and it worked for me in a non clustered environment (JBoss 4.0.7).
2.)
JBoss implementations (as the StatefulHandleImpl) sometimes rely on "new InitialContext()".
We sometimes come up, that a thread on a client didn't ever do a lookup by himself using new InitialContext(properties) and the system properties are not set at all. Must the client programmer provide informations, that a "new InitialContext()" works consistent, or must the implementation not rely on the use of getting a new initial context without "seeing" the right properties?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135403#4135403
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135403
18 years, 1 month
[Design of JBoss jBPM] - jBPM With Seam
by divakar.satyanarayan
Hi,
We are exploring options of using jBPM with Seam for a workflow process. We had certain queries around the approach that we are planning to take.
1. We plan to retrieve tasklist and assign task to the user using jBPM API's and not through Seam annotations as we found out that annotations dont provide the kind of flexibility that we need. We are not sure how would the application behave in following scenario
a. User kicks of a workflow process. Process is in progress.
b. Lets assume that we have some production issue and we fix the bug and redeploy the Seam Application. NOw since jPDL file is part of Seam application, jPDL would also get deployed and a new version is assigned to this. What would happen to processes that were in progress? How would task retrieval work since you dont have access to process id that was instantiated?
c. Lets assume that I modify the workflow and redeploy the process definition. How would the tasks that were pending behave when we have new process defined?
Are there any documentation available that we can look through for these scenarios?
Divakar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135401#4135401
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4135401
18 years, 1 month