Bug 918346

Summary:	Binding subcontexts with <lookup> does not work
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	James Livingston <jlivings>
Component:	Naming	Assignee:	emartins
Status:	CLOSED EOL	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.1	CC:	joallen
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-19 12:46:14 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Livingston 2013-03-06 02:11:06 UTC

If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it.

To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/

In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it.

As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works.

Comment 1 JBoss JIRA Server 2013-03-27 18:52:04 UTC

Eduardo Martins <emartins.redhat> made a comment on jira AS7-6655

Allowing resolveresult for naming contexts obtained through managed ref factories

Comment 2 JBoss JIRA Server 2013-03-27 18:56:11 UTC

Eduardo Martins <emartins.redhat> made a comment on jira AS7-6655

Please note, the fix allows this use case to go through, yet it does not introduce any change wrt msc dependencies, which are globally under discussion in the context of AS7-6787