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

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

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? 

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


On Thu, 2004-09-30 at 17:52, Dain Sundstrom wrote:
> On Sep 30, 2004, at 2:32 PM, karan singh malhi wrote:
> 
> > I am not sure if the questions below are fully relevant.
> >
> > Could you expand on this? Does this mean that if a packed application
> > needs to use an ejb from the .ear, then we would configure that in the
> > geronimo dd?
> 
> Either the geronimo dd or the spec dd.  It is sometimes either a pain 
> or not allowed to modify a spec dd inside of an ear.
> 
> >  What if the packed application itself had the same ejb-link
> > value as you would enter in the geronimo dd?
> 
> The ejb-link in the geronimo dd would override an ejb-link declared in 
> the spec dd.
> 
> -dain
> 

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

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

[Dain Sundstrom <ds...@gluecode.com>]

On Sep 30, 2004, at 3:28 PM, 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?

No. Since the introduction of JSR88 then vendor dd can be external to 
the module being deployed.  If you are going to open the ear to modify 
something, editing the ejb-links would be easier.

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

If the module fails to deploy, which would happen in the case of an 
unresolved ejb-ref, there would be nothing to manage on the server.

-dain