[jira] Resolved: (GERONIMO-5186) EJB spec EJBContainer.createEJBContainer() does not implement spec-defined search algorithm.

["Rick McGuire (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GERONIMO-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick McGuire resolved GERONIMO-5186.
------------------------------------

    Resolution: Fixed

This should be working now according to the spec algorithm and the openejb embedded container is also implementing the call correctly. 

> EJB spec EJBContainer.createEJBContainer() does not implement spec-defined search algorithm. 
> ---------------------------------------------------------------------------------------------
>
>                 Key: GERONIMO-5186
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5186
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: OpenEJB, specs
>    Affects Versions: 3.0
>            Reporter: Rick McGuire
>             Fix For: 3.0
>
>
> The EJB spec (section 22.3.3) defines the search order for EJBContainer.createEJBContainer as this: 
> The EJBContainer bootstrap class will locate all of the container providers by their provider configuration files and call EJBContainerProvider.createEJBContainer(Map<?, ?>) on them in turn until an appropriate backing provider returns an EJBContainer. A provider may deem itself as appropriate for the embeddable application if any of the following are true :
> •The javax.ejb.embeddable.provider property was included in the Map passed to createEJBContainer and the value of the property is the provider's implementation class.
> •No javax.ejb.embeddable.provider property was specified.
> If a provider does not qualify as the provider for the embeddable application, it must return null when createEJBContainer is invoked on it.
> Instead, this method is directly attempting to load the class if the java.ejb.embeddable.provider property is defined and only checking the first located META-INF/services definition otherwise.  In general, this produces the same result, but it is not guaranteed that it will. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.