From markcarl@sac.sfbay.sun.com Wed Feb 11 16:21:07 2009 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1C0L7vk019132 for ; Wed, 11 Feb 2009 16:21:07 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1C0L560015897; Wed, 11 Feb 2009 16:21:06 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEX00D0LFN5H300@nwk-avmta-1.sfbay.Sun.COM>; Wed, 11 Feb 2009 16:21:05 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEX004LXFN53160@nwk-avmta-1.sfbay.Sun.COM>; Wed, 11 Feb 2009 16:21:05 -0800 (PST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1C0L5HW022350; Wed, 11 Feb 2009 16:21:05 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1C0L3ej019127; Wed, 11 Feb 2009 16:21:03 -0800 (PST) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1C0L3XI019123; Wed, 11 Feb 2009 16:21:03 -0800 (PST) Date: Wed, 11 Feb 2009 16:21:03 -0800 (PST) From: Mark Carlson Subject: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] To: LSARC-ext@sun.com Cc: Drools_Team@sun.com Message-id: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 14179 I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 02/18/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc are in the case directory and the checklist and man page are attached. -- mark Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: jettison 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 11 February, 2009 2. Project Summary 2.1 Project Description Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. 4. Technical Description: Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. 5. Interfaces Exported interface Classification Interface type ============================= ============== ============== org.codehaus.jettison * Convention Uncommitted Interface org.codehaus.jettison.json * JSONString Uncommitted Interface The Jar file would go in "usr/share/lib/java" Imported interface Classification Comments ======================= ============== =================================== None 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: SFW 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open FCL--FOSS Check List 1.0 Project Information 1.1 Name of project/component jettison Ver 1.0 1.2 Author of document Vivek R. Titarmare 2.0 Project Summary 2.1 Project Description Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). Interface stabilities and contracts will be added to the consuming case(s) as needed. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [X] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name The Codehaus Jettison (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [X] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [X] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [X] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [X] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [X] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [X] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [X] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [X] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [X] Yes [ ] No If yes are these components packaged to be shared with the other FOSS? [X] Yes [ ] No - ARC review required [ ] N/A Are these components already in the Solaris WOS? [ ] Yes [X] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [X] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [X] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [X] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [X] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [X] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [X] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [X] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [X] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [X] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [X] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [X] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [X] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [X] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [X] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [X] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [ ] Yes [X] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [X] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [X] No 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces The jar file "jettison_1.0.jar" contains following interface. Interface Name Classification Comments --------------------------- ------------------- --------------------------- org.codehaus.jettison * Convention Uncommitted Interface org.codehaus.jettison.json * JSONString Uncommitted Interface The Jar file would go in "usr/share/lib/java" 4.2 Imported Interfaces Interface Name Classification Comments --------------------------- -------------------- -------------------------- None Appendix B - Suggested case materials 1. man pages Attached are the zipped Java docs (jittison.zip_) 2. SMF manifests 3. links to contracts Introduction to Library Functions jettison(3) NAME jettison - A JSON (JavaScript Object Notation) STax (Stream- ing API for XML) Implementation DESCRIPTION jettison(3) is a collection of Java APIs (like STaX and DOM - Document Object Model ) which read and write JSON. For additional information on using jettison, browse the com- plete html documentation at: file:/usr/share/lib/java/javadoc/jettison/index.html LICENSE ASL 2.0 FILES /usr/share/lib/java/jettison-1.0.jar jettison jar file /usr/share/lib/java/javadoc/jettison/index.html jettison API documentation generated with javadoc. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: _______________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE| |_______________________________________ | Availability | SUNWjettison | |_______________________________________ | Interface Stability| Uncommitted | |____________________|_________________| SEE ALSO http://jettison.codehaus.org NOTES Source for jettison is available on http://opensolaris.org SunOS 5.10 Last change: 6 Feb 2009 1 From margot.miller@sun.com Thu Feb 12 12:37:40 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1CKbdlE019889 for ; Thu, 12 Feb 2009 12:37:40 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n1CKbXGX005401; Fri, 13 Feb 2009 04:37:36 +0800 (SGT) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEY00A0HZYL0900@brm-avmta-1.central.sun.com>; Thu, 12 Feb 2009 13:37:33 -0700 (MST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEY00LP5ZYLYPA0@brm-avmta-1.central.sun.com>; Thu, 12 Feb 2009 13:37:33 -0700 (MST) Received: from [10.7.250.251] (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1CKbOQj813035; Thu, 12 Feb 2009 12:37:26 -0800 (PST) Date: Thu, 12 Feb 2009 12:34:01 -0800 From: Margot Miller Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> To: Mark Carlson Cc: LSARC-ext@sun.com, Drools_Team@sun.com Message-id: <499487B9.9020005@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 15149 Is this being delivered in its own package, and if so, can you put it in the interface table? Thanks Margot Mark Carlson wrote: > I am sponsoring this familiarity case for Vivek Titarmare. It requests minor > binding and times out 02/18/2009. This Fast Track represents a component of > LSARC 2008/748 - Drools. > The FOSS checklist, man page and javadoc are in the case directory and > the checklist and man page are attached. > > -- mark > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > jettison > 1.2. Name of Document Author/Supplier: > Author: Vivek Titarmare > 1.3 Date of This Document: > 11 February, 2009 > > 2. Project Summary > 2.1 Project Description > > Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. > > 4. Technical Description: > > Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. > > 5. Interfaces > > Exported interface Classification Interface type > ============================= ============== ============== > org.codehaus.jettison > * Convention Uncommitted Interface > > org.codehaus.jettison.json > * JSONString Uncommitted Interface > > > > The Jar file would go in "usr/share/lib/java" > > Imported interface Classification Comments > ======================= ============== =================================== > None > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > > > FCL--FOSS Check List > > 1.0 Project Information > 1.1 Name of project/component > jettison Ver 1.0 > > 1.2 Author of document > Vivek R. Titarmare > > 2.0 Project Summary > 2.1 Project Description > Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. > > This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). > Interface stabilities and contracts will be added to the consuming case(s) as needed. > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [X] Minor > [ ] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [X] Yes > [ ] No > > 2.4 Originating Community > 2.4.1 Community Name > The Codehaus Jettison (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) > > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [X] Monitoring > > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [X] Yes > [ ] No - briefly explain > > > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [X] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris Software > (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) > Does this project follow the Install Locations best practice? > [X] Yes > [ ] No - ARC review required > > Does this project install into /usr under [sbin|bin|lib|include|man|share]? > [X] Yes > [ ] No or N/A > > Does this project install into /opt? > [ ] Yes - explain below > [X] No or N/A > > Does this project install into a different directory structure? > [ ] Yes - ARC review required > [X] No or N/A > > Do any of the components of this project conflict with anything under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) > [ ] Yes - explain below > [X] No > > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [X] No > > 3.1.1W Windows Installation - section only required for Windows Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a > :\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > > Does the project use > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [X] Yes > [ ] No > > If yes are these components packaged to be shared with the other FOSS? > [X] Yes > [ ] No - ARC review required > [ ] N/A > > Are these components already in the Solaris WOS? > [ ] Yes > [X] No - continue with next section (section 3.2) > > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [X] Yes > [ ] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [X] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [X] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any private non-public files into /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [X] No > > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [X] No > > 3.4 Security > 3.4.1 Secure By Default > (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) > (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) > (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [X] No - continue with the next section (section 3.4.2) > > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [X] N/A > > Are network services automatically enabled by the project during installation? > [ ] Yes - ARC review required > [ ] No > [X] N/A > > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is the receiver authenticated prior to receiving any sensitive outbound communication? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > 3.4.2 Authorization > (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [X] No - continue with next section (section 3.4.3) > > If yes then are the setuid/setgid privileges handled by the use of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Does this component contain administrative or security enforcing software? > [ ] Yes - ARC review required > [X] No - continue to next section (section 3.4.4) > > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Do the components create audit logs detailing what took place including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [ ] No - ARC review required > > > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [X] No - continue to next section (section 3.4.5) > > If yes do the components use PAM (plugable authentication modules) for authentication? > [ ] Yes > [ ] No - ARC review required > > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > > If yes are the components sufficiently privileged to allow the requested > operations (authentication, password change, process credential manipulation, > audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [X] No - continue to next section (section 3.4.6) > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > > If yes are the permissions on the file such to protect exposing the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) > Are there any network protocols used by this project? > [ ] Yes > [X] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [X] No - continue with the next section (section 3.6) > > If yes do the components support IPv6? > [ ] Yes > [ ] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [X] No > > 4.0 Interfaces > (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) > 4.1 Exported Interfaces > > The jar file "jettison_1.0.jar" contains following interface. > > Interface Name Classification Comments > --------------------------- ------------------- --------------------------- > org.codehaus.jettison > * Convention Uncommitted Interface > > org.codehaus.jettison.json > * JSONString Uncommitted Interface > > The Jar file would go in "usr/share/lib/java" > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- -------------------------- > None > > > Appendix B - Suggested case materials > 1. man pages > > Attached are the zipped Java docs (jittison.zip_) > > 2. SMF manifests > 3. links to contracts > > > > > Introduction to Library Functions jettison(3) > > NAME > jettison - A JSON (JavaScript Object Notation) STax (Stream- > ing API for XML) Implementation > > DESCRIPTION > jettison(3) is a collection of Java APIs (like STaX and DOM > - Document Object Model ) which read and write JSON. For > additional information on using jettison, browse the com- > plete html documentation at: > > file:/usr/share/lib/java/javadoc/jettison/index.html > > LICENSE > ASL 2.0 > > FILES > /usr/share/lib/java/jettison-1.0.jar > > jettison jar file > > /usr/share/lib/java/javadoc/jettison/index.html > > jettison API documentation generated with javadoc. > > ATTRIBUTES > See attributes(5) for descriptions of the following attri- > butes: > > _______________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE| > |_______________________________________ > | Availability | SUNWjettison | > |_______________________________________ > | Interface Stability| Uncommitted | > |____________________|_________________| > > SEE ALSO > http://jettison.codehaus.org > > NOTES > Source for jettison is available on http://opensolaris.org > > SunOS 5.10 Last change: 6 Feb 2009 1 > > > From John.Fischer@sun.com Thu Feb 12 12:49:11 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1CKnBvK020439 for ; Thu, 12 Feb 2009 12:49:11 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1CKn912006748; Thu, 12 Feb 2009 13:49:10 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEZ00B1J0HY3000@brm-avmta-1.central.sun.com>; Thu, 12 Feb 2009 13:49:10 -0700 (MST) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEZ00L780HXYGB0@brm-avmta-1.central.sun.com>; Thu, 12 Feb 2009 13:49:09 -0700 (MST) Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n1CKn9HF012918; Thu, 12 Feb 2009 12:49:09 -0800 (PST) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEZ00H0005DO000@fe-sfbay-09.sun.com>; Thu, 12 Feb 2009 12:49:09 -0800 (PST) Received: from [192.168.10.10] ([unknown] [76.20.56.47]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEZ00C670HV42C0@fe-sfbay-09.sun.com>; Thu, 12 Feb 2009 12:49:08 -0800 (PST) Date: Thu, 12 Feb 2009 12:48:14 -0800 From: John Fischer Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <499487B9.9020005@sun.com> Sender: John.Fischer@sun.com To: Drools_Team@sun.com Cc: LSARC-ext@sun.com Reply-to: John.Fischer@sun.com Message-id: <49948B0E.8050105@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> <499487B9.9020005@sun.com> User-Agent: Thunderbird 2.0.0.18 (X11/20081216) Status: RO Content-Length: 15897 Vivek, There is also the question about which jar file these new interfaces are being included in. Thanks, John Margot Miller wrote: > Is this being delivered in its own package, and if so, can you > put it in the interface table? > > Thanks > Margot > > > Mark Carlson wrote: >> I am sponsoring this familiarity case for Vivek Titarmare. It requests >> minor binding and times out 02/18/2009. This Fast Track represents a >> component of LSARC 2008/748 - Drools. >> The FOSS checklist, man page and javadoc are in the case directory and >> the checklist and man page are attached. >> >> -- mark >> >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> jettison >> 1.2. Name of Document Author/Supplier: >> Author: Vivek Titarmare >> 1.3 Date of This Document: >> 11 February, 2009 >> >> 2. Project Summary >> 2.1 Project Description >> >> Jettison is a collection of Java APIs (like STaX and DOM) which >> read and write JSON. >> >> 4. Technical Description: >> >> Jettison is a collection of Java APIs (like STaX and DOM) which >> read and write JSON. >> 5. Interfaces >> Exported interface Classification >> Interface type >> ============================= ============== >> ============== >> org.codehaus.jettison >> * Convention Uncommitted Interface >> >> org.codehaus.jettison.json >> * JSONString Uncommitted Interface >> >> >> The Jar file would go in "usr/share/lib/java" >> >> Imported interface Classification Comments >> ======================= ============== >> =================================== None >> >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> SFW >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> >> >> FCL--FOSS Check List >> >> 1.0 Project Information >> 1.1 Name of project/component >> jettison Ver 1.0 >> >> 1.2 Author of document >> Vivek R. Titarmare >> >> 2.0 Project Summary >> 2.1 Project Description >> Jettison is a collection of Java APIs (like STaX and DOM) which >> read and write JSON. >> >> This case is a dependency for LSARC 2008/748 - Drools. Drools is a >> dependency for PSARC 2007/210 Automatic Data Migration (ADM). >> Interface stabilities and contracts will be added to the consuming >> case(s) as needed. >> >> 2.2 Release binding >> What is is the release binding? >> (see >> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [ ] Major >> [X] Minor >> [ ] Patch or Micro >> [ ] Unknown -- ARC review required >> >> 2.3 Type of project >> Is this case a Linux Familiarity project? >> [X] Yes >> [ ] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> The Codehaus Jettison >> (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) >> >> 2.4.2 Community Involvement >> Indicate Sun's involvement in the community >> [ ] Maintainer >> [ ] Contributor >> [X] Monitoring >> Will the project team work with the upstream community to >> resolve >> architectural issues of interest to Sun? >> [X] Yes [ ] No - briefly explain >> >> Will we or are we forking from the community? >> [ ] Yes - ARC review required prior to forking >> [X] No >> 3.0 Technical Description >> 3.1 Installation & Sharable >> 3.1.1S Solaris Installation - section only required for Solaris >> Software >> (see >> http://opensolaris.org/os/community/arc/policies/install-locations/ >> for details) >> Does this project follow the Install Locations best practice? >> [X] Yes [ ] No - ARC review required >> Does this project install into /usr under >> [sbin|bin|lib|include|man|share]? >> [X] Yes >> [ ] No or N/A >> Does this project install into /opt? >> [ ] Yes - explain below >> [X] No or N/A >> Does this project install into a different directory >> structure? >> [ ] Yes - ARC review required >> [X] No or N/A >> Do any of the components of this project conflict with >> anything under /usr? >> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ >> for details) >> [ ] Yes - explain below >> [X] No >> If conflicts exist then will this project install under >> /usr/gnu? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is this project installing into /usr/sfw? >> [ ] Yes - ARC review required >> [X] No >> 3.1.1W Windows Installation - section only required for >> Windows Software >> (see http://sac.sfbay/WSARC/2002/494 for details) >> Does this project install software into a > drive>:\Program Files\Sun\ or :\Sun\ >> directory? >> [ ] Yes >> [ ] No - ARC review required >> Does the project use the Windows registry? >> [ ] Yes >> [ ] No - ARC review required >> Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun >> Microsystems\\ >> for the registry key? >> [ ] Yes >> [ ] No - ARC review required >> Is the project's stored location >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\> id>\\Path? >> [ ] Yes >> [ ] No - ARC review required >> 3.1.2 Share and Sharable >> Does the module include any components that are used or shared >> by other projects? >> [X] Yes >> [ ] No >> If yes are these components packaged to be shared with the >> other FOSS? >> [X] Yes >> [ ] No - ARC review required >> [ ] N/A >> Are these components already in the Solaris WOS? >> [ ] Yes >> [X] No - continue with next section (section 3.2) >> If yes are these newer versions being delivered? >> [ ] Yes >> [ ] No - ARC review required >> If yes are the newer versions replacing the existing >> versions? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.2 Exported Libraries >> Are libraries being delivered by this project? >> [X] Yes >> [ ] No - continue with next section (section 3.3) >> Are 64-bit versions of the libraries being delivered? >> [X] Yes >> [ ] No - ARC review required >> Are static versions of the libraries being delivered? >> [ ] Yes - ARC review required >> [X] No 3.3 Services and the /etc Directory >> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >> [ ] Yes - ARC review required >> [X] No >> Does the project integrate any new entries into >> /etc/inittab or >> /etc/inetd.conf? >> [ ] Yes - ARC review required >> [X] No >> Does the project integrate any private non-public files >> into /etc/default >> or /etc/ configuration files? >> [ ] Yes - ARC review required >> [X] No >> Does the service manifests method context grant rights >> above that >> of the noaccess user and basic privilege set? >> [ ] Yes - ARC review required >> [X] No >> 3.4 Security >> 3.4.1 Secure By Default (see >> http://opensolaris.org/os/community/arc/policies/secure-by-default/ >> for details) >> (see >> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >> details) >> (see parts of >> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >> addtional details) >> Are there any network services provided by this project? >> [ ] Yes >> [X] No - continue with the next section (section 3.4.2) >> Are network services enabled by default? >> [ ] Yes - ARC review required >> [ ] No >> [X] N/A >> Are network services automatically enabled by the project >> during installation? >> [ ] Yes - ARC review required >> [ ] No >> [X] N/A >> Are inbound network communications denied by default? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is inbound data checked to prevent content-based attacks? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is the outbound receiver authenticated? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is the receiver authenticated prior to receiving any >> sensitive outbound communication? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> 3.4.2 Authorization >> (see >> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >> for details) >> Are there any setuid/setgid privileged binaries in the project? >> [ ] Yes - ARC review required >> [X] No - continue with next section (section 3.4.3) >> If yes then are the setuid/setgid privileges handled by >> the use of roles? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.3 Auditing >> (see >> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >> details) >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >> for details) >> Does this component contain administrative or security enforcing >> software? >> [ ] Yes - ARC review required >> [X] No - continue to next section (section 3.4.4) >> (see >> http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >> Do the components create audit logs detailing what took place >> including what event >> took place, who was involved, when the event took place? >> [ ] Yes - ARC contract and Audit project team review required >> [ ] No - ARC review required >> 3.4.4 Authentication >> (see http://opensolaris.org/os/community/arc/policies/PAM/) >> Do the components contain any authentication code? >> [ ] Yes >> [X] No - continue to next section (section 3.4.5) >> If yes do the components use PAM (plugable authentication >> modules) for authentication? >> [ ] Yes >> [ ] No - ARC review required >> If yes is a single PAM session maintained during >> authentication? >> [ ] Yes >> [ ] No - ARC review required >> If yes are the components sufficiently privileged to allow >> the requested operations (authentication, password change, >> process credential manipulation, audit state initialization)? >> [ ] Yes - briefly describe below >> [ ] No - ARC review required >> 3.4.5 Passwords >> (see >> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >> for details) >> Do any of the components for the project deal with passwords? >> [ ] Yes >> [X] No - continue to next section (section 3.4.6) >> If yes are these passwords entered via the CLI or >> environment? >> [ ] Yes - ARC review required >> [ ] No >> Are passwords stored within the file system for the >> component? >> [ ] Yes >> [ ] No - continue to next section (section 3.4.6) >> If yes are the permissions on the file such to protect >> exposing the password(s)? >> [ ] Yes >> [ ] No - ARC review required >> 3.4.6 General Security Questions >> (see >> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >> for details) >> Are there any network protocols used by this project? >> [ ] Yes >> [X] No - continue with the next section (section 3.5) >> Do the components use standard network protocols? >> [ ] Yes >> [ ] No - ARC review required >> Do network services for the project make decisions based >> upon user, host or service identities? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> Do the components make use of secret information during >> authentication and/or >> authorization? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> 3.5 Networking >> Do the components access the network? >> [ ] Yes >> [X] No - continue with the next section (section 3.6) >> If yes do the components support IPv6? >> [ ] Yes [ ] No - ARC review required >> 3.6 Core Solaris Components >> Do the components of this project compete with or duplicate core >> Solaris components? >> [ ] Yes - ARC review required >> [X] No 4.0 Interfaces >> (see >> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >> for details) >> 4.1 Exported Interfaces >> The jar file "jettison_1.0.jar" contains following interface. >> >> Interface Name Classification Comments >> --------------------------- ------------------- >> --------------------------- >> org.codehaus.jettison >> * Convention Uncommitted Interface >> >> org.codehaus.jettison.json >> * JSONString Uncommitted Interface >> The Jar file would go in "usr/share/lib/java" >> >> 4.2 Imported Interfaces >> Interface Name Classification Comments >> --------------------------- -------------------- >> -------------------------- >> None Appendix B - Suggested case materials >> 1. man pages >> >> Attached are the zipped Java docs (jittison.zip_) >> >> 2. SMF manifests >> 3. links to contracts >> >> >> >> >> Introduction to Library Functions jettison(3) >> >> NAME >> jettison - A JSON (JavaScript Object Notation) STax (Stream- >> ing API for XML) Implementation >> >> DESCRIPTION >> jettison(3) is a collection of Java APIs (like STaX and DOM >> - Document Object Model ) which read and write JSON. For >> additional information on using jettison, browse the com- >> plete html documentation at: >> >> file:/usr/share/lib/java/javadoc/jettison/index.html >> >> LICENSE >> ASL 2.0 >> >> FILES >> /usr/share/lib/java/jettison-1.0.jar >> >> jettison jar file >> >> /usr/share/lib/java/javadoc/jettison/index.html >> >> jettison API documentation generated with javadoc. >> >> ATTRIBUTES >> See attributes(5) for descriptions of the following attri- >> butes: >> >> _______________________________________ >> | ATTRIBUTE TYPE | ATTRIBUTE VALUE| >> |_______________________________________ >> | Availability | SUNWjettison | >> |_______________________________________ >> | Interface Stability| Uncommitted | >> |____________________|_________________| >> >> SEE ALSO >> http://jettison.codehaus.org >> >> NOTES >> Source for jettison is available on http://opensolaris.org >> >> SunOS 5.10 Last change: 6 Feb 2009 1 >> >> >> > From Vivek.Titarmare@sun.com Thu Feb 12 20:01:20 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1D41JxI009530 for ; Thu, 12 Feb 2009 20:01:19 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1D41HkV002055; Thu, 12 Feb 2009 20:01:19 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEZ0070VKI6VO00@brm-avmta-1.central.sun.com>; Thu, 12 Feb 2009 21:01:18 -0700 (MST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEZ006IZKI5Q800@brm-avmta-1.central.sun.com>; Thu, 12 Feb 2009 21:01:18 -0700 (MST) Received: from fe-apac-06.sun.com (fe-apac-06.sun.com [192.18.19.177] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1D41GhG009783; Fri, 13 Feb 2009 04:01:16 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KEZ00700K8L3N00@mail-apac.sun.com>; Fri, 13 Feb 2009 12:01:16 +0800 (SGT) Received: from VivekTPC ([unknown] [203.199.144.195]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KEZ00G16KI30OJ0@mail-apac.sun.com>; Fri, 13 Feb 2009 12:01:16 +0800 (SGT) Date: Fri, 13 Feb 2009 09:31:14 +0530 From: Vivek Titarmare Subject: RE: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <49948B0E.8050105@sun.com> Sender: Vivek.Titarmare@sun.com To: John.Fischer@sun.com, "'Margot Miller'" , Drools_Team@sun.com Cc: LSARC-ext@sun.com Message-id: <009a01c98d8f$b7bd0e30$27372a90$%Titarmare@Sun.com> MIME-version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Content-type: text/plain; charset=us-ascii Content-language: en-us Content-transfer-encoding: 7BIT Thread-index: AcmNU10RdHYUWpZdQUe4Vctj2NWMiwAO4wng X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> <499487B9.9020005@sun.com> <49948B0E.8050105@sun.com> Status: RO Content-Length: 16810 Hi John / Margot, As mentioned in the FOSS check list the interfaces are included in "jettison_1.0.jar" file. > Is this being delivered in its own package, and if so, can you > put it in the interface table? This case is dependent for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). The Interface stability and contracts will be added to the consuming case(s) as needed. All the Exported interfaces are part of jettison_1.0.jar file which are included in both FastTrack and FOSS check list. Let me know If I need to add anything extra in the FOSS check list or/and in the Fast Track. Thanks, ~Vivek R. Titarmare -----Original Message----- From: John.Fischer@Sun.COM [mailto:John.Fischer@Sun.COM] Sent: Friday, February 13, 2009 2:18 AM To: Drools_Team@sun.com Cc: LSARC-ext@sun.com Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] Vivek, There is also the question about which jar file these new interfaces are being included in. Thanks, John Margot Miller wrote: > Is this being delivered in its own package, and if so, can you > put it in the interface table? > > Thanks > Margot > > > Mark Carlson wrote: >> I am sponsoring this familiarity case for Vivek Titarmare. It requests >> minor binding and times out 02/18/2009. This Fast Track represents a >> component of LSARC 2008/748 - Drools. >> The FOSS checklist, man page and javadoc are in the case directory and >> the checklist and man page are attached. >> >> -- mark >> >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> jettison >> 1.2. Name of Document Author/Supplier: >> Author: Vivek Titarmare >> 1.3 Date of This Document: >> 11 February, 2009 >> >> 2. Project Summary >> 2.1 Project Description >> >> Jettison is a collection of Java APIs (like STaX and DOM) which >> read and write JSON. >> >> 4. Technical Description: >> >> Jettison is a collection of Java APIs (like STaX and DOM) which >> read and write JSON. >> 5. Interfaces >> Exported interface Classification >> Interface type >> ============================= ============== >> ============== >> org.codehaus.jettison >> * Convention Uncommitted Interface >> >> org.codehaus.jettison.json >> * JSONString Uncommitted Interface >> >> >> The Jar file would go in "usr/share/lib/java" >> >> Imported interface Classification Comments >> ======================= ============== >> =================================== None >> >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> SFW >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> >> >> FCL--FOSS Check List >> >> 1.0 Project Information >> 1.1 Name of project/component >> jettison Ver 1.0 >> >> 1.2 Author of document >> Vivek R. Titarmare >> >> 2.0 Project Summary >> 2.1 Project Description >> Jettison is a collection of Java APIs (like STaX and DOM) which >> read and write JSON. >> >> This case is a dependency for LSARC 2008/748 - Drools. Drools is a >> dependency for PSARC 2007/210 Automatic Data Migration (ADM). >> Interface stabilities and contracts will be added to the consuming >> case(s) as needed. >> >> 2.2 Release binding >> What is is the release binding? >> (see >> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [ ] Major >> [X] Minor >> [ ] Patch or Micro >> [ ] Unknown -- ARC review required >> >> 2.3 Type of project >> Is this case a Linux Familiarity project? >> [X] Yes >> [ ] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> The Codehaus Jettison >> (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) >> >> 2.4.2 Community Involvement >> Indicate Sun's involvement in the community >> [ ] Maintainer >> [ ] Contributor >> [X] Monitoring >> Will the project team work with the upstream community to >> resolve >> architectural issues of interest to Sun? >> [X] Yes [ ] No - briefly explain >> >> Will we or are we forking from the community? >> [ ] Yes - ARC review required prior to forking >> [X] No >> 3.0 Technical Description >> 3.1 Installation & Sharable >> 3.1.1S Solaris Installation - section only required for Solaris >> Software >> (see >> http://opensolaris.org/os/community/arc/policies/install-locations/ >> for details) >> Does this project follow the Install Locations best practice? >> [X] Yes [ ] No - ARC review required >> Does this project install into /usr under >> [sbin|bin|lib|include|man|share]? >> [X] Yes >> [ ] No or N/A >> Does this project install into /opt? >> [ ] Yes - explain below >> [X] No or N/A >> Does this project install into a different directory >> structure? >> [ ] Yes - ARC review required >> [X] No or N/A >> Do any of the components of this project conflict with >> anything under /usr? >> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ >> for details) >> [ ] Yes - explain below >> [X] No >> If conflicts exist then will this project install under >> /usr/gnu? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is this project installing into /usr/sfw? >> [ ] Yes - ARC review required >> [X] No >> 3.1.1W Windows Installation - section only required for >> Windows Software >> (see http://sac.sfbay/WSARC/2002/494 for details) >> Does this project install software into a > drive>:\Program Files\Sun\ or :\Sun\ >> directory? >> [ ] Yes >> [ ] No - ARC review required >> Does the project use the Windows registry? >> [ ] Yes >> [ ] No - ARC review required >> Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun >> Microsystems\\ >> for the registry key? >> [ ] Yes >> [ ] No - ARC review required >> Is the project's stored location >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\> id>\\Path? >> [ ] Yes >> [ ] No - ARC review required >> 3.1.2 Share and Sharable >> Does the module include any components that are used or shared >> by other projects? >> [X] Yes >> [ ] No >> If yes are these components packaged to be shared with the >> other FOSS? >> [X] Yes >> [ ] No - ARC review required >> [ ] N/A >> Are these components already in the Solaris WOS? >> [ ] Yes >> [X] No - continue with next section (section 3.2) >> If yes are these newer versions being delivered? >> [ ] Yes >> [ ] No - ARC review required >> If yes are the newer versions replacing the existing >> versions? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.2 Exported Libraries >> Are libraries being delivered by this project? >> [X] Yes >> [ ] No - continue with next section (section 3.3) >> Are 64-bit versions of the libraries being delivered? >> [X] Yes >> [ ] No - ARC review required >> Are static versions of the libraries being delivered? >> [ ] Yes - ARC review required >> [X] No 3.3 Services and the /etc Directory >> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >> [ ] Yes - ARC review required >> [X] No >> Does the project integrate any new entries into >> /etc/inittab or >> /etc/inetd.conf? >> [ ] Yes - ARC review required >> [X] No >> Does the project integrate any private non-public files >> into /etc/default >> or /etc/ configuration files? >> [ ] Yes - ARC review required >> [X] No >> Does the service manifests method context grant rights >> above that >> of the noaccess user and basic privilege set? >> [ ] Yes - ARC review required >> [X] No >> 3.4 Security >> 3.4.1 Secure By Default (see >> http://opensolaris.org/os/community/arc/policies/secure-by-default/ >> for details) >> (see >> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >> details) >> (see parts of >> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >> addtional details) >> Are there any network services provided by this project? >> [ ] Yes >> [X] No - continue with the next section (section 3.4.2) >> Are network services enabled by default? >> [ ] Yes - ARC review required >> [ ] No >> [X] N/A >> Are network services automatically enabled by the project >> during installation? >> [ ] Yes - ARC review required >> [ ] No >> [X] N/A >> Are inbound network communications denied by default? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is inbound data checked to prevent content-based attacks? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is the outbound receiver authenticated? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> Is the receiver authenticated prior to receiving any >> sensitive outbound communication? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> 3.4.2 Authorization >> (see >> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >> for details) >> Are there any setuid/setgid privileged binaries in the project? >> [ ] Yes - ARC review required >> [X] No - continue with next section (section 3.4.3) >> If yes then are the setuid/setgid privileges handled by >> the use of roles? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.3 Auditing >> (see >> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >> details) >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >> for details) >> Does this component contain administrative or security enforcing >> software? >> [ ] Yes - ARC review required >> [X] No - continue to next section (section 3.4.4) >> (see >> http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >> Do the components create audit logs detailing what took place >> including what event >> took place, who was involved, when the event took place? >> [ ] Yes - ARC contract and Audit project team review required >> [ ] No - ARC review required >> 3.4.4 Authentication >> (see http://opensolaris.org/os/community/arc/policies/PAM/) >> Do the components contain any authentication code? >> [ ] Yes >> [X] No - continue to next section (section 3.4.5) >> If yes do the components use PAM (plugable authentication >> modules) for authentication? >> [ ] Yes >> [ ] No - ARC review required >> If yes is a single PAM session maintained during >> authentication? >> [ ] Yes >> [ ] No - ARC review required >> If yes are the components sufficiently privileged to allow >> the requested operations (authentication, password change, >> process credential manipulation, audit state initialization)? >> [ ] Yes - briefly describe below >> [ ] No - ARC review required >> 3.4.5 Passwords >> (see >> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >> >> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >> for details) >> Do any of the components for the project deal with passwords? >> [ ] Yes >> [X] No - continue to next section (section 3.4.6) >> If yes are these passwords entered via the CLI or >> environment? >> [ ] Yes - ARC review required >> [ ] No >> Are passwords stored within the file system for the >> component? >> [ ] Yes >> [ ] No - continue to next section (section 3.4.6) >> If yes are the permissions on the file such to protect >> exposing the password(s)? >> [ ] Yes >> [ ] No - ARC review required >> 3.4.6 General Security Questions >> (see >> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >> for details) >> Are there any network protocols used by this project? >> [ ] Yes >> [X] No - continue with the next section (section 3.5) >> Do the components use standard network protocols? >> [ ] Yes >> [ ] No - ARC review required >> Do network services for the project make decisions based >> upon user, host or service identities? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> Do the components make use of secret information during >> authentication and/or >> authorization? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> 3.5 Networking >> Do the components access the network? >> [ ] Yes >> [X] No - continue with the next section (section 3.6) >> If yes do the components support IPv6? >> [ ] Yes [ ] No - ARC review required >> 3.6 Core Solaris Components >> Do the components of this project compete with or duplicate core >> Solaris components? >> [ ] Yes - ARC review required >> [X] No 4.0 Interfaces >> (see >> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >> for details) >> 4.1 Exported Interfaces >> The jar file "jettison_1.0.jar" contains following interface. >> >> Interface Name Classification Comments >> --------------------------- ------------------- >> --------------------------- >> org.codehaus.jettison >> * Convention Uncommitted Interface >> >> org.codehaus.jettison.json >> * JSONString Uncommitted Interface >> The Jar file would go in "usr/share/lib/java" >> >> 4.2 Imported Interfaces >> Interface Name Classification Comments >> --------------------------- -------------------- >> -------------------------- >> None Appendix B - Suggested case materials >> 1. man pages >> >> Attached are the zipped Java docs (jittison.zip_) >> >> 2. SMF manifests >> 3. links to contracts >> >> >> >> >> Introduction to Library Functions jettison(3) >> >> NAME >> jettison - A JSON (JavaScript Object Notation) STax (Stream- >> ing API for XML) Implementation >> >> DESCRIPTION >> jettison(3) is a collection of Java APIs (like STaX and DOM >> - Document Object Model ) which read and write JSON. For >> additional information on using jettison, browse the com- >> plete html documentation at: >> >> file:/usr/share/lib/java/javadoc/jettison/index.html >> >> LICENSE >> ASL 2.0 >> >> FILES >> /usr/share/lib/java/jettison-1.0.jar >> >> jettison jar file >> >> /usr/share/lib/java/javadoc/jettison/index.html >> >> jettison API documentation generated with javadoc. >> >> ATTRIBUTES >> See attributes(5) for descriptions of the following attri- >> butes: >> >> _______________________________________ >> | ATTRIBUTE TYPE | ATTRIBUTE VALUE| >> |_______________________________________ >> | Availability | SUNWjettison | >> |_______________________________________ >> | Interface Stability| Uncommitted | >> |____________________|_________________| >> >> SEE ALSO >> http://jettison.codehaus.org >> >> NOTES >> Source for jettison is available on http://opensolaris.org >> >> SunOS 5.10 Last change: 6 Feb 2009 1 >> >> >> > From Richard.Matthews@sun.com Fri Feb 13 10:09:07 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1DI96wi025828 for ; Fri, 13 Feb 2009 10:09:06 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n1DI8eQc026231 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Sat, 14 Feb 2009 02:09:05 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KF000L09NR4PB00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 10:09:04 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF000GN9NR3VX80@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 10:09:03 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1DI933R009029 for ; Fri, 13 Feb 2009 18:09:03 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KF000100LZFT900@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 11:09:03 -0700 (MST) Received: from [129.152.9.14] ([unknown] [129.152.9.14]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KF0003PSNQWSG90@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 11:08:57 -0700 (MST) Date: Fri, 13 Feb 2009 12:08:56 -0600 From: Rick Matthews Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> Sender: Richard.Matthews@sun.com Cc: LSARC-ext@sun.com Reply-to: Richard.Matthews@sun.com Message-id: <4995B738.20206@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 549 Minor nit: jettison spelled as jittison on one place in the FOSS checklist. +1 -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From margot.miller@sun.com Tue Feb 17 10:09:48 2009 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1HI9mLi024061 for ; Tue, 17 Feb 2009 10:09:48 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1HI8igb025960; Tue, 17 Feb 2009 10:09:44 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KF800F272FZZB00@nwk-avmta-2.sfbay.sun.com>; Tue, 17 Feb 2009 10:09:35 -0800 (PST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF800DKO2FXA450@nwk-avmta-2.sfbay.sun.com>; Tue, 17 Feb 2009 10:09:33 -0800 (PST) Received: from [10.7.250.251] (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1HI9WlE371406; Tue, 17 Feb 2009 10:09:32 -0800 (PST) Date: Tue, 17 Feb 2009 10:06:00 -0800 From: Margot Miller Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <009a01c98d8f$b7bd0e30$27372a90$%Titarmare@Sun.com> To: Vivek Titarmare Cc: John.Fischer@sun.com, Drools_Team@sun.com, LSARC-ext@sun.com Message-id: <499AFC88.2070400@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> <499487B9.9020005@sun.com> <49948B0E.8050105@sun.com> <009a01c98d8f$b7bd0e30$27372a90$%Titarmare@Sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 17498 Hey Vivek, Which SVR4 package is the jettison_1.0.jar file included in? Thanks Margot Vivek Titarmare wrote: > Hi John / Margot, > > As mentioned in the FOSS check list the interfaces are included in > "jettison_1.0.jar" file. > > >> Is this being delivered in its own package, and if so, can you >> put it in the interface table? >> > > This case is dependent for LSARC 2008/748 - Drools. Drools is a dependency > for PSARC 2007/210 Automatic Data Migration (ADM). The Interface stability > and contracts will be added to the consuming case(s) as needed. > > All the Exported interfaces are part of jettison_1.0.jar file which are > included in both FastTrack and FOSS check list. > > Let me know If I need to add anything extra in the FOSS check list or/and in > the Fast Track. > > Thanks, > ~Vivek R. Titarmare > > > -----Original Message----- > From: John.Fischer@Sun.COM [mailto:John.Fischer@Sun.COM] > Sent: Friday, February 13, 2009 2:18 AM > To: Drools_Team@sun.com > Cc: LSARC-ext@sun.com > Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] > > Vivek, > > There is also the question about which jar file these > new interfaces are being included in. > > Thanks, > > John > > Margot Miller wrote: > >> Is this being delivered in its own package, and if so, can you >> put it in the interface table? >> >> Thanks >> Margot >> >> >> Mark Carlson wrote: >> >>> I am sponsoring this familiarity case for Vivek Titarmare. It requests >>> minor binding and times out 02/18/2009. This Fast Track represents a >>> component of LSARC 2008/748 - Drools. >>> The FOSS checklist, man page and javadoc are in the case directory and >>> the checklist and man page are attached. >>> >>> -- mark >>> >>> Template Version: @(#)sac_nextcase %I% %G% SMI >>> This information is Copyright 2009 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> jettison >>> 1.2. Name of Document Author/Supplier: >>> Author: Vivek Titarmare >>> 1.3 Date of This Document: >>> 11 February, 2009 >>> >>> 2. Project Summary >>> 2.1 Project Description >>> >>> Jettison is a collection of Java APIs (like STaX and DOM) which >>> read and write JSON. >>> >>> 4. Technical Description: >>> >>> Jettison is a collection of Java APIs (like STaX and DOM) which >>> read and write JSON. >>> 5. Interfaces >>> Exported interface Classification >>> Interface type >>> ============================= ============== >>> ============== >>> org.codehaus.jettison >>> * Convention Uncommitted Interface >>> >>> org.codehaus.jettison.json >>> * JSONString Uncommitted Interface >>> >>> >>> The Jar file would go in "usr/share/lib/java" >>> >>> Imported interface Classification Comments >>> ======================= ============== >>> =================================== None >>> >>> >>> 6. Resources and Schedule >>> 6.4. Steering Committee requested information >>> 6.4.1. Consolidation C-team Name: >>> SFW >>> 6.5. ARC review type: FastTrack >>> 6.6. ARC Exposure: open >>> >>> >>> >>> FCL--FOSS Check List >>> >>> 1.0 Project Information >>> 1.1 Name of project/component >>> jettison Ver 1.0 >>> >>> 1.2 Author of document >>> Vivek R. Titarmare >>> >>> 2.0 Project Summary >>> 2.1 Project Description >>> Jettison is a collection of Java APIs (like STaX and DOM) which >>> read and write JSON. >>> >>> This case is a dependency for LSARC 2008/748 - Drools. Drools is a >>> dependency for PSARC 2007/210 Automatic Data Migration (ADM). >>> Interface stabilities and contracts will be added to the consuming >>> case(s) as needed. >>> >>> 2.2 Release binding >>> What is is the release binding? >>> (see >>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>> [ ] Major >>> [X] Minor >>> [ ] Patch or Micro >>> [ ] Unknown -- ARC review required >>> >>> 2.3 Type of project >>> Is this case a Linux Familiarity project? >>> [X] Yes >>> [ ] No >>> >>> 2.4 Originating Community >>> 2.4.1 Community Name >>> The Codehaus Jettison >>> >>> > (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) > > >>> 2.4.2 Community Involvement >>> Indicate Sun's involvement in the community >>> [ ] Maintainer >>> [ ] Contributor >>> [X] Monitoring >>> Will the project team work with the upstream community to >>> resolve >>> architectural issues of interest to Sun? >>> [X] Yes [ ] No - briefly explain >>> >>> Will we or are we forking from the community? >>> [ ] Yes - ARC review required prior to forking >>> [X] No >>> 3.0 Technical Description >>> 3.1 Installation & Sharable >>> 3.1.1S Solaris Installation - section only required for Solaris >>> Software >>> (see >>> http://opensolaris.org/os/community/arc/policies/install-locations/ >>> for details) >>> Does this project follow the Install Locations best practice? >>> [X] Yes [ ] No - ARC review required >>> Does this project install into /usr under >>> [sbin|bin|lib|include|man|share]? >>> [X] Yes >>> [ ] No or N/A >>> Does this project install into /opt? >>> [ ] Yes - explain below >>> [X] No or N/A >>> Does this project install into a different directory >>> structure? >>> [ ] Yes - ARC review required >>> [X] No or N/A >>> Do any of the components of this project conflict with >>> anything under /usr? >>> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ >>> for details) >>> [ ] Yes - explain below >>> [X] No >>> If conflicts exist then will this project install under >>> /usr/gnu? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is this project installing into /usr/sfw? >>> [ ] Yes - ARC review required >>> [X] No >>> 3.1.1W Windows Installation - section only required for >>> Windows Software >>> (see http://sac.sfbay/WSARC/2002/494 for details) >>> Does this project install software into a >> drive>:\Program Files\Sun\ or :\Sun\ >>> directory? >>> [ ] Yes >>> [ ] No - ARC review required >>> Does the project use the Windows registry? >>> [ ] Yes >>> [ ] No - ARC review required >>> Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun >>> Microsystems\\ >>> for the registry key? >>> [ ] Yes >>> [ ] No - ARC review required >>> Is the project's stored location >>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\>> id>\\Path? >>> [ ] Yes >>> [ ] No - ARC review required >>> 3.1.2 Share and Sharable >>> Does the module include any components that are used or shared >>> by other projects? >>> [X] Yes >>> [ ] No >>> If yes are these components packaged to be shared with the >>> other FOSS? >>> [X] Yes >>> [ ] No - ARC review required >>> [ ] N/A >>> Are these components already in the Solaris WOS? >>> [ ] Yes >>> [X] No - continue with next section (section 3.2) >>> If yes are these newer versions being delivered? >>> [ ] Yes >>> [ ] No - ARC review required >>> If yes are the newer versions replacing the existing >>> versions? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> 3.2 Exported Libraries >>> Are libraries being delivered by this project? >>> [X] Yes >>> [ ] No - continue with next section (section 3.3) >>> Are 64-bit versions of the libraries being delivered? >>> [X] Yes >>> [ ] No - ARC review required >>> Are static versions of the libraries being delivered? >>> [ ] Yes - ARC review required >>> [X] No 3.3 Services and the /etc Directory >>> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >>> [ ] Yes - ARC review required >>> [X] No >>> Does the project integrate any new entries into >>> /etc/inittab or >>> /etc/inetd.conf? >>> [ ] Yes - ARC review required >>> [X] No >>> Does the project integrate any private non-public files >>> into /etc/default >>> or /etc/ configuration files? >>> [ ] Yes - ARC review required >>> [X] No >>> Does the service manifests method context grant rights >>> above that >>> of the noaccess user and basic privilege set? >>> [ ] Yes - ARC review required >>> [X] No >>> 3.4 Security >>> 3.4.1 Secure By Default (see >>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ >>> for details) >>> (see >>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >>> details) >>> (see parts of >>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>> addtional details) >>> Are there any network services provided by this project? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.4.2) >>> Are network services enabled by default? >>> [ ] Yes - ARC review required >>> [ ] No >>> [X] N/A >>> Are network services automatically enabled by the project >>> during installation? >>> [ ] Yes - ARC review required >>> [ ] No >>> [X] N/A >>> Are inbound network communications denied by default? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is inbound data checked to prevent content-based attacks? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is the outbound receiver authenticated? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is the receiver authenticated prior to receiving any >>> sensitive outbound communication? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> 3.4.2 Authorization >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>> for details) >>> Are there any setuid/setgid privileged binaries in the project? >>> [ ] Yes - ARC review required >>> [X] No - continue with next section (section 3.4.3) >>> If yes then are the setuid/setgid privileges handled by >>> the use of roles? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> 3.4.3 Auditing >>> (see >>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>> details) >>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>> for details) >>> Does this component contain administrative or security enforcing >>> software? >>> [ ] Yes - ARC review required >>> [X] No - continue to next section (section 3.4.4) >>> (see >>> http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >>> Do the components create audit logs detailing what took place >>> including what event >>> took place, who was involved, when the event took place? >>> [ ] Yes - ARC contract and Audit project team review required >>> [ ] No - ARC review required >>> 3.4.4 Authentication >>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>> Do the components contain any authentication code? >>> [ ] Yes >>> [X] No - continue to next section (section 3.4.5) >>> If yes do the components use PAM (plugable authentication >>> modules) for authentication? >>> [ ] Yes >>> [ ] No - ARC review required >>> If yes is a single PAM session maintained during >>> authentication? >>> [ ] Yes >>> [ ] No - ARC review required >>> If yes are the components sufficiently privileged to allow >>> the requested operations (authentication, password change, >>> process credential manipulation, audit state initialization)? >>> [ ] Yes - briefly describe below >>> [ ] No - ARC review required >>> 3.4.5 Passwords >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>> for details) >>> Do any of the components for the project deal with passwords? >>> [ ] Yes >>> [X] No - continue to next section (section 3.4.6) >>> If yes are these passwords entered via the CLI or >>> environment? >>> [ ] Yes - ARC review required >>> [ ] No >>> Are passwords stored within the file system for the >>> component? >>> [ ] Yes >>> [ ] No - continue to next section (section 3.4.6) >>> If yes are the permissions on the file such to protect >>> exposing the password(s)? >>> [ ] Yes >>> [ ] No - ARC review required >>> 3.4.6 General Security Questions >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >>> > > >>> for details) >>> Are there any network protocols used by this project? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.5) >>> Do the components use standard network protocols? >>> [ ] Yes >>> [ ] No - ARC review required >>> Do network services for the project make decisions based >>> upon user, host or service identities? >>> [ ] Yes - explain below >>> [ ] No >>> [ ] N/A >>> Do the components make use of secret information during >>> authentication and/or >>> authorization? >>> [ ] Yes - explain below >>> [ ] No >>> [ ] N/A >>> 3.5 Networking >>> Do the components access the network? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.6) >>> If yes do the components support IPv6? >>> [ ] Yes [ ] No - ARC review required >>> 3.6 Core Solaris Components >>> Do the components of this project compete with or duplicate core >>> Solaris components? >>> [ ] Yes - ARC review required >>> [X] No 4.0 Interfaces >>> (see >>> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >>> for details) >>> 4.1 Exported Interfaces >>> The jar file "jettison_1.0.jar" contains following interface. >>> >>> Interface Name Classification Comments >>> --------------------------- ------------------- >>> --------------------------- >>> org.codehaus.jettison >>> * Convention Uncommitted Interface >>> >>> org.codehaus.jettison.json >>> * JSONString Uncommitted Interface >>> The Jar file would go in "usr/share/lib/java" >>> >>> 4.2 Imported Interfaces >>> Interface Name Classification Comments >>> --------------------------- -------------------- >>> -------------------------- >>> None Appendix B - Suggested case materials >>> 1. man pages >>> >>> Attached are the zipped Java docs (jittison.zip_) >>> >>> 2. SMF manifests >>> 3. links to contracts >>> >>> >>> >>> >>> Introduction to Library Functions jettison(3) >>> >>> NAME >>> jettison - A JSON (JavaScript Object Notation) STax (Stream- >>> ing API for XML) Implementation >>> >>> DESCRIPTION >>> jettison(3) is a collection of Java APIs (like STaX and DOM >>> - Document Object Model ) which read and write JSON. For >>> additional information on using jettison, browse the com- >>> plete html documentation at: >>> >>> file:/usr/share/lib/java/javadoc/jettison/index.html >>> >>> LICENSE >>> ASL 2.0 >>> >>> FILES >>> /usr/share/lib/java/jettison-1.0.jar >>> >>> jettison jar file >>> >>> /usr/share/lib/java/javadoc/jettison/index.html >>> >>> jettison API documentation generated with javadoc. >>> >>> ATTRIBUTES >>> See attributes(5) for descriptions of the following attri- >>> butes: >>> >>> _______________________________________ >>> | ATTRIBUTE TYPE | ATTRIBUTE VALUE| >>> |_______________________________________ >>> | Availability | SUNWjettison | >>> |_______________________________________ >>> | Interface Stability| Uncommitted | >>> |____________________|_________________| >>> >>> SEE ALSO >>> http://jettison.codehaus.org >>> >>> NOTES >>> Source for jettison is available on http://opensolaris.org >>> >>> SunOS 5.10 Last change: 6 Feb 2009 1 >>> >>> >>> >>> > > From Vivek.Titarmare@sun.com Wed Feb 18 07:49:35 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1IFnYq9004478 for ; Wed, 18 Feb 2009 07:49:35 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n1IFnTT8029119; Wed, 18 Feb 2009 23:49:33 +0800 (SGT) Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KF900K3VQMIGZ00@nwk-avmta-2.sfbay.sun.com>; Wed, 18 Feb 2009 07:49:30 -0800 (PST) Received: from sineb-mail-1.sun.com ([192.18.19.6]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF900EMAQMFWE90@nwk-avmta-2.sfbay.sun.com>; Wed, 18 Feb 2009 07:49:28 -0800 (PST) Received: from fe-apac-05.sun.com (fe-apac-05.sun.com [192.18.19.176] (may be forged)) by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1IFnRXk026426; Wed, 18 Feb 2009 15:49:27 +0000 (GMT) Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KF900B00QIV2800@mail-apac.sun.com>; Wed, 18 Feb 2009 23:49:27 +0800 (SGT) Received: from VivekTPC ([unknown] [115.109.15.116]) by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KF900LX6QM51L30@mail-apac.sun.com>; Wed, 18 Feb 2009 23:49:20 +0800 (SGT) Date: Wed, 18 Feb 2009 21:19:09 +0530 From: Vivek Titarmare Subject: RE: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <499AFC88.2070400@sun.com> Sender: Vivek.Titarmare@sun.com To: "'Margot Miller'" Cc: John.Fischer@sun.com, Drools_Team@sun.com, LSARC-ext@sun.com Message-id: <000001c991e0$761095b0$6231c110$%Titarmare@Sun.com> MIME-version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Content-type: text/plain; charset=us-ascii Content-language: en-us Content-transfer-encoding: 7BIT Thread-index: AcmRKxWsWe1bY+NcSH6Dd7H/yrZPowAtQrzg X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> <499487B9.9020005@sun.com> <49948B0E.8050105@sun.com> <009a01c98d8f$b7bd0e30$27372a90$%Titarmare@Sun.com> <499AFC88.2070400@sun.com> Status: RO Content-Length: 17849 Hi Margot, It is included in SUNWjettison. Regards, ~Vivek R. Titarmare -----Original Message----- From: Margot Miller [mailto:Margot.Miller@Sun.COM] Sent: Tuesday, February 17, 2009 11:36 PM To: Vivek Titarmare Cc: John.Fischer@Sun.COM; Drools_Team@sun.com; LSARC-ext@sun.com Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] Hey Vivek, Which SVR4 package is the jettison_1.0.jar file included in? Thanks Margot Vivek Titarmare wrote: > Hi John / Margot, > > As mentioned in the FOSS check list the interfaces are included in > "jettison_1.0.jar" file. > > >> Is this being delivered in its own package, and if so, can you >> put it in the interface table? >> > > This case is dependent for LSARC 2008/748 - Drools. Drools is a dependency > for PSARC 2007/210 Automatic Data Migration (ADM). The Interface stability > and contracts will be added to the consuming case(s) as needed. > > All the Exported interfaces are part of jettison_1.0.jar file which are > included in both FastTrack and FOSS check list. > > Let me know If I need to add anything extra in the FOSS check list or/and in > the Fast Track. > > Thanks, > ~Vivek R. Titarmare > > > -----Original Message----- > From: John.Fischer@Sun.COM [mailto:John.Fischer@Sun.COM] > Sent: Friday, February 13, 2009 2:18 AM > To: Drools_Team@sun.com > Cc: LSARC-ext@sun.com > Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] > > Vivek, > > There is also the question about which jar file these > new interfaces are being included in. > > Thanks, > > John > > Margot Miller wrote: > >> Is this being delivered in its own package, and if so, can you >> put it in the interface table? >> >> Thanks >> Margot >> >> >> Mark Carlson wrote: >> >>> I am sponsoring this familiarity case for Vivek Titarmare. It requests >>> minor binding and times out 02/18/2009. This Fast Track represents a >>> component of LSARC 2008/748 - Drools. >>> The FOSS checklist, man page and javadoc are in the case directory and >>> the checklist and man page are attached. >>> >>> -- mark >>> >>> Template Version: @(#)sac_nextcase %I% %G% SMI >>> This information is Copyright 2009 Sun Microsystems >>> 1. Introduction >>> 1.1. Project/Component Working Name: >>> jettison >>> 1.2. Name of Document Author/Supplier: >>> Author: Vivek Titarmare >>> 1.3 Date of This Document: >>> 11 February, 2009 >>> >>> 2. Project Summary >>> 2.1 Project Description >>> >>> Jettison is a collection of Java APIs (like STaX and DOM) which >>> read and write JSON. >>> >>> 4. Technical Description: >>> >>> Jettison is a collection of Java APIs (like STaX and DOM) which >>> read and write JSON. >>> 5. Interfaces >>> Exported interface Classification >>> Interface type >>> ============================= ============== >>> ============== >>> org.codehaus.jettison >>> * Convention Uncommitted Interface >>> >>> org.codehaus.jettison.json >>> * JSONString Uncommitted Interface >>> >>> >>> The Jar file would go in "usr/share/lib/java" >>> >>> Imported interface Classification Comments >>> ======================= ============== >>> =================================== None >>> >>> >>> 6. Resources and Schedule >>> 6.4. Steering Committee requested information >>> 6.4.1. Consolidation C-team Name: >>> SFW >>> 6.5. ARC review type: FastTrack >>> 6.6. ARC Exposure: open >>> >>> >>> >>> FCL--FOSS Check List >>> >>> 1.0 Project Information >>> 1.1 Name of project/component >>> jettison Ver 1.0 >>> >>> 1.2 Author of document >>> Vivek R. Titarmare >>> >>> 2.0 Project Summary >>> 2.1 Project Description >>> Jettison is a collection of Java APIs (like STaX and DOM) which >>> read and write JSON. >>> >>> This case is a dependency for LSARC 2008/748 - Drools. Drools is a >>> dependency for PSARC 2007/210 Automatic Data Migration (ADM). >>> Interface stabilities and contracts will be added to the consuming >>> case(s) as needed. >>> >>> 2.2 Release binding >>> What is is the release binding? >>> (see >>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >>> [ ] Major >>> [X] Minor >>> [ ] Patch or Micro >>> [ ] Unknown -- ARC review required >>> >>> 2.3 Type of project >>> Is this case a Linux Familiarity project? >>> [X] Yes >>> [ ] No >>> >>> 2.4 Originating Community >>> 2.4.1 Community Name >>> The Codehaus Jettison >>> >>> > (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) > > >>> 2.4.2 Community Involvement >>> Indicate Sun's involvement in the community >>> [ ] Maintainer >>> [ ] Contributor >>> [X] Monitoring >>> Will the project team work with the upstream community to >>> resolve >>> architectural issues of interest to Sun? >>> [X] Yes [ ] No - briefly explain >>> >>> Will we or are we forking from the community? >>> [ ] Yes - ARC review required prior to forking >>> [X] No >>> 3.0 Technical Description >>> 3.1 Installation & Sharable >>> 3.1.1S Solaris Installation - section only required for Solaris >>> Software >>> (see >>> http://opensolaris.org/os/community/arc/policies/install-locations/ >>> for details) >>> Does this project follow the Install Locations best practice? >>> [X] Yes [ ] No - ARC review required >>> Does this project install into /usr under >>> [sbin|bin|lib|include|man|share]? >>> [X] Yes >>> [ ] No or N/A >>> Does this project install into /opt? >>> [ ] Yes - explain below >>> [X] No or N/A >>> Does this project install into a different directory >>> structure? >>> [ ] Yes - ARC review required >>> [X] No or N/A >>> Do any of the components of this project conflict with >>> anything under /usr? >>> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ >>> for details) >>> [ ] Yes - explain below >>> [X] No >>> If conflicts exist then will this project install under >>> /usr/gnu? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is this project installing into /usr/sfw? >>> [ ] Yes - ARC review required >>> [X] No >>> 3.1.1W Windows Installation - section only required for >>> Windows Software >>> (see http://sac.sfbay/WSARC/2002/494 for details) >>> Does this project install software into a >> drive>:\Program Files\Sun\ or :\Sun\ >>> directory? >>> [ ] Yes >>> [ ] No - ARC review required >>> Does the project use the Windows registry? >>> [ ] Yes >>> [ ] No - ARC review required >>> Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun >>> Microsystems\\ >>> for the registry key? >>> [ ] Yes >>> [ ] No - ARC review required >>> Is the project's stored location >>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\>> id>\\Path? >>> [ ] Yes >>> [ ] No - ARC review required >>> 3.1.2 Share and Sharable >>> Does the module include any components that are used or shared >>> by other projects? >>> [X] Yes >>> [ ] No >>> If yes are these components packaged to be shared with the >>> other FOSS? >>> [X] Yes >>> [ ] No - ARC review required >>> [ ] N/A >>> Are these components already in the Solaris WOS? >>> [ ] Yes >>> [X] No - continue with next section (section 3.2) >>> If yes are these newer versions being delivered? >>> [ ] Yes >>> [ ] No - ARC review required >>> If yes are the newer versions replacing the existing >>> versions? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> 3.2 Exported Libraries >>> Are libraries being delivered by this project? >>> [X] Yes >>> [ ] No - continue with next section (section 3.3) >>> Are 64-bit versions of the libraries being delivered? >>> [X] Yes >>> [ ] No - ARC review required >>> Are static versions of the libraries being delivered? >>> [ ] Yes - ARC review required >>> [X] No 3.3 Services and the /etc Directory >>> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >>> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >>> [ ] Yes - ARC review required >>> [X] No >>> Does the project integrate any new entries into >>> /etc/inittab or >>> /etc/inetd.conf? >>> [ ] Yes - ARC review required >>> [X] No >>> Does the project integrate any private non-public files >>> into /etc/default >>> or /etc/ configuration files? >>> [ ] Yes - ARC review required >>> [X] No >>> Does the service manifests method context grant rights >>> above that >>> of the noaccess user and basic privilege set? >>> [ ] Yes - ARC review required >>> [X] No >>> 3.4 Security >>> 3.4.1 Secure By Default (see >>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ >>> for details) >>> (see >>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for >>> details) >>> (see parts of >>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >>> addtional details) >>> Are there any network services provided by this project? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.4.2) >>> Are network services enabled by default? >>> [ ] Yes - ARC review required >>> [ ] No >>> [X] N/A >>> Are network services automatically enabled by the project >>> during installation? >>> [ ] Yes - ARC review required >>> [ ] No >>> [X] N/A >>> Are inbound network communications denied by default? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is inbound data checked to prevent content-based attacks? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is the outbound receiver authenticated? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> Is the receiver authenticated prior to receiving any >>> sensitive outbound communication? >>> [ ] Yes >>> [ ] No - ARC review required >>> [X] N/A >>> 3.4.2 Authorization >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >>> for details) >>> Are there any setuid/setgid privileged binaries in the project? >>> [ ] Yes - ARC review required >>> [X] No - continue with next section (section 3.4.3) >>> If yes then are the setuid/setgid privileges handled by >>> the use of roles? >>> [ ] Yes >>> [ ] No - ARC review required >>> >>> 3.4.3 Auditing >>> (see >>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for >>> details) >>> (see http://opensolaris.org/os/community/arc/caselog/2003/397 >>> for details) >>> Does this component contain administrative or security enforcing >>> software? >>> [ ] Yes - ARC review required >>> [X] No - continue to next section (section 3.4.4) >>> (see >>> http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >>> Do the components create audit logs detailing what took place >>> including what event >>> took place, who was involved, when the event took place? >>> [ ] Yes - ARC contract and Audit project team review required >>> [ ] No - ARC review required >>> 3.4.4 Authentication >>> (see http://opensolaris.org/os/community/arc/policies/PAM/) >>> Do the components contain any authentication code? >>> [ ] Yes >>> [X] No - continue to next section (section 3.4.5) >>> If yes do the components use PAM (plugable authentication >>> modules) for authentication? >>> [ ] Yes >>> [ ] No - ARC review required >>> If yes is a single PAM session maintained during >>> authentication? >>> [ ] Yes >>> [ ] No - ARC review required >>> If yes are the components sufficiently privileged to allow >>> the requested operations (authentication, password change, >>> process credential manipulation, audit state initialization)? >>> [ ] Yes - briefly describe below >>> [ ] No - ARC review required >>> 3.4.5 Passwords >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >>> >>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ >>> for details) >>> Do any of the components for the project deal with passwords? >>> [ ] Yes >>> [X] No - continue to next section (section 3.4.6) >>> If yes are these passwords entered via the CLI or >>> environment? >>> [ ] Yes - ARC review required >>> [ ] No >>> Are passwords stored within the file system for the >>> component? >>> [ ] Yes >>> [ ] No - continue to next section (section 3.4.6) >>> If yes are the permissions on the file such to protect >>> exposing the password(s)? >>> [ ] Yes >>> [ ] No - ARC review required >>> 3.4.6 General Security Questions >>> (see >>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ >>> > > >>> for details) >>> Are there any network protocols used by this project? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.5) >>> Do the components use standard network protocols? >>> [ ] Yes >>> [ ] No - ARC review required >>> Do network services for the project make decisions based >>> upon user, host or service identities? >>> [ ] Yes - explain below >>> [ ] No >>> [ ] N/A >>> Do the components make use of secret information during >>> authentication and/or >>> authorization? >>> [ ] Yes - explain below >>> [ ] No >>> [ ] N/A >>> 3.5 Networking >>> Do the components access the network? >>> [ ] Yes >>> [X] No - continue with the next section (section 3.6) >>> If yes do the components support IPv6? >>> [ ] Yes [ ] No - ARC review required >>> 3.6 Core Solaris Components >>> Do the components of this project compete with or duplicate core >>> Solaris components? >>> [ ] Yes - ARC review required >>> [X] No 4.0 Interfaces >>> (see >>> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ >>> for details) >>> 4.1 Exported Interfaces >>> The jar file "jettison_1.0.jar" contains following interface. >>> >>> Interface Name Classification Comments >>> --------------------------- ------------------- >>> --------------------------- >>> org.codehaus.jettison >>> * Convention Uncommitted Interface >>> >>> org.codehaus.jettison.json >>> * JSONString Uncommitted Interface >>> The Jar file would go in "usr/share/lib/java" >>> >>> 4.2 Imported Interfaces >>> Interface Name Classification Comments >>> --------------------------- -------------------- >>> -------------------------- >>> None Appendix B - Suggested case materials >>> 1. man pages >>> >>> Attached are the zipped Java docs (jittison.zip_) >>> >>> 2. SMF manifests >>> 3. links to contracts >>> >>> >>> >>> >>> Introduction to Library Functions jettison(3) >>> >>> NAME >>> jettison - A JSON (JavaScript Object Notation) STax (Stream- >>> ing API for XML) Implementation >>> >>> DESCRIPTION >>> jettison(3) is a collection of Java APIs (like STaX and DOM >>> - Document Object Model ) which read and write JSON. For >>> additional information on using jettison, browse the com- >>> plete html documentation at: >>> >>> file:/usr/share/lib/java/javadoc/jettison/index.html >>> >>> LICENSE >>> ASL 2.0 >>> >>> FILES >>> /usr/share/lib/java/jettison-1.0.jar >>> >>> jettison jar file >>> >>> /usr/share/lib/java/javadoc/jettison/index.html >>> >>> jettison API documentation generated with javadoc. >>> >>> ATTRIBUTES >>> See attributes(5) for descriptions of the following attri- >>> butes: >>> >>> _______________________________________ >>> | ATTRIBUTE TYPE | ATTRIBUTE VALUE| >>> |_______________________________________ >>> | Availability | SUNWjettison | >>> |_______________________________________ >>> | Interface Stability| Uncommitted | >>> |____________________|_________________| >>> >>> SEE ALSO >>> http://jettison.codehaus.org >>> >>> NOTES >>> Source for jettison is available on http://opensolaris.org >>> >>> SunOS 5.10 Last change: 6 Feb 2009 1 >>> >>> >>> >>> > > From Mark.Carlson@sun.com Thu Feb 19 04:39:37 2009 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1JCdaQh008525 for ; Thu, 19 Feb 2009 04:39:37 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1JCdZPU011244; Thu, 19 Feb 2009 05:39:36 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFB00K0BCI0SP00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 19 Feb 2009 04:39:36 -0800 (PST) Received: from brmea-mail-1.sun.com ([192.18.98.31]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFB00JP6CHZ5T00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 19 Feb 2009 04:39:35 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1JCdZ3g022881; Thu, 19 Feb 2009 12:39:35 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFB00700C979W00@mail-amer.sun.com>; Thu, 19 Feb 2009 05:39:35 -0700 (MST) Received: from Macintosh-335.local ([unknown] [129.150.33.5]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFB0047ACHY8420@mail-amer.sun.com>; Thu, 19 Feb 2009 05:39:34 -0700 (MST) Date: Thu, 19 Feb 2009 05:39:33 -0700 From: "Mark A. Carlson" Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> Sender: Mark.Carlson@sun.com To: LSARC-ext@sun.com Cc: Drools_Team@sun.com Message-id: <499D5305.7030805@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_rpialrEFlTIZmdqpC3l0fg)" X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 33663 This is a multi-part message in MIME format. --Boundary_(ID_rpialrEFlTIZmdqpC3l0fg) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT This case, having resolved all outstanding issues, is being marked closed approved. -- mark Mark Carlson wrote: > I am sponsoring this familiarity case for Vivek Titarmare. It requests minor > binding and times out 02/18/2009. This Fast Track represents a component of > LSARC 2008/748 - Drools. > The FOSS checklist, man page and javadoc are in the case directory and > the checklist and man page are attached. > > -- mark > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > jettison > 1.2. Name of Document Author/Supplier: > Author: Vivek Titarmare > 1.3 Date of This Document: > 11 February, 2009 > > 2. Project Summary > 2.1 Project Description > > Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. > > 4. Technical Description: > > Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. > > 5. Interfaces > > Exported interface Classification Interface type > ============================= ============== ============== > org.codehaus.jettison > * Convention Uncommitted Interface > > org.codehaus.jettison.json > * JSONString Uncommitted Interface > > > > The Jar file would go in "usr/share/lib/java" > > Imported interface Classification Comments > ======================= ============== =================================== > None > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > SFW > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > > > FCL--FOSS Check List > > 1.0 Project Information > 1.1 Name of project/component > jettison Ver 1.0 > > 1.2 Author of document > Vivek R. Titarmare > > 2.0 Project Summary > 2.1 Project Description > Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. > > This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). > Interface stabilities and contracts will be added to the consuming case(s) as needed. > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [X] Minor > [ ] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [X] Yes > [ ] No > > 2.4 Originating Community > 2.4.1 Community Name > The Codehaus Jettison (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) > > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [X] Monitoring > > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [X] Yes > [ ] No - briefly explain > > > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [X] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris Software > (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) > Does this project follow the Install Locations best practice? > [X] Yes > [ ] No - ARC review required > > Does this project install into /usr under [sbin|bin|lib|include|man|share]? > [X] Yes > [ ] No or N/A > > Does this project install into /opt? > [ ] Yes - explain below > [X] No or N/A > > Does this project install into a different directory structure? > [ ] Yes - ARC review required > [X] No or N/A > > Do any of the components of this project conflict with anything under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) > [ ] Yes - explain below > [X] No > > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [X] No > > 3.1.1W Windows Installation - section only required for Windows Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a > :\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > > Does the project use > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [X] Yes > [ ] No > > If yes are these components packaged to be shared with the other FOSS? > [X] Yes > [ ] No - ARC review required > [ ] N/A > > Are these components already in the Solaris WOS? > [ ] Yes > [X] No - continue with next section (section 3.2) > > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [X] Yes > [ ] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [X] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [X] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any private non-public files into /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [X] No > > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [X] No > > 3.4 Security > 3.4.1 Secure By Default > (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) > (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) > (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [X] No - continue with the next section (section 3.4.2) > > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [X] N/A > > Are network services automatically enabled by the project during installation? > [ ] Yes - ARC review required > [ ] No > [X] N/A > > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is the receiver authenticated prior to receiving any sensitive outbound communication? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > 3.4.2 Authorization > (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [X] No - continue with next section (section 3.4.3) > > If yes then are the setuid/setgid privileges handled by the use of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Does this component contain administrative or security enforcing software? > [ ] Yes - ARC review required > [X] No - continue to next section (section 3.4.4) > > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Do the components create audit logs detailing what took place including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [ ] No - ARC review required > > > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [X] No - continue to next section (section 3.4.5) > > If yes do the components use PAM (plugable authentication modules) for authentication? > [ ] Yes > [ ] No - ARC review required > > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > > If yes are the components sufficiently privileged to allow the requested > operations (authentication, password change, process credential manipulation, > audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [X] No - continue to next section (section 3.4.6) > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > > If yes are the permissions on the file such to protect exposing the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) > Are there any network protocols used by this project? > [ ] Yes > [X] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [X] No - continue with the next section (section 3.6) > > If yes do the components support IPv6? > [ ] Yes > [ ] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [X] No > > 4.0 Interfaces > (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) > 4.1 Exported Interfaces > > The jar file "jettison_1.0.jar" contains following interface. > > Interface Name Classification Comments > --------------------------- ------------------- --------------------------- > org.codehaus.jettison > * Convention Uncommitted Interface > > org.codehaus.jettison.json > * JSONString Uncommitted Interface > > The Jar file would go in "usr/share/lib/java" > > 4.2 Imported Interfaces > Interface Name Classification Comments > --------------------------- -------------------- -------------------------- > None > > > Appendix B - Suggested case materials > 1. man pages > > Attached are the zipped Java docs (jittison.zip_) > > 2. SMF manifests > 3. links to contracts > > > > > Introduction to Library Functions jettison(3) > > NAME > jettison - A JSON (JavaScript Object Notation) STax (Stream- > ing API for XML) Implementation > > DESCRIPTION > jettison(3) is a collection of Java APIs (like STaX and DOM > - Document Object Model ) which read and write JSON. For > additional information on using jettison, browse the com- > plete html documentation at: > > file:/usr/share/lib/java/javadoc/jettison/index.html > > LICENSE > ASL 2.0 > > FILES > /usr/share/lib/java/jettison-1.0.jar > > jettison jar file > > /usr/share/lib/java/javadoc/jettison/index.html > > jettison API documentation generated with javadoc. > > ATTRIBUTES > See attributes(5) for descriptions of the following attri- > butes: > > _______________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE| > |_______________________________________ > | Availability | SUNWjettison | > |_______________________________________ > | Interface Stability| Uncommitted | > |____________________|_________________| > > SEE ALSO > http://jettison.codehaus.org > > NOTES > Source for jettison is available on http://opensolaris.org > > SunOS 5.10 Last change: 6 Feb 2009 1 > > > -- * Mark A. Carlson * Sr. Architect *Systems Group* Phone x69559 / 303-223-6139 Email Mark.Carlson@Sun.COM --Boundary_(ID_rpialrEFlTIZmdqpC3l0fg) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT This case, having resolved all outstanding issues, is being marked closed approved.
-- mark

Mark Carlson wrote: 
I am sponsoring this familiarity case for Vivek Titarmare. It requests minor 
binding and times out 02/18/2009. This Fast Track represents a component of 
LSARC 2008/748 - Drools.
The FOSS checklist, man page and javadoc are in the case directory and
the checklist and man page are attached.

-- mark

Template Version: @(#)sac_nextcase %I% %G% SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 jettison
    1.2. Name of Document Author/Supplier:
	 Author:  Vivek Titarmare
    1.3  Date of This Document:
	11 February, 2009

2. Project Summary
   2.1 Project Description

	Jettison is a collection of Java APIs (like STaX and DOM) which	read and write JSON.

4. Technical Description:

	Jettison is a collection of Java APIs (like STaX and DOM) which	read and write JSON. 

5. Interfaces 

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
   org.codehaus.jettison
	* Convention			Uncommitted    		Interface

   org.codehaus.jettison.json
	* JSONString			Uncommitted    		Interface
	 
	

   The Jar file would go in "usr/share/lib/java"

   Imported interface        Classification   Comments
   =======================   ==============   =================================== 
	None


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open



FCL--FOSS Check List

1.0 Project Information
1.1 Name of project/component
	jettison Ver 1.0

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
	Jettison is a collection of Java APIs (like STaX and DOM) which	read and write JSON.

	This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM).
	Interface stabilities and contracts will be added to the consuming case(s) as needed.

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [X] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [X] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
		The Codehaus Jettison (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released)
    
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [X] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [X] Yes 
      [ ] No - briefly explain
      
	
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [X] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [X] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [X] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [X] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [X] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [X] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [X] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      <system drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product>
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product id>\<version id>\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [X] Yes
      [ ] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [X] Yes
      [ ] No - ARC review required
      [ ] N/A
    
      Are these components already in the Solaris WOS?
      [ ] Yes
      [X] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [ ] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [X] Yes
      [ ] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [X] Yes
      [ ] No - ARC review required
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [X] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [X] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [X] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [X] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [X] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [X] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [X] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [ ] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [X] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [ ] Yes
      [X] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [ ] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [ ] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [ ] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [ ] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [ ] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [ ] Yes
      [X] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [ ] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [X] No 
      
4.0 Interfaces
  (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details)
  4.1 Exported Interfaces
  
    	The jar file "jettison_1.0.jar" contains following interface.

    Interface Name			Classification      	Comments
    --------------------------- ------------------- ---------------------------
   org.codehaus.jettison
	* Convention			Uncommitted    		Interface

   org.codehaus.jettison.json
	* JSONString			Uncommitted    		Interface
	 
   The Jar file would go in "usr/share/lib/java"

  4.2 Imported Interfaces
    Interface Name		Classification       Comments
    --------------------------- -------------------- --------------------------
	None    
    
  
Appendix B - Suggested case materials
  1. man pages

     Attached are the zipped Java docs (jittison.zip_)

  2. SMF manifests
  3. links to contracts




Introduction to Library Functions                     jettison(3)

NAME
     jettison - A JSON (JavaScript Object Notation) STax (Stream-
     ing API for XML) Implementation

DESCRIPTION
     jettison(3) is a collection of Java APIs (like STaX and  DOM
     -  Document  Object  Model  ) which read and write JSON. For
     additional information on using jettison,  browse  the  com-
     plete html documentation at:

          file:/usr/share/lib/java/javadoc/jettison/index.html

LICENSE
     ASL 2.0

FILES
     /usr/share/lib/java/jettison-1.0.jar

          jettison jar file

     /usr/share/lib/java/javadoc/jettison/index.html

          jettison API documentation generated with javadoc.

ATTRIBUTES
     See attributes(5) for descriptions of the  following  attri-
     butes:

     _______________________________________
    |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
    |_______________________________________
    | Availability       |  SUNWjettison   |
    |_______________________________________
    | Interface Stability|  Uncommitted    |
    |____________________|_________________|

SEE ALSO
     http://jettison.codehaus.org

NOTES
     Source for jettison is available on http://opensolaris.org

SunOS 5.10           Last change: 6 Feb 2009                    1

--
Mark A. Carlson
Sr. Architect

Systems Group
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM

--Boundary_(ID_rpialrEFlTIZmdqpC3l0fg)-- From margot.miller@sun.com Thu Feb 19 08:54:34 2009 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n1JGsX8b004708 for ; Thu, 19 Feb 2009 08:54:34 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1JGsTNV025685; Thu, 19 Feb 2009 16:54:31 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KFB00I17OAUMI00@nwk-avmta-1.sfbay.Sun.COM>; Thu, 19 Feb 2009 08:54:30 -0800 (PST) Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFB0015JOAQ0HB0@nwk-avmta-1.sfbay.Sun.COM>; Thu, 19 Feb 2009 08:54:26 -0800 (PST) Received: from [10.7.250.251] (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251]) by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1JGsNBW772207; Thu, 19 Feb 2009 08:54:23 -0800 (PST) Date: Thu, 19 Feb 2009 08:50:51 -0800 From: Margot Miller Subject: Re: jettison [LSARC/2009/094 FastTrack timeout 02/18/2009] In-reply-to: <499D5305.7030805@sun.com> To: "Mark A. Carlson" Cc: LSARC-ext@sun.com, Drools_Team@sun.com Message-id: <499D8DEB.9030609@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200902120021.n1C0L3XI019123@sac.sfbay.sun.com> <499D5305.7030805@sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 15873 Please just put the SVR4 package in the exported interface table. THanks Margot Mark A. Carlson wrote: > This case, having resolved all outstanding issues, is being marked > closed approved. > -- mark > > Mark Carlson wrote: >> I am sponsoring this familiarity case for Vivek Titarmare. It requests minor >> binding and times out 02/18/2009. This Fast Track represents a component of >> LSARC 2008/748 - Drools. >> The FOSS checklist, man page and javadoc are in the case directory and >> the checklist and man page are attached. >> >> -- mark >> >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> jettison >> 1.2. Name of Document Author/Supplier: >> Author: Vivek Titarmare >> 1.3 Date of This Document: >> 11 February, 2009 >> >> 2. Project Summary >> 2.1 Project Description >> >> Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. >> >> 4. Technical Description: >> >> Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. >> >> 5. Interfaces >> >> Exported interface Classification Interface type >> ============================= ============== ============== >> org.codehaus.jettison >> * Convention Uncommitted Interface >> >> org.codehaus.jettison.json >> * JSONString Uncommitted Interface >> >> >> >> The Jar file would go in "usr/share/lib/java" >> >> Imported interface Classification Comments >> ======================= ============== =================================== >> None >> >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> SFW >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> >> >> FCL--FOSS Check List >> >> 1.0 Project Information >> 1.1 Name of project/component >> jettison Ver 1.0 >> >> 1.2 Author of document >> Vivek R. Titarmare >> >> 2.0 Project Summary >> 2.1 Project Description >> Jettison is a collection of Java APIs (like STaX and DOM) which read and write JSON. >> >> This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). >> Interface stabilities and contracts will be added to the consuming case(s) as needed. >> >> 2.2 Release binding >> What is is the release binding? >> (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) >> [ ] Major >> [X] Minor >> [ ] Patch or Micro >> [ ] Unknown -- ARC review required >> >> 2.3 Type of project >> Is this case a Linux Familiarity project? >> [X] Yes >> [ ] No >> >> 2.4 Originating Community >> 2.4.1 Community Name >> The Codehaus Jettison (http://docs.codehaus.org/display/JETTISON/2008/02/21/Jettison+1.0+released) >> >> 2.4.2 Community Involvement >> Indicate Sun's involvement in the community >> [ ] Maintainer >> [ ] Contributor >> [X] Monitoring >> >> Will the project team work with the upstream community to resolve >> architectural issues of interest to Sun? >> [X] Yes >> [ ] No - briefly explain >> >> >> Will we or are we forking from the community? >> [ ] Yes - ARC review required prior to forking >> [X] No >> >> 3.0 Technical Description >> 3.1 Installation & Sharable >> 3.1.1S Solaris Installation - section only required for Solaris Software >> (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) >> Does this project follow the Install Locations best practice? >> [X] Yes >> [ ] No - ARC review required >> >> Does this project install into /usr under [sbin|bin|lib|include|man|share]? >> [X] Yes >> [ ] No or N/A >> >> Does this project install into /opt? >> [ ] Yes - explain below >> [X] No or N/A >> >> Does this project install into a different directory structure? >> [ ] Yes - ARC review required >> [X] No or N/A >> >> Do any of the components of this project conflict with anything under /usr? >> (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) >> [ ] Yes - explain below >> [X] No >> >> If conflicts exist then will this project install under /usr/gnu? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> >> Is this project installing into /usr/sfw? >> [ ] Yes - ARC review required >> [X] No >> >> 3.1.1W Windows Installation - section only required for Windows Software >> (see http://sac.sfbay/WSARC/2002/494 for details) >> Does this project install software into a >> :\Program Files\Sun\ or :\Sun\ >> directory? >> [ ] Yes >> [ ] No - ARC review required >> >> Does the project use the Windows registry? >> [ ] Yes >> [ ] No - ARC review required >> >> Does the project use >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ >> for the registry key? >> [ ] Yes >> [ ] No - ARC review required >> >> Is the project's stored location >> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.1.2 Share and Sharable >> Does the module include any components that are used or shared by >> other projects? >> [X] Yes >> [ ] No >> >> If yes are these components packaged to be shared with the other FOSS? >> [X] Yes >> [ ] No - ARC review required >> [ ] N/A >> >> Are these components already in the Solaris WOS? >> [ ] Yes >> [X] No - continue with next section (section 3.2) >> >> If yes are these newer versions being delivered? >> [ ] Yes >> [ ] No - ARC review required >> >> If yes are the newer versions replacing the existing versions? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.2 Exported Libraries >> Are libraries being delivered by this project? >> [X] Yes >> [ ] No - continue with next section (section 3.3) >> >> Are 64-bit versions of the libraries being delivered? >> [X] Yes >> [ ] No - ARC review required >> >> Are static versions of the libraries being delivered? >> [ ] Yes - ARC review required >> [X] No >> >> 3.3 Services and the /etc Directory >> (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) >> Does the project integrate anything into /etc/init.d or /etc/rc?.d? >> [ ] Yes - ARC review required >> [X] No >> >> Does the project integrate any new entries into /etc/inittab or >> /etc/inetd.conf? >> [ ] Yes - ARC review required >> [X] No >> >> Does the project integrate any private non-public files into /etc/default >> or /etc/ configuration files? >> [ ] Yes - ARC review required >> [X] No >> >> Does the service manifests method context grant rights above that >> of the noaccess user and basic privilege set? >> [ ] Yes - ARC review required >> [X] No >> >> 3.4 Security >> 3.4.1 Secure By Default >> (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) >> (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) >> (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for >> addtional details) >> Are there any network services provided by this project? >> [ ] Yes >> [X] No - continue with the next section (section 3.4.2) >> >> Are network services enabled by default? >> [ ] Yes - ARC review required >> [ ] No >> [X] N/A >> >> Are network services automatically enabled by the project during installation? >> [ ] Yes - ARC review required >> [ ] No >> [X] N/A >> >> Are inbound network communications denied by default? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> >> Is inbound data checked to prevent content-based attacks? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> >> Is the outbound receiver authenticated? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> >> Is the receiver authenticated prior to receiving any sensitive outbound communication? >> [ ] Yes >> [ ] No - ARC review required >> [X] N/A >> >> 3.4.2 Authorization >> (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and >> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ >> for details) >> Are there any setuid/setgid privileged binaries in the project? >> [ ] Yes - ARC review required >> [X] No - continue with next section (section 3.4.3) >> >> If yes then are the setuid/setgid privileges handled by the use of roles? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.3 Auditing >> (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >> Does this component contain administrative or security enforcing software? >> [ ] Yes - ARC review required >> [X] No - continue to next section (section 3.4.4) >> >> (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) >> Do the components create audit logs detailing what took place including what event >> took place, who was involved, when the event took place? >> [ ] Yes - ARC contract and Audit project team review required >> [ ] No - ARC review required >> >> >> 3.4.4 Authentication >> (see http://opensolaris.org/os/community/arc/policies/PAM/) >> Do the components contain any authentication code? >> [ ] Yes >> [X] No - continue to next section (section 3.4.5) >> >> If yes do the components use PAM (plugable authentication modules) for authentication? >> [ ] Yes >> [ ] No - ARC review required >> >> If yes is a single PAM session maintained during authentication? >> [ ] Yes >> [ ] No - ARC review required >> >> If yes are the components sufficiently privileged to allow the requested >> operations (authentication, password change, process credential manipulation, >> audit state initialization)? >> [ ] Yes - briefly describe below >> [ ] No - ARC review required >> >> 3.4.5 Passwords >> (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and >> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) >> Do any of the components for the project deal with passwords? >> [ ] Yes >> [X] No - continue to next section (section 3.4.6) >> >> If yes are these passwords entered via the CLI or environment? >> [ ] Yes - ARC review required >> [ ] No >> >> Are passwords stored within the file system for the component? >> [ ] Yes >> [ ] No - continue to next section (section 3.4.6) >> >> If yes are the permissions on the file such to protect exposing the password(s)? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.4.6 General Security Questions >> (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) >> Are there any network protocols used by this project? >> [ ] Yes >> [X] No - continue with the next section (section 3.5) >> >> Do the components use standard network protocols? >> [ ] Yes >> [ ] No - ARC review required >> >> Do network services for the project make decisions based upon user, host or >> service identities? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> >> Do the components make use of secret information during authentication and/or >> authorization? >> [ ] Yes - explain below >> [ ] No >> [ ] N/A >> >> 3.5 Networking >> Do the components access the network? >> [ ] Yes >> [X] No - continue with the next section (section 3.6) >> >> If yes do the components support IPv6? >> [ ] Yes >> [ ] No - ARC review required >> >> 3.6 Core Solaris Components >> Do the components of this project compete with or duplicate core >> Solaris components? >> [ ] Yes - ARC review required >> [X] No >> >> 4.0 Interfaces >> (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) >> 4.1 Exported Interfaces >> >> The jar file "jettison_1.0.jar" contains following interface. >> >> Interface Name Classification Comments >> --------------------------- ------------------- --------------------------- >> org.codehaus.jettison >> * Convention Uncommitted Interface >> >> org.codehaus.jettison.json >> * JSONString Uncommitted Interface >> >> The Jar file would go in "usr/share/lib/java" >> >> 4.2 Imported Interfaces >> Interface Name Classification Comments >> --------------------------- -------------------- -------------------------- >> None >> >> >> Appendix B - Suggested case materials >> 1. man pages >> >> Attached are the zipped Java docs (jittison.zip_) >> >> 2. SMF manifests >> 3. links to contracts >> >> >> >> >> Introduction to Library Functions jettison(3) >> >> NAME >> jettison - A JSON (JavaScript Object Notation) STax (Stream- >> ing API for XML) Implementation >> >> DESCRIPTION >> jettison(3) is a collection of Java APIs (like STaX and DOM >> - Document Object Model ) which read and write JSON. For >> additional information on using jettison, browse the com- >> plete html documentation at: >> >> file:/usr/share/lib/java/javadoc/jettison/index.html >> >> LICENSE >> ASL 2.0 >> >> FILES >> /usr/share/lib/java/jettison-1.0.jar >> >> jettison jar file >> >> /usr/share/lib/java/javadoc/jettison/index.html >> >> jettison API documentation generated with javadoc. >> >> ATTRIBUTES >> See attributes(5) for descriptions of the following attri- >> butes: >> >> _______________________________________ >> | ATTRIBUTE TYPE | ATTRIBUTE VALUE| >> |_______________________________________ >> | Availability | SUNWjettison | >> |_______________________________________ >> | Interface Stability| Uncommitted | >> |____________________|_________________| >> >> SEE ALSO >> http://jettison.codehaus.org >> >> NOTES >> Source for jettison is available on http://opensolaris.org >> >> SunOS 5.10 Last change: 6 Feb 2009 1 >> >> >> > > -- > * Mark A. Carlson * > Sr. Architect > > *Systems Group* > Phone x69559 / 303-223-6139 > Email Mark.Carlson@Sun.COM > > >