From markcarl@sac.sfbay.sun.com Wed Feb 11 17:07:47 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 n1C17kxr024674 for ; Wed, 11 Feb 2009 17:07:47 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1C17hs9029086; Thu, 12 Feb 2009 01:07:45 GMT Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KEX00J05HSWP700@nwk-avmta-1.sfbay.Sun.COM>; Wed, 11 Feb 2009 17:07:44 -0800 (PST) Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KEX004QPHSW31A0@nwk-avmta-1.sfbay.Sun.COM>; Wed, 11 Feb 2009 17:07:44 -0800 (PST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n1C17hcg049104; Wed, 11 Feb 2009 17:07:43 -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 n1C17g83024663; Wed, 11 Feb 2009 17:07:42 -0800 (PST) Received: (from markcarl@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n1C17gFZ024661; Wed, 11 Feb 2009 17:07:42 -0800 (PST) Date: Wed, 11 Feb 2009 17:07:42 -0800 (PST) From: Mark Carlson Subject: mvel [LSARC/2009/096 FastTrack timeout 02/18/2009] To: LSARC-ext@sun.com Cc: Drools_Team@sun.com Message-id: <200902120107.n1C17gFZ024661@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 17565 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: mvel 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 MVEL is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts. 4. Technical Description: MVEL has several specific components * An Integrated Lexer-Parser, including Subparsers. * An Execute-on-the-fly Interpreter * An Intermediate Compiler * An Interface for a JIT Accelerating Compiler o A Reflection-Based Implementation of the JIT: The FRET (Fast Reflection Evaluation Tree) Compiler o A Bytecode-Based Implementation: Known just as "The JIT". * Type Conversion API / System * External Resolver API 5. Interfaces Exported interface Classification Interface type ============================= ============== ============== org.mvel * Accessor Uncommitted Interface * AccessorNode Uncommitted Interface * ASTIterator Uncommitted Interface * ConversionHandler Uncommitted Interface * DataTypes Uncommitted Interface * ExecutableStatement Uncommitted Interface * Macro Uncommitted Interface * NodeType Uncommitted Interface * Operator Uncommitted Interface * PreProcessor Uncommitted Interface * TemplateRegistry Uncommitted Interface org.mvel.asm * AnnotationVisitor Uncommitted Interface * ClassVisitor Uncommitted Interface * FieldVisitor Uncommitted Interface * MethodVisitor Uncommitted Interface * Opcodes Uncommitted Interface org.mvel.ast * Assignment Uncommitted Interface * NestedStatement Uncommitted Interface org.mvel.conversion * Converter Uncommitted Interface org.mvel.debug * Debugger Uncommitted Interface org.mvel.integration * Interceptor Uncommitted Interface * VariableResolver Uncommitted Interface * VariableResolverFactory Uncommitted Interface org.mvel.integration.impl * LocalVariableResolverFactory Uncommitted Interface * TypeInjectionResolverFactory Uncommitted Interface org.mvel.math * MathProcessor Uncommitted Interface org.mvel.optimizers * AccessorOptimizer Uncommitted Interface * OptimizerHook Uncommitted Interface org.mvel.util * Stack 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 mvel Ver 1.2.22-java1.5.0 1.2 Author of document Vivek R. Titarmare 2.0 Project Summary 2.1 Project Description MVEL is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts. This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). Interface stabilities and contracts will be added to the consuming case(s) as needed. 2.2 Release binding What is is the release binding? (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) [ ] Major [X] Minor [ ] Patch or Micro [ ] Unknown -- ARC review required 2.3 Type of project Is this case a Linux Familiarity project? [X] Yes [ ] No 2.4 Originating Community 2.4.1 Community Name The Codehaus Mvel (http://codehaus.org/, http://dist.codehaus.org/) 2.4.2 Community Involvement Indicate Sun's involvement in the community [ ] Maintainer [ ] Contributor [X] Monitoring Will the project team work with the upstream community to resolve architectural issues of interest to Sun? [X] Yes [ ] No - briefly explain Will we or are we forking from the community? [ ] Yes - ARC review required prior to forking [X] No 3.0 Technical Description 3.1 Installation & Sharable 3.1.1S Solaris Installation - section only required for Solaris Software (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) Does this project follow the Install Locations best practice? [X] Yes [ ] No - ARC review required Does this project install into /usr under [sbin|bin|lib|include|man|share]? [X] Yes [ ] No or N/A Does this project install into /opt? [ ] Yes - explain below [X] No or N/A Does this project install into a different directory structure? [ ] Yes - ARC review required [X] No or N/A Do any of the components of this project conflict with anything under /usr? (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) [ ] Yes - explain below [X] No If conflicts exist then will this project install under /usr/gnu? [ ] Yes [ ] No - ARC review required [X] N/A Is this project installing into /usr/sfw? [ ] Yes - ARC review required [X] No 3.1.1W Windows Installation - section only required for Windows Software (see http://sac.sfbay/WSARC/2002/494 for details) Does this project install software into a :\Program Files\Sun\ or :\Sun\ directory? [ ] Yes [ ] No - ARC review required Does the project use the Windows registry? [ ] Yes [ ] No - ARC review required Does the project use HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ for the registry key? [ ] Yes [ ] No - ARC review required Is the project's stored location HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? [ ] Yes [ ] No - ARC review required 3.1.2 Share and Sharable Does the module include any components that are used or shared by other projects? [X] Yes [ ] No If yes are these components packaged to be shared with the other FOSS? [X] Yes [ ] No - ARC review required [ ] N/A Are these components already in the Solaris WOS? [ ] Yes [X] No - continue with next section (section 3.2) If yes are these newer versions being delivered? [ ] Yes [ ] No - ARC review required If yes are the newer versions replacing the existing versions? [ ] Yes [ ] No - ARC review required 3.2 Exported Libraries Are libraries being delivered by this project? [X] Yes [ ] No - continue with next section (section 3.3) Are 64-bit versions of the libraries being delivered? [X] Yes [ ] No - ARC review required Are static versions of the libraries being delivered? [ ] Yes - ARC review required [X] No 3.3 Services and the /etc Directory (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) Does the project integrate anything into /etc/init.d or /etc/rc?.d? [ ] Yes - ARC review required [X] No Does the project integrate any new entries into /etc/inittab or /etc/inetd.conf? [ ] Yes - ARC review required [X] No Does the project integrate any private non-public files into /etc/default or /etc/ configuration files? [ ] Yes - ARC review required [X] No Does the service manifests method context grant rights above that of the noaccess user and basic privilege set? [ ] Yes - ARC review required [X] No 3.4 Security 3.4.1 Secure By Default (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for addtional details) Are there any network services provided by this project? [ ] Yes [X] No - continue with the next section (section 3.4.2) Are network services enabled by default? [ ] Yes - ARC review required [ ] No [X] N/A Are network services automatically enabled by the project during installation? [ ] Yes - ARC review required [ ] No [X] N/A Are inbound network communications denied by default? [ ] Yes [ ] No - ARC review required [X] N/A Is inbound data checked to prevent content-based attacks? [ ] Yes [ ] No - ARC review required [X] N/A Is the outbound receiver authenticated? [ ] Yes [ ] No - ARC review required [X] N/A Is the receiver authenticated prior to receiving any sensitive outbound communication? [ ] Yes [ ] No - ARC review required [X] N/A 3.4.2 Authorization (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ for details) Are there any setuid/setgid privileged binaries in the project? [ ] Yes - ARC review required [X] No - continue with next section (section 3.4.3) If yes then are the setuid/setgid privileges handled by the use of roles? [ ] Yes [ ] No - ARC review required 3.4.3 Auditing (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Does this component contain administrative or security enforcing software? [ ] Yes - ARC review required [X] No - continue to next section (section 3.4.4) (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) Do the components create audit logs detailing what took place including what event took place, who was involved, when the event took place? [ ] Yes - ARC contract and Audit project team review required [ ] No - ARC review required 3.4.4 Authentication (see http://opensolaris.org/os/community/arc/policies/PAM/) Do the components contain any authentication code? [ ] Yes [X] No - continue to next section (section 3.4.5) If yes do the components use PAM (plugable authentication modules) for authentication? [ ] Yes [ ] No - ARC review required If yes is a single PAM session maintained during authentication? [ ] Yes [ ] No - ARC review required If yes are the components sufficiently privileged to allow the requested operations (authentication, password change, process credential manipulation, audit state initialization)? [ ] Yes - briefly describe below [ ] No - ARC review required 3.4.5 Passwords (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) Do any of the components for the project deal with passwords? [ ] Yes [X] No - continue to next section (section 3.4.6) If yes are these passwords entered via the CLI or environment? [ ] Yes - ARC review required [ ] No Are passwords stored within the file system for the component? [ ] Yes [ ] No - continue to next section (section 3.4.6) If yes are the permissions on the file such to protect exposing the password(s)? [ ] Yes [ ] No - ARC review required 3.4.6 General Security Questions (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) Are there any network protocols used by this project? [ ] Yes [X] No - continue with the next section (section 3.5) Do the components use standard network protocols? [ ] Yes [ ] No - ARC review required Do network services for the project make decisions based upon user, host or service identities? [ ] Yes - explain below [ ] No [ ] N/A Do the components make use of secret information during authentication and/or authorization? [ ] Yes - explain below [ ] No [ ] N/A 3.5 Networking Do the components access the network? [ ] Yes [X] No - continue with the next section (section 3.6) If yes do the components support IPv6? [ ] Yes [ ] No - ARC review required 3.6 Core Solaris Components Do the components of this project compete with or duplicate core Solaris components? [ ] Yes - ARC review required [X] No 4.0 Interfaces (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) 4.1 Exported Interfaces The jar file "mvel_1.2.22.jar" contains following interface. Interface Name Classification Comments --------------------------- ------------------- --------------------------- org.mvel * Accessor Uncommitted Interface * AccessorNode Uncommitted Interface * ASTIterator Uncommitted Interface * ConversionHandler Uncommitted Interface * DataTypes Uncommitted Interface * ExecutableStatement Uncommitted Interface * Macro Uncommitted Interface * NodeType Uncommitted Interface * Operator Uncommitted Interface * PreProcessor Uncommitted Interface * TemplateRegistry Uncommitted Interface org.mvel.asm * AnnotationVisitor Uncommitted Interface * ClassVisitor Uncommitted Interface * FieldVisitor Uncommitted Interface * MethodVisitor Uncommitted Interface * Opcodes Uncommitted Interface org.mvel.ast * Assignment Uncommitted Interface * NestedStatement Uncommitted Interface org.mvel.conversion * Converter Uncommitted Interface org.mvel.debug * Debugger Uncommitted Interface org.mvel.integration * Interceptor Uncommitted Interface * VariableResolver Uncommitted Interface * VariableResolverFactory Uncommitted Interface org.mvel.integration.impl * LocalVariableResolverFactory Uncommitted Interface * TypeInjectionResolverFactory Uncommitted Interface org.mvel.math * MathProcessor Uncommitted Interface org.mvel.optimizers * AccessorOptimizer Uncommitted Interface * OptimizerHook Uncommitted Interface org.mvel.util * Stack 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 (mvel.zip_) 2. SMF manifests 3. links to contracts Introduction to Library Functions mvel(3) NAME mvel - Java-based Expression Language DESCRIPTION mvel(3) is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts.For additional information on using mvel, browse the complete html documentation at: file:/usr/share/lib/java/javadoc/mvel/index.html LICENSE ASL 2.0 FILES /usr/share/lib/java/mvel-1.2.22.jar mvel jar file /usr/share/lib/java/javadoc/mvel/index.html mvel API documentation generated with javadoc. ATTRIBUTES See attributes(5) for descriptions of the following attri- butes: _______________________________________ | ATTRIBUTE TYPE | ATTRIBUTE VALUE| |_______________________________________ | Availability | SUNWmvel | |_______________________________________ | Interface Stability| Uncommitted | |____________________|_________________| SEE ALSO http://mvel.codehaus.org/ NOTES Source for mvel is available on http://opensolaris.org SunOS 5.10 Last change: 4 Feb 2009 1 From Richard.Matthews@sun.com Fri Feb 13 10:13:22 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 n1DIDMT4026143 for ; Fri, 13 Feb 2009 10:13:22 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n1DIDLcG008452 for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 13 Feb 2009 10:13:22 -0800 (PST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KF00050PNY9R900@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 10:13:21 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KF000GH2NY8GD80@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 10:13:20 -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 n1DIDKVf011022 for ; Fri, 13 Feb 2009 18:13:20 +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 <0KF000500NLV1300@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 11:13:20 -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 <0KF000CYXNXYARA0@mail-amer.sun.com> for LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Fri, 13 Feb 2009 11:13:11 -0700 (MST) Date: Fri, 13 Feb 2009 12:13:09 -0600 From: Rick Matthews Subject: Re: mvel [LSARC/2009/096 FastTrack timeout 02/18/2009] In-reply-to: <200902120107.n1C17gFZ024661@sac.sfbay.sun.com> Sender: Richard.Matthews@sun.com Cc: LSARC-ext@sun.com Reply-to: Richard.Matthews@sun.com Message-id: <4995B835.5080806@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: <200902120107.n1C17gFZ024661@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:40:37 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 n1JCebvF008550 for ; Thu, 19 Feb 2009 04:40:37 -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 n1JCeapu011424; Thu, 19 Feb 2009 04:40:37 -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 <0KFB00M05CJO5M00@nwk-avmta-2.sfbay.sun.com>; Thu, 19 Feb 2009 04:40:36 -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 <0KFB008CPCJNTTC0@nwk-avmta-2.sfbay.sun.com>; Thu, 19 Feb 2009 04:40:35 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1JCeYcI023210; Thu, 19 Feb 2009 12:40:35 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 23 2008)) id <0KFB00700C979W00@mail-amer.sun.com>; Thu, 19 Feb 2009 05:40:34 -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 <0KFB004EDCJM8420@mail-amer.sun.com>; Thu, 19 Feb 2009 05:40:34 -0700 (MST) Date: Thu, 19 Feb 2009 05:40:34 -0700 From: "Mark A. Carlson" Subject: Re: mvel [LSARC/2009/096 FastTrack timeout 02/18/2009] In-reply-to: <200902120107.n1C17gFZ024661@sac.sfbay.sun.com> Sender: Mark.Carlson@sun.com To: LSARC-ext@sun.com Cc: Drools_Team@sun.com Message-id: <499D5342.4080002@sun.com> MIME-version: 1.0 Content-type: multipart/alternative; boundary="Boundary_(ID_Ru3UHPHZAkcSWQRzbLBE5w)" X-PMX-Version: 5.4.1.325704 References: <200902120107.n1C17gFZ024661@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) Status: RO Content-Length: 40622 This is a multi-part message in MIME format. --Boundary_(ID_Ru3UHPHZAkcSWQRzbLBE5w) 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: > mvel > 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 > > MVEL is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts. > > 4. Technical Description: > > MVEL has several specific components > > * An Integrated Lexer-Parser, including Subparsers. > * An Execute-on-the-fly Interpreter > * An Intermediate Compiler > * An Interface for a JIT Accelerating Compiler > o A Reflection-Based Implementation of the JIT: The FRET > (Fast Reflection Evaluation Tree) Compiler > o A Bytecode-Based Implementation: Known just as "The JIT". > * Type Conversion API / System > * External Resolver API > > > 5. Interfaces > > Exported interface Classification Interface type > ============================= ============== ============== > org.mvel > * Accessor Uncommitted Interface > * AccessorNode Uncommitted Interface > * ASTIterator Uncommitted Interface > * ConversionHandler Uncommitted Interface > * DataTypes Uncommitted Interface > * ExecutableStatement Uncommitted Interface > * Macro Uncommitted Interface > * NodeType Uncommitted Interface > * Operator Uncommitted Interface > * PreProcessor Uncommitted Interface > * TemplateRegistry Uncommitted Interface > > org.mvel.asm > * AnnotationVisitor Uncommitted Interface > * ClassVisitor Uncommitted Interface > * FieldVisitor Uncommitted Interface > * MethodVisitor Uncommitted Interface > * Opcodes Uncommitted Interface > > org.mvel.ast > * Assignment Uncommitted Interface > * NestedStatement Uncommitted Interface > > org.mvel.conversion > * Converter Uncommitted Interface > > org.mvel.debug > * Debugger Uncommitted Interface > > org.mvel.integration > * Interceptor Uncommitted Interface > * VariableResolver Uncommitted Interface > * VariableResolverFactory Uncommitted Interface > > org.mvel.integration.impl > * LocalVariableResolverFactory Uncommitted Interface > * TypeInjectionResolverFactory Uncommitted Interface > > org.mvel.math > * MathProcessor Uncommitted Interface > > org.mvel.optimizers > * AccessorOptimizer Uncommitted Interface > * OptimizerHook Uncommitted Interface > > org.mvel.util > * Stack 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 > mvel Ver 1.2.22-java1.5.0 > > 1.2 Author of document > Vivek R. Titarmare > > 2.0 Project Summary > 2.1 Project Description > MVEL is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts. > > This case is a dependency for LSARC 2008/748 - Drools. Drools is a dependency for PSARC 2007/210 Automatic Data Migration (ADM). > Interface stabilities and contracts will be added to the consuming case(s) as needed. > > 2.2 Release binding > What is is the release binding? > (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/) > [ ] Major > [X] Minor > [ ] Patch or Micro > [ ] Unknown -- ARC review required > > 2.3 Type of project > Is this case a Linux Familiarity project? > [X] Yes > [ ] No > > 2.4 Originating Community > 2.4.1 Community Name > The Codehaus Mvel (http://codehaus.org/, http://dist.codehaus.org/) > > 2.4.2 Community Involvement > Indicate Sun's involvement in the community > [ ] Maintainer > [ ] Contributor > [X] Monitoring > > Will the project team work with the upstream community to resolve > architectural issues of interest to Sun? > [X] Yes > [ ] No - briefly explain > > > Will we or are we forking from the community? > [ ] Yes - ARC review required prior to forking > [X] No > > 3.0 Technical Description > 3.1 Installation & Sharable > 3.1.1S Solaris Installation - section only required for Solaris Software > (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details) > Does this project follow the Install Locations best practice? > [X] Yes > [ ] No - ARC review required > > Does this project install into /usr under [sbin|bin|lib|include|man|share]? > [X] Yes > [ ] No or N/A > > Does this project install into /opt? > [ ] Yes - explain below > [X] No or N/A > > Does this project install into a different directory structure? > [ ] Yes - ARC review required > [X] No or N/A > > Do any of the components of this project conflict with anything under /usr? > (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details) > [ ] Yes - explain below > [X] No > > If conflicts exist then will this project install under /usr/gnu? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is this project installing into /usr/sfw? > [ ] Yes - ARC review required > [X] No > > 3.1.1W Windows Installation - section only required for Windows Software > (see http://sac.sfbay/WSARC/2002/494 for details) > Does this project install software into a > :\Program Files\Sun\ or :\Sun\ > directory? > [ ] Yes > [ ] No - ARC review required > > Does the project use the Windows registry? > [ ] Yes > [ ] No - ARC review required > > Does the project use > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\ > for the registry key? > [ ] Yes > [ ] No - ARC review required > > Is the project's stored location > HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\\\Path? > [ ] Yes > [ ] No - ARC review required > > 3.1.2 Share and Sharable > Does the module include any components that are used or shared by > other projects? > [X] Yes > [ ] No > > If yes are these components packaged to be shared with the other FOSS? > [X] Yes > [ ] No - ARC review required > [ ] N/A > > Are these components already in the Solaris WOS? > [ ] Yes > [X] No - continue with next section (section 3.2) > > If yes are these newer versions being delivered? > [ ] Yes > [ ] No - ARC review required > > If yes are the newer versions replacing the existing versions? > [ ] Yes > [ ] No - ARC review required > > 3.2 Exported Libraries > Are libraries being delivered by this project? > [X] Yes > [ ] No - continue with next section (section 3.3) > > Are 64-bit versions of the libraries being delivered? > [X] Yes > [ ] No - ARC review required > > Are static versions of the libraries being delivered? > [ ] Yes - ARC review required > [X] No > > 3.3 Services and the /etc Directory > (see http://opensolaris.org/os/community/arc/policies/SMF-policy/) > Does the project integrate anything into /etc/init.d or /etc/rc?.d? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any new entries into /etc/inittab or > /etc/inetd.conf? > [ ] Yes - ARC review required > [X] No > > Does the project integrate any private non-public files into /etc/default > or /etc/ configuration files? > [ ] Yes - ARC review required > [X] No > > Does the service manifests method context grant rights above that > of the noaccess user and basic privilege set? > [ ] Yes - ARC review required > [X] No > > 3.4 Security > 3.4.1 Secure By Default > (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details) > (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details) > (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for > addtional details) > Are there any network services provided by this project? > [ ] Yes > [X] No - continue with the next section (section 3.4.2) > > Are network services enabled by default? > [ ] Yes - ARC review required > [ ] No > [X] N/A > > Are network services automatically enabled by the project during installation? > [ ] Yes - ARC review required > [ ] No > [X] N/A > > Are inbound network communications denied by default? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is inbound data checked to prevent content-based attacks? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is the outbound receiver authenticated? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > Is the receiver authenticated prior to receiving any sensitive outbound communication? > [ ] Yes > [ ] No - ARC review required > [X] N/A > > 3.4.2 Authorization > (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and > http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ > for details) > Are there any setuid/setgid privileged binaries in the project? > [ ] Yes - ARC review required > [X] No - continue with next section (section 3.4.3) > > If yes then are the setuid/setgid privileges handled by the use of roles? > [ ] Yes > [ ] No - ARC review required > > 3.4.3 Auditing > (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details) > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Does this component contain administrative or security enforcing software? > [ ] Yes - ARC review required > [X] No - continue to next section (section 3.4.4) > > (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details) > Do the components create audit logs detailing what took place including what event > took place, who was involved, when the event took place? > [ ] Yes - ARC contract and Audit project team review required > [ ] No - ARC review required > > > 3.4.4 Authentication > (see http://opensolaris.org/os/community/arc/policies/PAM/) > Do the components contain any authentication code? > [ ] Yes > [X] No - continue to next section (section 3.4.5) > > If yes do the components use PAM (plugable authentication modules) for authentication? > [ ] Yes > [ ] No - ARC review required > > If yes is a single PAM session maintained during authentication? > [ ] Yes > [ ] No - ARC review required > > If yes are the components sufficiently privileged to allow the requested > operations (authentication, password change, process credential manipulation, > audit state initialization)? > [ ] Yes - briefly describe below > [ ] No - ARC review required > > 3.4.5 Passwords > (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and > http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details) > Do any of the components for the project deal with passwords? > [ ] Yes > [X] No - continue to next section (section 3.4.6) > > If yes are these passwords entered via the CLI or environment? > [ ] Yes - ARC review required > [ ] No > > Are passwords stored within the file system for the component? > [ ] Yes > [ ] No - continue to next section (section 3.4.6) > > If yes are the permissions on the file such to protect exposing the password(s)? > [ ] Yes > [ ] No - ARC review required > > 3.4.6 General Security Questions > (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details) > Are there any network protocols used by this project? > [ ] Yes > [X] No - continue with the next section (section 3.5) > > Do the components use standard network protocols? > [ ] Yes > [ ] No - ARC review required > > Do network services for the project make decisions based upon user, host or > service identities? > [ ] Yes - explain below > [ ] No > [ ] N/A > > Do the components make use of secret information during authentication and/or > authorization? > [ ] Yes - explain below > [ ] No > [ ] N/A > > 3.5 Networking > Do the components access the network? > [ ] Yes > [X] No - continue with the next section (section 3.6) > > If yes do the components support IPv6? > [ ] Yes > [ ] No - ARC review required > > 3.6 Core Solaris Components > Do the components of this project compete with or duplicate core > Solaris components? > [ ] Yes - ARC review required > [X] No > > 4.0 Interfaces > (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details) > 4.1 Exported Interfaces > > The jar file "mvel_1.2.22.jar" contains following interface. > > Interface Name Classification Comments > --------------------------- ------------------- --------------------------- > org.mvel > * Accessor Uncommitted Interface > * AccessorNode Uncommitted Interface > * ASTIterator Uncommitted Interface > * ConversionHandler Uncommitted Interface > * DataTypes Uncommitted Interface > * ExecutableStatement Uncommitted Interface > * Macro Uncommitted Interface > * NodeType Uncommitted Interface > * Operator Uncommitted Interface > * PreProcessor Uncommitted Interface > * TemplateRegistry Uncommitted Interface > > org.mvel.asm > * AnnotationVisitor Uncommitted Interface > * ClassVisitor Uncommitted Interface > * FieldVisitor Uncommitted Interface > * MethodVisitor Uncommitted Interface > * Opcodes Uncommitted Interface > > org.mvel.ast > * Assignment Uncommitted Interface > * NestedStatement Uncommitted Interface > > org.mvel.conversion > * Converter Uncommitted Interface > > org.mvel.debug > * Debugger Uncommitted Interface > > org.mvel.integration > * Interceptor Uncommitted Interface > * VariableResolver Uncommitted Interface > * VariableResolverFactory Uncommitted Interface > > org.mvel.integration.impl > * LocalVariableResolverFactory Uncommitted Interface > * TypeInjectionResolverFactory Uncommitted Interface > > org.mvel.math > * MathProcessor Uncommitted Interface > > org.mvel.optimizers > * AccessorOptimizer Uncommitted Interface > * OptimizerHook Uncommitted Interface > > org.mvel.util > * Stack 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 (mvel.zip_) > > 2. SMF manifests > 3. links to contracts > > Introduction to Library Functions mvel(3) > > NAME > mvel - Java-based Expression Language > > DESCRIPTION > mvel(3) is a powerful expression language for Java-based > applications. It provides a plethora of features and is > suited for everything from the smallest property binding and > extraction, to full blown scripts.For additional information > on using mvel, browse the complete html documentation at: > > file:/usr/share/lib/java/javadoc/mvel/index.html > > LICENSE > ASL 2.0 > > FILES > /usr/share/lib/java/mvel-1.2.22.jar > > mvel jar file > > /usr/share/lib/java/javadoc/mvel/index.html > > mvel API documentation generated with javadoc. > > ATTRIBUTES > See attributes(5) for descriptions of the following attri- > butes: > > _______________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE| > |_______________________________________ > | Availability | SUNWmvel | > |_______________________________________ > | Interface Stability| Uncommitted | > |____________________|_________________| > > SEE ALSO > http://mvel.codehaus.org/ > > NOTES > Source for mvel is available on http://opensolaris.org > > SunOS 5.10 Last change: 4 Feb 2009 1 > -- * Mark A. Carlson * Sr. Architect *Systems Group* Phone x69559 / 303-223-6139 Email Mark.Carlson@Sun.COM --Boundary_(ID_Ru3UHPHZAkcSWQRzbLBE5w) Content-type: text/html; 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:
	 mvel
    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

	MVEL is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts.

4. Technical Description:

	MVEL has several specific components

	    * An Integrated Lexer-Parser, including Subparsers.
	    * An Execute-on-the-fly Interpreter
	    * An Intermediate Compiler
	    * An Interface for a JIT Accelerating Compiler
	          o A Reflection-Based Implementation of the JIT: The FRET
		    (Fast Reflection Evaluation Tree) Compiler
	          o A Bytecode-Based Implementation: Known just as "The JIT".
	    * Type Conversion API / System
	    * External Resolver API
 

5. Interfaces 

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
   org.mvel
	* Accessor			Uncommitted    		Interface
	* AccessorNode			Uncommitted    		Interface
	* ASTIterator			Uncommitted    		Interface
	* ConversionHandler		Uncommitted    		Interface
	* DataTypes			Uncommitted    		Interface
	* ExecutableStatement		Uncommitted    		Interface
	* Macro				Uncommitted    		Interface
	* NodeType			Uncommitted    		Interface
	* Operator			Uncommitted    		Interface
	* PreProcessor			Uncommitted    		Interface
	* TemplateRegistry		Uncommitted    		Interface

   org.mvel.asm
	* AnnotationVisitor		Uncommitted    		Interface
	* ClassVisitor			Uncommitted    		Interface
	* FieldVisitor			Uncommitted    		Interface
	* MethodVisitor			Uncommitted    		Interface
	* Opcodes			Uncommitted    		Interface

   org.mvel.ast
	* Assignment			Uncommitted    		Interface
	* NestedStatement		Uncommitted    		Interface

   org.mvel.conversion
	* Converter			Uncommitted    		Interface

   org.mvel.debug
	* Debugger			Uncommitted    		Interface

   org.mvel.integration
	* Interceptor			Uncommitted    		Interface
	* VariableResolver		Uncommitted    		Interface
	* VariableResolverFactory	Uncommitted    		Interface

   org.mvel.integration.impl
	* LocalVariableResolverFactory	Uncommitted    		Interface
	* TypeInjectionResolverFactory	Uncommitted    		Interface

   org.mvel.math
	* MathProcessor			Uncommitted    		Interface

   org.mvel.optimizers
	* AccessorOptimizer		Uncommitted    		Interface
	* OptimizerHook			Uncommitted    		Interface

   org.mvel.util 
	* Stack 			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
	mvel Ver 1.2.22-java1.5.0

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description
	MVEL is a powerful expression language for Java-based applications. It provides a plethora of features and is suited for everything from the smallest property binding and extraction, to full blown scripts.

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

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

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

  2.4 Originating Community
    2.4.1 Community Name
	  The Codehaus Mvel (http://codehaus.org/,  http://dist.codehaus.org/)
    
    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 "mvel_1.2.22.jar" contains following interface.

    Interface Name			Classification      	Comments
    --------------------------- ------------------- ---------------------------
   org.mvel
	* Accessor			Uncommitted    		Interface
	* AccessorNode			Uncommitted    		Interface
	* ASTIterator			Uncommitted    		Interface
	* ConversionHandler		Uncommitted    		Interface
	* DataTypes			Uncommitted    		Interface
	* ExecutableStatement		Uncommitted    		Interface
	* Macro				Uncommitted    		Interface
	* NodeType			Uncommitted    		Interface
	* Operator			Uncommitted    		Interface
	* PreProcessor			Uncommitted    		Interface
	* TemplateRegistry		Uncommitted    		Interface

   org.mvel.asm
	* AnnotationVisitor		Uncommitted    		Interface
	* ClassVisitor			Uncommitted    		Interface
	* FieldVisitor			Uncommitted    		Interface
	* MethodVisitor			Uncommitted    		Interface
	* Opcodes			Uncommitted    		Interface

   org.mvel.ast
	* Assignment			Uncommitted    		Interface
	* NestedStatement		Uncommitted    		Interface

   org.mvel.conversion
	* Converter			Uncommitted    		Interface

   org.mvel.debug
	* Debugger			Uncommitted    		Interface

   org.mvel.integration
	* Interceptor			Uncommitted    		Interface
	* VariableResolver		Uncommitted    		Interface
	* VariableResolverFactory	Uncommitted    		Interface

   org.mvel.integration.impl
	* LocalVariableResolverFactory	Uncommitted    		Interface
	* TypeInjectionResolverFactory	Uncommitted    		Interface

   org.mvel.math
	* MathProcessor			Uncommitted    		Interface

   org.mvel.optimizers
	* AccessorOptimizer		Uncommitted    		Interface
	* OptimizerHook			Uncommitted    		Interface

   org.mvel.util 
	* Stack 			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 (mvel.zip_)

  2. SMF manifests
  3. links to contracts

Introduction to Library Functions                         mvel(3)

NAME
     mvel - Java-based Expression Language

DESCRIPTION
     mvel(3)  is a powerful expression  language  for  Java-based
     applications.  It  provides  a  plethora  of features and is
     suited for everything from the smallest property binding and
     extraction, to full blown scripts.For additional information
     on using mvel, browse the complete html documentation at:

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

LICENSE
     ASL 2.0

FILES
     /usr/share/lib/java/mvel-1.2.22.jar

          mvel jar file

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

          mvel API documentation generated with javadoc.

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

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

SEE ALSO
     http://mvel.codehaus.org/

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

SunOS 5.10           Last change: 4 Feb 2009                    1

--
Mark A. Carlson
Sr. Architect

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

--Boundary_(ID_Ru3UHPHZAkcSWQRzbLBE5w)--