Excellent! Keep up the good work pal.

A suggestion:

<XDtConfig:ifConfigParamEquals paramName="useIds" value="true">
id="<XDtId:prefixId prefix="Servlet"/>"</XDtConfig:ifConfigParamEquals>

is not good. Change it to:

<XDtId:prefixId prefix="Servlet"/>

And handle udeIds check in the code, and also generate id="" inside the
code not in template. It's work for xmi too:

<servlet xmi:<XDtId:prefixId prefix="Servlet"/>>

Cheers,
Ara. 

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:xdoclet-user-
> [EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED]
> Sent: Thursday, February 07, 2002 7:52 AM
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-user] first steps for enhanced websphere servlet
support
> 
> Hi all,
> 
> I've made some initial steps towards adding better websphere support
to
> xdoclet.  These are by no means complete, but I would appreciate
feedback,
> as this is the first attempt I've made at extending XDoclet.
Basically, I
> was just looking to make sure that I could get servlets and resource
> references defined properly.
> 
> Basically, what I did is this.  At Ara's suggestion, I've modified
> IdTagsHandler a little bit to provide a functionality for prefixed
unique
> identifiers like the ones that WebSphere's AAT uses.  I've added a
> parameter to the deploymentdescriptor task called 'useIds' which will
> toggle the generation of these unique element id's on or off for
certain
> components in the web.xml file (with the appropriate changes to
> web_xml.j).
> 
> I've also created another task (webSphereWebBndXmi) to create the
> ibm-web-bnd.xmi deployment descriptor.  It scans for tags like
> @websphere:res-ref to map servlet resource references to jndi names.
(due
> to the indexed id stuff, there is a caveat that the
@servlet:resource-ref
> tags and the @websphere:res-ref tags must be in the same order -- I'm
> still thinking this one through --- I'm sure it's solvable with a
smarter
> indexed id method --- maybe in a new class specific for websphere --
we'll
> see)  You can also set the virtual host to be deployed on via the ant
task
> with the 'virtualHost' parameter (defaults to the WAS 4.0 default of
> 'default_host').
> 
> I've attached the diffs for the 3 files I modified, and the two
additional
> files I created.  I hope this helps a little, I'd like to extend this
to
> include all of the servlet options (including generation of
> ibm-web-ext.xmi), and then continue on to the ejb generation stuff
> (schemas, etc.)
> 
> thanks,
> jason
> 



_______________________________________________
Xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Reply via email to