Move code into JBoss svn + refactor rename packages
---------------------------------------------------
Key: JBRULES-679
URL: http://jira.jboss.com/jira/browse/JBRULES-679
Project: JBoss Rules
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Assigned To: Geoffrey De Smet
Priority: Minor
Rename package net.sf.taseree to
org.drools.solver
--
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
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
HTTP poller doesn't stop
------------------------
Key: JBMESSAGING-1039
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1039
Project: JBoss Messaging
Issue Type: Bug
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 1.4.0.CR2
I have temporarily commented out clusterviewupdatetst::testUpdateMixedConnectionFactory since, once started, the HTTP poller doesn't stop.
Maybe this is a bug in remoting - need to investigate.
--
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
Management Queue
----------------
Key: JBMESSAGING-934
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-934
Project: JBoss Messaging
Issue Type: Feature Request
Affects Versions: 1.2.0.SP1, 1.2.0.GA
Reporter: Clebert Suconic
Assigned To: Tim Fox
Fix For: 1.2.1.CR1
This is an Adrian's request...
We could have a management queue to create queues and topics...
--
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
Core refactoring
----------------
Key: JBMESSAGING-989
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-989
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta 1
Core refactoring-
The old core classes are in dire need of reviewing and refactoring.
The hierarchy of channel classes should be collapsed for simplicity, since there is only one real implementation of a channel.
And the router class should be re-examined - do we need iterator etc
Do we need iterator on the channel?
All classes should be made cluster aware (including router).
We can simplify things a *lot*!
--
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
Move client side transaction state to the server side
-----------------------------------------------------
Key: JBMESSAGING-1021
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1021
Project: JBoss Messaging
Issue Type: Task
Reporter: Tim Fox
Assigned To: Tim Fox
Fix For: 2.0.0 Beta 1
Currently we hold the incomplete JMS transactional state on the client side and send it all in one go on commit.
Instead we should store it on the server side. This will simplify things and allow larger transactions to be built without a large pause on commit or exhausting client side memory
--
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