[ http://jira.jboss.com/jira/browse/JBIDE-789?page=all ] Max Andersen reassigned JBIDE-789: ---------------------------------- Assignee: Viacheslav Kabanovich Slav - could you take a look and tell why seam 2 files gets errors ? Might just be because Seam 2 changed too much and we will need a way to detect if something is Seam 1.2 or Seam 2....2.0's have -2.0.xsd's in the schemalocation. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-789?page=all ] Max Andersen reassigned JBIDE-789: ---------------------------------- Assignee: Gavin King (was: Viacheslav Kabanovich) Gavin - could you please let us know if seam2migration.txt is uptodate ? (or point to someone that might know ? ,) -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-789?page=comments#action_12372524 ] Max Andersen commented on JBIDE-789: ------------------------------------ btw. are we able to handle the differences in seam.core ? e.g. different models for seam 1 and 2 or how is that intended to work ? -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-789?page=comments#action_12372538 ] Max Andersen commented on JBIDE-789: ------------------------------------ thanks slav! -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-789?page=comments#action_12372550 ] Viacheslav Kabanovich commented on JBIDE-789: --------------------------------------------- Yes, now components defined in 2.0 are ignored, and probably they were partly loaded before that. To restore even partial loading we need to recognize 2.0, then editor will say what exactly it is not able to recognize (this feature was implemented recently). That can be done in 1 day, I think. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-789?page=all ] Alexey Kazakov reassigned JBIDE-789: ------------------------------------ Assignee: Viacheslav Kabanovich (was: Gavin King) Slava is finishing this work. I hope it will be resolved tomorrow. -- 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

[ 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. -- 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

[ http://jira.jboss.com/jira/browse/JBIDE-789?page=comments#action_12373636 ] Viacheslav Kabanovich commented on JBIDE-789: --------------------------------------------- I mean, that it may happen that components.xml does not mention core:jbpm or other tags that would make migration required. If 1.2 versioned components.xml contains only tags identical in 1.2 and 2.0, then migration is not required, and 1.2 xml may be accepted as correct for 2.0 project. That reasoning is still more relevant for fine-grained configuration files (*.component.xml) which are intended to configure user components and hence are likely to be limited to using components.xsd, which is the same for versions 1.2 and 2.0. -- 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