[JBoss Seam] - Seam calling other ejbs
by bizimalem
Hi,
image this configuration:
On the same jboss 4.04 server, there are two .ear packages.
test1.ear, test2.ear deployed.
test1.ear contains one ejb 3.0 stateless bean (CustomerManager.java) and a customer domain object (Customer.java).
Test2.ear contains some seam components, which uses test1.ear:CustomerManager to add a new Customer. I have also use the Customer class (which is a transfer object actually) from test1.ear in test2.ear. The Problem is, that Customer.java has to be marked as Seam Component (@Name), but this is not possible, because it resides inside test1.ear. (This would be possible, if test1.ear and some residing components are marked as seam components and deployed so. test1.ear contains only business components and should not coupled with seam)
How can one use other domain objects deployed in other .ears in Seam, which are not seam components?
thanks.
Özcan Acar
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974446#3974446
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974446
19 years, 7 months
[JBoss jBPM] - Transient variables between process and subprocess II
by harrylette
Hi,
why is there not the same functionality for transient variables as for persistent ones when copying variables from a superprocess to a subprocess (process state)?
I have seen this thread
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70407
The proposed solution as seen in jira
http://jira.jboss.com/jira/browse/JBPM-399
is implemented in jbpm 3.1.2 that I am actually using.
I think this solution is simple but does not fit for the most common case, that a superprocess calls
a common suprocess and the subprocess does not know anything about the superprocess.
More specific, there could be different superprocesses with different transient variable names.
These superprocesses may call a general subprocess...
Using the present solution forces the subprocess to know about all possible variablenames of
all possible superprocesses - that's really bad!
What can we do?
Is it difficult to implement similar code for transient variables as you did for persistent ones?
| // loop over all the variable accesses
|
| Iterator iter = variableAccesses.iterator();
|
| while (iter.hasNext()) {
|
| VariableAccess variableAccess = (VariableAccess) iter.next();
|
| // if this variable access is readable
|
| if (variableAccess.isReadable()) {
|
| // the variable is copied from the super process variable name
|
| // to the sub process mapped name
|
| String variableName = variableAccess.getVariableName();
|
| Object value = superContextInstance.getVariable(variableName, superProcessToken);
|
| String mappedName = variableAccess.getMappedName();
|
| log.debug("copying super process var '"+variableName+"' to sub process var '"+mappedName+"': "+value);
|
| if (value!=null) {
|
| subContextInstance.setVariable(mappedName, value);
|
| }
|
| }
|
| }
|
|
Should I open a jira issue? Please give me a hint for a good approach to solve this problem..
Best regards
Harry
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974445#3974445
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974445
19 years, 7 months