[JBoss jBPM] - Re: conditional transition behavior
by ricardomarques
an update:
kukeltje, i don't think that the problem comes from bug jbpm-443, since the fields as bit have values, on the bug description is says that the fiekds had an empty string not the case here.
Another thing on the database, jbpm_decisionconditions is empty, and on jbpm_node the record that matches the decision node has all the fields empty except id, class, name, description, processdefinition, nodecollectionindex, isasync and isasyncexcl, don't know if that's usual.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064489#4064489
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064489
19Â years
[JBoss Seam] - Re: Workspaces and Concurrent Conversations
by harpritt
Hi ya
Got this one licked! Im not entirely sure what the exact reason is but i will try to explain what i had and what i did to correct it.
THIS IS WHAT I HAD
Symtoms : User A on Browser A would get logged out by user B on Browser B....
@Stateful
| @Name("ticketSystem")
| @Conversational
| public class TicketSystemAction implements TicketSystem {
|
| @In(required = false)
| @Out(scope = BUSINESS_PROCESS,required = false)
| ChangeRequest changerequest;
|
|
|
| @In(required = false)
| GsmsMetaData gsmsMetaData;
|
| @In(required = false)
| NewGSMSData newGsmsData;
|
| @In(required = false)
| RequestState requestState;
|
| @In(required = false)
| RequestReference requestReference;
|
| @In
| User user;
|
|
| @Begin
| public String newTicket() {
| if (changerequest.getCrAction().equals("EDIT")) {
| return "editdoc";
| }
| if (changerequest.getCrAction().equals("NEW")) {
| return "newdoc";
| }
| if (changerequest.getCrAction().equals("MOVE")) {
| return "movedoc";
| }
| if (changerequest.getCrAction().equals("DELETE")) {
| return "deletedoc";
| }
| if (changerequest.getCrAction().equals("OTHER")) {
| return "other";
| }
| //throw exception
| return "home";
| }
|
| @End
| @CreateProcess(definition = "changerequestprocess")
| public String submitTicket() {
|
| //CREATE Change request
|
| //PERSIST IT
| getChangeRequestDAO().saveCr(changerequest);
|
|
| return "home";
| }
|
|
|
| @BeginTask
| public String view_cr_waiting_appapproval() {
| return "viewcrwaitingappApproval";
| }
|
| @EndTask(transition = "accept")
| public String appAcceptcr() {
| return "home";
|
| }
|
| @EndTask(transition = "reject")
| public String appRejectCr() {
| return "home";
| }
|
| @BeginTask
| public String view_cr_waiting_editor_revise() {
| return "view_crwaiting_edrevise";
| }
THIS IS WHAT I DID
I Moved the methods invold in conversational scope into a seperate class....
@Stateful
| @Name("createChangeRequest")
| public class CreateChangeRequestAction implements CreateChangeRequest {
|
| @In(required = false)
| @Out(scope = BUSINESS_PROCESS,required = false)
| ChangeRequest changerequest;
| @In(required = false)
| GsmsMetaData gsmsMetaData;
|
| @In(required = false)
| NewGSMSData newGsmsData;
|
| @In(required = false)
| RequestState requestState;
|
| @In(required = false)
| RequestReference requestReference;
|
| @In
| User user;
|
|
| @Begin
| public String newTicket() {
| if (changerequest.getCrAction().equals("EDIT")) {
| return "editdoc";
| }
| if (changerequest.getCrAction().equals("NEW")) {
| return "newdoc";
| }
| if (changerequest.getCrAction().equals("MOVE")) {
| return "movedoc";
| }
| if (changerequest.getCrAction().equals("DELETE")) {
| return "deletedoc";
| }
| if (changerequest.getCrAction().equals("OTHER")) {
| return "other";
| }
| //throw exception
| return "home";
| }
|
| @End
| public String submitTicket() {
|
| //CREATE CHANGE REQUEST
|
| getChangeRequestDAO().saveCr(changerequest);
|
| TicketSystem TS = new TicketSystemAction();
|
|
| return TS.startTheCrProcess();
|
| }
|
This was a hunch that worked, Id really like to know why it did what it did but i dont have the time. Ill post again when i work out.....
...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064487#4064487
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064487
19Â years
[JBoss AOP] - Re: Strange problem of aspectizing EJBs
by kabir.khanï¼ jboss.com
I believe that the problem stems from the fact that your classes start with the com.sun prefix. When weaving we ignore a bunch of classes
| public boolean isNonAdvisableClassName(String classname)
| {
| if (ignoreClass(classname)) return true;
| if (includeClass(classname)) return false;
| if (excludeClass(classname)) return true;
| return (classname.startsWith("org.jboss.aop") ||
| classname.endsWith("$aop") ||
| classname.startsWith("javassist") ||
| classname.startsWith("org.jboss.util.") ||
| classname.startsWith("gnu.trove.") ||
| classname.startsWith("EDU.oswego.cs.dl.util.concurrent.") ||
| // System classes
| classname.startsWith("org.apache.tools.ant") ||
| classname.startsWith("org.apache.crimson") ||
| classname.startsWith("org.apache.xalan") ||
| classname.startsWith("org.apache.xml") ||
| classname.startsWith("org.apache.xpath") ||
| classname.startsWith("org.ietf.") ||
| classname.startsWith("org.omg.") ||
| classname.startsWith("org.w3c.") ||
| classname.startsWith("org.xml.sax.") ||
| classname.startsWith("sunw.") ||
| classname.startsWith("sun.") ||
| classname.startsWith("java.") ||
| classname.startsWith("javax.") ||
| classname.startsWith("com.sun.") ||
| classname.startsWith("junit") ||
| classname.startsWith("jrockit.") ||
| classname.startsWith("com.bea.vm.") ||
| classname.startsWith("$Proxy")
| );
| }
|
You will have to refactor your application to use another root package. While unfortunate, this is the simplest way we have at the moment to avoid weaving the com.sun classes internal to the JDK...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064486#4064486
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064486
19Â years
[JBoss jBPM] - persisting process after every single node
by gogoasa
Hello,
IIUC, a process instance is actually persisted when entering a wait node or finishing.
I have a process with non-wait (action) nodes that may last very long (hours) themselves. They are calls to remote clusters so while long, they are not resource-hungry. There is a business need to trace process execution from step to step and I wonder if there are some good practices to follow on this issue.
If I simply do, in each action :
executionContext.getJbpmContext().save(executionContext.getProcessInstance()); executionContext.getJbpmContext().getSessionFactory().getCurrentSession().flush();
nothing happens as the transaction does not commit until the first wait state.
Ideally I would like to save in the database the process after each and every node. My case is an "enterprise" jBPM deployed on JBoss.
Thank you,
Adrian.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064482#4064482
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064482
19Â years