From markcarl@sac.sfbay.sun.com Tue Feb 24 15:09:06 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 n1ON95Zb029822 for ; Tue, 24 Feb 2009 15:09:06 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n1ON8nCP026818; Wed, 25 Feb 2009 07:09:04 +0800 (SGT) 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 <0KFL00C09EZ2GO00@nwk-avmta-1.sfbay.Sun.COM>; Tue, 24 Feb 2009 15:09:02 -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 <0KFL005XBEYRH920@nwk-avmta-1.sfbay.Sun.COM>; Tue, 24 Feb 2009 15:08:51 -0800 (PST) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1ON8pvM049731; Tue, 24 Feb 2009 15:08:51 -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 n1ON8oOm029817; Tue, 24 Feb 2009 15:08:50 -0800 (PST) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1ON8ong029813; Tue, 24 Feb 2009 15:08:50 -0800 (PST) Date: Tue, 24 Feb 2009 15:08:50 -0800 (PST) From: Mark Carlson Subject: pullparser [LSARC/2009/133 FastTrack timeout 03/03/2009] To: LSARC-ext@sun.com Cc: Drools_team@sun.com Message-id: <200902242308.n1ON8ong029813@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 14277 I am sponsoring this familiarity case for Vivek Titarmare. It requests minor binding and times out 03/03/2009. This Fast Track represents a component of LSARC 2008/748 - Drools. The FOSS checklist, man page and javadoc (zip file) are in the case directory and also the checklist and man page are attached. -- mark Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: pullparser 1.2. Name of Document Author/Supplier: Author: Vivek Titarmare 1.3 Date of This Document: 24 February, 2009 2. Project Summary 2.1 Project Description Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors). 4. Technical Description: Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors). 5. Interfaces Exported interface Classification Interface type ============================= ============== ============== XmlEndTag Uncommitted Interface XmlFormatter Uncommitted Interface XmlNode Uncommitted Interface XmlPullNode Uncommitted Interface XmlPullParser Uncommitted Interface XmlPullParserBufferControl Uncommitted Interface XmlPullParserEventPosition Uncommitted Interface XmlRecorder Uncommitted Interface XmlStartTag Uncommitted Interface XmlTag Uncommitted Interface XmlWritable Uncommitted Interface SUNWpull-parser Uncommitted Package Name pullparser-2.1.10.jar Uncommitted Jar File The Jar file would go in "usr/share/lib/java" Imported interface Classification Comments ======================= ============== =================================== /usr/share/lib/ant/xercesImpl.jar Already in solaris. 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 pullparser Ver 2.1.10 1.2 Author of document Vivek R. Titarmare 2.0 Project Summary 2.1 Project Description Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors). 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 XML Pull Parser (http://www.extreme.indiana.edu/xgws/xsoap/xpp/) 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 project proposal Introduction to Library Functions pull-parser(3) NAME pull-parser - XML parser DESCRIPTION pull-parser(3) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors).For addi- tional information on using pull-parser, browse the complete html documentation at: file:/usr/share/lib/java/javadoc/pull-parser/index.html LICENSE Indiana University Exterme! Lab Software License FILES /usr/share/lib/java/pull-parser-2.1.10.jar pull-parser jar file /usr/share/lib/java/javadoc/pull-parser/index.html pull-parser API documentation generated with javadoc. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: _______________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE| |_______________________________________ | Availability | SUNWpull-parser| |_______________________________________ | Interface Stability| Uncommitted | |____________________|_________________| SEE ALSO http://www.extreme.indiana.edu/xgws/xsoap/xpp/ NOTES Source for pull-parser is available on http://opensolaris.org SunOS 5.10 Last change: 4 Feb 2009 1 From margot.miller@sun.com Wed Feb 25 11:34:26 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 n1PJYQZs016121 for ; Wed, 25 Feb 2009 11:34:26 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1PJYL9N062868; Wed, 25 Feb 2009 12:34:25 -0700 (MST) 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 <0KFM0042RZPAV900@nwk-avmta-2.sfbay.sun.com>; Wed, 25 Feb 2009 11:34:22 -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 <0KFM00JZRZP9K5D0@nwk-avmta-2.sfbay.sun.com>; Wed, 25 Feb 2009 11:34:21 -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 n1PJYDMP956083; Wed, 25 Feb 2009 11:34:13 -0800 (PST) Date: Wed, 25 Feb 2009 11:30:36 -0800 From: Margot Miller Subject: Re: pullparser [LSARC/2009/133 FastTrack timeout 03/03/2009] In-reply-to: <200902242308.n1ON8ong029813@sac.sfbay.sun.com> To: Mark Carlson Cc: LSARC-ext@sun.com, Drools_team@sun.com Message-id: <49A59C5C.6090202@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: <200902242308.n1ON8ong029813@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0b1 (X11/20070115) Status: RO Content-Length: 15236 +1 For completeness, the original ANT case was PSARC/2002/232 in the below imported interface table under comments. Thanks Margot Mark Carlson wrote: > I am sponsoring this familiarity case for Vivek Titarmare. It requests minor > binding and times out 03/03/2009. This Fast Track represents a component of > LSARC 2008/748 - Drools. > The FOSS checklist, man page and javadoc (zip file) are in the case directory > and also the checklist and man page are attached. > > -- mark > > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > pullparser > 1.2. Name of Document Author/Supplier: > Author: Vivek Titarmare > 1.3 Date of This Document: > 24 February, 2009 > > 2. Project Summary > 2.1 Project Description > > Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors). > > 4. Technical Description: > > Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors). > > 5. Interfaces > > Exported interface Classification Interface type > ============================= ============== ============== > XmlEndTag Uncommitted Interface > XmlFormatter Uncommitted Interface > XmlNode Uncommitted Interface > XmlPullNode Uncommitted Interface > XmlPullParser Uncommitted Interface > XmlPullParserBufferControl Uncommitted Interface > XmlPullParserEventPosition Uncommitted Interface > XmlRecorder Uncommitted Interface > XmlStartTag Uncommitted Interface > XmlTag Uncommitted Interface > XmlWritable Uncommitted Interface > SUNWpull-parser Uncommitted Package Name > pullparser-2.1.10.jar Uncommitted Jar File > > The Jar file would go in "usr/share/lib/java" > > Imported interface Classification Comments > ======================= ============== =================================== > > /usr/share/lib/ant/xercesImpl.jar Already in solaris. > > > 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 > pullparser Ver 2.1.10 > > 1.2 Author of document > Vivek R. Titarmare > > 2.0 Project Summary > 2.1 Project Description > Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors). > > 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 > XML Pull Parser (http://www.extreme.indiana.edu/xgws/xsoap/xpp/) > > 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 project proposal > > > Introduction to Library Functions pull-parser(3) > > NAME > pull-parser - XML parser > > DESCRIPTION > pull-parser(3) is a streaming pull XML parser and should be > used when there is a need to process quickly and efficiently > all input elements(for example in SOAP processors).For addi- > tional information on using pull-parser, browse the complete > html documentation at: > > file:/usr/share/lib/java/javadoc/pull-parser/index.html > > LICENSE > Indiana University Exterme! Lab Software License > > FILES > /usr/share/lib/java/pull-parser-2.1.10.jar > > pull-parser jar file > > /usr/share/lib/java/javadoc/pull-parser/index.html > > pull-parser API documentation generated with javadoc. > > ATTRIBUTES > See attributes(5) for descriptions of the following attri- > butes: > > _______________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE| > |_______________________________________ > | Availability | SUNWpull-parser| > |_______________________________________ > | Interface Stability| Uncommitted | > |____________________|_________________| > > SEE ALSO > http://www.extreme.indiana.edu/xgws/xsoap/xpp/ > > NOTES > Source for pull-parser is available on > http://opensolaris.org > > SunOS 5.10 Last change: 4 Feb 2009 1 > From Richard.Matthews@sun.com Mon Mar 2 15:29:40 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 n22NTdtX022395 for ; Mon, 2 Mar 2009 15:29:39 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n22NTdLP021902 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 2 Mar 2009 15:29:39 -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 <0KFW00007JXFY300@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 02 Mar 2009 15:29:39 -0800 (PST) Received: from brmea-mail-4.sun.com ([192.18.98.36]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KFW00EO4JX5TO60@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 02 Mar 2009 15:29:29 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n22NTTp7014342 for ; Mon, 02 Mar 2009 23:29:29 +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 <0KFW00G00JL7G700@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon, 02 Mar 2009 16:29:29 -0700 (MST) Received: from [129.152.9.11] ([unknown] [129.152.9.11]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFW006SOJX16YE0@mail-amer.sun.com>; Mon, 02 Mar 2009 16:29:26 -0700 (MST) Date: Mon, 02 Mar 2009 17:29:25 -0600 From: Rick Matthews Subject: Re: pullparser [LSARC/2009/133 FastTrack timeout 03/03/2009] In-reply-to: <200902242308.n1ON8ong029813@sac.sfbay.sun.com> Sender: Richard.Matthews@sun.com To: Mark Carlson Cc: LSARC-ext@sun.com Reply-to: Richard.Matthews@sun.com Message-id: <49AC6BD5.3080809@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: <200902242308.n1ON8ong029813@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 865 +1, also -- Rick On 02/24/09 17:08, Mark Carlson wrote: > I am sponsoring this familiarity case for Vivek Titarmare. It requests minor > binding and times out 03/03/2009. This Fast Track represents a component of > LSARC 2008/748 - Drools. > The FOSS checklist, man page and javadoc (zip file) are in the case directory > and also the checklist and man page are attached. > > -- mark > > > -- --------------------------------------------------------------------- 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 Mark.Carlson@Sun.COM Wed Mar 4 07:36:35 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 n24FaY2C019663 for ; Wed, 4 Mar 2009 07:36: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 n24FaERc018301; Wed, 4 Mar 2009 15:36:33 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 <0KFZ00439NCV7C00@nwk-avmta-1.sfbay.Sun.COM>; Wed, 04 Mar 2009 07:36:31 -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 <0KFZ006DBNCS24A0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 04 Mar 2009 07:36:28 -0800 (PST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n24FaSuJ002508; Wed, 04 Mar 2009 15:36:28 +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 <0KFZ00500MSQ7D00@mail-amer.sun.com>; Wed, 04 Mar 2009 08:36:28 -0700 (MST) Received: from Macintosh-335.local ([unknown] [129.150.33.102]) by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) with ESMTPSA id <0KFZ00607NCIK7G0@mail-amer.sun.com>; Wed, 04 Mar 2009 08:36:19 -0700 (MST) Date: Wed, 04 Mar 2009 08:36:17 -0700 From: "Mark A. Carlson" Subject: Re: pullparser [LSARC/2009/133 FastTrack timeout 03/03/2009] In-reply-to: <49A59C5C.6090202@sun.com> Sender: Mark.Carlson@Sun.COM To: LSARC-ext@Sun.COM Cc: Drools_Team@Sun.COM Message-id: <49AE9FF1.9000309@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_rlMBSORO12jCa9Eo+VqfyQ)" X-PMX-Version: 5.4.1.325704 References: <200902242308.n1ON8ong029813@sac.sfbay.sun.com> <49A59C5C.6090202@sun.com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 48383 This is a multi-part message in MIME format. --Boundary_(ID_rlMBSORO12jCa9Eo+VqfyQ) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Fixed in Proposal.txt - this case is now marked closed approved. -- mark Margot Miller wrote: > +1 > > For completeness, the original ANT case was PSARC/2002/232 > in the below imported interface table under comments. > > Thanks > Margot > > > > Mark Carlson wrote: >> I am sponsoring this familiarity case for Vivek Titarmare. It >> requests minor binding and times out 03/03/2009. This Fast Track >> represents a component of LSARC 2008/748 - Drools. >> The FOSS checklist, man page and javadoc (zip file) are in the case >> directory and also the checklist and man page are attached. >> >> -- mark >> >> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI >> This information is Copyright 2009 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> pullparser >> 1.2. Name of Document Author/Supplier: >> Author: Vivek Titarmare >> 1.3 Date of This Document: >> 24 February, 2009 >> >> 2. Project Summary >> 2.1 Project Description >> >> Xml Pull Parser (XPP) is a streaming pull XML parser and should >> be used when there is a need to process quickly and efficiently all >> input elements(for example in SOAP processors). >> >> 4. Technical Description: >> >> Xml Pull Parser (XPP) is a streaming pull XML parser and should >> be used when there is a need to process quickly and efficiently all >> input elements(for example in SOAP processors). >> >> 5. Interfaces >> Exported interface Classification >> Interface type >> ============================= ============== >> ============== >> XmlEndTag Uncommitted Interface >> XmlFormatter Uncommitted Interface >> XmlNode Uncommitted Interface >> XmlPullNode Uncommitted Interface >> XmlPullParser Uncommitted Interface >> XmlPullParserBufferControl Uncommitted Interface >> XmlPullParserEventPosition Uncommitted Interface >> XmlRecorder Uncommitted Interface >> XmlStartTag Uncommitted Interface >> XmlTag Uncommitted Interface >> XmlWritable Uncommitted Interface >> SUNWpull-parser Uncommitted >> Package Name >> pullparser-2.1.10.jar Uncommitted Jar File >> >> The Jar file would go in "usr/share/lib/java" >> >> Imported interface Classification Comments >> ======================= ============== >> =================================== >> /usr/share/lib/ant/xercesImpl.jar Already in solaris. >> >> >> 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 >> pullparser Ver 2.1.10 >> >> 1.2 Author of document >> Vivek R. Titarmare >> >> 2.0 Project Summary >> 2.1 Project Description >> Xml Pull Parser (XPP) is a streaming pull XML parser and should >> be used when there is a need to process quickly and efficiently all >> input elements(for example in SOAP processors). >> 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 >> XML Pull Parser (http://www.extreme.indiana.edu/xgws/xsoap/xpp/) >> 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 project proposal >> >> >> Introduction to Library Functions pull-parser(3) >> >> NAME >> pull-parser - XML parser >> >> DESCRIPTION >> pull-parser(3) is a streaming pull XML parser and should be >> used when there is a need to process quickly and efficiently >> all input elements(for example in SOAP processors).For addi- >> tional information on using pull-parser, browse the complete >> html documentation at: >> >> file:/usr/share/lib/java/javadoc/pull-parser/index.html >> >> LICENSE >> Indiana University Exterme! Lab Software License >> >> FILES >> /usr/share/lib/java/pull-parser-2.1.10.jar >> >> pull-parser jar file >> >> /usr/share/lib/java/javadoc/pull-parser/index.html >> >> pull-parser API documentation generated with javadoc. >> >> ATTRIBUTES >> See attributes(5) for descriptions of the following attri- >> butes: >> >> _______________________________________ >> | ATTRIBUTE TYPE | ATTRIBUTE VALUE| >> |_______________________________________ >> | Availability | SUNWpull-parser| >> |_______________________________________ >> | Interface Stability| Uncommitted | >> |____________________|_________________| >> >> SEE ALSO >> http://www.extreme.indiana.edu/xgws/xsoap/xpp/ >> >> NOTES >> Source for pull-parser is available on >> http://opensolaris.org >> >> SunOS 5.10 Last change: 4 Feb 2009 1 >> > -- * Mark A. Carlson * Sr. Architect *Systems Group* Phone x69559 / 303-223-6139 Email Mark.Carlson@Sun.COM --Boundary_(ID_rlMBSORO12jCa9Eo+VqfyQ) Content-type: text/html; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Fixed in Proposal.txt - this case is now marked closed approved.

-- mark

Margot Miller wrote:
+1

For completeness, the original ANT case was PSARC/2002/232
in the below imported interface table under comments.

Thanks
Margot



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

-- mark

Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
     pullparser
    1.2. Name of Document Author/Supplier:
     Author:  Vivek Titarmare
    1.3  Date of This Document:
    24 February, 2009

2. Project Summary
   2.1 Project Description

    Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors).

4. Technical Description:

    Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors).
 
5. Interfaces
   Exported interface                   Classification         Interface type
   =============================        ==============         ==============
    XmlEndTag            Uncommitted            Interface
    XmlFormatter            Uncommitted            Interface
    XmlNode                Uncommitted            Interface
    XmlPullNode            Uncommitted            Interface
    XmlPullParser            Uncommitted            Interface
    XmlPullParserBufferControl    Uncommitted            Interface
    XmlPullParserEventPosition    Uncommitted            Interface
    XmlRecorder            Uncommitted            Interface
    XmlStartTag            Uncommitted            Interface
    XmlTag                Uncommitted            Interface
    XmlWritable            Uncommitted            Interface
        SUNWpull-parser                 Uncommitted             Package Name
        pullparser-2.1.10.jar           Uncommitted             Jar File

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

   Imported interface        Classification   Comments
   =======================   ==============   ===================================
    /usr/share/lib/ant/xercesImpl.jar             Already in solaris.


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
    pullparser Ver 2.1.10

1.2 Author of document
    Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
    Xml Pull Parser (XPP) is a streaming pull XML parser and should be used when there is a need to process quickly and efficiently all input elements(for example in SOAP processors).
      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
        XML Pull Parser (http://www.extreme.indiana.edu/xgws/xsoap/xpp/)
        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 project proposal


Introduction to Library Functions                  pull-parser(3)

NAME
     pull-parser - XML parser

DESCRIPTION
     pull-parser(3)  is a streaming pull XML parser and should be
     used when there is a need to process quickly and efficiently
     all input elements(for example in SOAP processors).For addi-
     tional information on using pull-parser, browse the complete
     html documentation at:

          file:/usr/share/lib/java/javadoc/pull-parser/index.html

LICENSE
     Indiana University Exterme! Lab Software License

FILES
     /usr/share/lib/java/pull-parser-2.1.10.jar

          pull-parser jar file

     /usr/share/lib/java/javadoc/pull-parser/index.html

          pull-parser API documentation generated with javadoc.

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

     _______________________________________
    |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
    |_______________________________________
    | Availability       |  SUNWpull-parser|
    |_______________________________________
    | Interface Stability|  Uncommitted    |
    |____________________|_________________|

SEE ALSO
     http://www.extreme.indiana.edu/xgws/xsoap/xpp/

NOTES
     Source     for     pull-parser     is      available      on
     http://opensolaris.org

SunOS 5.10           Last change: 4 Feb 2009                    1
 


--
Mark A. Carlson
Sr. Architect

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

--Boundary_(ID_rlMBSORO12jCa9Eo+VqfyQ)--