[JBoss jBPM] - Question About Launching a Workflow from Within Another Work
by buggz
Hello all. I'm new to jBPM and I have searched the forums for an answer to this question. I saw a similar issue in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=78536, but it did not seem to completely answer my question...
We have an initial process definition from which a number of additional workflows may execute. Specifically, we are developing a Service Request workflow. The initial request entails reviewing the request for the request type (password change, new software requirement, etc.), and then spawning the necessary secondary workflow depending on the request type.
My question: We are trying to determine if each of these additional workflows should be considered sub-processes, or brand new workflows. I am concerned that if we consider them sub-processes, the main process instance will not end until the entire sub-process has completed. Therefore, instead we'd really like to spawn the secondary request workflow and then immediately end the initial workflow. Is this an advisable way to perform this task?
Here is my rudimentary processdefinition.xml:
<process-definition name="srq">
|
| <!-- SWIMLANES -->
| <swimlane name="analyst">
| <assignment class="org.jbpm.delegation.assignment.ActorAssignmentHandler" config-type="field">
| <type>role</type>
| <name>Analyst</name>
| </assignment>
| </swimlane>
| <swimlane name="requestor">
| <assignment class="org.jbpm.delegation.assignment.ActorAssignmentHandler" config-type="field">
| <type>role</type>
| <name>Requestor</name>
| </assignment>
| </swimlane>
|
| <!-- START-STATE -->
| <start-state name="incoming request">
| <transition to="review request"/>
| </start-state>
|
| <!-- NODES -->
| <task-node name="review request">
| <task name="review" description="#{review.description}">
| <assignment actor-id="#{actor.id}"/>
| </task>
| <transition name="" to="process1"></transition>
| <transition name="cancel" to="done"></transition>
| <transition name="reject" to="done"></transition>
| </task-node>
|
| <end-state name="done"/>
|
| <process-state name="process1">
| </process-state>
|
| </process-definition>
|
Thanks very much in advance for your help.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030707#4030707
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030707
19Â years, 1Â month
[Installation, Configuration & Deployment] - Classloading problem while migrating from jboss 4.0.3 to jbo
by meissa
Hi all,
I'v troubles while trying to deploy my application in jboss 4.0.5.
I've got the errors belows.
log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a "org.apache.log4j.spi.ErrorHandler" variable.
log4j:ERROR The class "org.apache.log4j.spi.ErrorHandler" was loaded by
log4j:ERROR [org.jboss.mx.loading.UnifiedClassLoader3@8c048e{ url=file:/D:/Documents/developpements/workspace/nis_portail_ear/deploy/portail_ear.ear/ ,addedOrder=48}] whereas object of type
log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by [org.jboss.system.server.NoAnnotationURLClassLoader@1a33d48].
log4j:ERROR Could not create an Appender. Reported error follows.
java.lang.ClassCastException: org.jboss.logging.appender.DailyRollingFileAppender
The same application is well deployed in jboss 4.0.3
It seems there is a change in jboss classloading beween the two versions.
I don't want to remove log4j.jar from my application librairies.
Can someone tells how to get rid off this kind of problem.
thank in advance.
Meissa
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030706#4030706
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030706
19Â years, 1Â month
[JBoss Seam] - context management for custom servlets
by codelion
Reference doc section "21.1.3 Seam servlet filters" subsection "Context management for custom servlets" discusses <web:context-filter url-pattern="/whatever/*"/>.
It reads "The context filter expects to find the conversation id of any conversation context in a request parameter named
conversationId. You are responsible for ensuring that it gets sent in the request."
Q1) It doesn't say what happens if there isn't one? If none is found a temporary conversation is started? Yes or no?
Q2) What are all the contexts available (also as found by lookupInStatefulContexts)? Method, Event, Page, Conversation, Session, Business Process and Application? Which ones of the list?
Q3) It isn't clear (says nothing) about transactions. Is the whole servlet request wrapped into one transaction? If so, great.
Q4 if answer to Q3 is "No") So could one annotate the Servlet with a @Name (scoped to event?) and then use @Transactional (for the doGet, doPost) or should one use another class as a component with @Name and in there @Transactional?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030705#4030705
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4030705
19Â years, 1Â month