October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-150) There are too many magic numbers/strings in the code

by Mark Little (JIRA)

There are too many magic numbers/strings in the code ---------------------------------------------------- Key: JBESB-150 URL: http://jira.jboss.com/jira/browse/JBESB-150 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 Particularly in the property space. -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-188) Move schemas to the root of product

by Mark Little (JIRA)

Move schemas to the root of product ----------------------------------- Key: JBESB-188 URL: http://jira.jboss.com/jira/browse/JBESB-188 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Maintenance Pack 1 Reporter: Mark Little Assigned To: Arvinder Singh Fix For: 4.0 Let's get rid of the etc directory for now and move schemas out to the root of product. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBSEAM-411) JPA outside EJB3

by Gavin King (JIRA)

JPA outside EJB3 ---------------- Key: JBSEAM-411 URL: http://jira.jboss.com/jira/browse/JBSEAM-411 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1 Currently we assume a JNDI-bound EMF. If you are using JPA in Tomcat or J2EE, this will not be the case, so we should have a different solution. -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBSEAM-63) Multiple SessionFactorys

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-63?page=all ] Gavin King closed JBSEAM-63. ---------------------------- Fix Version/s: 1.1 Resolution: Done > Multiple SessionFactorys > ------------------------ > > Key: JBSEAM-63 > URL: http://jira.jboss.com/jira/browse/JBSEAM-63 > Project: JBoss Seam > Issue Type: Feature Request > Components: Core > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.1 > > > Currently, you can have Seam boostrap a SF for you using a hibernate.cfg.xml file. There is no way to have multiple SFs started automagically. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-513) Auto compile of XLS found in rule projects

by Michael Neale (JIRA)

Auto compile of XLS found in rule projects ------------------------------------------ Key: JBRULES-513 URL: http://jira.jboss.com/jira/browse/JBRULES-513 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Michael Neale Assigned To: Kris Verlaenen Would be nice if .xls files are in a rules project, that the IDE will try and "compile" them, reporting any errors in the error view (it is possible to get row numbers as well, with some text magic - as the row number should be in the rule name - but the errors could be more serious in which case row numbers are not known). -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-275) Move Selector processing IN the Channel

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=all ] Ovidiu Feodorov updated JBMESSAGING-275: ---------------------------------------- Priority: Major (was: Critical) > Move Selector processing IN the Channel > --------------------------------------- > > Key: JBMESSAGING-275 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Fix For: 1.2.0.Beta1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector. > This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers. > A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-25) Integrate ServerPeer with the 5.0 micro-container

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-25?page=all ] Ovidiu Feodorov updated JBMESSAGING-25: --------------------------------------- Priority: Critical (was: Blocker) > Integrate ServerPeer with the 5.0 micro-container > ------------------------------------------------- > > Key: JBMESSAGING-25 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-25 > Project: JBoss Messaging > Issue Type: Task > Components: AS Integration > Reporter: Ovidiu Feodorov > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta1 > > Attachments: JBMESSAGING-26.tar > > Original Estimate: 1 week > Remaining Estimate: 1 week > > This is critical to kick start ESB -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-92) Integrate and enable multiplex transport

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-92?page=all ] Ovidiu Feodorov updated JBMESSAGING-92: --------------------------------------- Priority: Major (was: Critical) > Integrate and enable multiplex transport > ---------------------------------------- > > Key: JBMESSAGING-92 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-92 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Remoting > Reporter: Ovidiu Feodorov > Assigned To: Ron Sigal > Fix For: 1.2.0.Beta1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Replace "Connector per Consumer" solution with a Remoting UIL2-like transport > The ConsumerInterceptor creates a new Connector instance per each Consumer, and associates maintains a reference to it as transitory metadata, so it can shut it down when the Consumer closes. > The Connector is necessary as a callback server for asynchronous notifications. The MessageCallbackHandler instance is registered to it. Maintaining an instance per Consumer is necessary to avoid port conflicts. > This is a temporary solution until JBoss Remoting gets an UIL2-like transport. > As long as we maintain a server socket per consumer, it won't be possbile to receive asynchronous notifications over firewalls. > until multiplex performance is better it should not be the default tranport but should be available nevertheless -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-407) XARecovery integration of JBossMessaging with JBossTS

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Ovidiu Feodorov updated JBMESSAGING-407: ---------------------------------------- Priority: Critical (was: Major) > XARecovery integration of JBossMessaging with JBossTS > ----------------------------------------------------- > > Key: JBMESSAGING-407 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-407 > Project: JBoss Messaging > Issue Type: Patch > Components: Tests and Performance > Environment: JBoss 4.0.3SP1, JBossTs 4.2GA, JBOSS Messagig 1.0.1CR2 > Reporter: Madhusudhan Konda > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Beta1 > > Attachments: artifacts.zip, jms-recovery-patch-all.txt, jms.zip, JMSProviderXAResourceRecovery.java, xa.zip, xarecovery-patch.txt, XATestStandaloneRecovery.java > > Original Estimate: 1 week > Remaining Estimate: 1 week > > To make JBossMessaging XAResource as recoverable using JBossTS RecoveryManager -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-492) Debug views should remember if they are + or 1

by Mark Proctor (JIRA)

Debug views should remember if they are + or 1 ---------------------------------------------- Key: JBRULES-492 URL: http://jira.jboss.com/jira/browse/JBRULES-492 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Eclipse IDE Reporter: Mark Proctor Assigned To: Kris Verlaenen Fix For: 3.1-m1 When you are continually using the debug views its annoying to keep pressing the + to expand, it would be nice if it stayed expanded once it was selected. -- 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, 7 months

2
1
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 October 2006