avalon-phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: Phoenix and the Web
Date Thu, 03 Oct 2002 23:09:36 GMT

OK, you need to make the blocks available to your client webapps.

I think you'll have problems with classloaders.  I say this because you 
hope to get one block to register inserf in JNDI, and a WAR file app to 
pull the think from JNDI and cast it to an interface.  I suggest that 
you'll get a classcast exception because of the multiple classloaders 

You might find it best to use Cornerstone's publisher or autopublisher 
to publish a block via AltRMI.  In the servlet webapp use AltRMI's 
client to lookup the implementation.  Currently this will happen over 
sockets, getting round the classloader/classcast issue, but in time I 
will go back to AltRMI and allow an optimized lookup (a la WebLogic).


- Paul

>This discussion about SARs and Blocks has been very informative to me.  What
>I am writing for my client is a single application (SAR) with multiple
>Blocks which utilize the service of other Blocks...that is very clear to me
>now.  I need to make the other Blocks available to Webapps and plan to do so
>via JNDI.  The strategy I took in implementing CatalinaSevak was to try to
>replicate a standard installation of Catalina so that anyone familiar with
>Catalina administration would be able to maintain CatalinSevak.  Is this
>strategy acceptable in the long run with respect to Phoenix or should this
>SAR have a separate configuration/administration semantics?
>To unsubscribe, e-mail:   <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:avalon-phoenix-dev-help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:avalon-phoenix-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-phoenix-dev-help@jakarta.apache.org>

View raw message