geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dain Sundstrom <dsundst...@gluecode.com>
Subject Re: Defaulting client config ids
Date Thu, 30 Sep 2004 17:41:58 GMT
Quick clarification...

If parent is myApp.ear and the application.xml contains 
<java>a/b/c/d.jar</java>, do you want the clientConfigId to be 
myApp/a/b/c/d or myApp/d?

-dain

--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26

On Sep 30, 2004, at 9:51 AM, Jeremy Boynes wrote:

> Currently we have to have a deployment plan for an EAR in order to 
> specify the config id for generated app clients. This is a pain and I 
> would like to propose a defaulting solution.
>
> If we have a EAR file named "myApp.ear" then the configId for the ear 
> defaults to "myApp". We can use the hierarchical nature of URIs to 
> nest the client id inside this. So, for example, if the EAR contained 
> a client jar at path "myClient" the the configId used to run the 
> client could be defaulted to "myApp/myClient"
>
> For a standalone app client, then the config should just default to 
> the file name as for other objects. However, we also need a 
> server-side config to hold the admin objects - this canbe defaulted to 
> the configID + "/server" so for client "myClient.jar" the server-side 
> configId would be "myClient/server"
>
> --
> Jeremy


Mime
View raw message