Hi Charles,

You can fine the Javadocs for drools at

/workarea/yoda_export/Calsoft-ws3/usr/src/lib/drools/drools-4.0.7/dist/javad
oc

location on yoda-ks.central.sun.com setup.

Let me know if this works for you.

Best Regards,
~Vivek R. Titarmare

-----Original Message-----
From: Charles.Binford at Sun.COM [mailto:charles.binf...@sun.com] 
Sent: Monday, May 11, 2009 9:53 PM
To: Margot Miller; Vivek Titarmare
Cc: Mark A. Carlson; LSARC-ext at Sun.COM; 'Gregory Matthews'; Rick Matthews
Subject: Re: Drools [LSARC/2008/748 FastTrack timeout 05/05/2009]

Margot, answers inline.

*Vivek,* can you please send a zip file of the drools java docs to Rick
and/or Mark to put into the case directory?  Thanks.

Margot Miller wrote:
> Charles,
>
> Please specify the install directory for the jar files, as well as
> the commitment level.
The jar files are installed into /usr/share/lib/java
The commitment level is "uncommitted".
>
> Are there any java docs delivered with this project; didn't see
> any in the case directory.
Yes.  We'll get those delivered.
>
> What API's are in this:
>
>        drools-ant-4.7.jar jar file
To the best of my knowledge, there are no external interfaces.  This jar
file appears to be an internal to drools support library.
>
> Dependency on SUNWant?
>
> The below conflicts:
>
>      Does the module include any components that are used or shared by
>      other projects?
>      [ ] Yes
>      [x] No
>         If yes are these components packaged to be shared with the
> other FOSS?
>      [x] Yes
>      [ ] No - ARC review required
>      [ ] N/A
Rick, any suggestions on which way to resolve this?
>
> Thanks
> Margot
>
>
> Mark A. Carlson wrote:
>> I have started a timer on this familiarity case. It has had a
>> pre-inception and update reviews.
>> All dependent cases for this umbrella have been approved. I am
>> sponsoring for Charles Binford.
>> Minor binding is requested and it times out 05/05/2009. The materials
>> are in the fasttrack.materials
>> subdirectory of the case directory.
>>
>> -- mark
>> ------------------------------------------------------------------------
>>
>>
>> 1.0 Project Information
>> 1.1 Name of project/component
>>     Drools - LSARC 2008/748
>>
>> 1.2 Author of document
>>     Charles Binford
>>
>> 2.0 Project Summary
>>   2.1 Project Description
>> Drools is an open-source rules engine being proposed for use in
>> Open Solaris.  It is consumed by the community and by ADM
>> (PSARC/2007/210).
>>         There are a significant number of dependencies which have
>> been integrated
>>         already to Open Solaris in order to support Drools.  This
>> case and its
>>         dependencies are being provided for familiarity to developers,
>>         currently using various Linux distributions, moving to
>> OpenSolaris.
>>         An informational LSARC case was presented as LSARC 2008/748.
>>
>>         A complete listing of dependencies, LSARC cases, OSRs, etc.
>> is attached for
>>         reference.
>>     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 - JBOSS DROOLS - jboss.org/drools
>>         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 - /usr/share
>>       [ ] 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
>>       [ ] 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?
>>       [ ] Yes
>>       [x] 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
>>       [ ] N/A
>>             Are network services automatically enabled by the project
>> during installation?
>>       [ ] Yes - ARC review required
>>       [ ] No
>>       [ ] N/A
>>             Are inbound network communications denied by default?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [ ] N/A
>>             Is inbound data checked to prevent content-based attacks?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [ ] N/A
>>             Is the outbound receiver authenticated?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [ ] N/A
>>             Is the receiver authenticated prior to receiving any
>> sensitive outbound communication?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [ ] 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             Examples of Core Solaris Components include
>> but are not limited to:
>>               Secure By Default
>>         Authorizations
>>         PAM -- Plugable Authentication Module
>>         Privilege
>>         PRM -- Process Rights Management -- Privilege
>>         Audit
>>         xVm -- Virtualization
>>         zones / Solaris Containers
>>         PRM -- Process Rights Management
>>         RBAC -- Role Based Access Control
>>         TX / Trusted Extensions
>>         ZFS
>>         SMF -- Service Management Facility
>>         FMA -- Fault Management Architecture
>>         SCF -- Smart Card Facility
>>         IPsec
>>         4.0 Interfaces
>>   (see
>> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/
>> for details)
>>   4.1 Exported Interfaces
>>
>> Interface Name Classification       Comments
>> --------------------------- -------------------
>> ---------------------------
>> SUNWdrools Package
>>
>> drools-analytics-4.7.jar jar file
>>    * AnalyticsData Uncommitted interface
>>    * AnalysisResult Uncommitted interface
>>    * Cause Uncommitted interface
>>    * RangeCheckCause Uncommitted interface
>>    * Possibility Uncommitted interface
>>
>> drools-ant-4.7.jar jar file
>>
>> drools-compiler-4.7.jar jar file
>>    * CategorySelectHandler Uncommitted interface
>>    * CompletionItemsAsync Uncommitted interface
>>    * Dialect Uncommitted interface
>>    * DialectConfiguration Uncommitted interface
>>    * AgendaGroupFactory Uncommitted interface
>>    * WorkingMemoryAction Uncommitted interface
>>    * Expander Uncommitted interface
>>    * ExpanderResolver Uncommitted interface
>>    * PackageDescrDumper Uncommitted interface
>>    * PatternDestinationDescr Uncommitted interface
>>    * DSLMapping Uncommitted interface
>>    * FactHandleMemory Uncommitted interface
>>    * ObjectSink Uncommitted interface
>>    * ReteooComponentBuilder Uncommitted interface
>>
>> drools-core-4.7.jar jar file
>>    * Agenda Uncommitted interface
>>    * FactHandle Uncommitted interface
>>    * InitialFact Uncommitted interface
>>    * ObjectFilter Uncommitted interface
>>    * RuleBase Uncommitted interface
>>    * RuleBaseEventManager Uncommitted interface
>>    * StatefulSession Uncommitted interface
>>    * StatelessSession Uncommitted interface
>>    * StatelessSessionResult Uncommitted interface
>>    * Visitor Uncommitted interface
>>    * WorkingMemory Uncommitted interface
>>    * WorkMemoryEventmanager Uncommitted interface
>>    * AgentEventListener Uncommitted interface
>>    * FileLoader Uncommitted interface
>>    * IHttpClient Uncommitted interface
>>    * DroolsClassLoader Uncommitted interface
>>    * RuleFlowProcess Uncommitted interface
>>    * AgendaEventListener Uncommitted interface
>>    * RuleBaseEventListener Uncommitted interface
>>    * RuleFlowEventListener Uncommitted interface
>>    * WorkingMemoryEventListener
>> Uncommitted interface
>>
>> drools-decision-tables-4.7.jar jar file
>>    * DRLJavaEmitter Uncommitted interface
>>    * Cell Uncommitted interface
>>    * Column Uncommitted interface
>>    * DecisionTableParser Uncommitted interface
>>    * Generator Uncommitted interface
>>    * RuleSheetListener Uncommitted interface
>>    * SheetListener Uncommitted interface
>>    * SourceBuilder Uncommitted interface
>>    * TemplateContainer Uncommitted interface
>>    * TemplateRuleBase Uncommitted interface
>>
>> drools-jsr-4.7.jar jar file
>>
>>       4.2 Imported Interfaces
>>
>> Interface Name              Classification      Comments
>> --------------------------- -------------------
>> ---------------------------
>> antlr runtime               Uncommitted         LSARC 2009/075
>> janino                      Uncommitted         LSARC 2009/047
>> jd core                     Uncommitted         LSARC 2009/095
>> jexcelapi                   Uncommitted         LSARC 2009/131
>> junit                       Uncommitted         LSARC 2008/633
>> mvel                        Uncommitted         LSARC 2009/096
>> xstream                     Uncommitted         LSARC 2009/135
>>  
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc at opensolaris.org
>>   
>


Reply via email to