[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:all-tabpanel ]

Brian Stansberry reassigned WFLY-11609:
---------------------------------------

    Issue Type: Task  (was: Bug)
      Assignee:     (was: Jason Greene)


The attributes involved here are indeed supported in the EAP 6.4 management API. They may even have some true runtime impact. They do affect an MSC service but I haven't looked closely enough to check whether that service does anything meaningful or is just cruft.

Still, the attributes exist and that means for compatibility we have to handle them.

I won't just resolve this as a "Not a Bug" though, as this can serve as a reminder to clean this up if we get to a version where we don't care about supporting a legacy HC that uses this. I'll make it a Task though as the current use of these attributes is not a bug.

> 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)