Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Web Tools Project (WTP) » xml fragments (xdoclet merge files)
xml fragments (xdoclet merge files) [message #166131] Fri, 07 April 2006 09:09 Go to next message
Eclipse User
Originally posted by: mlybarger.com.gmail.backwards

wtp currently allows xdoclet for maintaining generated artifacts.
filter-mappings.xml and other merge files are commonly fragments of
actual xml files. they're not well formed xml documents in and of
themselves (if they contain more than one item). These show as errors
in eclipse and the project has an error icon.

i searched bugzilla quickly and didn't find anything on this, but i
suspect something is out there. is there a proposed solution to this?

even the build-user.xml that gets generated from exporting a project's
ant build scripts will eventually be an invalid xml document if a user
adds tasks or properties to it. i realize this item isn't in the scope
of wtp, but thought i'd provide it as another example.

thanks!
Re: xml fragments (xdoclet merge files) [message #166253 is a reply to message #166131] Sat, 08 April 2006 00:45 Go to previous messageGo to next message
David Williams is currently offline David Williams
Messages: 695
Registered: July 2009
Senior Member
On Fri, 07 Apr 2006 09:09:35 -0400, Mark Lybarger <mlybarger@com.gmail.backwards> wrote:

> wtp currently allows xdoclet for maintaining generated artifacts.
> filter-mappings.xml and other merge files are commonly fragments of
> actual xml files. they're not well formed xml documents in and of
> themselves (if they contain more than one item).

So, these are illformed xml files, but till in files with extensions "xml"?
That'll be a tough one.

You can certainly turn off XML Validation, but that's not great either. There's a
feature request in bugzilla to allow XML Validation to be turned off on a folder-by-folder
basis ... but, not implemented yet, but that might be one long term solution to this.

Better yet, if you have control over these files, is to give them a different extension,
like ".frag" ... I've seen some do that.

If, on the other hand, you are saying *we* generate these files ... then, I'd think that would
be worth opening a bug on. We should not be generating invalid XML files!?
Re: xml fragments (xdoclet merge files) [message #166360 is a reply to message #166131] Mon, 10 April 2006 12:52 Go to previous messageGo to next message
Eclipse User
Originally posted by: wknauf_NO_._INSIDE_hg-online.de

Hi Mark !

Mark Lybarger wrote:
>
> i searched bugzilla quickly and didn't find anything on this, but i
> suspect something is out there. is there a proposed solution to this?
>

This is the bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=125877

You might vote for it.

Best regards

Wolfgang
Re: xml fragments (xdoclet merge files) [message #170618 is a reply to message #166253] Mon, 05 June 2006 15:19 Go to previous message
Eclipse User
Originally posted by: sharper3.austin.dot.rr.dot.com

In article <op.s7n96wztac05ss@dmw2t23.raleigh.ibm.com>, "David Williams" <david_williams@us.ibm.com> wrote:
>On Fri, 07 Apr 2006 09:09:35 -0400, Mark Lybarger
> <mlybarger@com.gmail.backwards> wrote:
>
>> wtp currently allows xdoclet for maintaining generated artifacts.
>> filter-mappings.xml and other merge files are commonly fragments of
>> actual xml files. they're not well formed xml documents in and of
>> themselves (if they contain more than one item).
>
>So, these are illformed xml files, but till in files with extensions "xml"?
>That'll be a tough one.
>
>You can certainly turn off XML Validation, but that's not great either. There's
> a
>feature request in bugzilla to allow XML Validation to be turned off on a
> folder-by-folder
>basis ... but, not implemented yet, but that might be one long term solution to
> this.

I found that validation could be turned off on a project-by-project basis, but
that sort of defeats the purpose. I'd like to have the rest of my "real" XML
validated. And these are in fact "valid" files in the XDoclet sense, they
just aren't well-formed XML...

Better than folder-by-folder would be file-by-file. If you already have to
check on a folder basis, it shouldn't be too much more difficult to check on a
file basis. But, short of that, turning off validation for a folder would
provide a workable solution.

FWIW, I have a work-around for this issue, although it is less than perfect...
Just make your mergedir a directory somewhere outside of your project
hierarchy. The downside to this is that your merge files are now not part of
your project, are difficult to control with CVS, and you have to remember they
are out there.

>Better yet, if you have control over these files, is to give them a different
> extension,
>like ".frag" ... I've seen some do that.

I tried this too, but unfortunately XDoclet only looks at files with very
specific names. And all these specific names have .xml as an extension.


scott
Previous Topic:Leather Java Coat
Next Topic:already built web application
Goto Forum:
  


Current Time: Tue Jul 22 15:51:56 EDT 2014

Powered by FUDForum. Page generated in 0.02120 seconds