[prev in list] [next in list] [prev in thread] [next in thread] 

List:       tapestry-user
Subject:    RE: Best place to initialize central services
From:       "Howard M. Lewis Ship" <hlship () attbi ! com>
Date:       2003-03-24 18:37:49
[Download RAW message or body]

Application extensions are another good idea.  they are much like helper
beans, in that you give them a name and a class and can set their
parameters.

App extensions may be hooks used by Tapestry, but are also there for
app-specific usage.

<extension> tag, within <application>

--
Howard M. Lewis Ship
Creator, Tapestry: Java Web Components
http://jakarta.apache.org/proposals/tapestry



> -----Original Message-----
> From: F.R. Da Costa Gomez [mailto:dcg@fixed.com] 
> Sent: Tuesday, March 18, 2003 6:49 AM
> To: Tapestry users
> Subject: Best place to initialize central services
> 
> 
> Hi all,
>  
> Is the folowing assumption correct?
> The engine is the best place to initialize things like 
> database, service 
> and other pooled 'managers'. These are basically services supplied to 
> users of the system that have nothing to do with the UI. 
> Basically I want to use a multi-threaded dbMgr (connection 
> pool) to do 
> my db-stuff with. Q is however what is the best place to init 
> this Mgr.
> 
> Thx,
> 
> Fermin DCG
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
> 


[prev in list] [next in list] [prev in thread] [next in thread]