Nointerface view binding to a jndi name with non-existent subcontext can lead to NameNotFoundException ------------------------------------------------------------------------------------------------------ Key: EJBTHREE-2002 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2002 Project: EJB 3.0 Issue Type: Bug Components: nointerface Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB3_1 1.0.3 A stateful bean with a no-interface view deployed through an .ear runs into a NameNotFoundException while trying to bind to something like the following: A/b/no-interface The reason is the StatefulNoInterfaceViewJNDIBinder while binding, does not create any relevant sub-contexts. The fix is to use org.jboss.naming.Util.bind() API to bind to JNDI. This API internally creates any relevant sub-contexts. -- 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