Bug 1084933

Summary:	external-context object factory CL does not work in deployment CL if module is configured
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	baranowb <bbaranow>
Component:	Naming	Assignee:	baranowb <bbaranow>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	urgent
Version:	6.3.0	CC:	cdewolf, mnovak
Target Milestone:	---
Target Release:	EAP 6.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-08-07 12:04:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description baranowb 2014-04-07 10:19:08 UTC

Description of problem:
This is offspring of: https://issues.jboss.org/browse/WFLY-3197
The cause https://bugzilla.redhat.com/show_bug.cgi?id=1057168
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. create module
2. create external-context entry with module set to #1
3. create deployment which looks up Proxy via JNDI context created via #2

Actual results:
 - most likely failure, since InitialContext loaded classes may not fallback to CCL, rather use module CL to deserialize deployment interface for which proxy has been looked up

Expected results:
 - this should work.

Additional info:

Comment 1 baranowb 2014-04-25 16:06:05 UTC

JIRA: https://issues.jboss.org/browse/WFLY-3197
Upstream PR: https://github.com/wildfly/wildfly/pull/6204
6.x PR: https://github.com/jbossas/jboss-eap/pull/1283

Comment 2 Miroslav Novak 2014-08-07 12:04:49 UTC

Closing as upstream jira was also closed.