Bug 1084933 - external-context object factory CL does not work in deployment CL if module is configured
Summary: external-context object factory CL does not work in deployment CL if module i...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Naming
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: EAP 6.3.0
Assignee: baranowb
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-07 10:19 UTC by baranowb
Modified: 2014-08-07 12:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-07 12:04:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3197 0 Major Closed ExternalContextFactory cuts context from deployment context/requires dependency on module 2014-08-20 13:44:41 UTC

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 2 Miroslav Novak 2014-08-07 12:04:49 UTC
Closing as upstream jira was also closed.


Note You need to log in before you can comment on or make changes to this bug.