February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-697) Incorporate information from TSS articles into manual

by Richard Achmatowicz (JIRA)

Incorporate information from TSS articles into manual ----------------------------------------------------- Key: JGRP-697 URL: http://jira.jboss.com/jira/browse/JGRP-697 Project: JGroups Issue Type: Sub-task Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.x Incorporate relevant sections of Vladimir's TSS articles into the manual. -- 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] Created: (JBPORTAL-1898) Upgrade JBoss MC to the same version than ASB4

by Julien Viet (JIRA)

Upgrade JBoss MC to the same version than ASB4 ---------------------------------------------- Key: JBPORTAL-1898 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1898 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Portlet, Portal Web Affects Versions: Identity-1.1, Portlet-2.0, Web-1.2, Common-1.2 Reporter: Julien Viet Assigned To: Julien Viet Fix For: Identity-1.1, Portlet-2.0, Web-1.2, Common-1.2 -- 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
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1200) Session.executor is leaking the first classLoader used

by Clebert Suconic (JIRA)

Session.executor is leaking the first classLoader used ------------------------------------------------------ Key: JBMESSAGING-1200 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1200 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP2 Reporter: Clebert Suconic Assigned To: Clebert Suconic The Session.executor is holding the first ClassLoader reference on its ThreadContextClassLoader. This is also causing invalid classLoader usages when the first ClassLoader used was undeployed, and could lead to other problems on ObjectMessages and StreamMessages. (things like ClassNotFound becuase it's using the wrong classLoader on the executor). -- 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

2
8
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1918) Extend Portlet part of core admin portlet to Portlet 2.0 meta data

by Julien Viet (JIRA)

Extend Portlet part of core admin portlet to Portlet 2.0 meta data ------------------------------------------------------------------ Key: JBPORTAL-1918 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1918 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Julien Viet Fix For: Portlet-2.1 -- 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] Created: (JBPORTAL-1881) Rewrite Portlet Container component lifecycle SPI

by Julien Viet (JIRA)

Rewrite Portlet Container component lifecycle SPI ------------------------------------------------- Key: JBPORTAL-1881 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1881 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Portlet Reporter: Julien Viet Assigned To: Julien Viet Fix For: Portlet-2.0 - need to take in account filters and listeners - current SPI is leaky -- 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
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1913) Remove PortletAPIFactory

by Julien Viet (JIRA)

Remove PortletAPIFactory ------------------------ Key: JBPORTAL-1913 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1913 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Portlet Reporter: Julien Viet Assigned To: Julien Viet Fix For: Portlet-2.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
1
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-314) Extend messaging core to be fully functioning

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-314?page=all ] Tim Fox closed JBMESSAGING-314. ------------------------------- Fix Version/s: 2.0.0 Alpha (was: 2.0.0 Beta) Resolution: Done > Extend messaging core to be fully functioning > --------------------------------------------- > > Key: JBMESSAGING-314 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-314 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Fix For: 2.0.0 Alpha > > > The scope of messaging core should be extended out to the client side and JMS dependencies should only exist on thin layer on the client side. Core should be a fully functioning messaging system with useable clients. -- 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] Created: (JBMESSAGING-480) Change contract of Receiver

by Tim Fox (JIRA)

Change contract of Receiver --------------------------- Key: JBMESSAGING-480 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-480 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox -- 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

3
5
0 / 0

[JBoss JIRA] Deleted: (JBMESSAGING-1125) Allow replication to be turned off for transacted sessions

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-1125?page=all ] Tim Fox deleted JBMESSAGING-1125: --------------------------------- > Allow replication to be turned off for transacted sessions > ---------------------------------------------------------- > > Key: JBMESSAGING-1125 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1125 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > > We should allow the ability to turn off session replication for transacted sessions. > Replicating transacted sessions is only needed to cope with the possibility that another session grabs unacked messages from the queue before the original session. > If the user never has more than one session on the queue at any one time this becomes unnecessary. -- 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] Created: (JBMESSAGING-876) Allow onMessage to be executed on the remoting thread

by Tim Fox (JIRA)

Allow onMessage to be executed on the remoting thread ----------------------------------------------------- Key: JBMESSAGING-876 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-876 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 As an optimisation we should allow message listeners to be executed straight through using the same thread that delivers the message to the message callback handler. This would avoid an extra context switch.. Currently the thread used is from an executor per session - so as to be strictly JMS compliant. -- 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

2
3
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 February 2008