[JBoss jBPM] - "Runtime Task" Why not ?
by AlClientView
Hi everyone,
I have a question about what change can(not)/should(not) be allowed to be done at runtime. More specifically I'm thinking about Task:
The way Jbpm is implemented (if I'm not wrong) allows client application to create task instance(s) for one Task at runtime. This can be done easily by using the API. And my question is what about "Runtime Task". I mean by runtime Task: Adding a Task to a process instance.
>From what I've seen, nothing prevent a client application from adding a Task to a TaskNode at runtime but this means all process instances will be affected by this change (since the change is done at the process definition level).
I'm not saying this implementation is wrong, I just try to understand what is the logic behind this choice.
There are runtime actions for example why not to have also runtime Task. Is it against the BPM philosophy, saying this is part of the process design done by the BA and in anycase that should be changed at runtime ?
I can understand this rule but then how to support the implementation of a Task node for which the creation of Task is decided by a rule (RuleEngine) ?
Sorry to be long but I'm very interested and curious to know what you guys think about this, first regarding JBPM and then BPM in general...
Thanks in advance,
Arnaud.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214856#4214856
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214856
15 years, 10 months
[EJB 3.0] - Session Bean call from an MBean, isolation and the TCCL
by os
Hi,
I have an EAR containing an MBean and a Session Bean. Isolation is turned on. The Session Beans interface is not visible, since it should only be called via the MBean.
When I call the EJB3 Session bean from an MBeans method the org.jboss.ejb3.proxy.objectfactory.session.SessionProxyObjectFactory
checks if the Session Beans Proxy is loaded by the same classloader as the currents threads context classloader (TCCL). If not, it tries to relaod the Classes with the TCCL. But if the MBeans method is invoked from a WebContext (e.g. jmx-console) it fails with
RuntimeException("Can not find interface declared by Proxy in our CL + " + tcl, e)
since the Session Beans remote interface is not (and shall not) be visible from the Web context.
Is there a way to call a EJB3 Session Bean from an MBean while avoiding the reload of the classes by the SessionProxyObjectFactory?
Thanks in advance
Olaf
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214850#4214850
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214850
15 years, 10 months
[EJB 3.0] - ClassCastException on Stateless Session Bean
by robert.geisler
hello everybody,
currently we are migrating our EJB 2.1 (about 850 EJBs) to EJB 3.0. till now there have not been too many problems, but today i meet a special challeng when i migrated a Stateful Session Bean.
the SFSB, lets call it MyStatefulSessionBean implements a Remote Business Interface (MyStatefulSession) and gets deployed in a EAR (MyEAR.ear). from a standalone client i can lookup, cast and use the SFSB successfully.
otherwise we deploy a WAR, too. from there i can lookup the SFSB, but cannot use it, because casting results in ClassCastException:
Context context = ContextFactory.getInstance().getContext();
| MyStatefulSession session = (MyStatefulSession) context.lookup("MyEAR/MyStatefulSession/remote");
$Proxy123 cannot be cast to xzy.MyStatefulSession
the MyStatefulSession.class is packaged in server/MyServer/lib/MyLibrary.jar and in our EAR, too.
i tried to remove all duplicate interfaces and classes from the EAR, but than i get java.lang.VerifyError -that i cannot understand- in arbitrary implementation classes (even in EJB 2.1 SLSB).
2009-03-04 11:48:41,837 WARN [org.jboss.ejb.EJBDeployer] Verify failed; continuing
| java.lang.VerifyError: (class: a/b/c/ArbitraryBean, method: getSomething signature: (Ljava/lang/String;ILx/y/z/SomeDTO;)Ljava/util/ArrayList;) Incompatible argument to function
| at java.lang.Class.getDeclaredMethods0(Native Method)
| at java.lang.Class.privateGetDeclaredMethods(Unknown Source)
| at java.lang.Class.privateGetPublicMethods(Unknown Source)
| at java.lang.Class.getMethods(Unknown Source)
| at org.jboss.verifier.strategy.AbstractVerifier.hasEJBCreateMethod(AbstractVerifier.java:687)
| at org.jboss.verifier.strategy.EJBVerifier21.verifySessionBean(EJBVerifier21.java:858)
my idea is that all classes and interfaces that will be used from EAR and WAR, should go to server/MyServer/lib/, implementation classes should remain in EAR, servlets should go into WAR.
is that right? if so, we have to refactor our ANT builds, i guess ; )
anyway... i wonder why our packaging strategy do not show any conflicts for Stateless Session Beans. maybe someone can help me with this...?
thanks in advance
robert
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214841#4214841
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214841
15 years, 10 months