April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-911) Clustered recovery cleanup

by Tim Fox (JIRA)

Clustered recovery cleanup -------------------------- Key: JBMESSAGING-911 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-911 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 For a clustered config we assume we can get our xaresource for recovery from any node of the cluster and do recovery on that, this means that transactions can be recovered on different nodes to where they originally where - i.e. we have a shared transaction log. This means other nodes will also load them up into their in memory maps too. Therefore on successful resolution we need to broadcst this across the cluster so they can be removed from other nodes in transaction repositories too. -- 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

19 years

2
6
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-175) Move incomplete deployment checking into MainDeployer

by Scott M Stark (JIRA)

Move incomplete deployment checking into MainDeployer ----------------------------------------------------- Key: JBMICROCONT-175 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-175 Project: JBoss MicroContainer Issue Type: Feature Request Affects Versions: JBossMC_2_0_0 Beta3 Reporter: Scott M Stark Fix For: JBossMC_2_0_0_CR1 Currently all users of the MainDeployer.process have to externally code something like: protected void checkIncomplete() throws DeploymentException { IncompleteDeployments incomplete = IncompleteDeploymentsBuilder.build(mainDeployer, controller); if (incomplete.isIncomplete()) throw new IncompleteDeploymentException(incomplete); } to see if the last process has any deployments in an incomplete state. It would be better if this logic was passed in as a listener with helper implementations for the typical check to avoid this duplication and need to inject kernel controller. -- 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

19 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-886) Port OptimisticJBCCache et al to trunk

by Brian Stansberry (JIRA)

Port OptimisticJBCCache et al to trunk -------------------------------------- Key: EJBTHREE-886 URL: http://jira.jboss.com/jira/browse/EJBTHREE-886 Project: EJB 3.0 Issue Type: Sub-task Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: EJB 3.0 RC11 - FD Currently only on Branch_4_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

19 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-443) Verify JGroups runs on JDK 6

by Bela Ban (JIRA)

Verify JGroups runs on JDK 6 ---------------------------- Key: JGRP-443 URL: http://jira.jboss.com/jira/browse/JGRP-443 Project: JGroups Issue Type: Task Affects Versions: 2.5 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.x -- 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

19 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-414) Backport of 2.5 to run on JDK 1.4

by Bela Ban (JIRA)

Backport of 2.5 to run on JDK 1.4 --------------------------------- Key: JGRP-414 URL: http://jira.jboss.com/jira/browse/JGRP-414 Project: JGroups Issue Type: Task Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 Investigate whether 2.5 can be backported (retro and JSR 166 backport) to run on JDK 1.4 -- 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

19 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-228) move endpoint references to a separate package

by Alejandro Guizar (JIRA)

move endpoint references to a separate package ---------------------------------------------- Key: BPEL-228 URL: http://jira.jboss.com/jira/browse/BPEL-228 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 beta 3 In BPEL 2, endpoint references have been turned into an extensible mechanism, just like sublanguages. Moving endpoint references to a separate package is meant as an aid for the end developer to understand the structure and the components of the mechanism. -- 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

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-225) API documentation for packages and core classes

by Alejandro Guizar (JIRA)

API documentation for packages and core classes ----------------------------------------------- Key: BPEL-225 URL: http://jira.jboss.com/jira/browse/BPEL-225 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Documents Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 Altough the source code is well documented, API documentation is almost unexistent. Writing javadocs for all packages and at least the core classes is a must. -- 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

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-226) upgrade to jBPM jPDL 3.2.Beta1

by Alejandro Guizar (JIRA)

upgrade to jBPM jPDL 3.2.Beta1 ------------------------------ Key: BPEL-226 URL: http://jira.jboss.com/jira/browse/BPEL-226 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 beta 3 Upgrade the jBPM jPDL dependency and make sure unit tests and examples do not break. -- 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

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-227) update user guide to match new distribution package structure

by Alejandro Guizar (JIRA)

update user guide to match new distribution package structure ------------------------------------------------------------- Key: BPEL-227 URL: http://jira.jboss.com/jira/browse/BPEL-227 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Documents Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 The new project structure created a separation between the development and the distribution structure. The user guide must be updated to match the contents of the distribution package. -- 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

19 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (BPEL-223) Convert IntegrationServlet to a servlet context listener

by Alejandro Guizar (JIRA)

Convert IntegrationServlet to a servlet context listener -------------------------------------------------------- Key: BPEL-223 URL: http://jira.jboss.com/jira/browse/BPEL-223 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 beta 3 ServletContextListeners are a viable alternative to servlets for initializing and destroying the integration control. From the Servlet 2.4 spec, section 10.2: "Servlet event listeners support event notifications for state changes in the ServletContext, HttpSession and ServletRequest objects. Servlet context listeners are used to **manage resources** or state held at a JVM level for the application." Their intent definitely seems to match our purposes. Section 10.2.2 provides an example. When the application starts up, the listener creates a connection to the database and stores it in the servlet context. Servlets access the connection from the context as needed. When the application shuts down, the listener closes the connection. Our listener could initialize the integration control and store it in the servlet context, then destroy it. -- 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

19 years, 1 month

2
2
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 April 2007