[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-2091) Singleton EJBs do not honor @LocalBinding

[jaikiran pai (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-2091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12530656#action_12530656 ] 

jaikiran pai commented on EJBTHREE-2091:
----------------------------------------

>> Additionally, we're missing INFO logging about where the proxies are bound.

The real reason why I left out that INFO logging is because, the actual binding now happens separately for each binding. So we don't bind as a bunch. Maybe we can just log it at INFO as and when the binding happens? I'll create a separate JIRA for this one.

>> This warning is also present:

>> 18:35:11,166 WARN [org.jboss.ejb3.session.SessionContainer] No JndiSessionRegistrarBase was found; byassing binding of Proxies to jboss.j2ee:service=EJB3,name=DbInitializerBean in Global JNDI. 

Yes, that needs to go because the JNDI binding is no longer part of the container lifecycle. I'll add a JIRA to remove that WARN.


> Singleton EJBs do not honor @LocalBinding
> -----------------------------------------
>
>                 Key: EJBTHREE-2091
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2091
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: singleton
>    Affects Versions: EJB3_1 1.0.7
>            Reporter: Andrew Lee Rubinger
>            Assignee: jaikiran pai
>
> Given bean implementation class:
> @Singleton
> @Startup
> @Local(DbInitializerLocalBusiness.class)
> @LocalBinding(jndiBinding = DbInitializerLocalBusiness.JNDI_NAME)
> // JBoss-specific JNDI Binding annotation
> @TransactionManagement(TransactionManagementType.BEAN)
> // We'll use bean-managed Tx's here, because @PostConstruct is fired in a
> // non-transactional context anyway, and we want to have consistent
> // handling when we call via "refreshWithDefaultData".
> public class DbInitializerBean implements DbInitializerLocalBusiness
> Global JNDI reports:
>  +- DbInitializer (proxy: $Proxy143 implements interface org.jboss.ejb3.examples.chxx.transactions.ejb.DbInitializerLocalBusiness)
> Additionally, we're missing INFO logging about where the proxies are bound.  This warning is also present:
> 18:35:11,166 WARN  [org.jboss.ejb3.session.SessionContainer] No JndiSessionRegistrarBase was found; byassing binding of Proxies to jboss.j2ee:service=EJB3,name=DbInitializerBean in Global JNDI.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira