[JBoss jBPM] - Custom Context Definition
by mpardo
Issue #1
We would need to add some information to the jbpm s <process definition> (at definition moment).
More specifically, we need to specify feasible reasons for each transition from a task node (for example, in a transition called , we would need to indicate the feasible reasons for that cancellation: <incorrect customer>, <incorrect order number>, etc.). All the above at definition moment.
One possible solution might be creating a (which inherits from ContextDefinition) that creates a context instance with a set of variables given by the custom context definition.
In order to make the context definition configurable, we would use an xml file.
Do you think that this solution is adequate or there is a built-in mechanism offered by jbpm to the same thing in a cleaner way?
Issue #2
Does jbpm log each update to a variable of the context instance? How or where it does that?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212376#4212376
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212376
17 years, 2 months
[EJB/JBoss] - Issues with MDB transactions
by born_free_77
One of my MDB is behaving very strangely. The issue is as mentioned below.
When user does some action in web it puts one message in JMS which is consumed by MDB and it calls some SB which runs under transaction. This part works fine. But when request comes from different app for the same action we put that message in jms, mdb picks it up but only this time it does not commits the tx. I commits it only after entire method (onMessage()) is done.
This looks little bit strange as on of the SB's method has RequiresNew attribute which should commit the tx after the method is complete.
Example-
| MDB method
| ------------------------
|
| onMessage()
| {
| someClass.method();
| }
|
| someClass
|
| void method()
| {
| //1st call
| bean1.doSomething();
| bean2.doStuff();
| bean3.work();
| }
|
| bean1 - has required attribute set
| bean2 - has RequiresNew
| bean3 - checks for a flag set by bean2 which for workflow 2 does not commits unless entire method is complete.
|
Any pointer/references in this context is highly appreciated.
---Born
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212361#4212361
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212361
17 years, 2 months
[Beginners Corner] - Re: Serving Static Content JBoss5.0.0.GA
by PeterJ
Darn, that was an old post and they renamed the file, and I didn't double-check the name. Sorry. Look in conf/bootstrap/profile-repository.xml. You want to add a new entry to the applicationURIs property of the SerializableDeploymentRepositoryFactory bean.
As I mentioned, you need to place the static content into a directory that has a .war suffix and the directory you use for applicationURIs must be the parent of that directory. Assume this is your static content:
/opt/stuff/content.war/some.css
/opt/stuff/content.war/mugshot.png
Then set applicationURIs as follows:
<property name="applicationURIs">
| <array elementClass="java.net.URI">
| <value>${jboss.server.home.url}deploy</value>
| <value>/opt/stuff</value>
| </array>
| </property>
In addition, you will want these files:
/opt/stuff/content.war/WEB-INF/web.xml
/opt/stuff/content.war/WEB-INF/jboss-web.xml
The web.xml can be empty:
<web-app></web-app>
The jboss-web.xml can set the root context:
<jboss-web>
| <context-root>/</context-root>
| </jboss-web>
Then also remove the ROOT.war from the deploy directory (it also uses '/' as the context and you cant have two wab apps wit the same root context).
Now you should be able to access you static content as, for example http://localhost:8080/some.css
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212358#4212358
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4212358
17 years, 2 months