The following comment has been added to this issue:
Author: Andrew Stevens
Created: Tue, 13 Jan 2004 6:11 PM
Body:
res-url was only added in the JBoss 3.2 DTD; the module currently only supports 2.4
and 3.0.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-726
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-726
Summary: <jbosswebxml> subtask does not generate resource-refs with URLs
Type: Bug
Status: Open
Priority: Minor
Original Estimate: 10 minutes
Time Spent: Unknown
Remaining: 10 minutes
Project: XDoclet
Components:
JBoss Module
Versions:
1.2 Beta 3
Assignee: xdoclet-devel (Use for new issues)
Reporter: Ingo Kl�ckl
Created: Thu, 27 Nov 2003 2:15 AM
Updated: Tue, 13 Jan 2004 6:11 PM
Environment: Windows 2000/Jboss 3.0.4
Description:
I have used following tagging for a resource-ref:
/**
* @web.servlet name = "Bla"
* @web.servlet-mapping url-pattern = "/bla"
* @web.resource-ref name = "url/AsciiTemplate"
* type = "java.net.URL"
* auth = "Container"
* @jboss.resource-ref res-ref-name = "url/AsciiTemplate"
* res-url = "http://blo/template.asc";
*/
The <jbosswebxml/> subtask generated the jboss_web.xml fragment below:
<!-- Resource references -->
<resource-ref>
<res-ref-name>url/AsciiTemplate</res-ref-name>
<jndi-name></jndi-name>
</resource-ref>
It should be:
<!-- Resource references -->
<resource-ref>
<res-ref-name>url/AsciiTemplate</res-ref-name>
<res-url>http://blo/template.asc</res-url>
</resource-ref>
To resolve this issue, the file
xdoclet/modules/jboss/src/xdoclet/modules/jboss/web/resources/jboss_web_xml.xdt should
be changed as follows.
Substitute the block
<!-- Resource references -->
<XDtJBossWeb:forAllResourceRefs>
<resource-ref>
<res-ref-name><XDtClass:classTagValue tagName="jboss:resource-ref"
paramName="res-ref-name"/></res-ref-name>
<jndi-name><XDtClass:classTagValue tagName="jboss:resource-ref"
paramName="jndi-name"/></jndi-name>
</resource-ref>
</XDtJBossWeb:forAllResourceRefs>
with
<!-- Resource references -->
<XDtJBossWeb:forAllResourceRefs>
<resource-ref>
<res-ref-name><XDtClass:classTagValue tagName="jboss:resource-ref"
paramName="res-ref-name"/></res-ref-name>
<XDtClass:ifHasClassTag tagName="jboss:resource-ref" paramName="jndi-name">
<jndi-name><XDtClass:classTagValue tagName="jboss:resource-ref"
paramName="jndi-name"/></jndi-name>
</XDtClass:ifHasClassTag>
<XDtClass:ifHasClassTag tagName="jboss:resource-ref" paramName="res-url">
<res-url><XDtClass:classTagValue tagName="jboss:resource-ref"
paramName="res-url"/></res-url>
</XDtClass:ifHasClassTag>
</resource-ref>
</XDtJBossWeb:forAllResourceRefs>
Then, all <res-url> nodes will be generated whenever the res-url attribute of
@jboss.resource.ref will be used, and <jndi-name> nodes will be created when usig the
jndi-name attribute.
I think things were supposed to go this way?
Anyway, XDoclet&Co is a well-done software tool!!
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
