January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-323) File gateway and input directory parameter

by Burr Sutter (JIRA)

File gateway and input directory parameter ------------------------------------------ Key: JBESB-323 URL: http://jira.jboss.com/jira/browse/JBESB-323 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 CR2 Environment: Windows XP Pro Reporter: Burr Sutter Assigned To: Kevin Conner Fix For: 4.0 the drive letter was required on my Windows box and this might be a problem for other OSs. <fs-provider name="FSprovider1"> <fs-bus busid="helloFileChannel" > <fs-message-filter directory="C:/tmp/ESBInput" input-suffix=".dat" work-suffix=".esbWorking" post-delete="false" post-directory="C:/tmp/ESBOutput" post-suffix=".sentToEsb" error-delete="false" error-directory="C:/tmp/ESBInput" error-suffix=".IN_ERROR" /> </fs-bus> -- 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, 3 months

3
6
0 / 0

[JBoss JIRA] Resolved: (JBAS-3924) InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3924?page=all ] Brian Stansberry resolved JBAS-3924. ------------------------------------ Fix Version/s: JBossAS-4.0.5.SP1 JBossAS-3.2.8.SP2 Resolution: Done Resolved by converting any '$' to a '.' > InvlidationManager$InvlidationGroupImpl produces incorrect log4j DEBGU level setting > ------------------------------------------------------------------------------------ > > Key: JBAS-3924 > URL: http://jira.jboss.com/jira/browse/JBAS-3924 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Ben Wang > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.Beta2, JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 , JBossAS-3.2.8.SP2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > This is reported from a cusomter. The org.jboss.cache.InvalidationManager$InvalidationGroupImpl has log level tracing. However, log4j has problem to handle the InvalidationGroupImpl.getClass() since it has "$" sign to it. As a result, all the log are output as DEBUG even when the category is set as "INFO". > Fix is not to use that. Instead, code it manually. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-1799) Create additional integration tests for JBossCache

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1799?page=all ] Brian Stansberry updated JBAS-1799: ----------------------------------- Fix Version/s: JBossAS-5.0.0.GA (was: JBossAS-4.2.0.CR1) > Create additional integration tests for JBossCache > -------------------------------------------------- > > Key: JBAS-1799 > URL: http://jira.jboss.com/jira/browse/JBAS-1799 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: JBossAS-5.0.0.GA > > Original Estimate: 1 week > Remaining Estimate: 1 week > > When JBossCache module is supplied through the thirdparty jar, we will need additioanl integration testing under current AS to make sure the API is compliant. > Pieces that I can think of are: > 1. Core system classes > 2. JBossAop. This one can be more volatile. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Deleted: (JBAS-3980) test assigment

by Ryan Campbell (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3980?page=all ] Ryan Campbell deleted JBAS-3980: -------------------------------- > test assigment > -------------- > > Key: JBAS-3980 > URL: http://jira.jboss.com/jira/browse/JBAS-3980 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Ryan Campbell > Assigned To: A test commit user > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2853) Integrate JBoss Cache 2.0 into AS 5.0

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2853?page=comments#action_12350643 ] Brian Stansberry commented on JBAS-2853: ---------------------------------------- Trunk has been moved to JBC 2.0.0.Alpha2 > Integrate JBoss Cache 2.0 into AS 5.0 > ------------------------------------- > > Key: JBAS-2853 > URL: http://jira.jboss.com/jira/browse/JBAS-2853 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Manik Surtani > Assigned To: Brian Stansberry > Priority: Critical > Fix For: JBossAS-5.0.0.Beta2 > > > JBC 2.0.0.ALPHA1 was produced for JB5, Beta1. > I'm assigning this issue to the next beta, to track further integration issues. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2251) Fix integration issues

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2251?page=comments#action_12350641 ] Brian Stansberry commented on JBAS-2251: ---------------------------------------- At this point, JBC 2.0 is using: jboss-aop.jar jboss-common-core.jar jboss-j2ee.jar (TransactionManager interfaces) jboss-serialization.jar jboss-backport-concurrent.jar is also on the Eclipse buildpath, I believe to support a JDK 1.4 retro-version. > Fix integration issues > ---------------------- > > Key: JBAS-2251 > URL: http://jira.jboss.com/jira/browse/JBAS-2251 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JBoss Cache > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Priority: Minor > Fix For: JBossAS-5.0.0.Beta2 > > > The JBossCache standalone build includes: > jboss-aop.jar (ok - should be standalone project) > jboss-common.jar (ok - should be standalone project(s)) > jboss-j2ee.jar (TransactionManager interfaces) > jboss-jmx.jar (only for JBossNotificationBroadcasterSupport leaking from jboss-system.jar?) > jboss-minimal.jar (for MarshalledValue, etc.) > jboss-system.jar (for ServiceMBeanSupport) > We are heading for a fall on this (not to mention the other thirdparty jars that could get out-of-sync) > Some of this will probably have to wait until we have the proper federated build. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3956) JACC PolicyContextHandler usage leaks ThreadLocal values

