Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-4883047

JSR-114 JDBC Rowset: provider naming convention

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P2 P2
    • 5.0
    • 5.0
    • docs
    • beta
    • sparc
    • solaris_2.6



      Name: sdR10048 Date: 06/24/2003


      Filed By : SPB JCK team (###@###.###)
      JDK : This JSR is not yet in JDK 1.5
      JCK : 1.5
      Platform[s] : Solaris
      switch/Mode :
      JCK test owner : http://javaweb.eng/jct/sqe/JCK-tck/usr/owners.jto
      Failing Test [s] : N/A


      Problem description
      ===================
      Javadoc for SyncFactor.registerProvider says:

      > "See JDBC RowSet Implementations for guidelines on naming JDBC RowSet
      > persistence providers."

      Then we see in SyncProvider class javadoc:

      > "In order for the factory mechanism to provide a SyncProvider instance
      > the naming convention needs to follow a naming convention where by a
      > direct provider name to class name relationship exists. The reference
      > implementation factory mechanism uses this name directly to create a
      > class of this name. This permits RowSet implementations to then
      > acquire the appropriate javax.sql.RowSetReader and
      > javax.sql.RowSetWriter objects."

      Here we see the expected behaviour only for SUN RI. And I did not find
      any words about the naming convention itself. It only says that we
      should follow that convention.

      At this point we can not develop tests for related SyncProvider class
      methods. And that will stop JSR-114 usage by application developers.

      See http://java.sun.com/j2se/javadoc/writingapispecs/index.html#method for more information.

      ======================================================================
      ###@###.### 2003-12-09

            jbrucesunw Jonathan Bruce (Inactive)
            dsvsunw Dsv Dsv (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: