August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (EJBTHREE-524) implement <unauthenticated-principal> in jboss.xml

by William DeCoste (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-524?page=all ] William DeCoste closed EJBTHREE-524. ------------------------------------ Resolution: Done > implement <unauthenticated-principal> in jboss.xml > -------------------------------------------------- > > Key: EJBTHREE-524 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-524 > Project: EJB 3.0 > Issue Type: Task > Affects Versions: EJB 3.0 RC6 - PFD > Reporter: William DeCoste > Assigned To: William DeCoste > Fix For: EJB 3.0 RC9 - FD > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-598) MDB injection in embedded not working

by William DeCoste (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-598?page=all ] William DeCoste closed EJBTHREE-598. ------------------------------------ Resolution: Done > MDB injection in embedded not working > ------------------------------------- > > Key: EJBTHREE-598 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-598 > Project: EJB 3.0 > Issue Type: Bug > Reporter: Bill Burke > Assigned To: William DeCoste > Fix For: EJB 3.0 RC9 - FD > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3071) MemoryLeak (redeployment) on EJB3

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3071?page=comments#action_12340349 ] Clebert Suconic commented on JBAS-3071: --------------------------------------- No.. this is not related to the MBeanProxy... This is a redeployment leakage. I would need to work with BillB (or someone else he assigns) on this one. There are some containers holding references to datatypes referencing classLoaders (reflection?). This will need some refactoring/decision on how to do this. > MemoryLeak (redeployment) on EJB3 > --------------------------------- > > Key: JBAS-3071 > URL: http://jira.jboss.com/jira/browse/JBAS-3071 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.4.CR2 > Reporter: Clebert Suconic > Assigned To: Bill Burke > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > This might be caused by JBAS-3016: > But I'm seeing this strong reference: > org.jboss.mx.loading.UnifiedClassLoader3@33411906 > !--- org.jboss.ejb3.stateless.StatelessContainer@29610827 > We should make sure EJB3 packages are not leaking. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2225) FCI.getTargets() should be Immutable

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2225?page=all ] Brian Stansberry reopened JBAS-2225: ------------------------------------ Serializing the new ImmutableArrayList in a proxy will break clients that don't have that class, so all the proxy writeObject/External methods need to serialize a clone. Also, ImmutableArrayList needs to use delegation, not just subclassing. If it's a subclass, the internal array gets copied as part of the c'tor; if we're going to do that it makes as much sense to just return a defensive copy of the original ArrayList and not create a separate class. > FCI.getTargets() should be Immutable > ------------------------------------ > > Key: JBAS-2225 > URL: http://jira.jboss.com/jira/browse/JBAS-2225 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Clustering > Affects Versions: JBossAS-4.0.3RC2 > Reporter: Adrian Brock > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.5.CR1 > > > The targets returned from the FamilyClusterInfoImpl.getTargets() should not be modified, > otherwise you can cause ConcurrentModificationException. > To better trap people introducing errors in this area, make a subclass of ArrayList > called ImmutableArrayList and return an implementation of this class from getTargets. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3359) Implement StaleConnection checking logic in JBossJCA

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3359?page=all ] Weston Price resolved JBAS-3359. -------------------------------- Fix Version/s: JBossAS-5.0.0.Beta Resolution: Done Currently this is checked into HEAD. We need to determine with the client that requested this, how they want it applied (ie patch, version upgrade etc, etc) > Implement StaleConnection checking logic in JBossJCA > ---------------------------------------------------- > > Key: JBAS-3359 > URL: http://jira.jboss.com/jira/browse/JBAS-3359 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Weston Price > Assigned To: Weston Price > Priority: Minor > Fix For: JBossAS-5.0.0.Beta > > > Currently JBoss/JCA has no support for handling 'stale' connection conditions wherein a JDBC connection fails during use. The ValidConnectionChecker is only executed prior to use or in the background as of JBoss 4.0.5. Shutting of exception sorting in this situation is a bit drastic in that no exceptions would be seen as FATAL anymore. This feature would add the capablity of handling a stale connection and permit an application to retry SQL executions that may have failed under certain conditions. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3306) Upgrade JBoss AS to use MyFaces 1.1.3

by Stan Silvert (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3306?page=comments#action_12340337 ] Stan Silvert commented on JBAS-3306: ------------------------------------ The MyFaces team is working on this but progress has been slower than expected. I'd like to wait a little longer if we can. Here is a wiki page that is tracking the MyFaces 1.1.4 release: http://wiki.apache.org/myfaces/CoreRelease114 If we are at the point we can't wait any more then we have a tough decision to make. > Upgrade JBoss AS to use MyFaces 1.1.3 > ------------------------------------- > > Key: JBAS-3306 > URL: http://jira.jboss.com/jira/browse/JBAS-3306 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Stan Silvert > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > We need to upgrade JBoss to use MyFaces 1.1.3, which fixes many bugs. This is critical priority for Seam. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-64) General tidy-up of code

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-64?page=comments#action_12340333 ] Mark Little commented on JBESB-64: ---------------------------------- I'd like to remove I from the names of interfaces if its only purpose is to indicate they are interfaces. So IbatchHandler would become BatchHandler, for example. > General tidy-up of code > ----------------------- > > Key: JBESB-64 > URL: http://jira.jboss.com/jira/browse/JBESB-64 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ESB Core, Documentation > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Arvinder Singh > Priority: Minor > Fix For: 4.0 Beta 1 > > > 1) Naming Conventions, e.g IbatchHandler -> IBatchHandler > 2) Property naming conventions > 3) Categorize exceptions instead of just using Exception, e.g ConnectException, etc > 4) import specific classes not * -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3183) Integration with WebSphere MQ 5.x

by Weston Price (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3183?page=comments#action_12340331 ] Weston Price commented on JBAS-3183: ------------------------------------ No. I have been involved with prior tasks. Since I was assigned this late, I don't anticipate getting this done by the code freeze. WAS MQ is not setup in the lab yet. Note, I had luck in getting this to work with MQ 6.0. > Integration with WebSphere MQ 5.x > --------------------------------- > > Key: JBAS-3183 > URL: http://jira.jboss.com/jira/browse/JBAS-3183 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Environment: WebSphereMQ 5.3 with Extended TX client > Reporter: Luc Texier > Assigned To: Weston Price > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1 > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... > we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBESB-37) Architecture and code diagrams

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-37?page=all ] Mark Little closed JBESB-37. ---------------------------- Resolution: Done > Architecture and code diagrams > ------------------------------ > > Key: JBESB-37 > URL: http://jira.jboss.com/jira/browse/JBESB-37 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.0 Beta 1 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > For the rebadged Rosetta ESB codebase. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-29) Create administration guide

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-29?page=all ] Mark Little updated JBESB-29: ----------------------------- Fix Version/s: 4.0 (was: 4.0 Beta 1) > Create administration guide > --------------------------- > > Key: JBESB-29 > URL: http://jira.jboss.com/jira/browse/JBESB-29 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB Core, Documentation > Reporter: Mark Little > Assigned To: Mark Little > Fix For: 4.0 > > -- 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, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006