ICEfaces
  1. ICEfaces
  2. ICE-1066

NetBeans -> VWP Application Framework (run time) session scope database connection

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.1
    • Fix Version/s: 1.6DR#3, 1.6
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      Operating System: Windows 2000
      Platform: PC

      Description

      Summary:
      Using vwp netbeans 5.5, with data source (Any).

      Project set up:
      JDBC driver (db client) needs to copy to server container (tomcat) as well as
      add it to project classpath.

      Drag&Drop table from datasource to jsp page.

      set dataTable binding to row set being added.

      Running the project with default Tomcat bundled server

      Application Framework under:
      D:\Program Files\netbeans-5.5\rave2.0\docs\

      netbeans vwp shipped with a new version of Application Framework code
      (appbase.jar) works JSF 1.1 and JSF 1.2.

      Creator 2 Application Framework under:
      D:\Program Files\Sun\Creator2_1\rave2.0\docs

      It has a ViewHandle delegate to D2DViewHandle...

      The problem here is that the support of Application Framework code....


      The sessionBean1 is not in the JSP page, but inside the code in Page bean's. It
      is resolved in the back bean.

      flightDataProvider.setCachedRowSet((javax.sql.rowset.CachedRowSet)getValue("#
      {SessionBean1.flightRowSet}"));

      The problem is that SessionBean is not init.

      The above code works with fine (inside Creator 2). The old appbase library.


      Also, If we switch appbase.jar to the netbeans. It works fine with our
      libraries.

      Appbase is part of bundle inside JSF core design project.


      More likely two options here.

      #1. support new Application Framework. (change our code)

      #2. create a separate JSF core design project (defined separate library being
      used). So we could have full control over project. (required change in netbeans
      module particularly JSF core design project if open source module available).

      second approach allow us to control things in the future release etc ...

      Work Around exists by changing the libraries (several steps manually).

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              Frank Ye
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: