[ http://jira.jboss.com/jira/browse/JBMESSAGING-168?page=all ]
Tim Fox updated JBMESSAGING-168:
--------------------------------
Fix Version/s: 1.2.1.CR1
(was: Unscheduled)
> Message tests derive from MessageTestBase
> -----------------------------------------
>
> Key: JBMESSAGING-168
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-168
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Tests and Performance
> Reporter: Tim Fox
> Priority: Minor
> Fix For: 1.2.1.CR1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> The jms message tests, e.g. JMSExpirationHeaderTest inherit from MessageTest.
> Therefore all the tests in MessageTest are being re-run for each of the subtypes.
> The hierarchchy of tests is overly complex and confusing.
> We have messagetest, messagetestbase, jmstest, messagingtestcase...... (!)
> The structure should be flattened and simplified to aid comprehension.
--
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
Remote tests occasionaly fail with "Cannot find generator for serverid:server.0"
--------------------------------------------------------------------------------
Key: JBMESSAGING-548
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-548
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.0.1.CR4
Reporter: Ovidiu Feodorov
Assigned To: Ovidiu Feodorov
Priority: Minor
Fix For: 1.0.1.CR5
Apparently MessageIdGeneratorFactory gets inadvertently cleaned, or there are more check ins than check outs for a specific MessageIdGenerator instance.
--
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-225?page=all ]
Tim Fox updated JBMESSAGING-225:
--------------------------------
Fix Version/s: 2.0.0 Beta 1
(was: Unscheduled)
> Explore integrating Adrian's Microcontainer with the Messaging testing environment
> ----------------------------------------------------------------------------------
>
> Key: JBMESSAGING-225
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-225
> Project: JBoss Messaging
> Issue Type: Task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Priority: Minor
> Fix For: 2.0.0 Beta 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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-208?page=all ]
Tim Fox updated JBMESSAGING-208:
--------------------------------
Fix Version/s: Miscellaneous
(was: Unscheduled)
> Example of custom client-side/server-side interceptors
> ------------------------------------------------------
>
> Key: JBMESSAGING-208
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-208
> Project: JBoss Messaging
> Issue Type: Task
> Components: Documentation and Training
> Reporter: Ovidiu Feodorov
> Priority: Minor
> Fix For: Miscellaneous
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Provide an example of writing and configuring a custom client-side and server-side AOP interceptor.
> Add the example to docs/examples so it can be used as an integration test.
--
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
Support for the mail node
-------------------------
Key: GPD-72
URL: http://jira.jboss.com/jira/browse/GPD-72
Project: JBoss jBPM GPD
Issue Type: Task
Affects Versions: jBPM JPDL Designer 3.1.0.alpha3
Reporter: Koen Aers
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.0.alpha4
--
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
Timer and reminder configuration on tasks
-----------------------------------------
Key: GPD-43
URL: http://jira.jboss.com/jira/browse/GPD-43
Project: JBoss jBPM GPD
Issue Type: Task
Affects Versions: jBPM JPDL Designer 3.1.0 alpha1
Reporter: Koen Aers
Assigned To: Koen Aers
Fix For: jBPM JPDL Designer 3.1.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
[ http://jira.jboss.com/jira/browse/JBMESSAGING-217?page=all ]
Tim Fox closed JBMESSAGING-217.
-------------------------------
Resolution: Won't Fix
> DurableSubscription test should probe durable subscriptions instances for in-flight messages
> --------------------------------------------------------------------------------------------
>
> Key: JBMESSAGING-217
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-217
> Project: JBoss Messaging
> Issue Type: Task
> Components: Tests and Performance
> Reporter: Ovidiu Feodorov
> Priority: Minor
> Fix For: Unscheduled
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> Modify DurableSubscriptionTest.testDurableSubscriptionDifferentSelector() to look inside the durable subscription of in-flight messages when a durable subscription message count will be exposed and accessible via a JMX attribute,
--
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
Current Java serialization is always used
-----------------------------------------
Key: JBMESSAGING-794
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-794
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Beta1
Reporter: Tim Fox
Assigned To: Tim Fox
Priority: Minor
Fix For: 1.2.0.CR1
Currently, Java serialization is always used in the only places that serialization is used in JBM:
1) Serializating remoting internal invocations and pings
2) Serializing jms object messages
Although these are non critical, we may want the ability to use JBoss Serialization in this situation
--
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-82?page=all ]
Tim Fox updated JBMESSAGING-82:
-------------------------------
Fix Version/s: 2.0.0 Beta 1
(was: Unscheduled)
> CLIENT_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE optimizations
> -----------------------------------------------------
>
> Key: JBMESSAGING-82
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-82
> Project: JBoss Messaging
> Issue Type: Sub-task
> Components: JMS Facade
> Reporter: Ovidiu Feodorov
> Assigned To: Tim Fox
> Priority: Minor
> Fix For: 2.0.0 Beta 1
>
> Original Estimate: 2 days
> Remaining Estimate: 2 days
>
--
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