ICEfaces
  1. ICEfaces
  2. ICE-1368

separate ICEfaces into API and implementation jar files

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major 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

        Ted Goddard created issue -
        Ken Fyten made changes -
        Field Original Value New Value
        Estimated Complexity Medium
        Fix Version/s 2.0 [ 10032 ]
        Affects Version/s 1.5 [ 10027 ]
        Affects Version/s 1.6DR#2 [ 10040 ]
        Hide
        Ted Goddard added a comment -

        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.

        Show
        Ted Goddard added a comment - 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.
        Hide
        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.

        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.
        Ted Goddard made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Ken Fyten made changes -
        Resolution Fixed [ 1 ]
        Status Resolved [ 5 ] Reopened [ 4 ]
        Ken Fyten made changes -
        Status Reopened [ 4 ] Closed [ 6 ]
        Resolution Won't Fix [ 2 ]

          People

          • Assignee:
            Unassigned
            Reporter:
            Ted Goddard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: