CONTRACT ALLOWING/REQUIRING SPECIAL ARRANGEMENTS FOR INTERFACES

0.  Number: 1

1.  This contract is between a SUPPLIER of INTERFACES and
    a CONSUMER of those INTERFACES, both of whom are entities 
    within Sun Microsystems, Incorporated.

2.  The SUPPLIER (definer and/or implementor) is identified by the following:
    Product or Bundle:   Service tags
    Consolidation:  Sysnet
    Department or Group:  SMS Management
    Bugtraq Category/SubCategory: service tags
    Responsible Manager: David Wood

3.  The CONSUMER is identified by the following:
    Product or Bundle:  Sun Java System Message Queue
    Consolidation:   Sun Java System Message Queue 4.2
    Department or Group:  Application Platform Group
    Bugtraq Category/SubCategory: jmq
    Responsible Manager:  Edward Bratt

4.  The INTERFACES are:

    Contracted Project Private:

    Sysnet registration module/API
       * sysnet-all.jar (scn_stprs_util.jar)
 
    Note: the contents of sysnet-all.jar are a subset (created by the 
    application server) of intrfaces in scn_stprs_util.jar.

    These files will be integrated into the installer bundle which is part of the
    product.


5.  The ARC controlling these INTERFACES is: LSARC 

6.  The CASE describing (Exporting) these INTERFACES is: LSARC/2007/341

     These interfaces are private and were not explicitly exported in the ARC case.

7.  The following SPECIAL ARRANGEMENTS are made which modify the rules
    imposed by the stability levels listed in section 4 above:

    [Indicate all that apply by changing the N to a Y and fill in blanks
    as applicable...]

_N_ 7a. Although the stability level doesn't normally restrict it,
        SUPPLIER promises to only modify INTERFACES in an incompatible
 way as follows:

    The Sysnet team (SUPPLIER) does not guarantee any compatibility
    with the interfaces exposed.

_N_ 7b. Although the stability level doesn't normally allow it, CONSUMER will
        expose INTERFACES to a PARTNER, which is external to Sun, namely:

_N_ 7c. Although the stability level doesn't normally allow it, CONSUMER will
        import INTERFACES from a separate consolidation.

_N_ 7d. If SUPPLIER decides to change (including replace or remove) any
 portion of the INTERFACES, SUPPLIER will notify CONSUMER of the
 proposed new version, no later than the application for ARC
 approval of the new version.

 If SUPPLIER and CONSUMER are contained in the same consolidation,
 they have the option of arranging for simultaneous conversion
 to the new interfaces.  If this is not possible, or if they are
 not in the same consolidation, then SUPPLIER will either make best
 effort to work with CONSUMER so that CONSUMER can detect which
 version of INTERFACES is being supplied, or else SUPPLIER will
 make best effort to supply both old and new versions of
 INTERFACES.

 If SUPPLIER cannot make both versions of INTERFACES available,
 and SUPPLIER and CONSUMER cannot devise a method whereby
 CONSUMER can detect which version of INTERFACES is being
 supplied, and the old version of CONSUMER will not run with the
 new version of SUPPLIER, then either the EOL process must be
 followed by SUPPLIER, or else a major release of SUPPLIER will
 be required, or the change will not be allowed.

8. If CONSUMER requires changes in INTERFACES, SUPPLIER will make
   best effort to accommodate such changes, which shall then be
   treated in accordance with paragraph 7 above.

9. Notwithstanding paragraphs 7 and 8, a change to any portion
   of the INTERFACES shall be regarded as a completely new set of
   INTERFACES which require both ARC approval and execution of
   a new contract.

   Sysnet team (SUPPLIER) reserves the right to change 
   this interface in future releases of the software.

10. SUPPLIER and CONSUMER agree that evolution of INTERFACES shall be
    handled as follows:

     The Sysnet team (SUPPLIER) agrees to inform Sun Java System Message Queue team about any 
     future changes on the apis mentioned so that the necessary changes can be made.

11. SUPPLIER and CONSUMER agree that INTERFACES will be supported as
    follows:

     Sysnet (SUPPLIER) team will not guarantee delivering a new version of 
     these jar files for fixing some issues with the private interfaces
     if it is not related to an service tags defect. 

12. SUPPLIER and CONSUMER agree that INTERFACES will be documented as
    follows:

    javadocs and/or mails to the CONSUMER

13. SUPPLIER and CONSUMER agree that changes to the INTERFACES will be
    tested as follows:

    The CONSUMER will test the interfaces for use in their product.

14. SUPPLIER and CONSUMER agree that this contract can be terminated as
    follows:

    By mutual agreement, by making this interface public or due to end
    end of life of either the SUPPLIER or CONSUMER product.

15. This contract is not valid until "signed" via agreement from the
    SUPPLIER and CONSUMER, and approved by the ARC CASE referenced by
    this contract.  E-mail agreement to the contract should be archived
    in the mail archive of CASE; verbal agreement to the contract
    should be noted in the meeting minutes.  This contract remains
    valid until superseded or invalidated.

For SUPPLIER: Binod PG  Date: March 22 2007
For CONSUMER: Linda Schneider    Date: June 6. 2008
For ARC: Linda Schneider Date: June 6, 2008

16. (Not to be filled in until superseded or invalidated.)
    This contract was superseded or invalidated by CASE:
    For ARC:   Date: