From markcarl@sac.sfbay.sun.com Wed Feb 11 06:09:47 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 n1BE9lAV001533
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 11 Feb 2009 06:09:47 -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 n1BE9lbZ062910;
	Wed, 11 Feb 2009 07:09:47 -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 <0KEW00I05NCB8Q00@brm-avmta-1.central.sun.com>; Wed,
 11 Feb 2009 07:09:47 -0700 (MST)
Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KEW009GBNCA5W60@brm-avmta-1.central.sun.com>; Wed,
 11 Feb 2009 07:09:46 -0700 (MST)
Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n1BE9kqd041584; Wed, 11 Feb 2009 06:09:46 -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 n1BE9iK7001516; Wed,
 11 Feb 2009 06:09:44 -0800 (PST)
Received: (from markcarl@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1BE9ioU001512; Wed,
 11 Feb 2009 06:09:44 -0800 (PST)
Date: Wed, 11 Feb 2009 06:09:44 -0800 (PST)
From: Mark Carlson <markcarl@sac.sfbay.sun.com>
Subject: jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]
To: LSARC-ext@sun.com
Cc: Drools_Team@sun.com
Message-id: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 15866

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:
	 jsr94
    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

	Java runtime API for rule engines.

4. Technical Description:

	The interfaces and classes defined by the specification are in the javax.rules and javax.rules.admin packages. The javax.rules package contains classes and interfaces that are aimed at runtime clients of the rule engine. The runtime client API exposes methods to acquire a rule session for a registered rule execution set and interact with the rule session. The administrator API exposes methods to load an execution set from these external resources:URI, InputStream, XML Element, binary abstract syntax tree, or Reader. The administrator API also provides methods to register and unregister rule execution sets. Only registered rule execution sets are accessible through the runtime client API. A packaging separation between the runtime client API and the administrator API was made to reinforce the distinction between executing a rule execution set that has been previously loaded and registered into the runtime environment by an administrator, and the dynamic loading and execution!
  of external resources. The later actions can only be performed using the classes and interfaces in the javax.rules.admin package.

5. Interfaces 

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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
	jsr94 Ver 1.0.3

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
	Java runtime API for rule engines.

	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
	Java Rule Engine API. Java Community Process.  (http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html)	
	    
    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
  
    Interface Name			Classification      	Comments
    --------------------------- ------------------- ---------------------------
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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 (jsr94.zip_)

  2. SMF manifests
  3. links to contracts
Introduction to Library Functions                        jsr94(3)

NAME
     jsr94 - Java Rule Engine API

DESCRIPTION
     jsr94(3)  Java runtime API for rule engines. For  additional
     information  on  using jsr94, browse the complete html docu-
     mentation at:

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

LICENSE
     ASL 2.0

FILES
     /usr/share/lib/java/jsr94.jar

          jsr94 jar file

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

          jsr94 API documentation generated with javadoc.

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

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

SEE ALSO
     http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html

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

SunOS 5.10           Last change: 4 Feb 2009                    1




From Richard.Matthews@Sun.COM Fri Feb 13 10:10:43 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 n1DIAgJ7025980
	for <LSARC-ext@sac.sfbay.sun.com>; Fri, 13 Feb 2009 10:10:42 -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 n1DIAeCm027434
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Sat, 14 Feb 2009 02:10:41 +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 <0KF00050FNTRE600@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 10:10:39 -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 <0KF000GOCNTPGB80@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri,
 13 Feb 2009 10:10:37 -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 n1DIAbpC008213	for
 <LSARC-ext@sun.com>; Fri, 13 Feb 2009 18:10:37 +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:10:37 -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 <0KF0003U8NTLSG90@mail-amer.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri,
 13 Feb 2009 11:10:34 -0700 (MST)
Date: Fri, 13 Feb 2009 12:10:32 -0600
From: Rick Matthews <Richard.Matthews@Sun.COM>
Subject: Re: jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]
In-reply-to: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
Sender: Richard.Matthews@Sun.COM
Cc: LSARC-ext@Sun.COM
Reply-to: Richard.Matthews@Sun.COM
Message-id: <4995B798.2010109@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: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.16 (X11/20080807)
Status: RO
Content-Length: 472

+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 Mark.Carlson@sun.com Thu Feb 19 04:41:56 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 n1JCftNZ008574
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 19 Feb 2009 04:41:56 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1JCfQdL017297;
	Thu, 19 Feb 2009 12:41:54 GMT
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 <0KFB00M0VCLT7R00@nwk-avmta-2.sfbay.sun.com>; Thu,
 19 Feb 2009 04:41:53 -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 <0KFB008MKCLSU0D0@nwk-avmta-2.sfbay.sun.com>; Thu,
 19 Feb 2009 04:41:53 -0800 (PST)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1JCfqlm014842; Thu,
 19 Feb 2009 12:41:52 +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:41:52 -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 <0KFB004SCCLQ8420@mail-amer.sun.com>; Thu,
 19 Feb 2009 05:41:50 -0700 (MST)
Date: Thu, 19 Feb 2009 05:41:50 -0700
From: "Mark A. Carlson" <Mark.Carlson@sun.com>
Subject: Re: jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]
In-reply-to: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
Sender: Mark.Carlson@sun.com
To: LSARC-ext@sun.com
Cc: Drools_Team@sun.com
Message-id: <499D538E.9050307@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_FSpzq8AZXAkYmuu/ZI9Ncg)"
X-PMX-Version: 5.4.1.325704
References: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
Status: RO
Content-Length: 36890

This is a multi-part message in MIME format.

--Boundary_(ID_FSpzq8AZXAkYmuu/ZI9Ncg)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT



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:
> 	 jsr94
>     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
>
> 	Java runtime API for rule engines.
>
> 4. Technical Description:
>
> 	The interfaces and classes defined by the specification are in the javax.rules and javax.rules.admin packages. The javax.rules package contains classes and interfaces that are aimed at runtime clients of the rule engine. The runtime client API exposes methods to acquire a rule session for a registered rule execution set and interact with the rule session. The administrator API exposes methods to load an execution set from these external resources:URI, InputStream, XML Element, binary abstract syntax tree, or Reader. The administrator API also provides methods to register and unregister rule execution sets. Only registered rule execution sets are accessible through the runtime client API. A packaging separation between the runtime client API and the administrator API was made to reinforce the distinction between executing a rule execution set that has been previously loaded and registered into the runtime environment by an administrator, and the dynamic loading and executi!
 on!
>   of external resources. The later actions can only be performed using the classes and interfaces in the javax.rules.admin package.
>
> 5. Interfaces 
>
>    Exported interface                   Classification 		Interface type
>    =============================        ============== 		==============
>    javax.rules
> 	* Handle			Uncommitted    		Interface
> 	* ObjectFilter			Uncommitted    		Interface
> 	* RuleExecutionSetMetadata	Uncommitted    		Interface
> 	* RuleRuntime			Uncommitted    		Interface
> 	* RuleSession			Uncommitted    		Interface
> 	* StatefulRuleSession		Uncommitted    		Interface
> 	* StatelessRuleSession		Uncommitted    		Interface
>
>    javax.rules.admin 
> 	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
> 	* Rule				Uncommitted    		Interface
> 	* RuleAdministrator		Uncommitted    		Interface
> 	* RuleExecutionSet		Uncommitted    		Interface
> 	* RuleExecutionSetProvider	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
> 	jsr94 Ver 1.0.3
>
> 1.2 Author of document
> 	Vivek R. Titarmare
>
> 2.0 Project Summary
>   2.1 Project Description
> 	Java runtime API for rule engines.
>
> 	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
> 	Java Rule Engine API. Java Community Process.  (http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html)	
> 	    
>     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
>   
>     Interface Name			Classification      	Comments
>     --------------------------- ------------------- ---------------------------
>    javax.rules
> 	* Handle			Uncommitted    		Interface
> 	* ObjectFilter			Uncommitted    		Interface
> 	* RuleExecutionSetMetadata	Uncommitted    		Interface
> 	* RuleRuntime			Uncommitted    		Interface
> 	* RuleSession			Uncommitted    		Interface
> 	* StatefulRuleSession		Uncommitted    		Interface
> 	* StatelessRuleSession		Uncommitted    		Interface
>
>    javax.rules.admin 
> 	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
> 	* Rule				Uncommitted    		Interface
> 	* RuleAdministrator		Uncommitted    		Interface
> 	* RuleExecutionSet		Uncommitted    		Interface
> 	* RuleExecutionSetProvider	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 (jsr94.zip_)
>
>   2. SMF manifests
>   3. links to contracts
> Introduction to Library Functions                        jsr94(3)
>
> NAME
>      jsr94 - Java Rule Engine API
>
> DESCRIPTION
>      jsr94(3)  Java runtime API for rule engines. For  additional
>      information  on  using jsr94, browse the complete html docu-
>      mentation at:
>
>           file:/usr/share/lib/java/javadoc/jsr94/index.html
>
> LICENSE
>      ASL 2.0
>
> FILES
>      /usr/share/lib/java/jsr94.jar
>
>           jsr94 jar file
>
>      /usr/share/lib/java/javadoc/jsr94/index.html
>
>           jsr94 API documentation generated with javadoc.
>
> ATTRIBUTES
>      See attributes(5) for descriptions of the  following  attri-
>      butes:
>
>      _______________________________________
>     |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
>     |_______________________________________
>     | Availability       |  SUNWjsr94      |
>     |_______________________________________
>     | Interface Stability|  Uncommitted    |
>     |____________________|_________________|
>
> SEE ALSO
>      http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html
>
> NOTES
>      Source for jsr94 is available on http://opensolaris.org
>
> SunOS 5.10           Last change: 4 Feb 2009                    1
>
>
>
>   

-- 
<http://www.sun.com> 	* Mark A. Carlson *
Sr. Architect

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



--Boundary_(ID_FSpzq8AZXAkYmuu/ZI9Ncg)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Mark Carlson wrote:
<blockquote cite="mid:200902111409.n1BE9ioU001512@sac.sfbay.sun.com"
 type="cite">
  <pre wrap="">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:
	 jsr94
    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

	Java runtime API for rule engines.

4. Technical Description:

	The interfaces and classes defined by the specification are in the javax.rules and javax.rules.admin packages. The javax.rules package contains classes and interfaces that are aimed at runtime clients of the rule engine. The runtime client API exposes methods to acquire a rule session for a registered rule execution set and interact with the rule session. The administrator API exposes methods to load an execution set from these external resources:URI, InputStream, XML Element, binary abstract syntax tree, or Reader. The administrator API also provides methods to register and unregister rule execution sets. Only registered rule execution sets are accessible through the runtime client API. A packaging separation between the runtime client API and the administrator API was made to reinforce the distinction between executing a rule execution set that has been previously loaded and registered into the runtime environment by an administrator, and the dynamic loading and execution!

  of external resources. The later actions can only be performed using the classes and interfaces in the javax.rules.admin package.

5. Interfaces 

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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
	jsr94 Ver 1.0.3

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
	Java runtime API for rule engines.

	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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/release-taxonomy/">http://opensolaris.org/os/community/arc/policies/release-taxonomy/</a>)
      [ ] 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
	Java Rule Engine API. Java Community Process.  (<a class="moz-txt-link-freetext" href="http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html">http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html</a>)	
	    
    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 &amp; Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/install-locations/">http://opensolaris.org/os/community/arc/policies/install-locations/</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2007/047/">http://opensolaris.org/os/community/arc/caselog/2007/047/</a> 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 <a class="moz-txt-link-freetext" href="http://sac.sfbay/WSARC/2002/494">http://sac.sfbay/WSARC/2002/494</a> for details)
      Does this project install software into a 
      &lt;system drive&gt;:\Program Files\Sun\&lt;product&gt; or &lt;system drive&gt;:\Sun\&lt;product&gt;
      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\&lt;product&gt;\&lt;version&gt;
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\&lt;product id&gt;\&lt;version id&gt;\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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/SMF-policy/">http://opensolaris.org/os/community/arc/policies/SMF-policy/</a>)
      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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/secure-by-default/">http://opensolaris.org/os/community/arc/policies/secure-by-default/</a> for details)
      (see <a class="moz-txt-link-freetext" href="http://www.opensolaris.org/os/community/arc/policies/NITS-policy/">http://www.opensolaris.org/os/community/arc/policies/NITS-policy/</a> for details)
      (see parts of <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/SMF-policy/">http://opensolaris.org/os/community/arc/policies/SMF-policy/</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/">http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/</a> and
	   <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/">http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/</a> and
	   <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/">http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/</a>
           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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/audit-policy/">http://opensolaris.org/os/community/arc/policies/audit-policy/</a> for details)
      (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2003/397">http://opensolaris.org/os/community/arc/caselog/2003/397</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2003/397">http://opensolaris.org/os/community/arc/caselog/2003/397</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/PAM/">http://opensolaris.org/os/community/arc/policies/PAM/</a>)
      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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/">http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/</a> and
           <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/passwords-files/">http://opensolaris.org/os/community/arc/bestpractices/passwords-files/</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/security-questions/">http://opensolaris.org/os/community/arc/bestpractices/security-questions/</a> 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 <a class="moz-txt-link-freetext" href="http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/">http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/</a> for details)
  4.1 Exported Interfaces
  
    Interface Name			Classification      	Comments
    --------------------------- ------------------- ---------------------------
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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 (jsr94.zip_)

  2. SMF manifests
  3. links to contracts
Introduction to Library Functions                        jsr94(3)

NAME
     jsr94 - Java Rule Engine API

DESCRIPTION
     jsr94(3)  Java runtime API for rule engines. For  additional
     information  on  using jsr94, browse the complete html docu-
     mentation at:

          <a class="moz-txt-link-freetext" href="file:/usr/share/lib/java/javadoc/jsr94/index.html">file:/usr/share/lib/java/javadoc/jsr94/index.html</a>

LICENSE
     ASL 2.0

FILES
     /usr/share/lib/java/jsr94.jar

          jsr94 jar file

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

          jsr94 API documentation generated with javadoc.

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

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

SEE ALSO
     <a class="moz-txt-link-freetext" href="http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html">http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html</a>

NOTES
     Source for jsr94 is available on <a class="moz-txt-link-freetext" href="http://opensolaris.org">http://opensolaris.org</a>

SunOS 5.10           Last change: 4 Feb 2009                    1



  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title></title>
<table border="0" cellpadding="0" cellspacing="0" width="519">
  <tbody>
    <tr valign="top">
      <td height="121" width="98"><a moz-do-not-send="true"
 href="http://www.sun.com"><img moz-do-not-send="true"
 src="http://www.sun.com/emrkt/sigs/6h_top.gif" border="0" height="92"
 width="98"></a></td>
      <td style="font-family: Arial; font-size: 10px;" height="121"
 width="249"><b> Mark A. Carlson </b><br>
Sr. Architect<br>
      <br>
      <b>Systems Group</b><br>
Phone x69559 / 303-223-6139<br>
Email <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
 href="mailto:Mark.Carlson@Sun.COM">Mark.Carlson@Sun.COM</a><br>
      </td>
      <td style="font-family: Arial; font-size: 10px;" width="172"><img
 moz-do-not-send="true" src="http://www.sun.com/emrkt/sigs/q12.gif"
 height="118" width="172"></td>
    </tr>
  </tbody>
</table>
<div class="moz-signature"><br>
</div>
</div>
</body>
</html>

--Boundary_(ID_FSpzq8AZXAkYmuu/ZI9Ncg)--

From Mark.Carlson@Sun.COM Thu Feb 19 04:44:26 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 n1JCiPvr008640
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 19 Feb 2009 04:44:25 -0800 (PST)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1JCiPYT012924;
	Thu, 19 Feb 2009 04:44:25 -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 <0KFB00M0FCQ0CV00@nwk-avmta-2.sfbay.sun.com>; Thu,
 19 Feb 2009 04:44:24 -0800 (PST)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFB008E5CPYTYD0@nwk-avmta-2.sfbay.sun.com>; Thu,
 19 Feb 2009 04:44:23 -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 n1JCiM4G024407; Thu,
 19 Feb 2009 12:44:22 +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 <0KFB00L00CJD4K00@mail-amer.sun.com>; Thu, 19 Feb 2009 05:44:22 -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 <0KFB006XXCPWE660@mail-amer.sun.com>; Thu,
 19 Feb 2009 05:44:22 -0700 (MST)
Date: Thu, 19 Feb 2009 05:44:20 -0700
From: "Mark A. Carlson" <Mark.Carlson@Sun.COM>
Subject: Re: jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]
In-reply-to: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
Sender: Mark.Carlson@Sun.COM
To: LSARC-ext@Sun.COM
Cc: Drools_Team@Sun.COM
Message-id: <499D5424.5070304@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_AiVmtyGWFWCqdupU++VH+w)"
X-PMX-Version: 5.4.1.325704
References: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209)
Status: RO
Content-Length: 37091

