Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 1.5
-
Fix Version/s: 2.0-Alpha3
-
Component/s: Framework, ICE-Components
-
Labels:None
-
Environment:all
Description
ICEfaces jar files currently mix implementation and API classes into the component and icefaces .jar files. To make it easier to deploy ICEfaces in EJB and other contexts with classloader hierarchies, ICEfaces should be separated into icefaces-api.jar and icefaces-impl.jar. It is likely that the ICEfaces components do not need a separate .jar file and could be split across the API and implementation .jar files as appropriate.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Classloader configuration has allowed ICEfaces to be easily used in EAR environments without this .jar file separation. It appears to not be necessary.
Show
Ted Goddard
added a comment - Classloader configuration has allowed ICEfaces to be easily used in EAR environments without this .jar file separation. It appears to not be necessary.
Note that there are a number of complexities to this issue and the ultimate purpose is not strictly separation into API and implementation .jars but the simplified deployment of ICEfaces in all contexts.
EJB deployments make use of three classloaders: a webapp classloader, an EJB classloader, and a unified classloader. ICEfaces .jar separation must ensure that ICEfaces can be conveniently deployed into an EJB context and that ICEfaces TLDs, listeners, and any other .jar scanning takes place as desired.