You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2010/02/10 10:50:46 UTC
[DISCUSS] Include ODE by default in ServiceMix distribution
Hi guys,
I would like to discuss the possibility to include Apache ODE by default
in ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
4.4.2).
As I'm working on WSDL/WebServices support in ServiceMix components, it
can be great for the users to have the capability to make services
orchestration using ODE.
What do you think ?
Regards
JB
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Rafal Rusin <ra...@gmail.com>.
+1 from me. Although not binding, I can help by coding up some of your
requirements into ODE.
Recently we had some important contributions related to SMX4 in ODE-1.X.
Those are:
-jbi bundle
-karaf features
-maven2 build (http://hudson.zones.apache.org/hudson/job/ODE-1.X-maven2/)
-running bpel processes from OSGi bundles
So including ODE 1.3.4 in SMX4 is a kind of hot topic I believe.
I tested ODE 1.X bundle in apache-servicemix-4.2.0-fuse-01-00 recently
and it worked quite well, so I believe we are far already.
Regards
On 11 February 2010 17:41, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Good idea Gert.
>
> The project can be a good candidate for Google Summer of Code.
>
> Even if we begin to work on this topic, it can be a good base for the GSoC.
>
> Regards
> JB
>
> Gert Vanthienen wrote:
>>
>> L.S.,
>>
>> Actually, there's another GSoC this year and the ASF are participating
>> in it again, so if nobody has picked that up in a month or so when the
>> proposals have to go in, this might be a good candidate for a GSoC
>> project.
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> On 10 February 2010 14:04, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>>
>>> Hi Gert,
>>>
>>> My comments inline:
>>>
>>>> I agree that ODE would make a very nice addition for ServiceMix.
>>>> However, I seem to recall it needed some extra work to get it working
>>>> in ServiceMix 4 as the JBI SE they have had some dependencies on
>>>> ServiceMix 3 (I might be wrong here though).
>>>
>>> I plan to create a jira task about this to clearly identify the issues
>>> that
>>> we have.
>>> Totally agree that we need to perform tests. That's why I propose to add:
>>> - a SMX ODE component (based on ODE component itself): this project will
>>> mainly host unit tests and integration tests to validate the ODE deploys
>>> and
>>> runs correctly on SMX3 and SMX4
>>> - add a servicemix-ode feature to provide installable feature for SMX4.
>>>
>>>> Given that we're trying to stabilize things down for the 4.2.0
>>>> release, wouldn't it be a better idea to schedule the inclusion of ODE
>>>> for ServiceMix 4.3? It is likely to bring along some additional
>>>> dependencies (or dependency versions) and the delay would also give us
>>>> time to add some additional features (e.g. have a processes view in
>>>> the webconsole or in the shell) or build itests to ensure it
>>>> integrates nicely with everything else.
>>>
>>> In fact, there is no really emergency about ODE integration. So we can
>>> postpone this in the SMX 4.3 and 3.3.3 release.
>>> If we are all agree, we can release a new components set (2010.01) as
>>> soon
>>> as Camel 2.2 is release. Once this components set will be released, I
>>> propose to release ServiceMix 3.3.2. For ServiceMix 4.2, we are waiting
>>> for
>>> another bug fix in Felix Karaf.
>>> Related to this, what do you think to add a wiki page presenting the
>>> roadmap
>>> ? In the roadmap, we can define the steps required to cut off a release.
>>>
>>>> Personally, I would make ODE an optionally installable feature
>>>> (similar to what we do for e.g. the wrapper feature). We could make
>>>> sure that everything is packaged in the /system folder, so when people
>>>> do a features:install ode it can start it quickly and without having
>>>> to go and download things. That way, someone who wants to use can get
>>>> it "swiftly and with style", but we're not adding any more bundles to
>>>> slow down startup for the rest of our users.
>>>
>>> Agree, the most important is to provide ODE in the distribution and let
>>> the
>>> user enable it or not.
>>>
>>> Regards
>>> JB
>>>
>>>> Regards,
>>>>
>>>> Gert Vanthienen
>>>> ------------------------
>>>> Open Source SOA: http://fusesource.com
>>>> Blog: http://gertvanthienen.blogspot.com/
>>>>
>>>>
>>>>
>>>> On 10 February 2010 12:18, Charles Moulliard <cm...@gmail.com>
>>>> wrote:
>>>>>
>>>>> There is an implementation for that
>>>>>
>>>>> http://www.jopera.org/docs/publications/2008/bpel4rest
>>>>>
>>>>> Charles
>>>>>
>>>>>
>>>>> On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré
>>>>> <jb...@nanthrax.net>wrote:
>>>>>
>>>>>> Charles, CXF provides JAX-RS implementation. So basicly, we can have
>>>>>> support for REST annotations. However, as RESTful web services
>>>>>> couldn't
>>>>>> have
>>>>>> XML payload, it's not easy to use in the NMR.
>>>>>> Maybe we need to discuss about RESTful and NMR support with the team.
>>>>>> Any
>>>>>> idea is welcome :)
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>> Charles Moulliard wrote:
>>>>>>
>>>>>>> ++1
>>>>>>>
>>>>>>> I'm not a fan of an orchestration engine but I must admit that in
>>>>>>> some
>>>>>>> situations orchestration is required. The advantage of what
>>>>>>> Jean-Baptiste
>>>>>>> proposes is that we can expose the (JBI) endpoints of the ServiceMix
>>>>>>> platform as WebServices (or why not RESTfull services) and so we can
>>>>>>> orchestrate the communication between the existing components in an
>>>>>>> easiest
>>>>>>> way. Transforming any endpoint into a WebService (RESTfull service))
>>>>>>> could
>>>>>>> be interesting to integrate/interconnect platforms together or allow
>>>>>>> external package to work with our SMX (like Siebel, ....)
>>>>>>>
>>>>>>> Kind regards,
>>>>>>>
>>>>>>> Charles Moulliard
>>>>>>> Senior Enterprise Architect
>>>>>>> Apache Camel Committer
>>>>>>>
>>>>>>> *****************************
>>>>>>> blog : http://cmoulliard.blogspot.com
>>>>>>> twitter : http://twitter.com/cmoulliard
>>>>>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>>>>>
>>>>>>> Apache Camel Group :
>>>>>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré
>>>>>>> <jb@nanthrax.net
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>> I would like to discuss the possibility to include Apache ODE by
>>>>>>>> default
>>>>>>>> in
>>>>>>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and
>>>>>>>> ServiceMix
>>>>>>>> 4.4.2).
>>>>>>>>
>>>>>>>> As I'm working on WSDL/WebServices support in ServiceMix components,
>>>>>>>> it
>>>>>>>> can
>>>>>>>> be great for the users to have the capability to make services
>>>>>>>> orchestration
>>>>>>>> using ODE.
>>>>>>>>
>>>>>>>> What do you think ?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>>
>
--
Rafał Rusin
http://rrusin.blogspot.com
http://www.touk.pl
http://top.touk.pl
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Good idea Gert.
The project can be a good candidate for Google Summer of Code.
Even if we begin to work on this topic, it can be a good base for the GSoC.
Regards
JB
Gert Vanthienen wrote:
> L.S.,
>
> Actually, there's another GSoC this year and the ASF are participating
> in it again, so if nobody has picked that up in a month or so when the
> proposals have to go in, this might be a good candidate for a GSoC
> project.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 10 February 2010 14:04, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Hi Gert,
>>
>> My comments inline:
>>
>>> I agree that ODE would make a very nice addition for ServiceMix.
>>> However, I seem to recall it needed some extra work to get it working
>>> in ServiceMix 4 as the JBI SE they have had some dependencies on
>>> ServiceMix 3 (I might be wrong here though).
>> I plan to create a jira task about this to clearly identify the issues that
>> we have.
>> Totally agree that we need to perform tests. That's why I propose to add:
>> - a SMX ODE component (based on ODE component itself): this project will
>> mainly host unit tests and integration tests to validate the ODE deploys and
>> runs correctly on SMX3 and SMX4
>> - add a servicemix-ode feature to provide installable feature for SMX4.
>>
>>> Given that we're trying to stabilize things down for the 4.2.0
>>> release, wouldn't it be a better idea to schedule the inclusion of ODE
>>> for ServiceMix 4.3? It is likely to bring along some additional
>>> dependencies (or dependency versions) and the delay would also give us
>>> time to add some additional features (e.g. have a processes view in
>>> the webconsole or in the shell) or build itests to ensure it
>>> integrates nicely with everything else.
>> In fact, there is no really emergency about ODE integration. So we can
>> postpone this in the SMX 4.3 and 3.3.3 release.
>> If we are all agree, we can release a new components set (2010.01) as soon
>> as Camel 2.2 is release. Once this components set will be released, I
>> propose to release ServiceMix 3.3.2. For ServiceMix 4.2, we are waiting for
>> another bug fix in Felix Karaf.
>> Related to this, what do you think to add a wiki page presenting the roadmap
>> ? In the roadmap, we can define the steps required to cut off a release.
>>
>>> Personally, I would make ODE an optionally installable feature
>>> (similar to what we do for e.g. the wrapper feature). We could make
>>> sure that everything is packaged in the /system folder, so when people
>>> do a features:install ode it can start it quickly and without having
>>> to go and download things. That way, someone who wants to use can get
>>> it "swiftly and with style", but we're not adding any more bundles to
>>> slow down startup for the rest of our users.
>> Agree, the most important is to provide ODE in the distribution and let the
>> user enable it or not.
>>
>> Regards
>> JB
>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>> Blog: http://gertvanthienen.blogspot.com/
>>>
>>>
>>>
>>> On 10 February 2010 12:18, Charles Moulliard <cm...@gmail.com> wrote:
>>>> There is an implementation for that
>>>>
>>>> http://www.jopera.org/docs/publications/2008/bpel4rest
>>>>
>>>> Charles
>>>>
>>>>
>>>> On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré
>>>> <jb...@nanthrax.net>wrote:
>>>>
>>>>> Charles, CXF provides JAX-RS implementation. So basicly, we can have
>>>>> support for REST annotations. However, as RESTful web services couldn't
>>>>> have
>>>>> XML payload, it's not easy to use in the NMR.
>>>>> Maybe we need to discuss about RESTful and NMR support with the team.
>>>>> Any
>>>>> idea is welcome :)
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> Charles Moulliard wrote:
>>>>>
>>>>>> ++1
>>>>>>
>>>>>> I'm not a fan of an orchestration engine but I must admit that in some
>>>>>> situations orchestration is required. The advantage of what
>>>>>> Jean-Baptiste
>>>>>> proposes is that we can expose the (JBI) endpoints of the ServiceMix
>>>>>> platform as WebServices (or why not RESTfull services) and so we can
>>>>>> orchestrate the communication between the existing components in an
>>>>>> easiest
>>>>>> way. Transforming any endpoint into a WebService (RESTfull service))
>>>>>> could
>>>>>> be interesting to integrate/interconnect platforms together or allow
>>>>>> external package to work with our SMX (like Siebel, ....)
>>>>>>
>>>>>> Kind regards,
>>>>>>
>>>>>> Charles Moulliard
>>>>>> Senior Enterprise Architect
>>>>>> Apache Camel Committer
>>>>>>
>>>>>> *****************************
>>>>>> blog : http://cmoulliard.blogspot.com
>>>>>> twitter : http://twitter.com/cmoulliard
>>>>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>>>>
>>>>>> Apache Camel Group :
>>>>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>>>> wrote:
>>>>>> Hi guys,
>>>>>>> I would like to discuss the possibility to include Apache ODE by
>>>>>>> default
>>>>>>> in
>>>>>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>>>>>>> 4.4.2).
>>>>>>>
>>>>>>> As I'm working on WSDL/WebServices support in ServiceMix components,
>>>>>>> it
>>>>>>> can
>>>>>>> be great for the users to have the capability to make services
>>>>>>> orchestration
>>>>>>> using ODE.
>>>>>>>
>>>>>>> What do you think ?
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
Actually, there's another GSoC this year and the ASF are participating
in it again, so if nobody has picked that up in a month or so when the
proposals have to go in, this might be a good candidate for a GSoC
project.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On 10 February 2010 14:04, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi Gert,
>
> My comments inline:
>
>> I agree that ODE would make a very nice addition for ServiceMix.
>> However, I seem to recall it needed some extra work to get it working
>> in ServiceMix 4 as the JBI SE they have had some dependencies on
>> ServiceMix 3 (I might be wrong here though).
>
> I plan to create a jira task about this to clearly identify the issues that
> we have.
> Totally agree that we need to perform tests. That's why I propose to add:
> - a SMX ODE component (based on ODE component itself): this project will
> mainly host unit tests and integration tests to validate the ODE deploys and
> runs correctly on SMX3 and SMX4
> - add a servicemix-ode feature to provide installable feature for SMX4.
>
>>
>> Given that we're trying to stabilize things down for the 4.2.0
>> release, wouldn't it be a better idea to schedule the inclusion of ODE
>> for ServiceMix 4.3? It is likely to bring along some additional
>> dependencies (or dependency versions) and the delay would also give us
>> time to add some additional features (e.g. have a processes view in
>> the webconsole or in the shell) or build itests to ensure it
>> integrates nicely with everything else.
>
> In fact, there is no really emergency about ODE integration. So we can
> postpone this in the SMX 4.3 and 3.3.3 release.
> If we are all agree, we can release a new components set (2010.01) as soon
> as Camel 2.2 is release. Once this components set will be released, I
> propose to release ServiceMix 3.3.2. For ServiceMix 4.2, we are waiting for
> another bug fix in Felix Karaf.
> Related to this, what do you think to add a wiki page presenting the roadmap
> ? In the roadmap, we can define the steps required to cut off a release.
>
>>
>> Personally, I would make ODE an optionally installable feature
>> (similar to what we do for e.g. the wrapper feature). We could make
>> sure that everything is packaged in the /system folder, so when people
>> do a features:install ode it can start it quickly and without having
>> to go and download things. That way, someone who wants to use can get
>> it "swiftly and with style", but we're not adding any more bundles to
>> slow down startup for the rest of our users.
>
> Agree, the most important is to provide ODE in the distribution and let the
> user enable it or not.
>
> Regards
> JB
>
>>
>> Regards,
>>
>> Gert Vanthienen
>> ------------------------
>> Open Source SOA: http://fusesource.com
>> Blog: http://gertvanthienen.blogspot.com/
>>
>>
>>
>> On 10 February 2010 12:18, Charles Moulliard <cm...@gmail.com> wrote:
>>>
>>> There is an implementation for that
>>>
>>> http://www.jopera.org/docs/publications/2008/bpel4rest
>>>
>>> Charles
>>>
>>>
>>> On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré
>>> <jb...@nanthrax.net>wrote:
>>>
>>>> Charles, CXF provides JAX-RS implementation. So basicly, we can have
>>>> support for REST annotations. However, as RESTful web services couldn't
>>>> have
>>>> XML payload, it's not easy to use in the NMR.
>>>> Maybe we need to discuss about RESTful and NMR support with the team.
>>>> Any
>>>> idea is welcome :)
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> Charles Moulliard wrote:
>>>>
>>>>> ++1
>>>>>
>>>>> I'm not a fan of an orchestration engine but I must admit that in some
>>>>> situations orchestration is required. The advantage of what
>>>>> Jean-Baptiste
>>>>> proposes is that we can expose the (JBI) endpoints of the ServiceMix
>>>>> platform as WebServices (or why not RESTfull services) and so we can
>>>>> orchestrate the communication between the existing components in an
>>>>> easiest
>>>>> way. Transforming any endpoint into a WebService (RESTfull service))
>>>>> could
>>>>> be interesting to integrate/interconnect platforms together or allow
>>>>> external package to work with our SMX (like Siebel, ....)
>>>>>
>>>>> Kind regards,
>>>>>
>>>>> Charles Moulliard
>>>>> Senior Enterprise Architect
>>>>> Apache Camel Committer
>>>>>
>>>>> *****************************
>>>>> blog : http://cmoulliard.blogspot.com
>>>>> twitter : http://twitter.com/cmoulliard
>>>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>>>
>>>>> Apache Camel Group :
>>>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>>>
>>>>>
>>>>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>>>
>>>>>> wrote:
>>>>>
>>>>> Hi guys,
>>>>>>
>>>>>> I would like to discuss the possibility to include Apache ODE by
>>>>>> default
>>>>>> in
>>>>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>>>>>> 4.4.2).
>>>>>>
>>>>>> As I'm working on WSDL/WebServices support in ServiceMix components,
>>>>>> it
>>>>>> can
>>>>>> be great for the users to have the capability to make services
>>>>>> orchestration
>>>>>> using ODE.
>>>>>>
>>>>>> What do you think ?
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Gert,
My comments inline:
> I agree that ODE would make a very nice addition for ServiceMix.
> However, I seem to recall it needed some extra work to get it working
> in ServiceMix 4 as the JBI SE they have had some dependencies on
> ServiceMix 3 (I might be wrong here though).
I plan to create a jira task about this to clearly identify the issues
that we have.
Totally agree that we need to perform tests. That's why I propose to add:
- a SMX ODE component (based on ODE component itself): this project will
mainly host unit tests and integration tests to validate the ODE deploys
and runs correctly on SMX3 and SMX4
- add a servicemix-ode feature to provide installable feature for SMX4.
>
> Given that we're trying to stabilize things down for the 4.2.0
> release, wouldn't it be a better idea to schedule the inclusion of ODE
> for ServiceMix 4.3? It is likely to bring along some additional
> dependencies (or dependency versions) and the delay would also give us
> time to add some additional features (e.g. have a processes view in
> the webconsole or in the shell) or build itests to ensure it
> integrates nicely with everything else.
In fact, there is no really emergency about ODE integration. So we can
postpone this in the SMX 4.3 and 3.3.3 release.
If we are all agree, we can release a new components set (2010.01) as
soon as Camel 2.2 is release. Once this components set will be released,
I propose to release ServiceMix 3.3.2. For ServiceMix 4.2, we are
waiting for another bug fix in Felix Karaf.
Related to this, what do you think to add a wiki page presenting the
roadmap ? In the roadmap, we can define the steps required to cut off a
release.
>
> Personally, I would make ODE an optionally installable feature
> (similar to what we do for e.g. the wrapper feature). We could make
> sure that everything is packaged in the /system folder, so when people
> do a features:install ode it can start it quickly and without having
> to go and download things. That way, someone who wants to use can get
> it "swiftly and with style", but we're not adding any more bundles to
> slow down startup for the rest of our users.
Agree, the most important is to provide ODE in the distribution and let
the user enable it or not.
Regards
JB
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 10 February 2010 12:18, Charles Moulliard <cm...@gmail.com> wrote:
>> There is an implementation for that
>>
>> http://www.jopera.org/docs/publications/2008/bpel4rest
>>
>> Charles
>>
>>
>> On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>>
>>> Charles, CXF provides JAX-RS implementation. So basicly, we can have
>>> support for REST annotations. However, as RESTful web services couldn't have
>>> XML payload, it's not easy to use in the NMR.
>>> Maybe we need to discuss about RESTful and NMR support with the team. Any
>>> idea is welcome :)
>>>
>>> Regards
>>> JB
>>>
>>>
>>> Charles Moulliard wrote:
>>>
>>>> ++1
>>>>
>>>> I'm not a fan of an orchestration engine but I must admit that in some
>>>> situations orchestration is required. The advantage of what Jean-Baptiste
>>>> proposes is that we can expose the (JBI) endpoints of the ServiceMix
>>>> platform as WebServices (or why not RESTfull services) and so we can
>>>> orchestrate the communication between the existing components in an
>>>> easiest
>>>> way. Transforming any endpoint into a WebService (RESTfull service)) could
>>>> be interesting to integrate/interconnect platforms together or allow
>>>> external package to work with our SMX (like Siebel, ....)
>>>>
>>>> Kind regards,
>>>>
>>>> Charles Moulliard
>>>> Senior Enterprise Architect
>>>> Apache Camel Committer
>>>>
>>>> *****************************
>>>> blog : http://cmoulliard.blogspot.com
>>>> twitter : http://twitter.com/cmoulliard
>>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>>
>>>> Apache Camel Group :
>>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>>
>>>>
>>>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>> wrote:
>>>> Hi guys,
>>>>> I would like to discuss the possibility to include Apache ODE by default
>>>>> in
>>>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>>>>> 4.4.2).
>>>>>
>>>>> As I'm working on WSDL/WebServices support in ServiceMix components, it
>>>>> can
>>>>> be great for the users to have the capability to make services
>>>>> orchestration
>>>>> using ODE.
>>>>>
>>>>> What do you think ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Freeman Fang <fr...@gmail.com>.
+1 for Gert's suggestion
Freeman
On 2010-2-10, at 下午8:14, Gert Vanthienen wrote:
> L.S.,
>
> I agree that ODE would make a very nice addition for ServiceMix.
> However, I seem to recall it needed some extra work to get it working
> in ServiceMix 4 as the JBI SE they have had some dependencies on
> ServiceMix 3 (I might be wrong here though).
>
> Given that we're trying to stabilize things down for the 4.2.0
> release, wouldn't it be a better idea to schedule the inclusion of ODE
> for ServiceMix 4.3? It is likely to bring along some additional
> dependencies (or dependency versions) and the delay would also give us
> time to add some additional features (e.g. have a processes view in
> the webconsole or in the shell) or build itests to ensure it
> integrates nicely with everything else.
>
> Personally, I would make ODE an optionally installable feature
> (similar to what we do for e.g. the wrapper feature). We could make
> sure that everything is packaged in the /system folder, so when people
> do a features:install ode it can start it quickly and without having
> to go and download things. That way, someone who wants to use can get
> it "swiftly and with style", but we're not adding any more bundles to
> slow down startup for the rest of our users.
>
> Regards,
>
> Gert Vanthienen
> ------------------------
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 10 February 2010 12:18, Charles Moulliard <cm...@gmail.com>
> wrote:
>> There is an implementation for that
>>
>> http://www.jopera.org/docs/publications/2008/bpel4rest
>>
>> Charles
>>
>>
>> On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré <jb@nanthrax.ne
>> t>wrote:
>>
>>> Charles, CXF provides JAX-RS implementation. So basicly, we can have
>>> support for REST annotations. However, as RESTful web services
>>> couldn't have
>>> XML payload, it's not easy to use in the NMR.
>>> Maybe we need to discuss about RESTful and NMR support with the
>>> team. Any
>>> idea is welcome :)
>>>
>>> Regards
>>> JB
>>>
>>>
>>> Charles Moulliard wrote:
>>>
>>>> ++1
>>>>
>>>> I'm not a fan of an orchestration engine but I must admit that in
>>>> some
>>>> situations orchestration is required. The advantage of what Jean-
>>>> Baptiste
>>>> proposes is that we can expose the (JBI) endpoints of the
>>>> ServiceMix
>>>> platform as WebServices (or why not RESTfull services) and so we
>>>> can
>>>> orchestrate the communication between the existing components in an
>>>> easiest
>>>> way. Transforming any endpoint into a WebService (RESTfull
>>>> service)) could
>>>> be interesting to integrate/interconnect platforms together or
>>>> allow
>>>> external package to work with our SMX (like Siebel, ....)
>>>>
>>>> Kind regards,
>>>>
>>>> Charles Moulliard
>>>> Senior Enterprise Architect
>>>> Apache Camel Committer
>>>>
>>>> *****************************
>>>> blog : http://cmoulliard.blogspot.com
>>>> twitter : http://twitter.com/cmoulliard
>>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>>
>>>> Apache Camel Group :
>>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>>
>>>>
>>>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb@nanthrax.ne
>>>> t
>>>>> wrote:
>>>>
>>>> Hi guys,
>>>>>
>>>>> I would like to discuss the possibility to include Apache ODE by
>>>>> default
>>>>> in
>>>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and
>>>>> ServiceMix
>>>>> 4.4.2).
>>>>>
>>>>> As I'm working on WSDL/WebServices support in ServiceMix
>>>>> components, it
>>>>> can
>>>>> be great for the users to have the capability to make services
>>>>> orchestration
>>>>> using ODE.
>>>>>
>>>>> What do you think ?
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>
>>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
I agree that ODE would make a very nice addition for ServiceMix.
However, I seem to recall it needed some extra work to get it working
in ServiceMix 4 as the JBI SE they have had some dependencies on
ServiceMix 3 (I might be wrong here though).
Given that we're trying to stabilize things down for the 4.2.0
release, wouldn't it be a better idea to schedule the inclusion of ODE
for ServiceMix 4.3? It is likely to bring along some additional
dependencies (or dependency versions) and the delay would also give us
time to add some additional features (e.g. have a processes view in
the webconsole or in the shell) or build itests to ensure it
integrates nicely with everything else.
Personally, I would make ODE an optionally installable feature
(similar to what we do for e.g. the wrapper feature). We could make
sure that everything is packaged in the /system folder, so when people
do a features:install ode it can start it quickly and without having
to go and download things. That way, someone who wants to use can get
it "swiftly and with style", but we're not adding any more bundles to
slow down startup for the rest of our users.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
On 10 February 2010 12:18, Charles Moulliard <cm...@gmail.com> wrote:
> There is an implementation for that
>
> http://www.jopera.org/docs/publications/2008/bpel4rest
>
> Charles
>
>
> On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Charles, CXF provides JAX-RS implementation. So basicly, we can have
>> support for REST annotations. However, as RESTful web services couldn't have
>> XML payload, it's not easy to use in the NMR.
>> Maybe we need to discuss about RESTful and NMR support with the team. Any
>> idea is welcome :)
>>
>> Regards
>> JB
>>
>>
>> Charles Moulliard wrote:
>>
>>> ++1
>>>
>>> I'm not a fan of an orchestration engine but I must admit that in some
>>> situations orchestration is required. The advantage of what Jean-Baptiste
>>> proposes is that we can expose the (JBI) endpoints of the ServiceMix
>>> platform as WebServices (or why not RESTfull services) and so we can
>>> orchestrate the communication between the existing components in an
>>> easiest
>>> way. Transforming any endpoint into a WebService (RESTfull service)) could
>>> be interesting to integrate/interconnect platforms together or allow
>>> external package to work with our SMX (like Siebel, ....)
>>>
>>> Kind regards,
>>>
>>> Charles Moulliard
>>> Senior Enterprise Architect
>>> Apache Camel Committer
>>>
>>> *****************************
>>> blog : http://cmoulliard.blogspot.com
>>> twitter : http://twitter.com/cmoulliard
>>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>>
>>> Apache Camel Group :
>>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>>
>>>
>>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb@nanthrax.net
>>> >wrote:
>>>
>>> Hi guys,
>>>>
>>>> I would like to discuss the possibility to include Apache ODE by default
>>>> in
>>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>>>> 4.4.2).
>>>>
>>>> As I'm working on WSDL/WebServices support in ServiceMix components, it
>>>> can
>>>> be great for the users to have the capability to make services
>>>> orchestration
>>>> using ODE.
>>>>
>>>> What do you think ?
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>
>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Charles Moulliard <cm...@gmail.com>.
There is an implementation for that
http://www.jopera.org/docs/publications/2008/bpel4rest
Charles
On Wed, Feb 10, 2010 at 11:46 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Charles, CXF provides JAX-RS implementation. So basicly, we can have
> support for REST annotations. However, as RESTful web services couldn't have
> XML payload, it's not easy to use in the NMR.
> Maybe we need to discuss about RESTful and NMR support with the team. Any
> idea is welcome :)
>
> Regards
> JB
>
>
> Charles Moulliard wrote:
>
>> ++1
>>
>> I'm not a fan of an orchestration engine but I must admit that in some
>> situations orchestration is required. The advantage of what Jean-Baptiste
>> proposes is that we can expose the (JBI) endpoints of the ServiceMix
>> platform as WebServices (or why not RESTfull services) and so we can
>> orchestrate the communication between the existing components in an
>> easiest
>> way. Transforming any endpoint into a WebService (RESTfull service)) could
>> be interesting to integrate/interconnect platforms together or allow
>> external package to work with our SMX (like Siebel, ....)
>>
>> Kind regards,
>>
>> Charles Moulliard
>> Senior Enterprise Architect
>> Apache Camel Committer
>>
>> *****************************
>> blog : http://cmoulliard.blogspot.com
>> twitter : http://twitter.com/cmoulliard
>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>
>> Apache Camel Group :
>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>
>>
>> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb@nanthrax.net
>> >wrote:
>>
>> Hi guys,
>>>
>>> I would like to discuss the possibility to include Apache ODE by default
>>> in
>>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>>> 4.4.2).
>>>
>>> As I'm working on WSDL/WebServices support in ServiceMix components, it
>>> can
>>> be great for the users to have the capability to make services
>>> orchestration
>>> using ODE.
>>>
>>> What do you think ?
>>>
>>> Regards
>>> JB
>>>
>>>
>>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Charles, CXF provides JAX-RS implementation. So basicly, we can have
support for REST annotations. However, as RESTful web services couldn't
have XML payload, it's not easy to use in the NMR.
Maybe we need to discuss about RESTful and NMR support with the team.
Any idea is welcome :)
Regards
JB
Charles Moulliard wrote:
> ++1
>
> I'm not a fan of an orchestration engine but I must admit that in some
> situations orchestration is required. The advantage of what Jean-Baptiste
> proposes is that we can expose the (JBI) endpoints of the ServiceMix
> platform as WebServices (or why not RESTfull services) and so we can
> orchestrate the communication between the existing components in an easiest
> way. Transforming any endpoint into a WebService (RESTfull service)) could
> be interesting to integrate/interconnect platforms together or allow
> external package to work with our SMX (like Siebel, ....)
>
> Kind regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Hi guys,
>>
>> I would like to discuss the possibility to include Apache ODE by default in
>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>> 4.4.2).
>>
>> As I'm working on WSDL/WebServices support in ServiceMix components, it can
>> be great for the users to have the capability to make services orchestration
>> using ODE.
>>
>> What do you think ?
>>
>> Regards
>> JB
>>
>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Lars Heinemann <lh...@googlemail.com>.
+1
sounds like a very good idea.
Lars
2010/2/10 Charles Moulliard <cm...@gmail.com>:
> ++1
>
> I'm not a fan of an orchestration engine but I must admit that in some
> situations orchestration is required. The advantage of what Jean-Baptiste
> proposes is that we can expose the (JBI) endpoints of the ServiceMix
> platform as WebServices (or why not RESTfull services) and so we can
> orchestrate the communication between the existing components in an easiest
> way. Transforming any endpoint into a WebService (RESTfull service)) could
> be interesting to integrate/interconnect platforms together or allow
> external package to work with our SMX (like Siebel, ....)
>
> Kind regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
>
>> Hi guys,
>>
>> I would like to discuss the possibility to include Apache ODE by default in
>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>> 4.4.2).
>>
>> As I'm working on WSDL/WebServices support in ServiceMix components, it can
>> be great for the users to have the capability to make services orchestration
>> using ODE.
>>
>> What do you think ?
>>
>> Regards
>> JB
>>
>
--
http://lhein.blogspot.com
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Charles Moulliard <cm...@gmail.com>.
++1
I'm not a fan of an orchestration engine but I must admit that in some
situations orchestration is required. The advantage of what Jean-Baptiste
proposes is that we can expose the (JBI) endpoints of the ServiceMix
platform as WebServices (or why not RESTfull services) and so we can
orchestrate the communication between the existing components in an easiest
way. Transforming any endpoint into a WebService (RESTfull service)) could
be interesting to integrate/interconnect platforms together or allow
external package to work with our SMX (like Siebel, ....)
Kind regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard
Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
On Wed, Feb 10, 2010 at 10:50 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>wrote:
> Hi guys,
>
> I would like to discuss the possibility to include Apache ODE by default in
> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
> 4.4.2).
>
> As I'm working on WSDL/WebServices support in ServiceMix components, it can
> be great for the users to have the capability to make services orchestration
> using ODE.
>
> What do you think ?
>
> Regards
> JB
>
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Lars Heinemann <lh...@googlemail.com>.
I think Gert brought it to the point. The idea with the optional
feature is nice and
we should go for that for version 4.3.
Lars
2010/2/10 Guillaume Nodet <gn...@gmail.com>:
> +1
>
> On Wed, Feb 10, 2010 at 10:50, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Hi guys,
>>
>> I would like to discuss the possibility to include Apache ODE by default in
>> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
>> 4.4.2).
>>
>> As I'm working on WSDL/WebServices support in ServiceMix components, it can
>> be great for the users to have the capability to make services orchestration
>> using ODE.
>>
>> What do you think ?
>>
>> Regards
>> JB
>>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
--
http://lhein.blogspot.com
Re: [DISCUSS] Include ODE by default in ServiceMix distribution
Posted by Guillaume Nodet <gn...@gmail.com>.
+1
On Wed, Feb 10, 2010 at 10:50, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> Hi guys,
>
> I would like to discuss the possibility to include Apache ODE by default in
> ServiceMix distribution (beginning to ServiceMix 3.3.2 and ServiceMix
> 4.4.2).
>
> As I'm working on WSDL/WebServices support in ServiceMix components, it can
> be great for the users to have the capability to make services orchestration
> using ODE.
>
> What do you think ?
>
> Regards
> JB
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com