[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-789) seam components.xml editor seem to report errors when it shouldn't for Seam 2

Wed Aug 22 12:16:19 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBIDE-789?page=comments#action_12373338 ] 

Viacheslav Kabanovich commented on JBIDE-789:
---------------------------------------------

Having compared all xsd for versions 1.2 and 2.0 I see that a lot of things remained unchanged. For instance 
components-1.2.xsd = components-2.0.xsd,
security-1.2.xsd = security-2.0.xsd,
etc.

That means that components.xml written for version 1.2, may not need migration to 2.0 if it is limited 
to using these identical namespaces. The question is: does runtime check xml version? If it rejects versions 
other than current seam version, then IDE needs to take the same way. However, if runtime just reads 
xml and reports errors only if no match is found in seam model to xml declaration, then IDE may keep that 
way also, which is now the case. 
For instance, since core:jbpm migrated to bpm:jbpm, if in seam of version 2.0, components.xml of version 1.2 
contains <core:jbpm> (correct xml) seam model will not fine annotated class for it which will make it to 
report a problem. On the other hand, if that components contains <core:resource-bundle> which is defined 
identically in core-1.2.xsd and core-2.0.xsd, then probably we can accept it, as correct. 
So, all the difference makes the question above about processing xml versions by runtime.

> seam components.xml editor  seem to report errors when it shouldn't for Seam 2
> ------------------------------------------------------------------------------
>
>                 Key: JBIDE-789
>                 URL: http://jira.jboss.com/jira/browse/JBIDE-789
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: Seam
>    Affects Versions: 2.0.0.Beta3
>            Reporter: Max Andersen
>         Assigned To: Viacheslav Kabanovich
>            Priority: Critical
>             Fix For: 2.0.0.Beta4
>
>
> Gavin reports:
> The components.xml editor always shows errors at least with Seam2 
> metadata.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira