Hello,
after 2 days of work i got "all systems running" with xdoclet-1.2b3 and
websphere environment. Here's a short summary of all necessary patches to
get things right (i don't contribute my patches, because i'm not sure if
everyone is happy with them :-))
1. xdoclet.modules.ibm.websphere.web.WebSphereWebXmlSubTask.java
changed :
public WebSphereWebXmlSubTask()
{
}
to :
public WebSphereWebXmlSubTask()
{
setTemplateURL(getClass().getResource(BINDINGS_TEMPLATE_FILE));
setDestinationFile(GENERATED_BINDINGS_FILE_NAME);
}
comment :
avoids validateOptions error; it seems to me, that validation comes to
early - at least before the TemplateURL and DestinationFile is set in method
execute(), so i just set them as early as i can :-) (they are overriden
later on, anyway - just to get rid of the validateOptions error)
2. xdoclet.modules.ejb.dd.resources.ejb-jar_xml.xdt
comment : this template doesn't work with the
xdoclet.modules.ibm.websphere.ejb.resources.ibm-ejb-*.xtd's, because the
id's/href-attributes used in the templates don't match. Sometimes the
bean-name appears in one templates id's/hrefs and numeric ones in the other
and (may be) vice versa. One has to decide, what's the right direction. For
me, numeric id's/hrefs was less work, so i modified templates this way.
3. xdoclet.modules.ibm.websphere.ejb.resources.*.xdt
comment : see above.
4. xdoclet.modules.ibm.websphere.web.resources.ibm-web-*_xmi.xdt
comment : some minor changes on "different id's/href" issue.
5. xdoclet.modules.ibm.websphere.web.resources.ibm-web-bnd_xmi.xtd
comment : the generated jndi-name is taken out of @web.ejb-ref
description="my jndi name" now, because there is no attribute to place the
jndi-name of a bean. JBoss has own tags for this (@jboss.ejb-ref-jndi) but
websphere is missing those tags - so i decided to use the description
attribute of @web.ejb-ref as a container for this information (not
highly-sophisticated, but works as long as one decides to implement
websphere-specific tags ala jboss).
6. xdoclet.modules.ibm.websphere.web.resources.ibm-web-ext_xmi.xtd
comment : no <extendedServlets> tags are produced.
added the following after the <webApp> tag:
<XDtClass:forAllClassTags tagName="web.servlet">
<extendServlets xmi:<XDtId:prefixedId prefix="ServletExtension"/>>
<extendServlet href="WEB-INF/web.xml#<XDtId:prefixedId
prefix='Servlet'
wrapInIdEquals='false'/>"/>
</extendServlets>
</XDtClass:forAllClassTags>
7. xdoclet.modules.web.resources.web_xml.xdt
changed:
<servlet>
to:
<servlet <XDtId:prefixedId prefix="Servlet"/>>
comment : the servlet tag doesn't generate id's, even if told so
(useIDs="true"). this is extremly important for websphere.
Well, at least 1., 5., 6. and 7. is a bug, or ?
If anyone is interested in my patches (see attachment), let me know, but i
just optimized them so they look like my old hand-made ones, and i'm not
sure if the old ones were right. At least they were working :-)
Good bye, Joerg
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
