Calling Browser.Enumeration on deleted temporary queue is not throwing InvalidDestinationException
--------------------------------------------------------------------------------------------------
Key: JBMESSAGING-1156
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1156
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.4.0.SP1
Reporter: Clebert Suconic
Assigned To: Clebert Suconic
Priority: Minor
Fix For: 1.4.0.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
AS's JChannelFactory subclass should ignore duplicate lifecycle calls
---------------------------------------------------------------------
Key: JBAS-4728
URL: http://jira.jboss.com/jira/browse/JBAS-4728
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta2
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-5.0.0.Beta3
If already created, ignore create(), etc.
--
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
Convert EJB3 and aspects module to use new LoadBalancePolicy
------------------------------------------------------------
Key: EJBTHREE-1117
URL: http://jira.jboss.com/jira/browse/EJBTHREE-1117
Project: EJB 3.0
Issue Type: Task
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: AS 5.0.0.Beta3
Switch the type of all references from the legacy interface that leaks the legacy Invocation class to the new clean interface.
Open issue is what the default impl should be if an @Clustered annotation doesn't name a concrete class.
--
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
Create a LoadBalancePolicy interface that doesn't leak legacy classes
---------------------------------------------------------------------
Key: JBAS-4977
URL: http://jira.jboss.com/jira/browse/JBAS-4977
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Clustering
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.Beta3
Extract a parent interface from the current LBP interface that only has "Object chooseTarget(FamilyClusterInfo)"
--
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
Synchronize users on examples with user names and roles used on JBAS testsuite
------------------------------------------------------------------------------
Key: JBMESSAGING-1155
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1155
Project: JBoss Messaging
Issue Type: Feature Request
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: 1.4.0.SP2
We should have the examples exactly the way they should be used on a JBAS installation but for that we need to change the users and roles on -persistence-service.xml accordingly to what's needed on JBAS.
--
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
Upgrade hsqldb to v1.8.0.8 (from 1.8.0.2)
-----------------------------------------
Key: JBAS-4991
URL: http://jira.jboss.com/jira/browse/JBAS-4991
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Other
Reporter: Dimitris Andreadis
Fix For: JBossAS-5.0.0.Beta3
Use the same version from Branch_4_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
'port-component' not found as a child of 'ejb'
----------------------------------------------
Key: JBAS-4989
URL: http://jira.jboss.com/jira/browse/JBAS-4989
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Thomas Diesler
Fix For: JBossAS-5.0.0.Beta3
--
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
Use a tagged releases for the new jboss-ejb3-cache module
---------------------------------------------------------
Key: JBAS-4687
URL: http://jira.jboss.com/jira/browse/JBAS-4687
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Reporter: Dimitris Andreadis
Assigned To: Carlo de Wolf
Priority: Critical
Fix For: JBossAS-5.0.0.Beta3
Is this a task for Carlo or Brian ?
--
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
Upgrade JBossWeb to 2.1.0.CR2 (from 2.0.1.CR7)
----------------------------------------------
Key: JBAS-4657
URL: http://jira.jboss.com/jira/browse/JBAS-4657
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Web (Tomcat) service
Reporter: Dimitris Andreadis
Assigned To: Remy Maucherat
Fix For: JBossAS-5.0.0.Beta3
Component upgrades need to be tracked in JIRA.
--
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