[JBoss JIRA] Created: (BPEL-257) rename correlation patterns
by Alejandro Guizar (JIRA)
rename correlation patterns
---------------------------
Key: BPEL-257
URL: http://jira.jboss.com/jira/browse/BPEL-257
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
PROBLEM:
In BPEL 2, the enumerated values of the pattern attribute in <correlation> occurrences within <invoke> changed from the obscure "out", "in" and "out-in" to the much clearer "request", "response" and "request-response".
PROPOSAL:
Update the parser and the upgrade xsl templates to accommodate the new enumerated values.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month
[JBoss JIRA] Created: (BPEL-260) Flow activity might not reactivate parent token in race condition
by Alejandro Guizar (JIRA)
Flow activity might not reactivate parent token in race condition
-----------------------------------------------------------------
Key: BPEL-260
URL: http://jira.jboss.com/jira/browse/BPEL-260
Project: JBoss jBPM BPEL
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Engine
Affects Versions: jBPM BPEL 1.1 beta 3
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Priority: Critical
Fix For: jBPM BPEL 1.1 GA
The flow activity suffers from the same problem as the join node in jPDL. When child tokens performing each nested activity finish concurrently, it is possible that all of them determine that the parent token must not be reactivated yet, leading to deadlock. The cause of this behavior is transaction isolation.
To prevent this problem, the code to leave the flow must acquire exclusive access to the state of the concurrent tokens.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month
[JBoss JIRA] Created: (BPEL-261) use varbinary instead of varchar as data type to store dom elements
by Alejandro Guizar (JIRA)
use varbinary instead of varchar as data type to store dom elements
-------------------------------------------------------------------
Key: BPEL-261
URL: http://jira.jboss.com/jira/browse/BPEL-261
Project: JBoss jBPM BPEL
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Engine
Reporter: Alejandro Guizar
Assigned To: Alejandro Guizar
Fix For: jBPM BPEL 1.1 GA
The documentation for javax.xml.transform.stream.StreamResult {http://java.sun.com/j2se/1.4.2/docs/api/javax/xml/transform/stream/StreamResult.html} reads:
Normally, a stream should be used rather than a [writer], so that the transformer may use instructions contained in the transformation instructions to control the encoding.
It turns out byte streams are preferred over character streams. In consequence, the data type used to store dom elements in the database should be varbinary rather than varchar. Plus, the byte stream output lends itself better to compression.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 1 month