| The xml editor recognizes a single an end tag as valid xml [message #66568] |
Thu, 20 January 2005 11:11  |
Eclipse User |
|
|
|
Hi everybody,
I just got stuck with something strange.
If I create a new xml file, open it with the M2 XML Editor and just
write something like </test> the XML Editor doesn't underline it or
mark it as an error.
The other way round works perfectly: Only a beginning tag without an
end tag throws an error.
Is that issue known to anybody?
Thanks,
Raphael
|
|
|
| Re: The xml editor recognizes a single an end tag as valid xml [message #66890 is a reply to message #66568] |
Thu, 20 January 2005 23:46  |
| Eclipse User |
|
|
|
On Thu, 20 Jan 2005 17:11:32 +0100, Raphael A. Bauer <raphael.bauer@temis-group.com> wrote:
>
> Is that issue known to anybody?
>
Nope, not known. (But not too surprising, given our "fault tolerant parser" actually creates an element in taht case). We are hoping to improve much of that type of validation in future milestones. But I'll suggest you take one of two actions ... if its from a "real life" case that caused you some greif, please open a bugzilla, and we can try and be sure that case is handled better in future milestones (attaching example files, exact scenerios, or outright JUnit tests are always appreciated). Alternatively, if this was just an "oddity" you noticed, you might wait until validation is re-vamped and try it again.
|
|
|
| Re: The xml editor recognizes a single an end tag as valid xml [message #66911 is a reply to message #66890] |
Fri, 21 January 2005 04:53 |
| Eclipse User |
|
|
|
David Williams wrote:
> On Thu, 20 Jan 2005 17:11:32 +0100, Raphael A. Bauer
> <raphael.bauer@temis-group.com> wrote:
>> Is that issue known to anybody?
> Nope, not known. (But not too surprising, given our "fault tolerant
> parser" actually creates an element in taht case). We are hoping to
> improve much of that type of validation in future milestones. But I'll
> suggest you take one of two actions ... if its from a "real life" case
> that caused you some greif, please open a bugzilla, and we can try and
> be sure that case is handled better in future milestones (attaching
> example files, exact scenerios, or outright JUnit tests are always
> appreciated). Alternatively, if this was just an "oddity" you noticed,
> you might wait until validation is re-vamped and try it again.
I just digged a bit deeper and unfortunately I discovered some other
strange xsd validation behaviours...
I'll investigate these things in detail, and post them with examples to
the newsgroup within the next 2 weeks, so you can decide what's a
bugzilla thing and what not...
thanks,
Raphael
|
|
|
| Re: The xml editor recognizes a single an end tag as valid xml [message #66955 is a reply to message #66911] |
Fri, 21 January 2005 16:46 |
| Eclipse User |
|
|
|
On Fri, 21 Jan 2005 10:53:40 +0100, Raphael A. Bauer <raphael.bauer@temis-group.com> wrote:
> I'll investigate these things in detail, and post them with examples to
> the newsgroup within the next 2 weeks, so you can decide what's a
> bugzilla thing and what not...
Ok, thanks for digging and documenting. But ... it'd be better if *you* decided what's worth a bugzilla and what's not. Clients and Users opening bugzilla reports are our way of knowing and tracking "didn't work as expected". Problem reports to newsgroups won't deliberately be ignored, but in the course of things are sometimes lost and in general receive less priority. Thanks again.
|
|
|
Powered by
FUDForum. Page generated in 0.02798 seconds
Home