by Brian Stansberry (JIRA)

JACC PolicyContextHandler usage leaks ThreadLocal values -------------------------------------------------------- Key: JBAS-3956 URL: http://jira.jboss.com/jira/browse/JBAS-3956 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2, Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1, JBossAS-4.0.3 Final Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1, JBossAS-4.0.5.SP1 A number of the JACC PolicyContextHandler impls use a ThreadLocal. In many cases, the users of these classes are not making the necessary cleanup call and objects are leaking to the thread via the ThreadLocal. A search for implementations of PolicyContextHandler and then a review of the usage of each impl found problems with: org.jboss.ejb.BeanMetaDataPolicyContextHandler org.jboss.ejb.plugins.EnterpriseBeanPolicyContextHandler org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-3980) test assigment

by Ryan Campbell (JIRA)

test assigment -------------- Key: JBAS-3980 URL: http://jira.jboss.com/jira/browse/JBAS-3980 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Ryan Campbell -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Commented: (JBRULES-218) Add 'forall' Conditional Element

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-218?page=comments#action_12350633 ] Edson Tirelli commented on JBRULES-218: --------------------------------------- $ svn log -r 8834 -v ------------------------------------------------------------------------ r8834 | tirelli | 2007-01-11 20:40:19 -0300 (Thu, 11 Jan 2007) | 1 line Changed paths: M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/ReteooBuilder.java A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/AccumulateBuilder.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/CollectBuilder.java M /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/builder/ReteooRuleBuilder.java JBRULES-218: collect and accumulate are now working ------------------------------------------------------------------------ > Add 'forall' Conditional Element > -------------------------------- > > Key: JBRULES-218 > URL: http://jira.jboss.com/jira/browse/JBRULES-218 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 3.1-m2 > > > Add 'forall' Conditional Element -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBRULES-218) Add 'forall' Conditional Element

by Edson Tirelli (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-218?page=comments#action_12350632 ] Edson Tirelli commented on JBRULES-218: --------------------------------------- $ svn log -r 8829 -v ------------------------------------------------------------------------ r8829 | tirelli | 2007-01-11 17:33:20 -0300 (Thu, 11 Jan 2007) | 1 line Changed paths: A /labs/jbossrules/trunk/drools-core/src/main/java/org/drools/reteoo/TerminalNode.java JBRULES-218: Adding TerminalNode interface ------------------------------------------------------------------------ > Add 'forall' Conditional Element > -------------------------------- > > Key: JBRULES-218 > URL: http://jira.jboss.com/jira/browse/JBRULES-218 > Project: JBoss Rules > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Mark Proctor > Assigned To: Edson Tirelli > Fix For: 3.1-m2 > > > Add 'forall' Conditional Element -- 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, 3 months

1
0
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 January 2007