[Installation, Configuration & Deployment] - problem in deployment in 4.0.4 GA due to mutual dependecy be
by amitguz
I migrate my application from jboss 4.0.4 RC1 to JBOSS 4.0.4 GA
and I got error during the deployment.
In general the error is about mutual dependecy .
i.e - suppose I have 2 Stateless session bean:
1.) XXBean 2.)YYBean
and I have the following code:
|
| @Remote ({XX.class})
| public @Stateless class XXBean implements XX {
|
| @EJB YYBean ybean;
| }
|
| @Remote ({YY.class})
| public @Stateless class YYBean implements YY {
|
| @EJB XXBean ybean;
| }
|
|
this code in 4.0.4 GA will raise error during the depolyment process.
Does anybody know why? and how to overcome it?
thanks, amit
p.s - this is the error I got
anonymous wrote :
| --- MBeans waiting for other MBeans ---
| ObjectName: jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=XXBean,service=EJB3
| State: NOTYETINSTALLED
| I Depend On:
| jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=YYBean,service=EJB3
| Depends On Me:
| jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=YYBean,service=EJB3
|
| ObjectName: jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=YYBean,service=EJB3
| State: NOTYETINSTALLED
| I Depend On:
| jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=XXBean,service=EJB3
| Depends On Me:
| jboss.j2ee:ear=testApp.ear,jar=testLogic.jar,name=XXBean,service=EJB3
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959096#3959096
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959096
19 years, 9 months
[JBoss jBPM] - Re: Modeling simple process(tasks)
by dlipski
Ok so I accept 'transformation' as one step of the design process.
So how to transform such situation:
1)shop creates order - order is in state 'created'
2)supplier can create or reject order. When accepts order go's to 'accepted' state, but have to provide some additional data. When rejects order go's to 'rejected' state.
And there is one more requirement, all tasks that have to be performed by end users should be displayed in one generic way, this mean that if i add new action to 'created' state and deploy new process definition UI should display one button more. But end users have different permissions, some can only reject some can do both. One thing that is not generic is set of action which are implemented in Java.
At first glance i wanted to do this with task nodes but this causes some problems which i can't solve.
Now i want to do this with wait states. Where 'created', 'accepted', 'rejected' are wait states and 'accept', 'reject' are transition between them. But this aproach have few disadventages:
1)I can't use swimlanes. If in the future order after supplier acceptance should be accepted also by shop user WHO CREATED ORDER how to achive this ?
2)Actions now represents user tasks which should be represented by tasks.
3)Can i have one general action ex. 'modify order' and use it in different places in process and configure it to let users modify only quantities and somewere else let user modify only prices ? Or i have to do two distinct actions ?
Do u see any more ?
If u have any idea please help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959089#3959089
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3959089
19 years, 9 months