[seam-dev] Please remember to actually try validate xml with xsd's ; )
Max Rydahl Andersen
max.andersen at redhat.com
Sun Nov 23 06:29:01 EST 2008
> This is what we call a "bug" - they do happen in products outside JBDS
> where we don't have such excellent engineers as you :p
blah ;) I know it was a bug, but since it looked like a deliberate change
I wanted
to let you know that it affects validation in IDE's.
> Actually, I think this was already reported in JIRA?
Well, it is - the reporter first did it in JBoss Tools and then realized
that we
were reporting it correctly according to what the XSD told us.
/max
>
> On 22 Nov 2008, at 03:13, Max Rydahl Andersen wrote:
>
>> On Fri, 21 Nov 2008 17:07:08 +0100, Jay Balunas <tech4j at gmail.com>
>> wrote:
>>
>>> I wondering why this was not caught in our release testing - I would
>>> assume that it is because none of the examples and/or current JBDS
>>> tests strike this issue. We will look further into this and try to
>>> come up with a good way to verify.
>>
>> Enable schema validation in a test run and it should reveal it - this
>> isn't really a JBDS specific issue, it would fail in any validating
>> xml editor.
>>
>> Note: Seam's xml is extremely nice and strict compared to other
>> projects like
>> e.g. ESB where the DTD/XSD is basically useless since anything can be
>> nested
>> in anything according to the XSD but the runtime doesn't support that
>> and
>> in other places it is stated that the attribute is a number/string etc.
>> but
>> actually they have support for ${} property style replacement too
>> causing us
>> to disable validation and do custom hacks around the xsd to have the
>> editing
>> not fail on valid files...a paain!
>>
>> So big kudos to seam XSD files - but remember to use them for
>> validation once
>> in a while and we should avoid degenerating into what ESB XSD's are ;)
>>
>> /max
>>
>>>
>>> -Jay
>>>
>>>
>>> On Nov 21, 2008, at 10:56 AM, Norman Richards wrote:
>>>
>>>>
>>>> On Nov 21, 2008, at 9:47 AM, Max Rydahl Andersen wrote:
>>>>
>>>>> Right now redirect view-id can't use EL expression's according to
>>>>> the XSD
>>>>>
>>>>> Causing xml validators to complain
>>>>> (https://jira.jboss.org/jira/browse/JBIDE-3248)
>>>>> because of the XSD having a weird limitation as reported in
>>>>> https://jira.jboss.org/jira/browse/JBSEAM-3741
>>>>>
>>>>> I assume that .xsd change was not what you actually wanted ?
>>>>
>>>> I'll fix this for 2.1.1.CR2. It looks like the components.xml
>>>> stricter typing made it to pages.xml, but without the addition of
>>>> allowing EL
>>>> expressions._______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>
>>
>>
>> --/max
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
--
/max
More information about the seam-dev
mailing list