It is very interesting...
jboss JRMP supports the notion of "proxy container" introduced in jboss 1.0
that is there to provide a distributed containers. I would need to see the
specific javabean that would hold the client data and lifecycle stuff to
make sure there is need for standardization
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Terry Child
> Sent: Monday, June 19, 2000 8:31 AM
> To: jboss
> Subject: [jBoss-User] Client side modules?
>
>
> Hi All,
>
> Does anyone know of a Java Technology/API which allows parts of a client
> application to be deployed
> independently in a similar fashion to EJB jars containing server
> side beans?
> The client 'container' would
> supply life-cycle services for the client side modules i.e. setContext() -
> which would pass the module
> information such as its JNDI server location , load(),unload() etc. Each
> module would be pluggable
> into various clients without the need for recompilation. There
> could be xml
> files associated with each
> client side module, just like EJBs, which the container could use
> for things
> such as inserting entries into menus.
> Each module could sit in its own JAR on the client.
>
> I know JavaBeans has some of this sort of functionality but it
> doesn't seem
> to define any higher level protocols
> which a container application could use to hot deploy client side
> functionality.
>
> Any suggestions/ideas?
>
> Regards
>
> Terry Child
>
>
>
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
