The URL to the HK2 mailing lists is:
https://hk2.dev.java.net/servlets/ProjectMailingListList
Ignore the "no mailing lists" in the front page of the HK2 page. That's
because the pages are Maven-generated and there is a (temporary) bug in
the setting...
- eduard/o
Jerome Dochez wrote:
>
> On May 11, 2007, at 6:37 AM, Eduardo Pelegri-Llopart wrote:
>
>> Hi Stefan.
>>
>> > Is this also the place to ask questions about V3 and HK2?
>>
>> Jerome, Kohsuke and I were just discussing this yesterday.
>>
>> Our inclination was to start a new DEV @ HK2 for discussions specific
>> to the HK2 modular system, while keeping the V3 discussions here. The
>> argument for a separate forum was that there will be other
>> applications of HK2, and a spearate forum would encourage them.
>> Similar to the case of Grizzly. Either approach has its own PRO and
>> CONs, so we can fine-tune.
>
> I will add the hk2_at_dev today, however like Eduardo mentioned, keep the
> V3 discussions here.
>
>>
>> > I am very interested in in deploying non-web stuff in Glassfish. For
>> > example Spring applications, network servers, etc. Is that one of the
>> > goals of V3 too?
>>
>> YES!
>>
>> > I get the impression that the container, deployer and
>> > sniffer objects are all very web centric at the moment. For example
>> > Sniffer.getURLPattern.
>>
>> We will have to wait for Mr Jerome to surface after J1...
>
> resurface was the right word...
>
> so the short answer is no, I am not trying to make it web centric yet I
> realize that most folks are using the web platform. Anyhow, the long
> answer is that there are some applications container which are both
> handling an application type and serving particular url types. Take for
> example Phobos, you have phobos applications which are packaged in a jar
> file like a web app for instance but the phobos engine is also capable
> of serving isolated .ejs files. So v3 really need to start the phobos
> engine when someone is deploying a phobos application OR if someone is
> accessing a .ejs in the docroot of the web server.
>
> For the containers that do not have a web front end, they really should
> return null from getURLPattern(). I think that I could split the
> interfaces in 2 but I felt that it was a bit of an overkill at this
> point. For now, I will make this situation (and the optional nature of
> getURLPattern) more explicit in the javadocs and if the community feel
> that we should have 2 interfaces, they should speak up.
>
> Thanks for trying V3, let me know if I can be of further help.
>
> Jerome
>
>>
>> - eduard/o
>>
>>
>> Stefan Arentz wrote:
>>> On May 11, 2007, at 9:27 AM, Shreedhar Ganapathy wrote:
>>>> Yup. You're the at right place :)
>>> My first question is a simple one .. I looked at the current V3 code
>>> and the previews. I get the impression that the container, deployer
>>> and sniffer objects are all very web centric at the moment. For
>>> example Sniffer.getURLPattern.
>>> I am very interested in in deploying non-web stuff in Glassfish. For
>>> example Spring applications, network servers, etc. Is that one of the
>>> goals of V3 too?
>>> (I know it is all work in progress :-)
>>> S.
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>