ICEfaces
  1. ICEfaces
  2. ICE-4513

Adopt LIbrary provider framework for ICEfaces tooling

          Details

          • Type: New Feature New Feature
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 1.8.1
          • Fix Version/s: 1.8.2
          • Component/s: Tool Integrations
          • Labels:
            None
          • Environment:
            Eclipse v3.5

            Description

            Eclipse v3.5, actually WTP 3.1, introduces lIbrary provider framework for managing web app libraries properly. The WTP/JSF library management gets deprecated even though existing library will be handled through legacy library provider.

            Have tried OSGIbundle provider, icefaces user library bundle with actionPanel. Finally use jst.jsf downloable library provider is the best due to "immaturity" of library provider framework.

            Later on, a whole new set of osgiBundle provider with icefaces actionalPanel, actionDelegate is required for best ICEfaces library support.

              Activity

              Hide
              Permalink
              Liming Wu added a comment -

              Looks like new library provider framework still have some limitations.
              OSGI bundle provider was first considered but due to "immaturity", we will delay the adoption (no option to remove one of predefined bundle in osgi action panel). user library provider is also considered but due to the fact that icefaces facet is based on wtp.jsf facet, having a separated actionPanel for icefaces specific libraries doesn't work well (BUG?, immaturity?)

              using Downloadable provider associated with jsf facet is current stable solution.

              Show
              Liming Wu added a comment - Looks like new library provider framework still have some limitations. OSGI bundle provider was first considered but due to "immaturity", we will delay the adoption (no option to remove one of predefined bundle in osgi action panel). user library provider is also considered but due to the fact that icefaces facet is based on wtp.jsf facet, having a separated actionPanel for icefaces specific libraries doesn't work well (BUG?, immaturity?) using Downloadable provider associated with jsf facet is current stable solution.

                People

                • Assignee:
                  Liming Wu
                  Reporter:
                  Liming Wu
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: