Return-Path: Delivered-To: apmail-jakarta-avalon-cvs-archive@apache.org Received: (qmail 17471 invoked from network); 12 Nov 2002 13:30:00 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 12 Nov 2002 13:30:00 -0000 Received: (qmail 11416 invoked by uid 97); 12 Nov 2002 13:30:57 -0000 Delivered-To: qmlist-jakarta-archive-avalon-cvs@jakarta.apache.org Received: (qmail 11368 invoked by uid 97); 12 Nov 2002 13:30:56 -0000 Mailing-List: contact avalon-cvs-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Avalon CVS List" Reply-To: "Avalon Developers List" Delivered-To: mailing list avalon-cvs@jakarta.apache.org Received: (qmail 11357 invoked by uid 97); 12 Nov 2002 13:30:55 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: 12 Nov 2002 13:29:48 -0000 Message-ID: <20021112132948.93713.qmail@icarus.apache.org> From: donaldp@apache.org To: jakarta-avalon-excalibur-cvs@apache.org Subject: cvs commit: jakarta-avalon-excalibur/info/src/xdocs attributes.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N donaldp 2002/11/12 05:29:48 Modified: info/src/xdocs attributes.xml Log: Add some lifecycle hoohaa Revision Changes Path 1.2 +83 -0 jakarta-avalon-excalibur/info/src/xdocs/attributes.xml Index: attributes.xml =================================================================== RCS file: /home/cvs/jakarta-avalon-excalibur/info/src/xdocs/attributes.xml,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- attributes.xml 12 Nov 2002 07:07:49 -0000 1.1 +++ attributes.xml 12 Nov 2002 13:29:48 -0000 1.2 @@ -150,6 +150,89 @@ ]]> + + + + + + + + + + + + + + + + + + +

Target	Component,Service
Allow Multiple	false
Inherit	true
Description	The "lifecycle" attribute is used to define + the "lifecycle" of a particular component. The lifecycle + is defined by a number of parameters. The most important + of which is the scope in which a component can be, the scope + in which it is visible and the activation policy. +

+ +

Parameters:

+ + + + + + + + + + + + + + + + + + + + + + + + + +

Name	Default	Required	Description
scope	application	false	This defines the scope with in which the the component is + capable of being used. The valid scopes include "application", + "thread", "access" and "transaction". "application" scope means + that each lookup will return the same component. "thread" scope + means that each access in the same thread will return the same + component (usually it also means that the component can only be used + in that thread). "access" scope means that each access will return a + new instance. "transaction" scope means that each access in the + same transaction will return the same component. The notion of + "transaction" is container specific and requires some context to + be shared between the client and the container.
public	false	false	This parameter specifies whether the component + is visible outside this particular partition.
activation	startup	false	This parameter specifies the activation policy of + component. Possible values include "startup" which + indicates that the component is created at startup and + remains till the application ends. "jit" which means the + component is created the first time it is needed. + The "on-demand" policy indicates that the component is + created when it is needed and that it may be passivated + if it is no longer needed. The exact scheduling of "on-demand" + is container specific.

+ +

The following is an example of a component declaring + that it is scoped per access and which can be exported + to other partitions.

+ + + + + + ]]> + -- To unsubscribe, e-mail: For additional commands, e-mail: