[JBoss jBPM] - Clarification
by elifarley
Let me clarify the last post with an imaginary use case (close to the real one).
A node in my workflow loads a text file describing stages through which an order request must pass in order to be approved:
--
actor-A, actor-B;
actor-C, actor-D, actor-E;
actor-F;
--
Each order request has its associated text file (otherwise I could simply design a fixed workflow with the appropriate task nodes).
For each line, a task should be assigned to the group of actors listed on that line.
I tried to parse the text file and create a transient, dynamic process definition based on it, so that I could persist it, call it using a process-state node, and then purge it from the database - all from the same master process.
Unfortunately, it doesn't seem to work like that.
I'll try to create this transient process definition and post a JMS message to be later processed. At least it sounds more promising...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208751#4208751
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208751
17 years, 5 months
[Tomcat, HTTPD, Servlets & JSP] - Re: Rewrite url, http code 302 instead of 301.-->It s seem
by jadtn@laposte.net
Hi
The problem seem to be a bug see at the end.
But now how can I have a jbossweb-extras.jar (probabably another jar org/apache/catalina has modification for the patch) for jboss 4.2.x?
I m trying in jboss 4.2.3, jboss 5 GA and the problem exists always.
The jbossweb-extras.jar from jbossweb 1.0 and 2 don't work.
I've trying to do my redirect in a servlet but some files are not in war but in deploy/stats.war/ and this is not hanle by the servlet.
Thanks for your help.
https://jira.jboss.org/jira/browse/JBWEB-67
I'm providing this patch which fixes the following issues with the rewrite valve and makes it's behavior more consistent with mod_rewrite.
| 1: Rewrite conditions were not being processed
| 2: Case insensitive pattern matches were not working
| 3: Send redirect with an arbitrary code now works and uses reflection to see if the method is available so the valve will still work with standalone tomcat
| 4: Patterns are no longer forced to match the whole input for conditions and rules
| 5: The server variable HTTP_HOST included the port if the server wasn't running on the standard ones (80/443)
| 6: QSA is how handled and query strings are appended where appropriate
| 7: Comments are now allowed in the rewrite.properties file
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4208748#4208748
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4208748
17 years, 5 months