moving camel-jbi module from Camel to the servicemix-camel module...

[James Strachan <ja...@gmail.com>]

In the Camel project we've an EIP implementation which can route any
JBI components (as well as other things)...
http://activemq.apache.org/camel/jbi.html

the current list of EIP patterns implemented is here...
http://activemq.apache.org/camel/enterprise-integration-patterns.html

you can use Java code or XML (spring XML) to implement the routing...
http://activemq.apache.org/camel/spring.html

The current camel-jbi depends on trunk of ServiceMix (as it plugs into
all the nice features in ServiceMix, like dynamic endpoint resolution,
URI syntax and so forth). Given this dependency on the internals of
ServiceMix (and it only really uses the simple public APIs of Camel),
plus I'd like to hopefully unify serviceix-eip with Camel routing
capabilities - I'm gonna move the following modules from Camel into
ServiceMix...

camel/components/camel-jbi
  -> servicemix/deployables/serviceengines/servicemix-camel

camel/tooling/archetypes/camel-jbi-service-unit
  -> servicemix/archetypes/servicemix-camel-service-unit

As usual, any feedback most welcome. We can always move it back if
folks think of a good reason later on (for once, I'm glad all of
apache is a single svn repo ;-).

-- 
James
-------
http://macstrac.blogspot.com/

Re: moving camel-jbi module from Camel to the servicemix-camel module...

[James Strachan <ja...@gmail.com>]

On 8/8/07, James Strachan <ja...@gmail.com> wrote:
> In the Camel project we've an EIP implementation which can route any
> JBI components (as well as other things)...
> http://activemq.apache.org/camel/jbi.html
>
> the current list of EIP patterns implemented is here...
> http://activemq.apache.org/camel/enterprise-integration-patterns.html
>
> you can use Java code or XML (spring XML) to implement the routing...
> http://activemq.apache.org/camel/spring.html
>
> The current camel-jbi depends on trunk of ServiceMix (as it plugs into
> all the nice features in ServiceMix, like dynamic endpoint resolution,
> URI syntax and so forth). Given this dependency on the internals of
> ServiceMix (and it only really uses the simple public APIs of Camel),
> plus I'd like to hopefully unify serviceix-eip with Camel routing
> capabilities - I'm gonna move the following modules from Camel into
> ServiceMix...
>
> camel/components/camel-jbi
>   -> servicemix/deployables/serviceengines/servicemix-camel
>
> camel/tooling/archetypes/camel-jbi-service-unit
>   -> servicemix/archetypes/servicemix-camel-service-unit
>
> As usual, any feedback most welcome. We can always move it back if
> folks think of a good reason later on (for once, I'm glad all of
> apache is a single svn repo ;-).

FWIW the move is now complete...

https://svn.apache.org/repos/asf/incubator/servicemix/trunk/deployables/serviceengines/servicemix-camel/
https://svn.apache.org/repos/asf/incubator/servicemix/trunk/archetypes/servicemix-camel-service-unit/

I'll document this new service engine & service unit on the ServiceMix shortly

-- 
James
-------
http://macstrac.blogspot.com/

Re: moving camel-jbi module from Camel to the servicemix-camel module...

[Gert Vanthienen <ge...@skynet.be>]

Sounds like a good idea to me as well.
+1

James Strachan wrote:
> In the Camel project we've an EIP implementation which can route any
> JBI components (as well as other things)...
> http://activemq.apache.org/camel/jbi.html
>
> the current list of EIP patterns implemented is here...
> http://activemq.apache.org/camel/enterprise-integration-patterns.html
>
> you can use Java code or XML (spring XML) to implement the routing...
> http://activemq.apache.org/camel/spring.html
>
> The current camel-jbi depends on trunk of ServiceMix (as it plugs into
> all the nice features in ServiceMix, like dynamic endpoint resolution,
> URI syntax and so forth). Given this dependency on the internals of
> ServiceMix (and it only really uses the simple public APIs of Camel),
> plus I'd like to hopefully unify serviceix-eip with Camel routing
> capabilities - I'm gonna move the following modules from Camel into
> ServiceMix...
>
> camel/components/camel-jbi
>   -> servicemix/deployables/serviceengines/servicemix-camel
>
> camel/tooling/archetypes/camel-jbi-service-unit
>   -> servicemix/archetypes/servicemix-camel-service-unit
>
> As usual, any feedback most welcome. We can always move it back if
> folks think of a good reason later on (for once, I'm glad all of
> apache is a single svn repo ;-).
>
>   

Re: moving camel-jbi module from Camel to the servicemix-camel module...

[Guillaume Nodet <gn...@gmail.com>]

+1

On 8/8/07, James Strachan <ja...@gmail.com> wrote:
> In the Camel project we've an EIP implementation which can route any
> JBI components (as well as other things)...
> http://activemq.apache.org/camel/jbi.html
>
> the current list of EIP patterns implemented is here...
> http://activemq.apache.org/camel/enterprise-integration-patterns.html
>
> you can use Java code or XML (spring XML) to implement the routing...
> http://activemq.apache.org/camel/spring.html
>
> The current camel-jbi depends on trunk of ServiceMix (as it plugs into
> all the nice features in ServiceMix, like dynamic endpoint resolution,
> URI syntax and so forth). Given this dependency on the internals of
> ServiceMix (and it only really uses the simple public APIs of Camel),
> plus I'd like to hopefully unify serviceix-eip with Camel routing
> capabilities - I'm gonna move the following modules from Camel into
> ServiceMix...
>
> camel/components/camel-jbi
>   -> servicemix/deployables/serviceengines/servicemix-camel
>
> camel/tooling/archetypes/camel-jbi-service-unit
>   -> servicemix/archetypes/servicemix-camel-service-unit
>
> As usual, any feedback most welcome. We can always move it back if
> folks think of a good reason later on (for once, I'm glad all of
> apache is a single svn repo ;-).
>
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>


-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/