JBossDeveloper

Fantastic idea Tom!  This would be a great baby step for 4.x.  I'll go ahead and leave the JBESB_4_8_Camel workspace alone, and create a new workspace that flushes out your idea.  Luckily, most of the work I already did can be re-used with this idea, so I can do a lot of copy/paste. 

     <camel-listener ... /> 

 

Hmmm...  <camel-listener/>, or <camel-gateway/>?  Decisions, decisions... 

I'm thinking that it would still be nice to have a <providers> section too, so that we can have multiple routes in one CamelContext.  Since, if you do this:

<listeners>
    <camel-gateway from="file://xxx" />
    <camel-gateway from="ftp://yyy" />
</listeners>

, we would have to create 2 different CamelContexts, one for each gateway.  However, if we do this:

<providers>
    <camel-provider name="...">
        <camel-bus busid="foo">
            <from uri="file://xxx" />
            <from uri="ftp://yyy" />
        </camel-bus>
    </camel-provider>
</providers>
<services>
    <listeners>
        <camel-gateway name="..." busidref="foo" />
    </listeners>
    <actions>...</actions>
</services>

, then we can have multiple Camel routes as part of a single CamelContext - one per bus.  I also like using the <from> tag in the <camel-bus> section, as it is familiar to current Camel users.  The only caveat - for 4.x, anyway - is that ONLY the <from> tag would be supported by us.

What do you think?  Should we also allow the <camel-gateway from="" /> shorthand?  I wonder if we can define in XSD that you use either the busidref attribute, OR the from attribute?  Or maybe we let them do both, and all "from's" get put into the same CamelContext?  I think I prefer that...

Okay, a bit more discussion on the team, and this is looking like the new direction.  You would have several options, including some shorthand:

<listeners>
    <camel-gateway name="..." from="foo://bar" />
</listeners>

<listeners>
     <camel-gateway name="...">
        <from uri="foo://bar" />
        <from uri="foo://bar" />
    </camel-gateway>
</listeners>

<listeners>
     <camel-gateway name="..." from="foo://bar">
        <from uri="foo://bar" />
        <from uri="foo://bar" />
    </camel-gateway>
</listeners>

<providers>
    <camel-provider name="...">
        <camel-bus busid="xxx" from="foo://bar">
    </camel-provider>
</providers>
<services>
    <service category="..." name="...">
        <listeners>
            <camel-gateway name="..." busidref="xxx" />
        </listeners>
        <actions>...</actions>
    </service>
</services>

<providers>
     <camel-provider name="...">
         <camel-bus busid="xxx">
            <from uri="foo://bar" />
            <from uri="foo://bar" />
        </camel-bus>
    </camel-provider>
</providers>
<services>
    <service category="..." name="...">
        <listeners>
            <camel-gateway name="..." busidref="xxx" />
        </listeners>
        <actions>...</actions>
    </service>
</services>

You get the idea.    Basically, all "from's" associated with a gateway would be combined into a single CamelContext.  If you specify multiple camel-gateways in the listeners section that refer to the same bus, then the routes defined in the <camel-bus> section are created separately in each CamelContext - again, one per gateway.

I've improved upon the XML suggestion above, and now support native Camel <route>s, with NO dependency on Spring.  All of this is explained in the new wiki page ("CamelGateway"), located here:

http://community.jboss.org/wiki/CamelGateway

(The old wiki page and workspace have been delted in favor of the above.)

Understood.

I do have a question, though...  So the <from>s under <camel-gateway> are additive to the <from>s under <camel-bus>, but what if the user chooses the from-uri attribute in both the gateway and the bus?  Should those be additive as well, or should the gateway's from-uri attribute override/trounce the bus'?

A jira feature request has been added: https://jira.jboss.org/browse/JBESB-3329

After giving it some thought, I think that attributes defined at the <camel-gateway> level should override those at the <camel-bus> level (so that the from-uri attribute behaves just like the async and timeout attributes), however <from> elements defined inside camel-gateway are added to those at the <camel-bus> level.

Scaling back to only supporting Camel "from" URIs has been done in this workspace:

     http://anonsvn.jboss.org/repos/labs/labs/jbossesb/workspace/dward/JBESB_4_8_Camel_Gateway

, and the wiki page has been updated to match:

     http://community.jboss.org/wiki/CamelGateway

There are a couple things I need to clean up before I merge it into trunk for ESB 4.9.

The code and wiki have been updated to reflect the cummulative nature of from-uri attributes so they are added just like <from uri=""> elements.

The CamelGateway has been committed to trunk in revision 33127.  Woot!