October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-231) integration service opens request listeners even if tx marked for rollback

by Alejandro Guizar (JIRA)

integration service opens request listeners even if tx marked for rollback -------------------------------------------------------------------------- Key: BPEL-231 URL: http://jira.jboss.com/jira/browse/BPEL-231 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 Fix For: jBPM BPEL 1.1.GA When JmsIntegrationService closes, it opens the request listeners created by inbound message activities that were reached in the closing bpm operation. However, it carelessly opens request listeners even if the transaction is marked for rollback. In this situation the opened request listeners end up referencing tokens that do not exist in the database. -- 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

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-232) Missing "description" property in BpelDefinition mapping

by Alejandro Guizar (JIRA)

Missing "description" property in BpelDefinition mapping -------------------------------------------------------- Key: BPEL-232 URL: http://jira.jboss.com/jira/browse/BPEL-232 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 Fix For: jBPM BPEL 1.1.GA In jBPM 3.2.beta1, the ProcessDefinition mapping contains a "description" property. This property is missing in the BpelDefinition mapping. Go to the JBoss Forum Reference for an explanation. Beyond synchronizing the BpelDefinition mapping with the ProcessDefinition mapping, a definitive solution for this mapping duplication is desirable. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (BPEL-233) Clean up activity XML readers

by Alejandro Guizar (JIRA)

Clean up activity XML readers ----------------------------- Key: BPEL-233 URL: http://jira.jboss.com/jira/browse/BPEL-233 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 -- 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

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-234) Merge Invoker, Receiver and Replier into a single table

by Alejandro Guizar (JIRA)

Merge Invoker, Receiver and Replier into a single table ------------------------------------------------------- Key: BPEL-234 URL: http://jira.jboss.com/jira/browse/BPEL-234 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 -- 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

1
4
0 / 0

[JBoss JIRA] Created: (BPEL-217) make bpel-definition.xml optional

by Alejandro Guizar (JIRA)

make bpel-definition.xml optional --------------------------------- Key: BPEL-217 URL: http://jira.jboss.com/jira/browse/BPEL-217 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 the definition descriptor fills the gap of a document import mechanism in v1.1. v2 does provide such a mechanism, making the descriptor redundant for v2 deployments. -- 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

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-218) use imported documents as the default service catalog

by Alejandro Guizar (JIRA)

use imported documents as the default service catalog ----------------------------------------------------- Key: BPEL-218 URL: http://jira.jboss.com/jira/browse/BPEL-218 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 wsdl documents imported by a process are not examined during resolution of partner services, because an alternate, more dynamic service catalog (e.g. an XML registry) is expected to be in place. however, in trivial scenarios, such as deployment from the designer, no alternate catalog exists and the main, if not sole, source of partner information is the list of imported documents. -- 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

2
9
0 / 0

[JBoss JIRA] Created: (BPEL-229) Migrate from a SAR to an EAR-based deployment

by Alejandro Guizar (JIRA)

Migrate from a SAR to an EAR-based deployment --------------------------------------------- Key: BPEL-229 URL: http://jira.jboss.com/jira/browse/BPEL-229 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 current SAR-based deployment model is nonportable. Migrate to the new EAR-based deployment model introduced in jBPM jPDL 3.2. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-216) integration with the eclipse bpel designer

by Alejandro Guizar (JIRA)

integration with the eclipse bpel designer ------------------------------------------ Key: BPEL-216 URL: http://jira.jboss.com/jira/browse/BPEL-216 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 Enable one-step deployment of a bpel process + interface wsdl definitions. -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4639) Optimized replication of ClusteredSession metadata

by Brian Stansberry (JIRA)

Optimized replication of ClusteredSession metadata -------------------------------------------------- Key: JBAS-4639 URL: http://jira.jboss.com/jira/browse/JBAS-4639 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Stop storing clustered session metadata as a single key value pair in JBossCache. Instead, separate those attributes prone to frequent change (s/b just the access timestamp) from those that are largely fixed at session creation. Call cache.put() with the "fixed" ones only on the first request (or in the less likely event that something changes in them, e.g. timeout interval, in a later request.) Store the timestamp with every request; perhaps less often if the request didn't change anything else in the session, i.e. no more often than every 30 secs. With this we can get rid of hacky stuff like using Subject/Observer to track FIELD granularity pojo attribute changes. We just do that so we know whether to replicate session the metadata. -- 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

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4068) Port JBAS-4067 fix to trunk

by Brian Stansberry (JIRA)

Port JBAS-4067 fix to trunk --------------------------- Key: JBAS-4068 URL: http://jira.jboss.com/jira/browse/JBAS-4068 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2 -- 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

3
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007