Hi,

Just in case you were not aware there is a project at eas.betaversion.org
that has Blocks for OpenEJB server, Tomcat and possibly more in the future.
It may be useful to use their implementations of Blocks (like TomcatBlock)
etc.

At 02:21  30/3/01 +0200, Stephen McConnell wrote:
>Just for reference, we intent to include the James and Tomcat blocks
>(enabling the introduction of email and web gateways to the OSM platform).
>Getting symcronization between Avalon/Phoenix/James/Tomcat is to say the
>least a painful experience. One of the principal "pains" in this process
>is the lack of support in Avalon for lifecycle components "install",
>"upgrade", "degrade" and "uninstall".  For example, when a new version
>of James is released, and the new version contains an updated assembly.xml
>file - its a pain because I have to go though and figure out what needs
>to be changed in my "James block that I'm declaring to my customers" -
>actually this is a complaint - centralised handling of configurations
>in Avalon/Phoenix doesn't work when attempting to build and deploy real
>applications with cross-vendor-block dependencies.  Its just too painful.
>I would prefer to see a clear and distinct install phase in which different
>blocks publish default configuration profiles ... during this phase, and
>block should be able to validate an exiting profile (preferably marked with
>a version identifier) and incorporate existing information into a new
>configurations. On the Tomcat block front - we have encountered lots of
>problems - inconstancies between CVS content on the apache site and build
>files (i.e. build files include targets to create an avalon block but
>the source code does not exist under the CVS) and a few horror stories when
>attempting to build the Tomcat block (which is not to say that we have
>given up on the Tomcat block - its just that its we are at the point of
>deciding if we do this ourselves or wait).

agreed 100%
I am actually trying to work on this at the moment but are having some
problems finding a good design. I was trying to use JNDI and allow
configurations to be sucked down from LDAP ... but I am having a few issues ;)

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to