The following comment has been added to this issue:

     Author: Andrew Stevens
    Created: Mon, 17 Mar 2003 5:10 PM
       Body:
Now that's an argument I don't want to get into ;-)
If you think we should drop jboss 2.x support, the xdoclet-user and/or jboss mailing 
lists are probably better places to suggest it.  IMO it should only be considered for 
2.0, though, 1.2 should continue to support it.

All the merge files thing needs is to change one of the merge filenames to e.g. 
jaws-db-more-settings-{0}.xml, but I figured it was better done by a jboss module 
maintainer (or at least someone that actually uses jboss) than doing it myself.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-385


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XDT-385
    Summary: Clashing merge files
       Type: Bug

     Status: Assigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: XDoclet
  Component: JBoss Module
   Versions:
             1.2 Beta 2
             SNAPSHOT (CVS)

   Assignee: xdoclet-devel (Use for new issues)
   Reporter: Andrew Stevens

    Created: Fri, 14 Mar 2003 6:29 PM
    Updated: Fri, 14 Mar 2003 6:29 PM

Description:
In the course of my efforts to document all merge points (XDT-342), I noticed that in 
jboss-jaws_xml.xdt the
<XDtMerge:merge file="jaws-db-settings-{0}.xml">
merge point has been used twice, both for the (ejb-name , datasource?) elements (lines 
23-25) and also for the (read-only? , table-name? , tuned-updates? , create-table? , 
remove-table? , row-locking? , time-out? , pk-constraint?) elements (lines 70-101).  
Obviously, if anyone were to actually try and use this merge point, the resulting file 
could never be valid...

Also, I noticed that although the read-ahead sub-element of finder is included, the 
optional read-ahead element from between the finder elements and the read-only element 
isn't actually catered for, even though it appears in the DTD:

<!ELEMENT entity (ejb-name , datasource? , cmp-field* , finder* , read-ahead? , 
read-only? , table-name? , tuned-updates? , create-table? , remove-table? , 
row-locking? , time-out? , pk-constraint?)>



---------------------------------------------------------------------
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/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:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to