Re: [jira] Created: (GERONIMO-339) Add support for an ejb-link in geronimo deployment descriptors

[Jeremy Boynes <jb...@gluecode.com>]

karan singh malhi wrote:
> Thanks for the reply.
> 
> Since we would be adding a geronimo dd to the ear file, that means we
> would be updating the .ear anyways, so why not modify the ejb-link in
> the spec dd itself. If we are not allowed to modify the spec dd, then
> should we be allowed to modify the ear file. If not, then how are we
> going to add the geronimo dd to the ear? 
> 

We support deployment with external plans so you would not need to add 
it into the ear file itself (this fits the JSR88 model).

> I may be totally wrong here ,but shouldnt we be able to update the spec
> dd by updating properties through a management interface?
> 

You can generate the plan using the Configuration side of JSR88. 
However, this writes out an external plan rather than modifying the 
original file.

The reason for all this is to allow the same, possibly signed, EAR to be 
deployed to multiple servers (possibly ones from different vendors). 
However, if you want to put the plans inside the archive, that is 
supported as well.

--
Jeremy

Re: [jira] Created: (GERONIMO-339) Add support for an ejb-link in geronimo deployment descriptors

[karan singh malhi <ka...@verizon.net>]

Thanks Jeremy

On Thu, 2004-09-30 at 18:33, Jeremy Boynes wrote:
> karan singh malhi wrote:
> > Thanks for the reply.
> > 
> > Since we would be adding a geronimo dd to the ear file, that means we
> > would be updating the .ear anyways, so why not modify the ejb-link in
> > the spec dd itself. If we are not allowed to modify the spec dd, then
> > should we be allowed to modify the ear file. If not, then how are we
> > going to add the geronimo dd to the ear? 
> > 
> 
> We support deployment with external plans so you would not need to add 
> it into the ear file itself (this fits the JSR88 model).
> 
> > I may be totally wrong here ,but shouldnt we be able to update the spec
> > dd by updating properties through a management interface?
> > 
> 
> You can generate the plan using the Configuration side of JSR88. 
> However, this writes out an external plan rather than modifying the 
> original file.
> 
> The reason for all this is to allow the same, possibly signed, EAR to be 
> deployed to multiple servers (possibly ones from different vendors). 
> However, if you want to put the plans inside the archive, that is 
> supported as well.
> 
> --
> Jeremy