On Wed, 2 Oct 2002 23:46, Daniel Krieg wrote:
> First of all I would like to thankyou for your input. I am currently
> working on a specific project and can easily "HACK" together a solution
> that might not necessarily be the best design for standard use. If I am
> able to create something that will benefit many others in the process, I
> would much rather adjust my strategies.
So would we ;)
> Wrong. Phoenix will control the lifecyle of Catalina and all WARs within
> it. I am simply offering a work interface that allows other SARs the
> capability to deploy/undeploy WARs specific to that SAR...at least that is
> the current interface ( posted a message to the Avalon-Phoenix Developers
> List earlier today discussing this). WARs should be able to access the
> work interface for other SARs within Phoenix and utiltize their
> capabilities.
If you replace SAR with Block then I agree ;)
> More people use Servlets than use Phoenix and is therefore a recognized
> standard. I can create a WAR that depends on other J2EE standard
> components, such as TransactionManagers, etc. configure the application
> server (Phoenix) to map its resources instances (SARs) into the JNDI
> namespace that the WAR searches, to supply that WAR with appropriate
> component implementations. Many application servers offer additional
> "proprietary" funcationality. This is my goal with Phoenix. Create the
> ability to map Phoenix resources into the JNDI ENC of deployed WARs.
woohoo!
--
Cheers,
Peter Donald
----------------------------------------
"Liberty means responsibility. That is
why most men dread it." - Locke
----------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
