[jboss-jira] [JBoss JIRA] (WFLY-11609) ejb3 subsystem configuration for element <entity-bean> will not have any effect and should be removed

[Brian Stansberry (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13684428#comment-13684428 ] 

Brian Stansberry commented on WFLY-11609:
-----------------------------------------

A more immediate task is to deprecate the "default-entity-bean-instance-pool" and "default-entity-bean-optimistic-locking" management attributes and to confirm that the runtime handling related to them done in EJB3SubsystemAdd.performBoottime is cruft and can be removed.

> ejb3 subsystem configuration for element <entity-bean> will not have any effect and should be removed
> -----------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-11609
>                 URL: https://issues.jboss.org/browse/WFLY-11609
>             Project: WildFly
>          Issue Type: Task
>          Components: EJB
>            Reporter: Wolf-Dieter Fink
>            Priority: Trivial
>
> There is the following configuration element 
>         <subsystem xmlns="urn:jboss:domain:ejb3:5.0">
>             ...
>             <entity-bean>
>                 <optimistic-locking enabled="false"/>
>                 <bean-instance-pool pool-name="aPool"/>
>             </entity-bean>
> for the ejb3 subsystem, this seems related to EJB2 EntityBeans which are removed from the container.
> This settings does not have any affect for the current JPA (EJB3) implementation and the EJB2 implementation is removed completely.
> It looks like that only the handler to read, write and manipulate the configuration are still there.
> So the element should be removed from the schema and code.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)