September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1021) Fix DnD code to work in JDK1.4_

by Roy Russo (JIRA)

Fix DnD code to work in JDK1.4_ ------------------------------- Key: JBPORTAL-1021 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1021 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 -- 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, 8 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBESB-39) Add more QA and unit tests

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-39?page=all ] Mark Little updated JBESB-39: ----------------------------- Priority: Critical (was: Major) > Add more QA and unit tests > -------------------------- > > Key: JBESB-39 > URL: http://jira.jboss.com/jira/browse/JBESB-39 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assigned To: Tom Fennelly > Priority: Critical > Fix For: 4.0 > > Time Spent: 1 week, 4 minutes > Remaining Estimate: 0 minutes > > The Rosetta codebase does not come with a lot of tests. We need a lot more before the beta release and certainly for the 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBESB-15) Basic transformation integration using Smooks

by Tom Fennelly (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-15?page=comments#action_12342943 ] Tom Fennelly commented on JBESB-15: ----------------------------------- Will start by integrating it into the existing Rosetta architecture. This will change considerably once the "ultimate" architecture is evolved. > Basic transformation integration using Smooks > --------------------------------------------- > > Key: JBESB-15 > URL: http://jira.jboss.com/jira/browse/JBESB-15 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Transformation Service > Affects Versions: 4.0 > Reporter: Mark Little > Assigned To: Tom Fennelly > Fix For: 4.0 > > > Develop an abstract transformation service interface that does not tie us to any specific implementation. > Look at smooks (http://milyn.org/Smooks) as an initial implementation. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-649) IdentityLock.getFqn() always returns Fqn.ROOT

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-649?page=comments#action_12342942 ] Brian Stansberry commented on JBCACHE-649: ------------------------------------------ Previous comment incorrect; it was broken in 1.4.0.Alpha and 1.4.0.Beta, fixed in 1.4.0.Beta2. > IdentityLock.getFqn() always returns Fqn.ROOT > --------------------------------------------- > > Key: JBCACHE-649 > URL: http://jira.jboss.com/jira/browse/JBCACHE-649 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: 1.4.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Somewhere along the way the fqn field got removed from IdentityLock, and getFqn() got hardcoded to always return Fqn.ROOT. This leads to misleading exception messages and log statements like "org.jboss.cache.lock.TimeoutException: read lock for / could not be acquired by ..." -- when actually the problem was on "/JSESSON/localhost". Just spent an hour on a fruitless search for who could have a WL on "/" . -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-48) I18N/L10N compliance

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-48?page=all ] Mark Little updated JBESB-48: ----------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] Priority: Optional (was: Major) > I18N/L10N compliance > -------------------- > > Key: JBESB-48 > URL: http://jira.jboss.com/jira/browse/JBESB-48 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ESB Core > Reporter: Mark Little > Assigned To: Kurt Stam > Priority: Optional > 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-59) Add in generic bus abstraction

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-59?page=all ] Mark Little updated JBESB-59: ----------------------------- Priority: Critical (was: Major) > Add in generic bus abstraction > ------------------------------ > > Key: JBESB-59 > URL: http://jira.jboss.com/jira/browse/JBESB-59 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Mark Little > Priority: Critical > Fix For: 4.0 > > > Prior to Rosetta, we had the notion of a generic bus with client/service plugins, dispatchers and a message format. All of this needs to be added back to the new 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-58) Add back EPR functionality

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-58?page=all ] Mark Little updated JBESB-58: ----------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.), Interactive Demo/Tutorial] Priority: Critical (was: Major) > Add back EPR functionality > -------------------------- > > Key: JBESB-58 > URL: http://jira.jboss.com/jira/browse/JBESB-58 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ESB Core > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Mark Little > Priority: Critical > Fix For: 4.0 > > > Prior to Rosetta, the Alpha 1 codebase has the EPR capabilities. Add this back. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-60) Place non-public classes and interfaces into internal package structure

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-60?page=all ] Mark Little updated JBESB-60: ----------------------------- Assignee: Esteban Schifman (was: Mark Little) > Place non-public classes and interfaces into internal package structure > ----------------------------------------------------------------------- > > Key: JBESB-60 > URL: http://jira.jboss.com/jira/browse/JBESB-60 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Esteban Schifman > 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

19 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-649) IdentityLock.getFqn() always returns Fqn.ROOT

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-649?page=comments#action_12342941 ] Brian Stansberry commented on JBCACHE-649: ------------------------------------------ Please note that this issue was to fix an issue that cropped up during 1.4 development. The problem was never in any released version of JBoss Cache, not even a beta. > IdentityLock.getFqn() always returns Fqn.ROOT > --------------------------------------------- > > Key: JBCACHE-649 > URL: http://jira.jboss.com/jira/browse/JBCACHE-649 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: 1.4.0 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Somewhere along the way the fqn field got removed from IdentityLock, and getFqn() got hardcoded to always return Fqn.ROOT. This leads to misleading exception messages and log statements like "org.jboss.cache.lock.TimeoutException: read lock for / could not be acquired by ..." -- when actually the problem was on "/JSESSON/localhost". Just spent an hour on a fruitless search for who could have a WL on "/" . -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-21) Registry service interface

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-21?page=all ] Mark Little updated JBESB-21: ----------------------------- Component/s: Registry (was: ESB Core) > Registry service interface > -------------------------- > > Key: JBESB-21 > URL: http://jira.jboss.com/jira/browse/JBESB-21 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Registry > Reporter: Mark Little > Assigned To: Mugdho > Fix For: 4.0 > > > We need a registry. It cannot be WS specific, but JAX-R looks like it still matches. Check out what is available in JBossWS (or elsewhere). Assuming we go the JAX-R route (discuss on forum please), then we need stand-alone JAX-R support and a plugin. -- 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, 8 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 September 2006