[jboss-jira] [JBoss JIRA] Moved: (JBJCA-17) JMS Message Inflow

[Jesper Pedersen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBJCA-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesper Pedersen moved JBAS-1434 to JBJCA-17:
--------------------------------------------

              Project: JBoss JCA  (was: JBoss Application Server)
                  Key: JBJCA-17  (was: JBAS-1434)
          Component/s: JMS
                           (was: JCA service)
        Fix Version/s:     (was: JBossAS-5.1.0.Beta1)
    Affects Version/s:     (was: JBossAS-4.0.2 Final)
             Security:     (was: Public)


> JMS Message Inflow
> ------------------
>
>                 Key: JBJCA-17
>                 URL: https://jira.jboss.org/jira/browse/JBJCA-17
>             Project: JBoss JCA
>          Issue Type: Task
>          Components: JMS
>            Reporter: Adrian Brock
>            Assignee: Jesper Pedersen
>
> Forums Discussion Thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=48672
> The JMS message inflow in the JMS resource adapter needs properly testing.
> There are basic tests, but the following are missing:
> 1) Complete tests of edge cases for each configuration parameter in the activation spec
> 2) Failure tests to confirm the implementation handles error gracefully
> 3) Stress tests to make sure there the implementation is stable
> 4) Performance tests to optimize the implementation
> Additionally, we need to confirm that it is possible to use this implementation for EJB2.0
> style deployments and hence as the default configuration. 
> This should be possible provided the user has not created their own
> container configuration that uses the old JMSContainerInvoker explicitly.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira