Add in thread pool for GpListener
---------------------------------
Key: JBESB-165
URL: http://jira.jboss.com/jira/browse/JBESB-165
Project: JBoss ESB
Issue Type: Feature Request
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
--
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
[ http://jira.jboss.com/jira/browse/JBESB-21?page=all ]
Mark Little closed JBESB-21.
----------------------------
> Registry service interface
> --------------------------
>
> Key: JBESB-21
> URL: http://jira.jboss.com/jira/browse/JBESB-21
> Project: JBoss ESB
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Registry
> Reporter: Mark Little
> Assigned To: Kurt Stam
> Priority: Critical
> Fix For: 4.0
>
>
> We need a registry. It cannot be WS specific, but JAX-R looks like it still matches. Check out what is available in JBossWS (or elsewhere). Assuming we go the JAX-R route (discuss on forum please), then we need stand-alone JAX-R support and a plugin.
--
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
Integrate Registry with services and clients
--------------------------------------------
Key: JBESB-171
URL: http://jira.jboss.com/jira/browse/JBESB-171
Project: JBoss ESB
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation, Registry
Affects Versions: 4.0 Beta 1 Maintenance Pack 1
Reporter: Mark Little
Assigned To: Kurt Stam
Fix For: 4.0
Once the registry support goes into the ESB, we need to look at integrating it within the ESB and how to present it to users. Hopefully a lot of the static configuration information we currently have can be replaced with calls to the registry to obtain EPRs that contain the same information, but in a more dynamic way.
--
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
[ http://jira.jboss.com/jira/browse/JBESB-55?page=comments#action_12346079 ]
Mark Little commented on JBESB-55:
----------------------------------
We'll use Continuum for now as it provides what we need and is freely available to everyone.
> Nightly builds of unit tests
> ----------------------------
>
> Key: JBESB-55
> URL: http://jira.jboss.com/jira/browse/JBESB-55
> Project: JBoss ESB
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Testing
> Reporter: Mark Little
> Assigned To: Kevin Conner
> Priority: Critical
> Fix For: 4.0 RC1
>
> Time Spent: 2 days
> Remaining Estimate: 0 minutes
>
--
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
[ http://jira.jboss.com/jira/browse/JBAS-3272?page=all ]
Dimitris Andreadis updated JBAS-3272:
-------------------------------------
Priority: Critical (was: Major)
Just raising the priority so it's included in the next release.
> update JBossRemoting to version 2.0.0
> -------------------------------------
>
> Key: JBAS-3272
> URL: http://jira.jboss.com/jira/browse/JBAS-3272
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Remoting
> Reporter: Tom Elrod
> Assigned To: Tom Elrod
> Priority: Critical
> Fix For: JBossAS-4.0.6.CR1
>
>
> Need to update JBossAS to include jboss-remoting.jar for version 2.0.0.GA of JBossRemoting.
--
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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-348?page=comments#action_12... ]
Tim Fox commented on JBMESSAGING-348:
-------------------------------------
We should also ensure all tests are run on multi processor machines to ensure we catch multiprocessor specific race conditions.
> Automate test run against all supported databases
> -------------------------------------------------
>
> Key: JBMESSAGING-348
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-348
> Project: JBoss Messaging
> Issue Type: Task
> Reporter: Tim Fox
> Assigned To: Richard Achmatowicz
> Fix For: 1.2.0.CR1
>
>
> The test suite should be run continuously against all databases we supply a configuration for.
> Initially this should be:
> Oracle, MSSQL, MySQL, PostgreSQL, DB2, Sybase and Derby.
--
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
Modify the smoke test suite to run tests in top of JBoss 4.0.5.GA instead of 4.0.5.CR1
--------------------------------------------------------------------------------------
Key: JBMESSAGING-621
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-621
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Ovidiu Feodorov
Assigned To: Tim Fox
Fix For: 1.2.0.Alpha2
--
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
Add an integer check for release-admin.xml's -Did=...
-----------------------------------------------------
Key: JBMESSAGING-583
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-583
Project: JBoss Messaging
Issue Type: Feature Request
Components: Configuration and Management
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Trivial
Fix For: 1.2.0.Alpha2
--
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