Geronimo XDoclet (geronimo-jetty tags)

["L. Yeung" <l_...@yahoo.com>]

I'm looking at geronimo-jetty specs and I'm planning
to implement it in coming days. The things that I'm
wondering are as follows:

a. One thing that I can think of currently is that the
tag should start with @geronimo.web instead of
@geronimo.jetty. What if Geronimo starts to support
tomcat, should the it also support a tag of
@geronimo.tomcat? Are there any plans to support
different specs for different web containers? Maybe
one universal geronimo web tags should implement
jetty, geronimo and other future web containers.

b. Are the tags made as class level sufficient enough.
I honestly don't have much experience with web
deployment descriptors.

-len


		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 

RE:Geronimo XDoclet2 plugin

["L. Yeung" <l_...@yahoo.com>]

Jacek,

I'm in Asia, GMT+8. I'm still uncertain if I will be
available since I have to spend some of my time for my
day-job projects. I'll try to be there on Dec 27 2am
(GMT+8)
I'll try to spare some if I could on Dec 27, 11pm
(GMT+8).

-len

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Geronimo XDoclet (geronimo-jetty tags)

[David Jencks <dj...@gluecode.com>]

On Dec 25, 2004, at 11:46 AM, L. Yeung wrote:

>>> b. Are the tags made as class level sufficient
>> enough.
>>> I honestly don't have much experience with web
>>> deployment descriptors.
>>
>> At the moment, I don't see how to usefully use
>> xdoclet to construct a
>> geronimo web plan, since all the information in the
>> plan is at the web
>> application level rather than the servlet level,
>> which the class level
>> tags would correspond to.  Since none of the
>> information is specific to
>> a particular servlet, I don't think any information
>> should be provided
>> by a particular class.  Am I missing something?
>> Constructing the
>> standard web.xml deployment descriptor could be
>> useful, but this does
>> not rely on anything having to do with geronimo.
>>
>
> (I dont know if I get this question right). I mean
> class level tags for geronimo-jetty.xml, such as
> security access, resource references and etc (???)

Those are the principal things that need to be resolved, but they apply 
across the entire web application rather than per servlet, so I 
question how appropriate it is to include the information needed to 
resolve them in a particular (servlet) source file.  For ejbs, the jndi 
references are per ejb instance rather than per ejb application/module, 
but the security role-mapping still applies across the entire module.

IIRC xdoclet suffers from a similar problem even for the spec 
deployment descriptors, in that a particular class may appear many 
times in a descriptor with a different environment each time, whereas 
xdoclet only provides the means to include it once, with a single 
environment specified in the source file.  I have no idea how to solve 
this problem or even if it has already been solved in xdoclet 2.

many thanks,
david jencks

>
> Thanks.
>
> -len
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>

Re: Geronimo XDoclet (geronimo-jetty tags)

["L. Yeung" <l_...@yahoo.com>]

> > b. Are the tags made as class level sufficient
> enough.
> > I honestly don't have much experience with web
> > deployment descriptors.
> 
> At the moment, I don't see how to usefully use
> xdoclet to construct a 
> geronimo web plan, since all the information in the
> plan is at the web 
> application level rather than the servlet level,
> which the class level 
> tags would correspond to.  Since none of the
> information is specific to 
> a particular servlet, I don't think any information
> should be provided 
> by a particular class.  Am I missing something? 
> Constructing the 
> standard web.xml deployment descriptor could be
> useful, but this does 
> not rely on anything having to do with geronimo.
> 

(I dont know if I get this question right). I mean
class level tags for geronimo-jetty.xml, such as
security access, resource references and etc (???)

Thanks.

-len


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: Geronimo XDoclet (geronimo-jetty tags)

[David Jencks <dj...@gluecode.com>]

On Dec 25, 2004, at 9:38 AM, L. Yeung wrote:

> I'm looking at geronimo-jetty specs and I'm planning
> to implement it in coming days. The things that I'm
> wondering are as follows:
>
> a. One thing that I can think of currently is that the
> tag should start with @geronimo.web instead of
> @geronimo.jetty. What if Geronimo starts to support
> tomcat, should the it also support a tag of
> @geronimo.tomcat? Are there any plans to support
> different specs for different web containers? Maybe
> one universal geronimo web tags should implement
> jetty, geronimo and other future web containers.

I agree.  We are thinking of changing the default plan name to 
geronimo-web.xml since we hope that jetty and tomcat can use exactly 
the same plan.
>
> b. Are the tags made as class level sufficient enough.
> I honestly don't have much experience with web
> deployment descriptors.

At the moment, I don't see how to usefully use xdoclet to construct a 
geronimo web plan, since all the information in the plan is at the web 
application level rather than the servlet level, which the class level 
tags would correspond to.  Since none of the information is specific to 
a particular servlet, I don't think any information should be provided 
by a particular class.  Am I missing something?  Constructing the 
standard web.xml deployment descriptor could be useful, but this does 
not rely on anything having to do with geronimo.

many thanks,
david jencks

>
> -len
>
>
> 		
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
>