This is a multi-part message in MIME format.

--Boundary_(ID_AiVmtyGWFWCqdupU++VH+w)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

This case, having received the requisite +1, 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:
> 	 jsr94
>     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
>
> 	Java runtime API for rule engines.
>
> 4. Technical Description:
>
> 	The interfaces and classes defined by the specification are in the javax.rules and javax.rules.admin packages. The javax.rules package contains classes and interfaces that are aimed at runtime clients of the rule engine. The runtime client API exposes methods to acquire a rule session for a registered rule execution set and interact with the rule session. The administrator API exposes methods to load an execution set from these external resources:URI, InputStream, XML Element, binary abstract syntax tree, or Reader. The administrator API also provides methods to register and unregister rule execution sets. Only registered rule execution sets are accessible through the runtime client API. A packaging separation between the runtime client API and the administrator API was made to reinforce the distinction between executing a rule execution set that has been previously loaded and registered into the runtime environment by an administrator, and the dynamic loading and executi!
 on!
>   of external resources. The later actions can only be performed using the classes and interfaces in the javax.rules.admin package.
>
> 5. Interfaces 
>
>    Exported interface                   Classification 		Interface type
>    =============================        ============== 		==============
>    javax.rules
> 	* Handle			Uncommitted    		Interface
> 	* ObjectFilter			Uncommitted    		Interface
> 	* RuleExecutionSetMetadata	Uncommitted    		Interface
> 	* RuleRuntime			Uncommitted    		Interface
> 	* RuleSession			Uncommitted    		Interface
> 	* StatefulRuleSession		Uncommitted    		Interface
> 	* StatelessRuleSession		Uncommitted    		Interface
>
>    javax.rules.admin 
> 	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
> 	* Rule				Uncommitted    		Interface
> 	* RuleAdministrator		Uncommitted    		Interface
> 	* RuleExecutionSet		Uncommitted    		Interface
> 	* RuleExecutionSetProvider	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
> 	jsr94 Ver 1.0.3
>
> 1.2 Author of document
> 	Vivek R. Titarmare
>
> 2.0 Project Summary
>   2.1 Project Description
> 	Java runtime API for rule engines.
>
> 	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
> 	Java Rule Engine API. Java Community Process.  (http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html)	
> 	    
>     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
>   
>     Interface Name			Classification      	Comments
>     --------------------------- ------------------- ---------------------------
>    javax.rules
> 	* Handle			Uncommitted    		Interface
> 	* ObjectFilter			Uncommitted    		Interface
> 	* RuleExecutionSetMetadata	Uncommitted    		Interface
> 	* RuleRuntime			Uncommitted    		Interface
> 	* RuleSession			Uncommitted    		Interface
> 	* StatefulRuleSession		Uncommitted    		Interface
> 	* StatelessRuleSession		Uncommitted    		Interface
>
>    javax.rules.admin 
> 	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
> 	* Rule				Uncommitted    		Interface
> 	* RuleAdministrator		Uncommitted    		Interface
> 	* RuleExecutionSet		Uncommitted    		Interface
> 	* RuleExecutionSetProvider	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 (jsr94.zip_)
>
>   2. SMF manifests
>   3. links to contracts
> Introduction to Library Functions                        jsr94(3)
>
> NAME
>      jsr94 - Java Rule Engine API
>
> DESCRIPTION
>      jsr94(3)  Java runtime API for rule engines. For  additional
>      information  on  using jsr94, browse the complete html docu-
>      mentation at:
>
>           file:/usr/share/lib/java/javadoc/jsr94/index.html
>
> LICENSE
>      ASL 2.0
>
> FILES
>      /usr/share/lib/java/jsr94.jar
>
>           jsr94 jar file
>
>      /usr/share/lib/java/javadoc/jsr94/index.html
>
>           jsr94 API documentation generated with javadoc.
>
> ATTRIBUTES
>      See attributes(5) for descriptions of the  following  attri-
>      butes:
>
>      _______________________________________
>     |   ATTRIBUTE TYPE   |  ATTRIBUTE VALUE|
>     |_______________________________________
>     | Availability       |  SUNWjsr94      |
>     |_______________________________________
>     | Interface Stability|  Uncommitted    |
>     |____________________|_________________|
>
> SEE ALSO
>      http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html
>
> NOTES
>      Source for jsr94 is available on http://opensolaris.org
>
> SunOS 5.10           Last change: 4 Feb 2009                    1
>
>
>
>   

-- 
<http://www.sun.com> 	* Mark A. Carlson *
Sr. Architect

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



--Boundary_(ID_AiVmtyGWFWCqdupU++VH+w)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>This case, having received the requisite +1, is being marked closed
<br>
approved. <br>
<br>
-- mark</tt><br>
<br>
<br>
Mark Carlson wrote:
<blockquote cite="mid:200902111409.n1BE9ioU001512@sac.sfbay.sun.com"
 type="cite">
  <pre wrap="">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:
	 jsr94
    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

	Java runtime API for rule engines.

4. Technical Description:

	The interfaces and classes defined by the specification are in the javax.rules and javax.rules.admin packages. The javax.rules package contains classes and interfaces that are aimed at runtime clients of the rule engine. The runtime client API exposes methods to acquire a rule session for a registered rule execution set and interact with the rule session. The administrator API exposes methods to load an execution set from these external resources:URI, InputStream, XML Element, binary abstract syntax tree, or Reader. The administrator API also provides methods to register and unregister rule execution sets. Only registered rule execution sets are accessible through the runtime client API. A packaging separation between the runtime client API and the administrator API was made to reinforce the distinction between executing a rule execution set that has been previously loaded and registered into the runtime environment by an administrator, and the dynamic loading and execution!

  of external resources. The later actions can only be performed using the classes and interfaces in the javax.rules.admin package.

