[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1787) Refactor the source of jndi-name(s) for no-interface view bindings
jaikiran pai (JIRA)
jira-events at lists.jboss.org
Wed Feb 3 06:03:19 EST 2010
[ https://jira.jboss.org/jira/browse/EJBTHREE-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12510048#action_12510048 ]
jaikiran pai commented on EJBTHREE-1787:
----------------------------------------
The jndi names are now being resolved through JNDI name resolvers. Marking this as resolved.
> Refactor the source of jndi-name(s) for no-interface view bindings
> ------------------------------------------------------------------
>
> Key: EJBTHREE-1787
> URL: https://jira.jboss.org/jira/browse/EJBTHREE-1787
> Project: EJB 3.0
> Issue Type: Task
> Affects Versions: 1.1.2
> Reporter: jaikiran pai
> Assignee: jaikiran pai
>
> Right now, the no-interface view component hardcodes the jndi-names for various binding:
> 1) The no-interface view jndi name is hardcoded to SBMD.getEjbName() + "/no-interface";
> 2) The jndi name for the no-interface stateful view factory is hardcoded to SBMD.getEjbName() + "no-interface-stateful-proxyfactory";
> These names should ideally come from the metadata or some other common component which is available across components so that the jndi-names remain accessible and common to every component.
--
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
More information about the jboss-jira
mailing list