[ http://jira.jboss.com/jira/browse/JBIDE-1670?page=all ] Max Andersen updated JBIDE-1670: -------------------------------- Component/s: esb -- 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-1670?page=all ] Viacheslav Kabanovich reassigned JBIDE-1670: -------------------------------------------- Assignee: Viacheslav Kabanovich -- 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-1670?page=comments#action_12398807 ] Viacheslav Kabanovich commented on JBIDE-1670: ---------------------------------------------- In esb, there are different kinds of bus elements (fs-bus, ftp-bus, etc.) and of bus providers elements (respectively, fs-provider, ftp-provider, etc.). Schema allows to make each kind of bus a child element of any kind of provider element. Does it make sence to have fs-bus in ftp-provider? Which combinations are relevant? Maybe, if schema allows all combinations, model can read and understand them all, but do we need New- wizard family to support creating all combinations or just those of them that make sense? -- 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-1670?page=comments#action_12398870 ] Tom Fennelly commented on JBIDE-1670: ------------------------------------- The combinations actually do matter... the ESB will generate errors on startup if you attempt to define (e.g.) a jms-bus inside an ftp-provider. Why is the XSD allowing it... I guess a combination of ignorance/haste etc on our part when defining the 1st version + it has evolved since then in some weird and wonderful ways :-) The general rule of thumb is... "jms-provider/jms-bus"... "ftp-provider/ftp-bus" etc -- 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-1670?page=all ] Viacheslav Kabanovich resolved JBIDE-1670. ------------------------------------------ Resolution: Done -- 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-1670?page=all ] Max Andersen updated JBIDE-1670: -------------------------------- Fix Version/s: 2.1.0.beta1 (was: 2.1) batch update of issues with 2.1 fix instead of the correct 2.1.b1 -- 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