[
https://jira.jboss.org/jira/browse/JBCL-131?page=com.atlassian.jira.plugi...
]
Adrian Brock commented on JBCL-131:
-----------------------------------
Can we please keep discussions in the forums.
To avoid future confusion, jboss-cl has the exactly the same semantics.
Optional dependencies can't trigger a new "wire" getting constructed once
the deployment
has passed the classloader created stage.
Dynamic imports get resolved at runtime so they can pick up the results from lazy
resolution
(or plain old non-lazy resolution).
Add a notion of on demand resolution
------------------------------------
Key: JBCL-131
URL:
https://jira.jboss.org/jira/browse/JBCL-131
Project: JBoss ClassLoader
Issue Type: Sub-task
Components: Dependencies
Reporter: Adrian Brock
Assignee: Adrian Brock
Fix For: JBossCL.2.0.9.GA , JBossCL.2.2.0.Alpha
OSGi has a notion where a dependent classloader/bundle is not rcreated/resolved until
somebody wants to import
one of its exports.
--
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