August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-384) Unable to remove a rule after package was merged (addPackage on RuleBase)

by Michael Neale (JIRA)

Unable to remove a rule after package was merged (addPackage on RuleBase) ------------------------------------------------------------------------- Key: JBRULES-384 URL: http://jira.jboss.com/jira/browse/JBRULES-384 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Rule Assemply/SPI Affects Versions: 3.0.3 Reporter: Michael Neale Assigned To: Michael Neale Fix For: 3.0.4, 3.1-m1 Problem is RuleBase was not keeping track of new Rule instances that were added to the RuleBase in binary form. Easy fixed. Need to put in 3.0.x and trunk branches. -- 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

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBAS-2040) Spring Deployer

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2040?page=all ] Dimitris Andreadis updated JBAS-2040: ------------------------------------- Fix Version/s: (was: JBossAS-4.0.5.CR1) The spring deployer is released independently of JBossAS > Spring Deployer > --------------- > > Key: JBAS-2040 > URL: http://jira.jboss.com/jira/browse/JBAS-2040 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Deployment services > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Optional > > Complete me for release notes. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2153) Spring-int tests

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2153?page=all ] Dimitris Andreadis updated JBAS-2153: ------------------------------------- Fix Version/s: (was: JBossAS-4.0.5.CR1) The spring deployer is released independently of JBossAS > Spring-int tests > ---------------- > > Key: JBAS-2153 > URL: http://jira.jboss.com/jira/browse/JBAS-2153 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Test Suite > Reporter: Adrian Brock > Assigned To: Ales Justin > > Need some ant unit tests for spring-int such that we don't break 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2042) Spring deployer and coding standards

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2042?page=all ] Dimitris Andreadis updated JBAS-2042: ------------------------------------- Fix Version/s: (was: JBossAS-4.0.5.CR1) The spring deployer is released independently of JBossAS > Spring deployer and coding standards > ------------------------------------ > > Key: JBAS-2042 > URL: http://jira.jboss.com/jira/browse/JBAS-2042 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Adrian Brock > Assigned To: Ales Justin > Priority: Trivial > > The spring deployer follows incorrect coding standards. > i.e. Kernigan and Ritchie > Also, it should not use printStackTrace(), > nor should it use the horrible log.error and throw paradigm > that just leads to a console full of annoying duplicate logging of errors. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-90) Add recovery module to facilitate coordinator-driven recovery

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBTM-90?page=all ] Mark Little closed JBTM-90. --------------------------- Resolution: Done > Add recovery module to facilitate coordinator-driven recovery > ------------------------------------------------------------- > > Key: JBTM-90 > URL: http://jira.jboss.com/jira/browse/JBTM-90 > Project: JBoss Transaction Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Affects Versions: 4.2 > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.2.1 > > Time Spent: 4 hours > Remaining Estimate: 0 minutes > -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBSEAM-279) Component lifetimes not guaranteed for SFSB backed components.

by Charles Abreu (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-279?page=comments#action_12340430 ] Charles Abreu commented on JBSEAM-279: -------------------------------------- Maybe it is related to this: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=87887 > Component lifetimes not guaranteed for SFSB backed components. > -------------------------------------------------------------- > > Key: JBSEAM-279 > URL: http://jira.jboss.com/jira/browse/JBSEAM-279 > Project: JBoss Seam > Issue Type: Bug > Components: Core > Affects Versions: 1.0.1 > Reporter: ryan dewell > > Seam does not guarantee component lifecycles for SFSB backed components. > The container controls when SFSB's are removed / timed out. When Seam accesses an SFSB that has been removed by the container, it results in an EJBNoSuchObjectException. > The JBoss specific workaround for Session scoped components is to use the @CacheConfig annotation, setting the idle timeout to match the HttpSession timeout. Similar changes would have to be made to any Conversation scoped component that uses a timeout greater than the default SFSB timeout of 5 minutes (which just happens to be the default timeout for Seam conversations). > There is no workaround for Application scoped components. Once removed by the container, EJBNoSuchObjectException's will continue to be thrown as Seam tries to access them. > Seam's context model needs to somehow guarantee that its SFSB instances aren't removed by the container before Seam is finished with them. And/or, it needs to recover from EJBNoSuchObjectException's more gracefully, especially with regards to Application scoped components for which there is no workaround. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-43) Change the module name to "messaging"

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-43?page=all ] Ovidiu Feodorov closed JBMESSAGING-43. -------------------------------------- Resolution: Done > Change the module name to "messaging" > ------------------------------------- > > Key: JBMESSAGING-43 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-43 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Changing the CVS module name from "jms" to "messaging". Things to change: > * the module's directory name > * CVSROOT/modules > * tools/etc/buildmagic/modules.ent > * tools/etc/buildmagic/modules.xml > * jms/tests/build.xml > * jms/build.xml -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-43) Change the module name to "messaging"

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-43?page=all ] Ovidiu Feodorov closed JBMESSAGING-43. -------------------------------------- Resolution: Out of Date Rendered irrelevant by migration to SVN > Change the module name to "messaging" > ------------------------------------- > > Key: JBMESSAGING-43 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-43 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Changing the CVS module name from "jms" to "messaging". Things to change: > * the module's directory name > * CVSROOT/modules > * tools/etc/buildmagic/modules.ent > * tools/etc/buildmagic/modules.xml > * jms/tests/build.xml > * jms/build.xml -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBMESSAGING-43) Change the module name to "messaging"

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-43?page=all ] Ovidiu Feodorov reopened JBMESSAGING-43: ---------------------------------------- > Change the module name to "messaging" > ------------------------------------- > > Key: JBMESSAGING-43 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-43 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Changing the CVS module name from "jms" to "messaging". Things to change: > * the module's directory name > * CVSROOT/modules > * tools/etc/buildmagic/modules.ent > * tools/etc/buildmagic/modules.xml > * jms/tests/build.xml > * jms/build.xml -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-43) Change the module name to "messaging"

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-43?page=all ] Ovidiu Feodorov updated JBMESSAGING-43: --------------------------------------- Fix Version/s: 1.2.0.Alpha1 (was: 1.2.1) > Change the module name to "messaging" > ------------------------------------- > > Key: JBMESSAGING-43 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-43 > Project: JBoss Messaging > Issue Type: Task > Components: Build System > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Minor > Fix For: 1.2.0.Alpha1 > > Original Estimate: 1 day > Remaining Estimate: 1 day > > Changing the CVS module name from "jms" to "messaging". Things to change: > * the module's directory name > * CVSROOT/modules > * tools/etc/buildmagic/modules.ent > * tools/etc/buildmagic/modules.xml > * jms/tests/build.xml > * jms/build.xml -- 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

17 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006