geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Delos <dait...@gmail.com>
Subject Re: RFC 66 and Geronimo
Date Thu, 29 Oct 2009 06:20:04 GMT
I'm just curious about the RFC 66 implementation in Geronimo. Is there any
resources we can learn just like the new framework in trunk?

Thanks!

2009/10/8 Lin Sun <linsun.unc@gmail.com>

> Ok, I was under the impression that you need to modify the bundle
> before the bundle is started/starting, thus I was suggesting the url
> handler to do so.
>
> Lin
>
>
> On Thu, Oct 8, 2009 at 10:17 AM, Rick McGuire <rickmcg@gmail.com> wrote:
> > I'm not trying to implement a new way for Geronimo to convert a WAB
> bundle
> > into Geronimo artifacts
> > that require pre-install conversion.  I'm working on an RFC 66 extender
> that
> > recognizes that a WAB
> > bundle has been started and deploys this to the Geronimo hosted container
> > implementing the behavior
> > specified in RFC 66.  This means that the only additional metadata in the
> > bundle is the manifest header that
> > specifies the context path.  At this point, it is not possible to do a
> > conversion on the bundle, it's too late for that.
> > The deployment needs to be made using the information that available in
> the
> > bundle already without requiring any
> > side metadata such as an external Geronimo deployment descriptor.  This
> > essentially requires much of the same
> > decision making as is used for JEE WAR installs, but needs to be done
> using
> > runtime resources rather than by
> > converting this into a static configuration.
> >
> > Rick
> >>
> >> Lin
> >>
> >>
> >
> >
>



-- 
Best Regards,

Delos

Mime
View raw message