You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Romain Manni-Bucau (JIRA)" <ji...@apache.org> on 2014/05/12 12:13:15 UTC
[jira] [Resolved] (OPENEJB-2093) Testing a WebService through
ApplicationComposer may lead to a null WebServiceContext
[ https://issues.apache.org/jira/browse/OPENEJB-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Romain Manni-Bucau resolved OPENEJB-2093.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 4.6.1
Assignee: Romain Manni-Bucau
@Classes means you define which classes are managed in the app so you need to put the ejb inside the list
> Testing a WebService through ApplicationComposer may lead to a null WebServiceContext
> -------------------------------------------------------------------------------------
>
> Key: OPENEJB-2093
> URL: https://issues.apache.org/jira/browse/OPENEJB-2093
> Project: OpenEJB
> Issue Type: Bug
> Components: tests
> Affects Versions: 4.6.1
> Reporter: Xavier Dury
> Assignee: Romain Manni-Bucau
> Fix For: 4.6.1
>
> Attachments: openejb-2093.zip
>
>
> This bug was really hard to isolate:
> A @Stateless @WebService bean deployed through an ApplicationComposer @Module of type EnterpriseBean|EjbJar|EjbModule will not have its @Resource WebServiceContext injected IF the @Module is annotated with @Classes (even if @Classes is empty).
> The same @Module without the @Classes will work. It will also work if the @Module returns Class<?>[] instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)