The following comment has been added to this issue:
Author: Heiko W. Rupp
Created: Tue, 31 Aug 2004 11:44 AM
Body:
New merge files have been named ".ent".
Just renaming the existing ones would break existing projects.
One should do something like the following in the merge tags handler
look for file.ent
if there
use it
else
print a fat warning that .xml are deprecated
use them anyway
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1049?page=comments#action_14707
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1049
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-1049
Summary: merge files have .xml extension but are not legal xml (multiple root
elements) and cause errors in our projects
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Versions:
1.2
Assignee: xdoclet-devel (Use for new issues)
Reporter: Brett Connor
Created: Tue, 31 Aug 2004 11:25 AM
Updated: Tue, 31 Aug 2004 11:44 AM
Environment: WinXP Pro, Eclipse 3.0, MyEclipse 3.7
Description:
I am using merge files for various parts of a project, including reference to ejbs,
JBoss specifics. The merge files currently in use are:
jbossweb-ejb-ref.xml
listeners.xml
servlet-mappings.xml
servlets.xml
taglibs.xml
web-ejbrefs.xml
Some of these have more than one entry, eg. taglibs, web-ejbrefs. The files are
therefore not legal xml because they have multiple root elements. Because the merge
file names are forced to be .xml however the IDEs validate them and the resulting
errors are poluting the error lists . Can these filenames be changed to something
indicating that they are a fragment, or any other solution (eg wrap the fragments in
another element eg. <taglibs><taglib>...</taglib></taglibs> although this is probably
more work than it's worth, these are all unparsed entities IIRC).
While this is minor, it does sadly jeopardise our use of xdoclet for this part of the
project.
---------------------------------------------------------------------
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 BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
