Hi All,
Hope all is well.
Parts of our Cocoon 2 application use external information that needs
to be initialised at startup time.
Currently we have a separate servlet that is initialised at container
startup time (specified by the web.xml). Part of it's init sequence is
performs our initialisation routines.
I'm beginning to dislike this approach though, because this servlet
is no longer used for any requests (Cocoon 2 replaced it) - it's now
purely used for these initialisation methods.
One of my thoughts was to subclass CocoonServlet and place our init
routines in this class.
I'm wondering though, what does everyone else do ? Is this
subclassing frowned upon (if so, should those C2 classes be final?) ?
Does everyone have an extra init servlet ? or am I the only one with
this problem ?
It would be good if we had an 'official' way to do this, where (if
subclassing is not the way to go) we had some method to initialise
user named classes at Cocoon 2 startup time ?
What does everyone else think ?
Cheers,
Marcus
--
.....
,,$$$$$$$$$, Marcus Crafter
;$' '$$$$: Computer Systems Engineer
$: $$$$: Open Software Associates GmbH
$ o_)$$$: 82-84 Mainzer Landstrasse
;$, _/\ &&:' 60327 Frankfurt Germany
' /( &&&
\_&&&&' Email : [EMAIL PROTECTED]
&&&&. Business Hours : +49 69 9757 200
&&&&&&&: After Hours : +49 69 49086750
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
