[jira] Closed: (OWB-429) OpenWebBeansEjbPlugin Class Hierarchy

["Gurkan Erdogdu (JIRA)" <ji...@apache.org>]

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

Gurkan Erdogdu closed OWB-429.
------------------------------

    Fix Version/s: 1.0.0-GA
       Resolution: Fixed

> OpenWebBeansEjbPlugin Class Hierarchy
> -------------------------------------
>
>                 Key: OWB-429
>                 URL: https://issues.apache.org/jira/browse/OWB-429
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Java EE Integration
>            Reporter: Jacquelle Leggett
>            Assignee: Gurkan Erdogdu
>             Fix For: 1.0.0-GA
>
>
> Currently, the class hierarchy for OpenWebBeansEjbPlugin is:
> OpenWebBeansEjbPlugin -> OpenWebBeansJavaEEPlugin -> OpenWebBeansWebPlugin -> OpenWebBeansPlugin 
> This forces an OWB EJB plugin to be a web plugin and an EE plugin.  This can be problematic for processes that provide an EJB and web container.  Currently, if the EJB plugin is defined first in org.apache.webbeans.spi.plugins.OpenWebBeansPlugin, then it will always be selected as the web plugin.  To work around this problem, a web plugin has to be defined before the EJB plugin.  
> I also think OpenWebBeansJavaEEPlugin should be removed from OpenWebBeansEjbPlugin's class hierarchy for similar reasons.  A provider should be able to specify the plugin that will serve as the EE plugin and not be forced to use OpenWebBeansEjbPlugin as the EE plugin.  
> I think the resulting plugin class hierarchy should become:
> OpenWebBeansEjbPlugin ->  OpenWebBeansPlugin 
> OpenWebBeansWebPlugin -> OpenWebBeansPlugin 
> OpenWebBeansJavaEEPlugin  -> OpenWebBeansPlugin 

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