[ https://jira.jboss.org/browse/JBIDE-6615?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-6615: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Viacheslav Kabanovich (was: Brian Fitzpatrick) Fix Version/s: 3.2.0.Beta (was: 3.2.x) Slava, we have some new functionality to support in the ESB editor for ESB 4.9... (Note that I'm bumping it to the 3.2.0.BETA milestone, not M2 since we're getting close and I'm betting you have other priorities right now.) [This info came from the http://community.jboss.org/wiki/CamelGateway wiki page] # The first thing to note is the jbossesb-1.3.0.xsd version of the schema. This allows us to introduce the new camel configuration elements. # Next note the <camel-provider> and <camel-bus> elements. Those familiar with JBossESB configuration should be very comfortable with this, as it maps well to other existing elements, like <jms-provider> and <jms-bus>. # What is contained within the <camel-bus> element is the most interesting part, where you can have an unbounded number of <from uri=""/> elements. Those familiar with Camel XML configuration should be very comfortable with that element, as it does exactly what it does in native Camel XML configuration. # Finally, the <camel-gateway> element in the <listeners> section of the <service> references the bus via the busidref attribute. So we have: * a new schema (jbossesb-1.3.0.xsd) * a new <camel-provider> available in the <providers> element * each <camel-provider> element can have one or more <from uri=""/> elements * a new <camel-gateway> listener in the <listeners> element of <service> Unfortunately it looks like there are shorthand ways of expressing various things, such as... * configure <from>s at the <camel-gateway> level without needing a <camel-bus> section <camel-gateway name="gateway1"> <from uri="file://.../samples/quickstarts/camel_helloworld/build/input1?delete=true"/> <from uri="file://.../samples/quickstarts/camel_helloworld/build/input2?delete=true"/> </camel-gateway> * or something even like this... <camel-gateway name="gateway1" from-uri="file://.../samples/quickstarts/camel_helloworld/build/input1?delete=true"/> So there are some variants we'll have to handle somehow in this as well. If you need more info, don't hesitate to ask, but hopefully the http://community.jboss.org/wiki/CamelGateway wiki page will have most of the answers. If not, David Ward should be able to answer any other questions we have since he wrote it. :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6615?page=com.atlassian.jira.plugin.s... ] Viacheslav Kabanovich resolved JBIDE-6615. ------------------------------------------ Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBIDE-6615?page=com.atlassian.jira.plugin.s... ] Brian Fitzpatrick updated JBIDE-6615: ------------------------------------- Labels: new_and_noteworthy (was: ) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira