December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-742) Message.getJMSDestination could be null on redeployment of a queue

by Clebert Suconic (JIRA)

Message.getJMSDestination could be null on redeployment of a queue ------------------------------------------------------------------ Key: JBMESSAGING-742 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-742 Project: JBoss Messaging Issue Type: Support Patch Affects Versions: 1.0.1.SP2 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.0.2.CR1, 1.0.2.GA, 1.0.1.SP2 -- 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

15 years, 12 months

3
27
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1201) one MINA connection per VM

by Jeff Mesnil (JIRA)

one MINA connection per VM -------------------------- Key: JBMESSAGING-1201 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1201 Project: JBoss Messaging Issue Type: Sub-task Reporter: Jeff Mesnil Assigned To: Jeff Mesnil -- 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

15 years, 12 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1183) Message Bridge use QueueFactoryRef or TopicFactoryRef instead of FactoryRef when looking up Source and Target Connection Factories

by Aaron Walker (JIRA)

Message Bridge use QueueFactoryRef or TopicFactoryRef instead of FactoryRef when looking up Source and Target Connection Factories ---------------------------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1183 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1183 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Affects Versions: 1.4.0.SP1 Reporter: Aaron Walker Assigned To: Aaron Walker Priority: Minor Some message providers don't have a single base class the implements both the Queue and Topic Connection Factories so you can't create a single JMSProviderLoader where you can set the FactoryRef attribute to a single JNDI name. Really the Message bridge should use the QueueFactoryRef or TopicFactoryRef attribute depending on the destination type that the bridge is trying to connect to. -- 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

15 years, 12 months

3
13
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1195) Optimize in-vm communication

by Jeff Mesnil (JIRA)

Optimize in-vm communication ---------------------------- Key: JBMESSAGING-1195 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1195 Project: JBoss Messaging Issue Type: Sub-task Components: JMS Remoting Reporter: Jeff Mesnil Assigned To: Jeff Mesnil Fix For: 2.0.0 Alpha The new remoting implementation based on MINA is not optimized for in-vm communication: if the JMS client and the JMS server are in the same JVM, the remoting code should not go through the socket and the codec shouldn't be used -- 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

15 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1181) document configuration

by Andy Taylor (JIRA)

document configuration ---------------------- Key: JBMESSAGING-1181 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1181 Project: JBoss Messaging Issue Type: Sub-task Components: Documentation and Training Reporter: Andy Taylor Assigned To: Andy Taylor Fix For: 2.0.0 Alpha document how to configure JBM both inside JBoss and stand alone. -- 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

15 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1182) AuthenticationManager implementation for embedded JBM

by Andy Taylor (JIRA)

AuthenticationManager implementation for embedded JBM ----------------------------------------------------- Key: JBMESSAGING-1182 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1182 Project: JBoss Messaging Issue Type: Sub-task Components: Messaging Core Reporter: Andy Taylor Assigned To: Andy Taylor Priority: Minor Fix For: 2.0.0 Beta When running embedded JBM will need an implementation of an Authentication manager . At the minute a skeleton has been provided with no functionality or the user can provide their own. -- 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

15 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1174) hot deploy for jbm-configuration

by Andy Taylor (JIRA)

hot deploy for jbm-configuration -------------------------------- Key: JBMESSAGING-1174 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1174 Project: JBoss Messaging Issue Type: Sub-task Components: Configuration and Management Affects Versions: 2.0.0 Alpha Reporter: Andy Taylor Assigned To: Andy Taylor Fix For: 2.0.0 Alpha Since Destinations and connection factories are now simple pojos and not mbeans they are not redeployed when the config is changed. we need to add this so we don't regress functionally -- 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

15 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1179) move all jndi into seperate layer

by Andy Taylor (JIRA)

move all jndi into seperate layer --------------------------------- Key: JBMESSAGING-1179 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1179 Project: JBoss Messaging Issue Type: Sub-task Affects Versions: 2.0.0 Alpha Reporter: Andy Taylor Assigned To: Andy Taylor Fix For: 2.0.0 Beta All JNDI lookups should be done in a seperate layer so we can removal depency on JNDI if need be. This is dependant on http://jira.jboss.com/jira/browse/JBMESSAGING-1178 being completed -- 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

15 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1178) Provide simple API for accessing connection factories, creatingconnections and for use in a non jndi environment.

by Andy Taylor (JIRA)

Provide simple API for accessing connection factories, creatingconnections and for use in a non jndi environment. ----------------------------------------------------------------------------------------------------------------- Key: JBMESSAGING-1178 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1178 Project: JBoss Messaging Issue Type: Sub-task Affects Versions: 2.0.0 Alpha Reporter: Andy Taylor Assigned To: Andy Taylor Fix For: 2.0.0 Beta This is typically for users who want to run JBM embedded within their own application. They should be able to lookup destinations etc without needing JNDI -- 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

15 years, 12 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1175) tests need migrating to new framework

by Andy Taylor (JIRA)

tests need migrating to new framework ------------------------------------- Key: JBMESSAGING-1175 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1175 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Affects Versions: 2.0.0 Alpha Reporter: Andy Taylor Assigned To: Andy Taylor Fix For: 2.0.0 Alpha The test framework currently uses a service container to deploy a set of mbean services such as destinations, connection factories etc. We need to re write the framework to use the micro-container to boot the server where needed. -- 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

15 years, 12 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007