5. Interfaces 

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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
	jsr94 Ver 1.0.3

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
	Java runtime API for rule engines.

	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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/release-taxonomy/">http://opensolaris.org/os/community/arc/policies/release-taxonomy/</a>)
      [ ] 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
	Java Rule Engine API. Java Community Process.  (<a class="moz-txt-link-freetext" href="http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html">http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html</a>)	
	    
    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 &amp; Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/install-locations/">http://opensolaris.org/os/community/arc/policies/install-locations/</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2007/047/">http://opensolaris.org/os/community/arc/caselog/2007/047/</a> 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 <a class="moz-txt-link-freetext" href="http://sac.sfbay/WSARC/2002/494">http://sac.sfbay/WSARC/2002/494</a> for details)
      Does this project install software into a 
      &lt;system drive&gt;:\Program Files\Sun\&lt;product&gt; or &lt;system drive&gt;:\Sun\&lt;product&gt;
      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\&lt;product&gt;\&lt;version&gt;
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\&lt;product id&gt;\&lt;version id&gt;\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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/SMF-policy/">http://opensolaris.org/os/community/arc/policies/SMF-policy/</a>)
      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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/secure-by-default/">http://opensolaris.org/os/community/arc/policies/secure-by-default/</a> for details)
      (see <a class="moz-txt-link-freetext" href="http://www.opensolaris.org/os/community/arc/policies/NITS-policy/">http://www.opensolaris.org/os/community/arc/policies/NITS-policy/</a> for details)
      (see parts of <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/SMF-policy/">http://opensolaris.org/os/community/arc/policies/SMF-policy/</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/">http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/</a> and
	   <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/">http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/</a> and
	   <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/">http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/</a>
           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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/audit-policy/">http://opensolaris.org/os/community/arc/policies/audit-policy/</a> for details)
      (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2003/397">http://opensolaris.org/os/community/arc/caselog/2003/397</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2003/397">http://opensolaris.org/os/community/arc/caselog/2003/397</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/PAM/">http://opensolaris.org/os/community/arc/policies/PAM/</a>)
      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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/">http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/</a> and
           <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/passwords-files/">http://opensolaris.org/os/community/arc/bestpractices/passwords-files/</a> 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 <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/security-questions/">http://opensolaris.org/os/community/arc/bestpractices/security-questions/</a> 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 <a class="moz-txt-link-freetext" href="http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/">http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/</a> for details)
  4.1 Exported Interfaces
  
    Interface Name			Classification      	Comments
    --------------------------- ------------------- ---------------------------
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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 (jsr94.zip_)

  2. SMF manifests
  3. links to contracts
Introduction to Library Functions                        jsr94(3)

NAME
     jsr94 - Java Rule Engine API

DESCRIPTION
     jsr94(3)  Java runtime API for rule engines. For  additional
     information  on  using jsr94, browse the complete html docu-
     mentation at:

          <a class="moz-txt-link-freetext" href="file:/usr/share/lib/java/javadoc/jsr94/index.html">file:/usr/share/lib/java/javadoc/jsr94/index.html</a>

LICENSE
     ASL 2.0

FILES
     /usr/share/lib/java/jsr94.jar

          jsr94 jar file

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

          jsr94 API documentation generated with javadoc.

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

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

SEE ALSO
     <a class="moz-txt-link-freetext" href="http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html">http://jcp.org/aboutJava/communityprocess/first/jsr094/index.html</a>

NOTES
     Source for jsr94 is available on <a class="moz-txt-link-freetext" href="http://opensolaris.org">http://opensolaris.org</a>

SunOS 5.10           Last change: 4 Feb 2009                    1



  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title></title>
<table border="0" cellpadding="0" cellspacing="0" width="519">
  <tbody>
    <tr valign="top">
      <td height="121" width="98"><a moz-do-not-send="true"
 href="http://www.sun.com"><img moz-do-not-send="true"
 src="http://www.sun.com/emrkt/sigs/6h_top.gif" border="0" height="92"
 width="98"></a></td>
      <td style="font-family: Arial; font-size: 10px;" height="121"
 width="249"><b> Mark A. Carlson </b><br>
Sr. Architect<br>
      <br>
      <b>Systems Group</b><br>
Phone x69559 / 303-223-6139<br>
Email <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
 href="mailto:Mark.Carlson@Sun.COM">Mark.Carlson@Sun.COM</a><br>
      </td>
      <td style="font-family: Arial; font-size: 10px;" width="172"><img
 moz-do-not-send="true" src="http://www.sun.com/emrkt/sigs/q12.gif"
 height="118" width="172"></td>
    </tr>
  </tbody>
</table>
<div class="moz-signature"><br>
</div>
</div>
</body>
</html>

--Boundary_(ID_AiVmtyGWFWCqdupU++VH+w)--

From Vivek.Titarmare@sun.com Tue Feb 24 01:25:59 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 n1O9PwHP019342
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 24 Feb 2009 01:25:59 -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 n1O9PsHo003511
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 24 Feb 2009 17:25:58 +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 <0KFK00507CV8YV00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 01:25:56 -0800 (PST)
Received: from sineb-mail-2.sun.com ([192.18.19.7])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KFK00DNHCV66ND0@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 24 Feb 2009 01:25:55 -0800 (PST)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1O9Pssw006526	for
 <LSARC-ext@sun.com>; Tue, 24 Feb 2009 09:25:54 +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 <0KFK00400CKTM200@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 24 Feb 2009 17:25:54 +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 <0KFK006J3CV2PIF0@mail-apac.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 24 Feb 2009 17:25:53 +0800 (SGT)
Date: Tue, 24 Feb 2009 14:55:50 +0530
From: Vivek Titarmare <Vivek.Titarmare@sun.com>
Subject: RE: jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]
In-reply-to: <4995B798.2010109@Sun.COM>
Sender: Vivek.Titarmare@sun.com
To: Richard.Matthews@sun.com
Cc: LSARC-ext@sun.com
Message-id: <004201c99661$e34d2e10$a9e78a30$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/mixed; boundary="Boundary_(ID_V1xq1mxyKTFUs1suOcHYGw)"
Content-language: en-us
Thread-index: AcmOBm5nBpmF3OvvSWqaRq4TXfpPfAIWx5NQ
X-PMX-Version: 5.4.1.325704
References: <200902111409.n1BE9ioU001512@sac.sfbay.sun.com>
 <4995B798.2010109@Sun.COM>
Status: RO
Content-Length: 16439

This is a multipart message in MIME format.

--Boundary_(ID_V1xq1mxyKTFUs1suOcHYGw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi Rick,

I think I missed to updates of jsr94 (needed to add jsr94-tck) attached are
the same. pl. add the same to the required folder.

Thanks,
~Vivek R. Titarmare


-----Original Message-----
From: Richard.Matthews@Sun.COM [mailto:Richard.Matthews@Sun.COM] 
Sent: Friday, February 13, 2009 11:41 PM
Cc: LSARC-ext@sun.com
Subject: Re: jsr94 [LSARC/2009/087 FastTrack timeout 02/18/2009]

+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		
---------------------------------------------------------------------



--Boundary_(ID_V1xq1mxyKTFUs1suOcHYGw)
Content-type: text/plain; name=FastTrack_jsr94.txt
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: attachment; filename=FastTrack_jsr94.txt

Template Version: @(#)sac_nextcase %I% %G% SMI This information is Co=
pyright 2009 Sun Microsystems 1. Introduction
    1.1. Project/Component Working Name:

=09 jsr94
=09 *  jsr94
=09 * jsr94-tck

    1.2. Name of Document Author/Supplier:
=09 Author:  Vivek R. Titarmare
    1.3  Date of This Document:
=09 22 January, 2009

2. Project Summary
   2.1 Project Description

=09Java runtime API for rule engines.

4. Technical Description:

=09The interfaces and classes defined by the specification are in the=
 javax.rules and javax.rules.admin packages. The javax.rules package =
contains classes and interfaces that are aimed at runtime clients of =
the rule engine. The runtime client API exposes methods to acquire a =
rule session for a registered rule execution set and interact with th=
e rule session. The administrator API exposes methods to load an exec=
ution set from these external resources:URI, InputStream, XML Element=
, binary abstract syntax tree, or Reader. The administrator API also =
provides methods to register and unregister rule execution sets. Only=
 registered rule execution sets are accessible through the runtime cl=
ient API. A packaging separation between the runtime client API and t=
he administrator API was made to reinforce the distinction between ex=
ecuting a rule execution set that has been previously loaded and regi=
stered into the runtime environment by an administrator, and the dyna=
mic loading and execution of external resources. The later actions ca=
n only be performed using the classes and interfaces in the javax.rul=
es.admin package.

5. Interfaces=20

   Exported interface                   Classification =09=09Interfac=
e type
   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D =09=09=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   javax.rules
=09* Handle=09=09=09Uncommitted    =09=09Interface
=09* ObjectFilter=09=09=09Uncommitted    =09=09Interface
=09* RuleExecutionSetMetadata=09Uncommitted    =09=09Interface
=09* RuleRuntime=09=09=09Uncommitted    =09=09Interface
=09* RuleSession=09=09=09Uncommitted    =09=09Interface
=09* StatefulRuleSession=09=09Uncommitted    =09=09Interface
=09* StatelessRuleSession=09=09Uncommitted    =09=09Interface

   javax.rules.admin=20
=09* LocalRuleExecutionSetProvider=09Uncommitted    =09=09Interface
=09* Rule=09=09=09=09Uncommitted    =09=09Interface
=09* RuleAdministrator=09=09Uncommitted    =09=09Interface
=09* RuleExecutionSet=09=09Uncommitted    =09=09Interface
=09* RuleExecutionSetProvider=09Uncommitted    =09=09Interface
=09

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

   Imported interface        Classification   Comments
   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D   =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D   =3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
=09None


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

--Boundary_(ID_V1xq1mxyKTFUs1suOcHYGw)
Content-type: text/plain; name=FOSS_jsr94.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=FOSS_jsr94.txt

FCL--FOSS Check List

1.0 Project Information
1.1 Name of project/component
	
	jsr94
	* jsr94 Ver 1.0.3
	* jsr94-tck Ver 1.0.3

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
	Java runtime API for rule engines.

	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
	Java Rule Engine API. Java Community Process.  (http://jcp.org/aboutJava/communityprocess/final/jsr094/index.html)	
	    
    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 "jsr94-1.0.3.jar" contains following interface.

    Interface Name			Classification      	Comments
    --------------------------- ------------------- ---------------------------
   javax.rules
	* Handle			Uncommitted    		Interface
	* ObjectFilter			Uncommitted    		Interface
	* RuleExecutionSetMetadata	Uncommitted    		Interface
	* RuleRuntime			Uncommitted    		Interface
	* RuleSession			Uncommitted    		Interface
	* StatefulRuleSession		Uncommitted    		Interface
	* StatelessRuleSession		Uncommitted    		Interface

   javax.rules.admin 
	* LocalRuleExecutionSetProvider	Uncommitted    		Interface
	* Rule				Uncommitted    		Interface
	* RuleAdministrator		Uncommitted    		Interface
	* RuleExecutionSet		Uncommitted    		Interface
	* RuleExecutionSetProvider	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 (jsr94.zip_)

  2. SMF manifests
  3. links to contracts

--Boundary_(ID_V1xq1mxyKTFUs1suOcHYGw)--