geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: Remove server-environment from app client
Date Mon, 07 Aug 2006 06:30:27 GMT

On Aug 6, 2006, at 12:13 PM, Aaron Mulder wrote:

> On 8/6/06, David Jencks <david_jencks@yahoo.com> wrote:
>> How do we install the required yet idiotic jsr-77 gbean that
>> represents the app client without a module to put it in?
>
> So as far as I can tell, it doesn't matter at runtime if the JSR-77
> GBean module and the app client module had the same module ID, since
> they'll always run in different VMs.  However, it is an issue in
> practice because we can't put the config.ser in the same place for
> both, and we need one config.ser containing all the client stuff and a
> different config.ser containing the JSR-77 GBean.
>
> I'd suggest in the EAR-with-app-client case, we put the app client
> JSR-77 GBean in the EAR configuration, just to indicate that the EAR
> contains an app client with such-and-such a name.  (You still can't
> use it via JMX to start the client in the server VM.)
>
> I'd suggest in the standalone-app-client case, we skip the JSR-77 app
> client GBean, since the app client may not be present at all in the
> server installation of Geronimo (again, it may be installed only in a
> client distribution of Geronimo).  I don't think there's any
> requirement that the application client container supports a JSR-77
> interface.
>

correct, but I'm pretty sure we still need the server side jsr-77  
gbean for the app client even for standalone app clients where as you  
point out it makes particularly little sense.  Please check the spec  
before you get too much farther.

thanks
david jencks
> Thanks,
>     Aaron


Mime
View raw message