You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Igor Lobanov <cr...@mail.ru> on 2003/08/09 22:11:39 UTC
Virtual hosting and different components
Hi, fellow geronimos,
New idea concerning "Virtual Hosting" feature under discussion.
If different applications can be deployed in separate "operational
spaces", we also cound specify in their deployment configuration wich
of implementations of base service to use. For example, naming
service. It could be full-blown LDAP backed component or simply
lightning fast in-memory file-based implementation. Does it make
sense?
Igor
Re: RES: Virtual hosting and different components
Posted by Craig Wohlfeil <cr...@darklighter.com>.
I don't think that there is anything wrong with having a
platform-specific descriptor where the spec allows. You can still deploy
the same EAR file on multiple platforms. For instance I am doing this
now with WebLogic and WebSphere. WebLogic pays attention to
weblogic-ejb-jar.xml and WebSphere pays attention to ibm-yadayada.xmi.
It doesn't matter that both files exist.
Denes wrote:
> I don't like the idea of a proprietary config file inside ear, as in
> jboss.xml. You can say that I still believe in the myth of one ear being
> deployed in every application server :)
RES: Virtual hosting and different components
Posted by Denes <de...@ppgia.pucpr.br>.
I agree with you on that.
But what I don't like in JBOSS is that the application developer should
know how to configure JBOSS. In WebSphere, I can deploy my ear with no
proprietary file to the WebSphere administrator and he is the guy
responsible for all configurations (including CMP mapping). He wouldn't
like (the ones I known at least doesn't) to open the archive to put a
configuration file inside it, as he can do this same job easily with the
admin console (which leads to the user interface thread that is already
being discussed.)
Please note that it's only a though, I wouldn't stand for it.
Denes
> -----Mensagem original-----
> De: Test Account [mailto:cmiller900@earthlink.net]
> Enviada em: domingo, 10 de agosto de 2003 11:15
> Para: geronimo-dev@incubator.apache.org
> Assunto: Re: Virtual hosting and different components
>
> Denes,
>
> I deploy an application onto many application servers using one
ear
> file
> which contains many proprietary xml config files. Each application
server
> only looks for its own proprietary set and ignores the rest. This
makes
> it
> very easy to deploy an atomic unit ( the ear ) while still tuning each
> proprietary app server.
>
> Hope this helps,
>
> Craig
>
> ----- Original Message -----
> From: "Denes" <de...@ppgia.pucpr.br>
> To: <ge...@incubator.apache.org>; "'Igor Lobanov'"
> <ge...@incubator.apache.org>
> Sent: Saturday, August 09, 2003 9:18 PM
> Subject: RES: Virtual hosting and different components
>
>
> Makes really sense to me, although I´d rather prefer a config dir or
> something like that to configure the base services for all
"operational
> spaces", because the idea of multiple ears in the same "operational
> space" that was discussed earlier.
>
> I don't like the idea of a proprietary config file inside ear, as in
> jboss.xml. You can say that I still believe in the myth of one ear
being
> deployed in every application server :)
>
> Just a tough...
>
> Denes
>
>
> > -----Mensagem original-----
> > De: Igor Lobanov [mailto:cryozot@mail.ru]
> > Enviada em: sábado, 9 de agosto de 2003 17:12
> > Para: Geronimo-Dev
> > Assunto: Virtual hosting and different components
> >
> > Hi, fellow geronimos,
> >
> > New idea concerning "Virtual Hosting" feature under discussion.
> > If different applications can be deployed in separate "operational
> > spaces", we also cound specify in their deployment configuration
wich
> > of implementations of base service to use. For example, naming
> > service. It could be full-blown LDAP backed component or simply
> > lightning fast in-memory file-based implementation. Does it make
> > sense?
> >
> > Igor
Re: Virtual hosting and different components
Posted by Test Account <cm...@earthlink.net>.
Denes,
I deploy an application onto many application servers using one ear file
which contains many proprietary xml config files. Each application server
only looks for its own proprietary set and ignores the rest. This makes it
very easy to deploy an atomic unit ( the ear ) while still tuning each
proprietary app server.
Hope this helps,
Craig
----- Original Message -----
From: "Denes" <de...@ppgia.pucpr.br>
To: <ge...@incubator.apache.org>; "'Igor Lobanov'"
<ge...@incubator.apache.org>
Sent: Saturday, August 09, 2003 9:18 PM
Subject: RES: Virtual hosting and different components
Makes really sense to me, although I´d rather prefer a config dir or
something like that to configure the base services for all "operational
spaces", because the idea of multiple ears in the same "operational
space" that was discussed earlier.
I don't like the idea of a proprietary config file inside ear, as in
jboss.xml. You can say that I still believe in the myth of one ear being
deployed in every application server :)
Just a tough...
Denes
> -----Mensagem original-----
> De: Igor Lobanov [mailto:cryozot@mail.ru]
> Enviada em: sábado, 9 de agosto de 2003 17:12
> Para: Geronimo-Dev
> Assunto: Virtual hosting and different components
>
> Hi, fellow geronimos,
>
> New idea concerning "Virtual Hosting" feature under discussion.
> If different applications can be deployed in separate "operational
> spaces", we also cound specify in their deployment configuration wich
> of implementations of base service to use. For example, naming
> service. It could be full-blown LDAP backed component or simply
> lightning fast in-memory file-based implementation. Does it make
> sense?
>
> Igor
RES: Virtual hosting and different components
Posted by Denes <de...@ppgia.pucpr.br>.
Makes really sense to me, although I´d rather prefer a config dir or
something like that to configure the base services for all "operational
spaces", because the idea of multiple ears in the same "operational
space" that was discussed earlier.
I don't like the idea of a proprietary config file inside ear, as in
jboss.xml. You can say that I still believe in the myth of one ear being
deployed in every application server :)
Just a tough...
Denes
> -----Mensagem original-----
> De: Igor Lobanov [mailto:cryozot@mail.ru]
> Enviada em: sábado, 9 de agosto de 2003 17:12
> Para: Geronimo-Dev
> Assunto: Virtual hosting and different components
>
> Hi, fellow geronimos,
>
> New idea concerning "Virtual Hosting" feature under discussion.
> If different applications can be deployed in separate "operational
> spaces", we also cound specify in their deployment configuration wich
> of implementations of base service to use. For example, naming
> service. It could be full-blown LDAP backed component or simply
> lightning fast in-memory file-based implementation. Does it make
> sense?
>
> Igor