October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBESB-176) Add a message-attachment driven listener pipeline config option to the Action Processing Pipeline code...

by Tom Fennelly (JIRA)

Add a message-attachment driven listener pipeline config option to the Action Processing Pipeline code... --------------------------------------------------------------------------------------------------------- Key: JBESB-176 URL: http://jira.jboss.com/jira/browse/JBESB-176 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 4.0 Reporter: Tom Fennelly Assigned To: Tom Fennelly Fix For: 4.0 At the moment, the message Action Processing pipeline configuration is always read from a statically configured attribute on the listener configuration. Add an override facility whereby the incoming message can define actions for the processing pipeline via a well known message attachement property (comma separated list same as the static config). -- 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, 3 months

1
1
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=all ] Tim Fox updated JBMESSAGING-275: -------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.2.0.Alpha2) > 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 > Priority: Critical > 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

18 years, 3 months

1
0
0 / 0

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

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-407?page=all ] Tim Fox updated JBMESSAGING-407: -------------------------------- Fix Version/s: 1.2.0.Beta1 (was: 1.2.0.Alpha2) > 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 > 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

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-127) Delayed delivery, redelivery count and pluggable expiration behavior

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-127?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-127: ------------------------------------- This task inlcudes implementing standard DLQ behaviour > Delayed delivery, redelivery count and pluggable expiration behavior > -------------------------------------------------------------------- > > Key: JBMESSAGING-127 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-127 > Project: JBoss Messaging > Issue Type: Feature Request > Components: JMS Facade, Messaging Core > Reporter: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Beta1 > > Original Estimate: 1 week, 2 days > Remaining Estimate: 1 week, 2 days > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-291) Make AOP DTD available online

by Kabir Khan (JIRA)

Make AOP DTD available online ----------------------------- Key: JBAOP-291 URL: http://jira.jboss.com/jira/browse/JBAOP-291 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan The move to labs has rendered the old url http://www.jboss.org/aop/dtd/jboss-aop_1_0.dtd obsolete. Add it to labs so that is is available at http://labs.jboss.com/portal/jbossaop/dtd/jboss-aop_1_0.dtd -- 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, 3 months

1
2
0 / 0

Olvídese de los problemas ... cámbiese con los que saben.

by Hostex

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-389) client-side interceptors are not serializable!

by Gavin King (JIRA)

client-side interceptors are not serializable! ---------------------------------------------- Key: JBSEAM-389 URL: http://jira.jboss.com/jira/browse/JBSEAM-389 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1 ClientSideInterceptor keeps a reference to a SeamInterceptor, which is fine, but the transient Component reference in SeamInterceptor is handled by @PrePassivate/@PostActivate, instead of by readObject()/writeObject(). -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Assigned: (EJBTHREE-640) jboss.xml security-domain element syntax is inconsistent with ejb2.x, jboss-web.xml

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-640?page=all ] Anil Saldhana reassigned EJBTHREE-640: -------------------------------------- Assignee: Anil Saldhana > jboss.xml security-domain element syntax is inconsistent with ejb2.x, jboss-web.xml > ----------------------------------------------------------------------------------- > > Key: EJBTHREE-640 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-640 > Project: EJB 3.0 > Issue Type: Bug > Components: Security > Reporter: Scott M Stark > Assigned To: Anil Saldhana > > Apparently the security-domain element in the ejb3 usage cannot have the java:/jaas prefix. It should be stripped off to remain consistent with existing usage. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (EJBTHREE-640) jboss.xml security-domain element syntax is inconsistent with ejb2.x, jboss-web.xml

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-640?page=all ] Anil Saldhana closed EJBTHREE-640. ---------------------------------- Resolution: Done Taken care of by EJBTHREE-732 > jboss.xml security-domain element syntax is inconsistent with ejb2.x, jboss-web.xml > ----------------------------------------------------------------------------------- > > Key: EJBTHREE-640 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-640 > Project: EJB 3.0 > Issue Type: Bug > Components: Security > Reporter: Scott M Stark > > Apparently the security-domain element in the ejb3 usage cannot have the java:/jaas prefix. It should be stripped off to remain consistent with existing usage. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-399) @Synchronized

by Gavin King (JIRA)

@Synchronized ------------- Key: JBSEAM-399 URL: http://jira.jboss.com/jira/browse/JBSEAM-399 Project: JBoss Seam Issue Type: Feature Request Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1 We can allow some level of multi-client safety using a client-side interceptor. This can't do any better than plain 'ol synchronization though. -- 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, 3 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006