You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "S. Ali Tokmen" <sa...@bull.net> on 2008/11/17 16:27:49 UTC
Registry/Repository support in CAMEL
Hello
I'm currently working in integrating CAMEL into the JOnAS Application
Server. I had previously worked on Mule and I can tell you that
integrating CAMEL in an application server has been much easier and neater.
When working with CAMEL, one functionality I've found missing is the
Registry/Repository support.
So, I'm asking: has anyone tried linking CAMEL with any registry or
repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
Cheers
--
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Great
Thanks for your help
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Hadrian Zbarcea a écrit :
> I doubt gpl v3 is gonna be a compatible license, as it's crazier than v2.
>
> The link below from Claus's message is the authoritative document.
>
> Cheers
> Hadrian
>
> On Nov 18, 2008, at 6:31 AM, Claus Ibsen wrote:
>
>> Hi
>>
>> You can see the license comp. list here
>> http://www.apache.org/legal/3party.html
>>
>>
>> /Claus Ibsen
>> Apache Camel Committer
>> Blog: http://davsclaus.blogspot.com/
>>
>>
>>
>> On Tue, Nov 18, 2008 at 11:53 AM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>> Hello
>>>
>>> I'll then wait for your reply, I'll also check out if we can change the
>>> license for that module (which is not here yet).
>>>
>>> Regards
>>>
>>> S. Ali Tokmen
>>> savas-ali.tokmen@bull.net
>>>
>>> Office: +33 4 76 29 76 19
>>> GSM: +33 66 43 00 555
>>>
>>> Bull, Architect of an Open World TM
>>> http://www.bull.com
>>>
>>>
>>>
>>> Claus Ibsen a écrit :
>>>>
>>>> Hi
>>>>
>>>> LGPL is afair not a compliant license.
>>>> But GPL v3 might be. This should be confirmed by other Apache people
>>>> that is into the license.
>>>>
>>>> We can host it at camel-extra, but still have the documentation with
>>>> all the other components.
>>>>
>>>>
>>>>
>>>> /Claus Ibsen
>>>> Apache Camel Committer
>>>> Blog: http://davsclaus.blogspot.com/
>>>>
>>>>
>>>>
>>>> On Tue, Nov 18, 2008 at 11:38 AM, S. Ali Tokmen
>>>> <sa...@bull.net> wrote:
>>>>
>>>>>
>>>>> Hello
>>>>>
>>>>> The project will be using an LGPL license (like many other OW2
>>>>> projects).
>>>>> I
>>>>> think LGPL was compatible with most of the other licences, if it
>>>>> is an
>>>>> issue
>>>>> I could ask my project leaders for licensing exceptions.
>>>>>
>>>>> I'll call again once things start running smoothly.
>>>>>
>>>>> Regards
>>>>>
>>>>> S. Ali Tokmen
>>>>> savas-ali.tokmen@bull.net
>>>>>
>>>>> Office: +33 4 76 29 76 19
>>>>> GSM: +33 66 43 00 555
>>>>>
>>>>> Bull, Architect of an Open World TM
>>>>> http://www.bull.com
>>>>>
>>>>>
>>>>>
>>>>> Claus Ibsen a écrit :
>>>>>
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Yes we love contributions:
>>>>>> http://activemq.apache.org/camel/contributing.html
>>>>>>
>>>>>> To be included in the camel distribution out-of-the-box it has to
>>>>>> have
>>>>>> a compliant license.
>>>>>> Using Apache 2.0 license is of course preferred.
>>>>>> However there is a list of compliant licenses somewhere on the
>>>>>> Apache
>>>>>> site. Can't find it at the moment.
>>>>>>
>>>>>>
>>>>>> If using a non compliant license (eg GPL) we have a camel-extra
>>>>>> project for such components:
>>>>>> http://code.google.com/p/camel-extra/
>>>>>> that can host the code.
>>>>>>
>>>>>> But I am sure Hadrian or other that is a bit more into the Apache
>>>>>> will
>>>>>> be able to explain the details.
>>>>>>
>>>>>> So yes keep up the work and if and when you have a component you
>>>>>> would
>>>>>> like to be included we can discuss further.
>>>>>>
>>>>>>
>>>>>> /Claus Ibsen
>>>>>> Apache Camel Committer
>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
>>>>>> <sa...@bull.net> wrote:
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Great news. I'll keep you updated.
>>>>>>>
>>>>>>> FYI, the SVN is on
>>>>>>> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4
>>>>>>> and a
>>>>>>> corresponding CI will be created once the MAVEN integration is OK.
>>>>>>>
>>>>>>> Another question: if I keep the Registry/Repository module as a
>>>>>>> standalone
>>>>>>> MAVEN module (i.e. a module that doesn't depend on my project or
>>>>>>> any
>>>>>>> application server but only on CAMEL), can it be integrated as a
>>>>>>> CAMEL
>>>>>>> example someday? Would it be against any copyright or other
>>>>>>> policy from
>>>>>>> Apache/ActiveMQ/CAMEL?
>>>>>>>
>>>>>>> Regards
>>>>>>>
>>>>>>> S. Ali Tokmen
>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>
>>>>>>> Office: +33 4 76 29 76 19
>>>>>>> GSM: +33 66 43 00 555
>>>>>>>
>>>>>>> Bull, Architect of an Open World TM
>>>>>>> http://www.bull.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Claus Ibsen a écrit :
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Yes please keep us posted and you are very welcome to give
>>>>>>>> feedback on
>>>>>>>> the Camel API if there is something we could do to improve it to
>>>>>>>> better support your use case. As we really would like it to be
>>>>>>>> very
>>>>>>>> easy to integrate with whatever is out there.
>>>>>>>>
>>>>>>>> So we are very interested in your work.
>>>>>>>>
>>>>>>>>
>>>>>>>> /Claus Ibsen
>>>>>>>> Apache Camel Committer
>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>>>>>>>> <sa...@bull.net> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello
>>>>>>>>>
>>>>>>>>> I've also thought about that Registry interface, since I had
>>>>>>>>> to do
>>>>>>>>> some
>>>>>>>>> manual configuration for JNDI (JNDI is not supported
>>>>>>>>> out-of-the-box
>>>>>>>>> for
>>>>>>>>> JMS,
>>>>>>>>> for example).
>>>>>>>>>
>>>>>>>>> Note that the registry/repository support will be done as part
>>>>>>>>> of an
>>>>>>>>> open
>>>>>>>>> source project. It will be providing an API and a "default"
>>>>>>>>> implementation
>>>>>>>>> with File system (XML files).
>>>>>>>>>
>>>>>>>>> Please let me know if you're interested in the details.
>>>>>>>>>
>>>>>>>>> Thank you
>>>>>>>>>
>>>>>>>>> S. Ali Tokmen
>>>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>>>
>>>>>>>>> Office: +33 4 76 29 76 19
>>>>>>>>> GSM: +33 66 43 00 555
>>>>>>>>>
>>>>>>>>> Bull, Architect of an Open World TM
>>>>>>>>> http://www.bull.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Claus Ibsen a écrit :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> This is really a question for James Strachan ;)
>>>>>>>>>>
>>>>>>>>>> You can check out the camel-guice component that he recently
>>>>>>>>>> added
>>>>>>>>>> it
>>>>>>>>>> shows how it integrated with Guice and how camel uses the guice
>>>>>>>>>> context for registry lookup.
>>>>>>>>>> The DefaultCamelContext has a setRegistry(Registry) method
>>>>>>>>>> you can
>>>>>>>>>> call to inject your registry. I also think it has a
>>>>>>>>>> setRegistry that
>>>>>>>>>> support jndi out-of-the-box.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> /Claus Ibsen
>>>>>>>>>> Apache Camel Committer
>>>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>>>>>>>> <sa...@bull.net> wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Hello
>>>>>>>>>>>
>>>>>>>>>>> I'm currently working in integrating CAMEL into the JOnAS
>>>>>>>>>>> Application
>>>>>>>>>>> Server. I had previously worked on Mule and I can tell you that
>>>>>>>>>>> integrating
>>>>>>>>>>> CAMEL in an application server has been much easier and neater.
>>>>>>>>>>>
>>>>>>>>>>> When working with CAMEL, one functionality I've found
>>>>>>>>>>> missing is
>>>>>>>>>>> the
>>>>>>>>>>> Registry/Repository support.
>>>>>>>>>>>
>>>>>>>>>>> So, I'm asking: has anyone tried linking CAMEL with any
>>>>>>>>>>> registry or
>>>>>>>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>>>>>>>
>>>>>>>>>>> Cheers
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>>
>>>>>>>>>>> S. Ali Tokmen
>>>>>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>>>>>
>>>>>>>>>>> Office: +33 4 76 29 76 19
>>>>>>>>>>> GSM: +33 66 43 00 555
>>>>>>>>>>>
>>>>>>>>>>> Bull, Architect of an Open World TM
>>>>>>>>>>> http://www.bull.com
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I doubt gpl v3 is gonna be a compatible license, as it's crazier than
v2.
The link below from Claus's message is the authoritative document.
Cheers
Hadrian
On Nov 18, 2008, at 6:31 AM, Claus Ibsen wrote:
> Hi
>
> You can see the license comp. list here
> http://www.apache.org/legal/3party.html
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Tue, Nov 18, 2008 at 11:53 AM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>> Hello
>>
>> I'll then wait for your reply, I'll also check out if we can change
>> the
>> license for that module (which is not here yet).
>>
>> Regards
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>> Claus Ibsen a écrit :
>>>
>>> Hi
>>>
>>> LGPL is afair not a compliant license.
>>> But GPL v3 might be. This should be confirmed by other Apache people
>>> that is into the license.
>>>
>>> We can host it at camel-extra, but still have the documentation with
>>> all the other components.
>>>
>>>
>>>
>>> /Claus Ibsen
>>> Apache Camel Committer
>>> Blog: http://davsclaus.blogspot.com/
>>>
>>>
>>>
>>> On Tue, Nov 18, 2008 at 11:38 AM, S. Ali Tokmen
>>> <sa...@bull.net> wrote:
>>>
>>>>
>>>> Hello
>>>>
>>>> The project will be using an LGPL license (like many other OW2
>>>> projects).
>>>> I
>>>> think LGPL was compatible with most of the other licences, if it
>>>> is an
>>>> issue
>>>> I could ask my project leaders for licensing exceptions.
>>>>
>>>> I'll call again once things start running smoothly.
>>>>
>>>> Regards
>>>>
>>>> S. Ali Tokmen
>>>> savas-ali.tokmen@bull.net
>>>>
>>>> Office: +33 4 76 29 76 19
>>>> GSM: +33 66 43 00 555
>>>>
>>>> Bull, Architect of an Open World TM
>>>> http://www.bull.com
>>>>
>>>>
>>>>
>>>> Claus Ibsen a écrit :
>>>>
>>>>>
>>>>> Hi
>>>>>
>>>>> Yes we love contributions:
>>>>> http://activemq.apache.org/camel/contributing.html
>>>>>
>>>>> To be included in the camel distribution out-of-the-box it has
>>>>> to have
>>>>> a compliant license.
>>>>> Using Apache 2.0 license is of course preferred.
>>>>> However there is a list of compliant licenses somewhere on the
>>>>> Apache
>>>>> site. Can't find it at the moment.
>>>>>
>>>>>
>>>>> If using a non compliant license (eg GPL) we have a camel-extra
>>>>> project for such components:
>>>>> http://code.google.com/p/camel-extra/
>>>>> that can host the code.
>>>>>
>>>>> But I am sure Hadrian or other that is a bit more into the
>>>>> Apache will
>>>>> be able to explain the details.
>>>>>
>>>>> So yes keep up the work and if and when you have a component you
>>>>> would
>>>>> like to be included we can discuss further.
>>>>>
>>>>>
>>>>> /Claus Ibsen
>>>>> Apache Camel Committer
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
>>>>> <sa...@bull.net> wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> Great news. I'll keep you updated.
>>>>>>
>>>>>> FYI, the SVN is on
>>>>>> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-
>>>>>> jonas4 and a
>>>>>> corresponding CI will be created once the MAVEN integration is
>>>>>> OK.
>>>>>>
>>>>>> Another question: if I keep the Registry/Repository module as a
>>>>>> standalone
>>>>>> MAVEN module (i.e. a module that doesn't depend on my project
>>>>>> or any
>>>>>> application server but only on CAMEL), can it be integrated as
>>>>>> a CAMEL
>>>>>> example someday? Would it be against any copyright or other
>>>>>> policy from
>>>>>> Apache/ActiveMQ/CAMEL?
>>>>>>
>>>>>> Regards
>>>>>>
>>>>>> S. Ali Tokmen
>>>>>> savas-ali.tokmen@bull.net
>>>>>>
>>>>>> Office: +33 4 76 29 76 19
>>>>>> GSM: +33 66 43 00 555
>>>>>>
>>>>>> Bull, Architect of an Open World TM
>>>>>> http://www.bull.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> Claus Ibsen a écrit :
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> Yes please keep us posted and you are very welcome to give
>>>>>>> feedback on
>>>>>>> the Camel API if there is something we could do to improve it to
>>>>>>> better support your use case. As we really would like it to be
>>>>>>> very
>>>>>>> easy to integrate with whatever is out there.
>>>>>>>
>>>>>>> So we are very interested in your work.
>>>>>>>
>>>>>>>
>>>>>>> /Claus Ibsen
>>>>>>> Apache Camel Committer
>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>>>>>>> <sa...@bull.net> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Hello
>>>>>>>>
>>>>>>>> I've also thought about that Registry interface, since I had
>>>>>>>> to do
>>>>>>>> some
>>>>>>>> manual configuration for JNDI (JNDI is not supported out-of-
>>>>>>>> the-box
>>>>>>>> for
>>>>>>>> JMS,
>>>>>>>> for example).
>>>>>>>>
>>>>>>>> Note that the registry/repository support will be done as
>>>>>>>> part of an
>>>>>>>> open
>>>>>>>> source project. It will be providing an API and a "default"
>>>>>>>> implementation
>>>>>>>> with File system (XML files).
>>>>>>>>
>>>>>>>> Please let me know if you're interested in the details.
>>>>>>>>
>>>>>>>> Thank you
>>>>>>>>
>>>>>>>> S. Ali Tokmen
>>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>>
>>>>>>>> Office: +33 4 76 29 76 19
>>>>>>>> GSM: +33 66 43 00 555
>>>>>>>>
>>>>>>>> Bull, Architect of an Open World TM
>>>>>>>> http://www.bull.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Claus Ibsen a écrit :
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hi
>>>>>>>>>
>>>>>>>>> This is really a question for James Strachan ;)
>>>>>>>>>
>>>>>>>>> You can check out the camel-guice component that he recently
>>>>>>>>> added
>>>>>>>>> it
>>>>>>>>> shows how it integrated with Guice and how camel uses the
>>>>>>>>> guice
>>>>>>>>> context for registry lookup.
>>>>>>>>> The DefaultCamelContext has a setRegistry(Registry) method
>>>>>>>>> you can
>>>>>>>>> call to inject your registry. I also think it has a
>>>>>>>>> setRegistry that
>>>>>>>>> support jndi out-of-the-box.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> /Claus Ibsen
>>>>>>>>> Apache Camel Committer
>>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>>>>>>> <sa...@bull.net> wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hello
>>>>>>>>>>
>>>>>>>>>> I'm currently working in integrating CAMEL into the JOnAS
>>>>>>>>>> Application
>>>>>>>>>> Server. I had previously worked on Mule and I can tell you
>>>>>>>>>> that
>>>>>>>>>> integrating
>>>>>>>>>> CAMEL in an application server has been much easier and
>>>>>>>>>> neater.
>>>>>>>>>>
>>>>>>>>>> When working with CAMEL, one functionality I've found
>>>>>>>>>> missing is
>>>>>>>>>> the
>>>>>>>>>> Registry/Repository support.
>>>>>>>>>>
>>>>>>>>>> So, I'm asking: has anyone tried linking CAMEL with any
>>>>>>>>>> registry or
>>>>>>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>>>>>>
>>>>>>>>>> Cheers
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>> S. Ali Tokmen
>>>>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>>>>
>>>>>>>>>> Office: +33 4 76 29 76 19
>>>>>>>>>> GSM: +33 66 43 00 555
>>>>>>>>>>
>>>>>>>>>> Bull, Architect of an Open World TM
>>>>>>>>>> http://www.bull.com
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
You can see the license comp. list here
http://www.apache.org/legal/3party.html
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Tue, Nov 18, 2008 at 11:53 AM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Hello
>
> I'll then wait for your reply, I'll also check out if we can change the
> license for that module (which is not here yet).
>
> Regards
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Claus Ibsen a écrit :
>>
>> Hi
>>
>> LGPL is afair not a compliant license.
>> But GPL v3 might be. This should be confirmed by other Apache people
>> that is into the license.
>>
>> We can host it at camel-extra, but still have the documentation with
>> all the other components.
>>
>>
>>
>> /Claus Ibsen
>> Apache Camel Committer
>> Blog: http://davsclaus.blogspot.com/
>>
>>
>>
>> On Tue, Nov 18, 2008 at 11:38 AM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>
>>>
>>> Hello
>>>
>>> The project will be using an LGPL license (like many other OW2 projects).
>>> I
>>> think LGPL was compatible with most of the other licences, if it is an
>>> issue
>>> I could ask my project leaders for licensing exceptions.
>>>
>>> I'll call again once things start running smoothly.
>>>
>>> Regards
>>>
>>> S. Ali Tokmen
>>> savas-ali.tokmen@bull.net
>>>
>>> Office: +33 4 76 29 76 19
>>> GSM: +33 66 43 00 555
>>>
>>> Bull, Architect of an Open World TM
>>> http://www.bull.com
>>>
>>>
>>>
>>> Claus Ibsen a écrit :
>>>
>>>>
>>>> Hi
>>>>
>>>> Yes we love contributions:
>>>> http://activemq.apache.org/camel/contributing.html
>>>>
>>>> To be included in the camel distribution out-of-the-box it has to have
>>>> a compliant license.
>>>> Using Apache 2.0 license is of course preferred.
>>>> However there is a list of compliant licenses somewhere on the Apache
>>>> site. Can't find it at the moment.
>>>>
>>>>
>>>> If using a non compliant license (eg GPL) we have a camel-extra
>>>> project for such components:
>>>> http://code.google.com/p/camel-extra/
>>>> that can host the code.
>>>>
>>>> But I am sure Hadrian or other that is a bit more into the Apache will
>>>> be able to explain the details.
>>>>
>>>> So yes keep up the work and if and when you have a component you would
>>>> like to be included we can discuss further.
>>>>
>>>>
>>>> /Claus Ibsen
>>>> Apache Camel Committer
>>>> Blog: http://davsclaus.blogspot.com/
>>>>
>>>>
>>>>
>>>> On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
>>>> <sa...@bull.net> wrote:
>>>>
>>>>
>>>>>
>>>>> Great news. I'll keep you updated.
>>>>>
>>>>> FYI, the SVN is on
>>>>> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4 and a
>>>>> corresponding CI will be created once the MAVEN integration is OK.
>>>>>
>>>>> Another question: if I keep the Registry/Repository module as a
>>>>> standalone
>>>>> MAVEN module (i.e. a module that doesn't depend on my project or any
>>>>> application server but only on CAMEL), can it be integrated as a CAMEL
>>>>> example someday? Would it be against any copyright or other policy from
>>>>> Apache/ActiveMQ/CAMEL?
>>>>>
>>>>> Regards
>>>>>
>>>>> S. Ali Tokmen
>>>>> savas-ali.tokmen@bull.net
>>>>>
>>>>> Office: +33 4 76 29 76 19
>>>>> GSM: +33 66 43 00 555
>>>>>
>>>>> Bull, Architect of an Open World TM
>>>>> http://www.bull.com
>>>>>
>>>>>
>>>>>
>>>>> Claus Ibsen a écrit :
>>>>>
>>>>>
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> Yes please keep us posted and you are very welcome to give feedback on
>>>>>> the Camel API if there is something we could do to improve it to
>>>>>> better support your use case. As we really would like it to be very
>>>>>> easy to integrate with whatever is out there.
>>>>>>
>>>>>> So we are very interested in your work.
>>>>>>
>>>>>>
>>>>>> /Claus Ibsen
>>>>>> Apache Camel Committer
>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>>>>>> <sa...@bull.net> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Hello
>>>>>>>
>>>>>>> I've also thought about that Registry interface, since I had to do
>>>>>>> some
>>>>>>> manual configuration for JNDI (JNDI is not supported out-of-the-box
>>>>>>> for
>>>>>>> JMS,
>>>>>>> for example).
>>>>>>>
>>>>>>> Note that the registry/repository support will be done as part of an
>>>>>>> open
>>>>>>> source project. It will be providing an API and a "default"
>>>>>>> implementation
>>>>>>> with File system (XML files).
>>>>>>>
>>>>>>> Please let me know if you're interested in the details.
>>>>>>>
>>>>>>> Thank you
>>>>>>>
>>>>>>> S. Ali Tokmen
>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>
>>>>>>> Office: +33 4 76 29 76 19
>>>>>>> GSM: +33 66 43 00 555
>>>>>>>
>>>>>>> Bull, Architect of an Open World TM
>>>>>>> http://www.bull.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Claus Ibsen a écrit :
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> This is really a question for James Strachan ;)
>>>>>>>>
>>>>>>>> You can check out the camel-guice component that he recently added
>>>>>>>> it
>>>>>>>> shows how it integrated with Guice and how camel uses the guice
>>>>>>>> context for registry lookup.
>>>>>>>> The DefaultCamelContext has a setRegistry(Registry) method you can
>>>>>>>> call to inject your registry. I also think it has a setRegistry that
>>>>>>>> support jndi out-of-the-box.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> /Claus Ibsen
>>>>>>>> Apache Camel Committer
>>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>>>>>> <sa...@bull.net> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Hello
>>>>>>>>>
>>>>>>>>> I'm currently working in integrating CAMEL into the JOnAS
>>>>>>>>> Application
>>>>>>>>> Server. I had previously worked on Mule and I can tell you that
>>>>>>>>> integrating
>>>>>>>>> CAMEL in an application server has been much easier and neater.
>>>>>>>>>
>>>>>>>>> When working with CAMEL, one functionality I've found missing is
>>>>>>>>> the
>>>>>>>>> Registry/Repository support.
>>>>>>>>>
>>>>>>>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>>>>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>>>>>
>>>>>>>>> Cheers
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> S. Ali Tokmen
>>>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>>>
>>>>>>>>> Office: +33 4 76 29 76 19
>>>>>>>>> GSM: +33 66 43 00 555
>>>>>>>>>
>>>>>>>>> Bull, Architect of an Open World TM
>>>>>>>>> http://www.bull.com
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>
>
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello
I'll then wait for your reply, I'll also check out if we can change the
license for that module (which is not here yet).
Regards
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> Hi
>
> LGPL is afair not a compliant license.
> But GPL v3 might be. This should be confirmed by other Apache people
> that is into the license.
>
> We can host it at camel-extra, but still have the documentation with
> all the other components.
>
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Tue, Nov 18, 2008 at 11:38 AM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Hello
>>
>> The project will be using an LGPL license (like many other OW2 projects). I
>> think LGPL was compatible with most of the other licences, if it is an issue
>> I could ask my project leaders for licensing exceptions.
>>
>> I'll call again once things start running smoothly.
>>
>> Regards
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>> Claus Ibsen a écrit :
>>
>>> Hi
>>>
>>> Yes we love contributions:
>>> http://activemq.apache.org/camel/contributing.html
>>>
>>> To be included in the camel distribution out-of-the-box it has to have
>>> a compliant license.
>>> Using Apache 2.0 license is of course preferred.
>>> However there is a list of compliant licenses somewhere on the Apache
>>> site. Can't find it at the moment.
>>>
>>>
>>> If using a non compliant license (eg GPL) we have a camel-extra
>>> project for such components:
>>> http://code.google.com/p/camel-extra/
>>> that can host the code.
>>>
>>> But I am sure Hadrian or other that is a bit more into the Apache will
>>> be able to explain the details.
>>>
>>> So yes keep up the work and if and when you have a component you would
>>> like to be included we can discuss further.
>>>
>>>
>>> /Claus Ibsen
>>> Apache Camel Committer
>>> Blog: http://davsclaus.blogspot.com/
>>>
>>>
>>>
>>> On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
>>> <sa...@bull.net> wrote:
>>>
>>>
>>>> Great news. I'll keep you updated.
>>>>
>>>> FYI, the SVN is on
>>>> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4 and a
>>>> corresponding CI will be created once the MAVEN integration is OK.
>>>>
>>>> Another question: if I keep the Registry/Repository module as a
>>>> standalone
>>>> MAVEN module (i.e. a module that doesn't depend on my project or any
>>>> application server but only on CAMEL), can it be integrated as a CAMEL
>>>> example someday? Would it be against any copyright or other policy from
>>>> Apache/ActiveMQ/CAMEL?
>>>>
>>>> Regards
>>>>
>>>> S. Ali Tokmen
>>>> savas-ali.tokmen@bull.net
>>>>
>>>> Office: +33 4 76 29 76 19
>>>> GSM: +33 66 43 00 555
>>>>
>>>> Bull, Architect of an Open World TM
>>>> http://www.bull.com
>>>>
>>>>
>>>>
>>>> Claus Ibsen a écrit :
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> Yes please keep us posted and you are very welcome to give feedback on
>>>>> the Camel API if there is something we could do to improve it to
>>>>> better support your use case. As we really would like it to be very
>>>>> easy to integrate with whatever is out there.
>>>>>
>>>>> So we are very interested in your work.
>>>>>
>>>>>
>>>>> /Claus Ibsen
>>>>> Apache Camel Committer
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>>>>> <sa...@bull.net> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hello
>>>>>>
>>>>>> I've also thought about that Registry interface, since I had to do some
>>>>>> manual configuration for JNDI (JNDI is not supported out-of-the-box for
>>>>>> JMS,
>>>>>> for example).
>>>>>>
>>>>>> Note that the registry/repository support will be done as part of an
>>>>>> open
>>>>>> source project. It will be providing an API and a "default"
>>>>>> implementation
>>>>>> with File system (XML files).
>>>>>>
>>>>>> Please let me know if you're interested in the details.
>>>>>>
>>>>>> Thank you
>>>>>>
>>>>>> S. Ali Tokmen
>>>>>> savas-ali.tokmen@bull.net
>>>>>>
>>>>>> Office: +33 4 76 29 76 19
>>>>>> GSM: +33 66 43 00 555
>>>>>>
>>>>>> Bull, Architect of an Open World TM
>>>>>> http://www.bull.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> Claus Ibsen a écrit :
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Hi
>>>>>>>
>>>>>>> This is really a question for James Strachan ;)
>>>>>>>
>>>>>>> You can check out the camel-guice component that he recently added it
>>>>>>> shows how it integrated with Guice and how camel uses the guice
>>>>>>> context for registry lookup.
>>>>>>> The DefaultCamelContext has a setRegistry(Registry) method you can
>>>>>>> call to inject your registry. I also think it has a setRegistry that
>>>>>>> support jndi out-of-the-box.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> /Claus Ibsen
>>>>>>> Apache Camel Committer
>>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>>>>> <sa...@bull.net> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Hello
>>>>>>>>
>>>>>>>> I'm currently working in integrating CAMEL into the JOnAS Application
>>>>>>>> Server. I had previously worked on Mule and I can tell you that
>>>>>>>> integrating
>>>>>>>> CAMEL in an application server has been much easier and neater.
>>>>>>>>
>>>>>>>> When working with CAMEL, one functionality I've found missing is the
>>>>>>>> Registry/Repository support.
>>>>>>>>
>>>>>>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>>>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>>
>>>>>>>> --
>>>>>>>>
>>>>>>>> S. Ali Tokmen
>>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>>
>>>>>>>> Office: +33 4 76 29 76 19
>>>>>>>> GSM: +33 66 43 00 555
>>>>>>>>
>>>>>>>> Bull, Architect of an Open World TM
>>>>>>>> http://www.bull.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
LGPL is afair not a compliant license.
But GPL v3 might be. This should be confirmed by other Apache people
that is into the license.
We can host it at camel-extra, but still have the documentation with
all the other components.
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Tue, Nov 18, 2008 at 11:38 AM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Hello
>
> The project will be using an LGPL license (like many other OW2 projects). I
> think LGPL was compatible with most of the other licences, if it is an issue
> I could ask my project leaders for licensing exceptions.
>
> I'll call again once things start running smoothly.
>
> Regards
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Claus Ibsen a écrit :
>>
>> Hi
>>
>> Yes we love contributions:
>> http://activemq.apache.org/camel/contributing.html
>>
>> To be included in the camel distribution out-of-the-box it has to have
>> a compliant license.
>> Using Apache 2.0 license is of course preferred.
>> However there is a list of compliant licenses somewhere on the Apache
>> site. Can't find it at the moment.
>>
>>
>> If using a non compliant license (eg GPL) we have a camel-extra
>> project for such components:
>> http://code.google.com/p/camel-extra/
>> that can host the code.
>>
>> But I am sure Hadrian or other that is a bit more into the Apache will
>> be able to explain the details.
>>
>> So yes keep up the work and if and when you have a component you would
>> like to be included we can discuss further.
>>
>>
>> /Claus Ibsen
>> Apache Camel Committer
>> Blog: http://davsclaus.blogspot.com/
>>
>>
>>
>> On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>
>>>
>>> Great news. I'll keep you updated.
>>>
>>> FYI, the SVN is on
>>> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4 and a
>>> corresponding CI will be created once the MAVEN integration is OK.
>>>
>>> Another question: if I keep the Registry/Repository module as a
>>> standalone
>>> MAVEN module (i.e. a module that doesn't depend on my project or any
>>> application server but only on CAMEL), can it be integrated as a CAMEL
>>> example someday? Would it be against any copyright or other policy from
>>> Apache/ActiveMQ/CAMEL?
>>>
>>> Regards
>>>
>>> S. Ali Tokmen
>>> savas-ali.tokmen@bull.net
>>>
>>> Office: +33 4 76 29 76 19
>>> GSM: +33 66 43 00 555
>>>
>>> Bull, Architect of an Open World TM
>>> http://www.bull.com
>>>
>>>
>>>
>>> Claus Ibsen a écrit :
>>>
>>>>
>>>> Hi
>>>>
>>>> Yes please keep us posted and you are very welcome to give feedback on
>>>> the Camel API if there is something we could do to improve it to
>>>> better support your use case. As we really would like it to be very
>>>> easy to integrate with whatever is out there.
>>>>
>>>> So we are very interested in your work.
>>>>
>>>>
>>>> /Claus Ibsen
>>>> Apache Camel Committer
>>>> Blog: http://davsclaus.blogspot.com/
>>>>
>>>>
>>>>
>>>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>>>> <sa...@bull.net> wrote:
>>>>
>>>>
>>>>>
>>>>> Hello
>>>>>
>>>>> I've also thought about that Registry interface, since I had to do some
>>>>> manual configuration for JNDI (JNDI is not supported out-of-the-box for
>>>>> JMS,
>>>>> for example).
>>>>>
>>>>> Note that the registry/repository support will be done as part of an
>>>>> open
>>>>> source project. It will be providing an API and a "default"
>>>>> implementation
>>>>> with File system (XML files).
>>>>>
>>>>> Please let me know if you're interested in the details.
>>>>>
>>>>> Thank you
>>>>>
>>>>> S. Ali Tokmen
>>>>> savas-ali.tokmen@bull.net
>>>>>
>>>>> Office: +33 4 76 29 76 19
>>>>> GSM: +33 66 43 00 555
>>>>>
>>>>> Bull, Architect of an Open World TM
>>>>> http://www.bull.com
>>>>>
>>>>>
>>>>>
>>>>> Claus Ibsen a écrit :
>>>>>
>>>>>
>>>>>>
>>>>>> Hi
>>>>>>
>>>>>> This is really a question for James Strachan ;)
>>>>>>
>>>>>> You can check out the camel-guice component that he recently added it
>>>>>> shows how it integrated with Guice and how camel uses the guice
>>>>>> context for registry lookup.
>>>>>> The DefaultCamelContext has a setRegistry(Registry) method you can
>>>>>> call to inject your registry. I also think it has a setRegistry that
>>>>>> support jndi out-of-the-box.
>>>>>>
>>>>>>
>>>>>>
>>>>>> /Claus Ibsen
>>>>>> Apache Camel Committer
>>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>>>> <sa...@bull.net> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Hello
>>>>>>>
>>>>>>> I'm currently working in integrating CAMEL into the JOnAS Application
>>>>>>> Server. I had previously worked on Mule and I can tell you that
>>>>>>> integrating
>>>>>>> CAMEL in an application server has been much easier and neater.
>>>>>>>
>>>>>>> When working with CAMEL, one functionality I've found missing is the
>>>>>>> Registry/Repository support.
>>>>>>>
>>>>>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>>>
>>>>>>> Cheers
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> S. Ali Tokmen
>>>>>>> savas-ali.tokmen@bull.net
>>>>>>>
>>>>>>> Office: +33 4 76 29 76 19
>>>>>>> GSM: +33 66 43 00 555
>>>>>>>
>>>>>>> Bull, Architect of an Open World TM
>>>>>>> http://www.bull.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>
>
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello
The project will be using an LGPL license (like many other OW2
projects). I think LGPL was compatible with most of the other licences,
if it is an issue I could ask my project leaders for licensing exceptions.
I'll call again once things start running smoothly.
Regards
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> Hi
>
> Yes we love contributions:
> http://activemq.apache.org/camel/contributing.html
>
> To be included in the camel distribution out-of-the-box it has to have
> a compliant license.
> Using Apache 2.0 license is of course preferred.
> However there is a list of compliant licenses somewhere on the Apache
> site. Can't find it at the moment.
>
>
> If using a non compliant license (eg GPL) we have a camel-extra
> project for such components:
> http://code.google.com/p/camel-extra/
> that can host the code.
>
> But I am sure Hadrian or other that is a bit more into the Apache will
> be able to explain the details.
>
> So yes keep up the work and if and when you have a component you would
> like to be included we can discuss further.
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Great news. I'll keep you updated.
>>
>> FYI, the SVN is on
>> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4 and a
>> corresponding CI will be created once the MAVEN integration is OK.
>>
>> Another question: if I keep the Registry/Repository module as a standalone
>> MAVEN module (i.e. a module that doesn't depend on my project or any
>> application server but only on CAMEL), can it be integrated as a CAMEL
>> example someday? Would it be against any copyright or other policy from
>> Apache/ActiveMQ/CAMEL?
>>
>> Regards
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>> Claus Ibsen a écrit :
>>
>>> Hi
>>>
>>> Yes please keep us posted and you are very welcome to give feedback on
>>> the Camel API if there is something we could do to improve it to
>>> better support your use case. As we really would like it to be very
>>> easy to integrate with whatever is out there.
>>>
>>> So we are very interested in your work.
>>>
>>>
>>> /Claus Ibsen
>>> Apache Camel Committer
>>> Blog: http://davsclaus.blogspot.com/
>>>
>>>
>>>
>>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>>> <sa...@bull.net> wrote:
>>>
>>>
>>>> Hello
>>>>
>>>> I've also thought about that Registry interface, since I had to do some
>>>> manual configuration for JNDI (JNDI is not supported out-of-the-box for
>>>> JMS,
>>>> for example).
>>>>
>>>> Note that the registry/repository support will be done as part of an open
>>>> source project. It will be providing an API and a "default"
>>>> implementation
>>>> with File system (XML files).
>>>>
>>>> Please let me know if you're interested in the details.
>>>>
>>>> Thank you
>>>>
>>>> S. Ali Tokmen
>>>> savas-ali.tokmen@bull.net
>>>>
>>>> Office: +33 4 76 29 76 19
>>>> GSM: +33 66 43 00 555
>>>>
>>>> Bull, Architect of an Open World TM
>>>> http://www.bull.com
>>>>
>>>>
>>>>
>>>> Claus Ibsen a écrit :
>>>>
>>>>
>>>>> Hi
>>>>>
>>>>> This is really a question for James Strachan ;)
>>>>>
>>>>> You can check out the camel-guice component that he recently added it
>>>>> shows how it integrated with Guice and how camel uses the guice
>>>>> context for registry lookup.
>>>>> The DefaultCamelContext has a setRegistry(Registry) method you can
>>>>> call to inject your registry. I also think it has a setRegistry that
>>>>> support jndi out-of-the-box.
>>>>>
>>>>>
>>>>>
>>>>> /Claus Ibsen
>>>>> Apache Camel Committer
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>>> <sa...@bull.net> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Hello
>>>>>>
>>>>>> I'm currently working in integrating CAMEL into the JOnAS Application
>>>>>> Server. I had previously worked on Mule and I can tell you that
>>>>>> integrating
>>>>>> CAMEL in an application server has been much easier and neater.
>>>>>>
>>>>>> When working with CAMEL, one functionality I've found missing is the
>>>>>> Registry/Repository support.
>>>>>>
>>>>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>>
>>>>>> Cheers
>>>>>>
>>>>>> --
>>>>>>
>>>>>> S. Ali Tokmen
>>>>>> savas-ali.tokmen@bull.net
>>>>>>
>>>>>> Office: +33 4 76 29 76 19
>>>>>> GSM: +33 66 43 00 555
>>>>>>
>>>>>> Bull, Architect of an Open World TM
>>>>>> http://www.bull.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yes we love contributions:
http://activemq.apache.org/camel/contributing.html
To be included in the camel distribution out-of-the-box it has to have
a compliant license.
Using Apache 2.0 license is of course preferred.
However there is a list of compliant licenses somewhere on the Apache
site. Can't find it at the moment.
If using a non compliant license (eg GPL) we have a camel-extra
project for such components:
http://code.google.com/p/camel-extra/
that can host the code.
But I am sure Hadrian or other that is a bit more into the Apache will
be able to explain the details.
So yes keep up the work and if and when you have a component you would
like to be included we can discuss further.
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Tue, Nov 18, 2008 at 11:15 AM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Great news. I'll keep you updated.
>
> FYI, the SVN is on
> svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4 and a
> corresponding CI will be created once the MAVEN integration is OK.
>
> Another question: if I keep the Registry/Repository module as a standalone
> MAVEN module (i.e. a module that doesn't depend on my project or any
> application server but only on CAMEL), can it be integrated as a CAMEL
> example someday? Would it be against any copyright or other policy from
> Apache/ActiveMQ/CAMEL?
>
> Regards
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Claus Ibsen a écrit :
>>
>> Hi
>>
>> Yes please keep us posted and you are very welcome to give feedback on
>> the Camel API if there is something we could do to improve it to
>> better support your use case. As we really would like it to be very
>> easy to integrate with whatever is out there.
>>
>> So we are very interested in your work.
>>
>>
>> /Claus Ibsen
>> Apache Camel Committer
>> Blog: http://davsclaus.blogspot.com/
>>
>>
>>
>> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>
>>>
>>> Hello
>>>
>>> I've also thought about that Registry interface, since I had to do some
>>> manual configuration for JNDI (JNDI is not supported out-of-the-box for
>>> JMS,
>>> for example).
>>>
>>> Note that the registry/repository support will be done as part of an open
>>> source project. It will be providing an API and a "default"
>>> implementation
>>> with File system (XML files).
>>>
>>> Please let me know if you're interested in the details.
>>>
>>> Thank you
>>>
>>> S. Ali Tokmen
>>> savas-ali.tokmen@bull.net
>>>
>>> Office: +33 4 76 29 76 19
>>> GSM: +33 66 43 00 555
>>>
>>> Bull, Architect of an Open World TM
>>> http://www.bull.com
>>>
>>>
>>>
>>> Claus Ibsen a écrit :
>>>
>>>>
>>>> Hi
>>>>
>>>> This is really a question for James Strachan ;)
>>>>
>>>> You can check out the camel-guice component that he recently added it
>>>> shows how it integrated with Guice and how camel uses the guice
>>>> context for registry lookup.
>>>> The DefaultCamelContext has a setRegistry(Registry) method you can
>>>> call to inject your registry. I also think it has a setRegistry that
>>>> support jndi out-of-the-box.
>>>>
>>>>
>>>>
>>>> /Claus Ibsen
>>>> Apache Camel Committer
>>>> Blog: http://davsclaus.blogspot.com/
>>>>
>>>>
>>>>
>>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>>> <sa...@bull.net> wrote:
>>>>
>>>>
>>>>>
>>>>> Hello
>>>>>
>>>>> I'm currently working in integrating CAMEL into the JOnAS Application
>>>>> Server. I had previously worked on Mule and I can tell you that
>>>>> integrating
>>>>> CAMEL in an application server has been much easier and neater.
>>>>>
>>>>> When working with CAMEL, one functionality I've found missing is the
>>>>> Registry/Repository support.
>>>>>
>>>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>>
>>>>> Cheers
>>>>>
>>>>> --
>>>>>
>>>>> S. Ali Tokmen
>>>>> savas-ali.tokmen@bull.net
>>>>>
>>>>> Office: +33 4 76 29 76 19
>>>>> GSM: +33 66 43 00 555
>>>>>
>>>>> Bull, Architect of an Open World TM
>>>>> http://www.bull.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>
>
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Great news. I'll keep you updated.
FYI, the SVN is on
svn://svn.forge.objectweb.org/svnroot/jonas/sandbox/camel-jonas4 and a
corresponding CI will be created once the MAVEN integration is OK.
Another question: if I keep the Registry/Repository module as a
standalone MAVEN module (i.e. a module that doesn't depend on my project
or any application server but only on CAMEL), can it be integrated as a
CAMEL example someday? Would it be against any copyright or other policy
from Apache/ActiveMQ/CAMEL?
Regards
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> Hi
>
> Yes please keep us posted and you are very welcome to give feedback on
> the Camel API if there is something we could do to improve it to
> better support your use case. As we really would like it to be very
> easy to integrate with whatever is out there.
>
> So we are very interested in your work.
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Hello
>>
>> I've also thought about that Registry interface, since I had to do some
>> manual configuration for JNDI (JNDI is not supported out-of-the-box for JMS,
>> for example).
>>
>> Note that the registry/repository support will be done as part of an open
>> source project. It will be providing an API and a "default" implementation
>> with File system (XML files).
>>
>> Please let me know if you're interested in the details.
>>
>> Thank you
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>> Claus Ibsen a écrit :
>>
>>> Hi
>>>
>>> This is really a question for James Strachan ;)
>>>
>>> You can check out the camel-guice component that he recently added it
>>> shows how it integrated with Guice and how camel uses the guice
>>> context for registry lookup.
>>> The DefaultCamelContext has a setRegistry(Registry) method you can
>>> call to inject your registry. I also think it has a setRegistry that
>>> support jndi out-of-the-box.
>>>
>>>
>>>
>>> /Claus Ibsen
>>> Apache Camel Committer
>>> Blog: http://davsclaus.blogspot.com/
>>>
>>>
>>>
>>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>>> <sa...@bull.net> wrote:
>>>
>>>
>>>> Hello
>>>>
>>>> I'm currently working in integrating CAMEL into the JOnAS Application
>>>> Server. I had previously worked on Mule and I can tell you that
>>>> integrating
>>>> CAMEL in an application server has been much easier and neater.
>>>>
>>>> When working with CAMEL, one functionality I've found missing is the
>>>> Registry/Repository support.
>>>>
>>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>>
>>>> Cheers
>>>>
>>>> --
>>>>
>>>> S. Ali Tokmen
>>>> savas-ali.tokmen@bull.net
>>>>
>>>> Office: +33 4 76 29 76 19
>>>> GSM: +33 66 43 00 555
>>>>
>>>> Bull, Architect of an Open World TM
>>>> http://www.bull.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Yes please keep us posted and you are very welcome to give feedback on
the Camel API if there is something we could do to improve it to
better support your use case. As we really would like it to be very
easy to integrate with whatever is out there.
So we are very interested in your work.
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Tue, Nov 18, 2008 at 9:22 AM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Hello
>
> I've also thought about that Registry interface, since I had to do some
> manual configuration for JNDI (JNDI is not supported out-of-the-box for JMS,
> for example).
>
> Note that the registry/repository support will be done as part of an open
> source project. It will be providing an API and a "default" implementation
> with File system (XML files).
>
> Please let me know if you're interested in the details.
>
> Thank you
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Claus Ibsen a écrit :
>>
>> Hi
>>
>> This is really a question for James Strachan ;)
>>
>> You can check out the camel-guice component that he recently added it
>> shows how it integrated with Guice and how camel uses the guice
>> context for registry lookup.
>> The DefaultCamelContext has a setRegistry(Registry) method you can
>> call to inject your registry. I also think it has a setRegistry that
>> support jndi out-of-the-box.
>>
>>
>>
>> /Claus Ibsen
>> Apache Camel Committer
>> Blog: http://davsclaus.blogspot.com/
>>
>>
>>
>> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>
>>>
>>> Hello
>>>
>>> I'm currently working in integrating CAMEL into the JOnAS Application
>>> Server. I had previously worked on Mule and I can tell you that
>>> integrating
>>> CAMEL in an application server has been much easier and neater.
>>>
>>> When working with CAMEL, one functionality I've found missing is the
>>> Registry/Repository support.
>>>
>>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>>
>>> Cheers
>>>
>>> --
>>>
>>> S. Ali Tokmen
>>> savas-ali.tokmen@bull.net
>>>
>>> Office: +33 4 76 29 76 19
>>> GSM: +33 66 43 00 555
>>>
>>> Bull, Architect of an Open World TM
>>> http://www.bull.com
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello
I've also thought about that Registry interface, since I had to do some
manual configuration for JNDI (JNDI is not supported out-of-the-box for
JMS, for example).
Note that the registry/repository support will be done as part of an
open source project. It will be providing an API and a "default"
implementation with File system (XML files).
Please let me know if you're interested in the details.
Thank you
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> Hi
>
> This is really a question for James Strachan ;)
>
> You can check out the camel-guice component that he recently added it
> shows how it integrated with Guice and how camel uses the guice
> context for registry lookup.
> The DefaultCamelContext has a setRegistry(Registry) method you can
> call to inject your registry. I also think it has a setRegistry that
> support jndi out-of-the-box.
>
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Hello
>>
>> I'm currently working in integrating CAMEL into the JOnAS Application
>> Server. I had previously worked on Mule and I can tell you that integrating
>> CAMEL in an application server has been much easier and neater.
>>
>> When working with CAMEL, one functionality I've found missing is the
>> Registry/Repository support.
>>
>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>
>> Cheers
>>
>> --
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by "raulvk.soa" <ra...@gmail.com>.
Is it possible to define these endpoint refs in a Global XML file that ALL
Camel routes can see and use?
Or do the endpoint refs have to be defined inside the route that is going to
use them?
Claus Ibsen-2 wrote:
>
> Hi
>
> Camel supports defining endpoints so you can ref then using the id
> instead of the actual uri.
>
> <endpoint id="foo" uri="jms:qeue:a?disableReply=true"/>
>
> And then you can ref the endpoint just as foo
> from("foo").to("log:hello");
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Thu, Nov 20, 2008 at 1:32 PM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>> Hello
>>
>> Time for me to be more elaborate, then... :)
>>
>> When we're doing a Repository service, our aim is to link logical URLs to
>> technical URLs.
>>
>> For example:
>>
>> * The logical URL reference:sampleTopic has as technical
>> correspondent jms:topic:sampleTopic?disableReplyTo=true
>> * Therefore, if the user writes reference:sampleTopic in its
>> camel-context.xml file, CAMEL should act exactly as if
>> jms:topic:sampleTopic?disableReplyTo=true was written
>>
>> What I've seen in CAMEL is that JNDI on JMS also does a similar job:
>>
>> * The default JMS implementation requires the JMS worker names to be
>> written (for example, jms:queue:#0.0.1023)
>> * To replace that with a JNDI lookup, we need to set the
>> destinationResolver property of the JmsComponent bean with a
>> JndiDestinationResolver bean (in camel-context.xml)
>> * Once that is done, writing jms:queue:sampleQueue becomes
>> equivalent to writing jms:queue:#0.0.1023
>>
>> And that's why I'm mentioning the destinationResolvers...
>>
>> Do you think I'm going in the wrong direction?
>>
>> Cheers
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>> Claus Ibsen a écrit :
>>>
>>> On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
>>> <sa...@bull.net> wrote:
>>>
>>>>
>>>> Hello
>>>>
>>>> After some tests, I have the impression that the real property to look
>>>> after
>>>> is the "destinationResolver" property. Do you think that's expected?
>>>>
>>>
>>> Could you elaborate what you mean, eg. write some more?
>>> Which destinationResolver. I can not find destinationResolver in Camel.
>>>
>>>
>>>
>>>
>>
>
>
--
View this message in context: http://www.nabble.com/Registry-Repository-support-in-CAMEL-tp20541572s22882p20628908.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Registry/Repository support in CAMEL
Posted by James Strachan <ja...@gmail.com>.
2008/11/21 S. Ali Tokmen <sa...@bull.net>:
> Hello
>
> This is very good to know :) A repository would in fact resemble the
> "endpoint id" mechanism, the only difference being that the endpoint
> identifier would not be "hardcoded" but rather obtained from a Repository
> service.
>
> I'm launching debug sessions to see at which points integration fits best. I
> hope to be able of doing what I want without having do change CAMEL core.
Sorry I'm so slow diving into this interesting thread; I've been on
paternity leave & trying to sleep :)
So the reference mechanism Claus mentioned is really intended for
local aliasing; for example if you refer to the same endpoint many
times within routes & you don't want to have to include all the
various URI parameters and so forth - you can introduce a logical name
for it. A bit like introducing a shared variable in code.
I think what you are after is some kind of registry/repository
mechanism so that you can look up logical named endpoints - but at
runtime have some separate database/JNDI/LDAP thing map the logical
name to some physical endpoint class and/or URI string etc.
There are a few ways to do this; I'll just list some ideas to see
which one seems the most fitting.
One of the design ideas behind Camel was that there can be many
Endpoints; they can be lazily created on demand or registered by the
user into a CamelContext. A Component is really just a factory of
Endpoints; it takes a URI and creates an Endpoint instance for it.
Sometimes a Component can share some configuration information across
actual endpoints (e.g. a JMS component can share JMS ConnectionFactory
objects across endpoints for individual queues and topics etc)
http://activemq.apache.org/camel/component.html
So you could create some kind of Registry Component which takes a
logical URI and maps it to some Endpoint instance somehow. e.g. your
component could use the scheme 'foo' so that a URI
foo:someLogicalName
then takes the remaining name and looks it up somewhere - then returns
the Endpoint object - or looks up an Endpoint by URI to lazily create
the physical endpoint etc.
We should probably have standard JNDI / ldap / OSGi components which
just look up a logical endpoint name in those particular registry
implementations. Though in some ways we can just reuse existing IoC
contains for this. e.g. we could refer to an Endpoint by its logical
name - then use Spring Dynamic Modules to look up the endpoint by name
in OSGi; or use Spring's JNDI lookup mechanism to look up in JNDI etc
Incidentally another approach to this is to use OSGi / JBI / NMR as a
level of indirection. e.g. when using Camel inside ServiceMix you can
refer to JBI endpoints using their logical name - then the NMR can
resolve those logical names to physical endpoints. I tend to view the
JBI NMR as being an endpoint registry; capable of mapping a logical
endpoint to one or more physical endpoints.
Finally on the licensing & including in an example; we can't
redistribute or link with any LGPL code in an Apache project. However
so long as the Apache code doesn't import directly any LGPL code - it
seems allowable to have an example maven program download the LGPL
code. e.g. an Apache example could use JPA and then have a maven build
use either OpenJPA or Hibernate.
So I think we could have an example program which routes using URIs
which use an LGPL component at runtime to resolve the URIs into
physical endpoints
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello
This is very good to know :) A repository would in fact resemble the
"endpoint id" mechanism, the only difference being that the endpoint
identifier would not be "hardcoded" but rather obtained from a
Repository service.
I'm launching debug sessions to see at which points integration fits
best. I hope to be able of doing what I want without having do change
CAMEL core.
Cheers
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> Hi
>
> Camel supports defining endpoints so you can ref then using the id
> instead of the actual uri.
>
> <endpoint id="foo" uri="jms:qeue:a?disableReply=true"/>
>
> And then you can ref the endpoint just as foo
> from("foo").to("log:hello");
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Thu, Nov 20, 2008 at 1:32 PM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Hello
>>
>> Time for me to be more elaborate, then... :)
>>
>> When we're doing a Repository service, our aim is to link logical URLs to
>> technical URLs.
>>
>> For example:
>>
>> * The logical URL reference:sampleTopic has as technical
>> correspondent jms:topic:sampleTopic?disableReplyTo=true
>> * Therefore, if the user writes reference:sampleTopic in its
>> camel-context.xml file, CAMEL should act exactly as if
>> jms:topic:sampleTopic?disableReplyTo=true was written
>>
>> What I've seen in CAMEL is that JNDI on JMS also does a similar job:
>>
>> * The default JMS implementation requires the JMS worker names to be
>> written (for example, jms:queue:#0.0.1023)
>> * To replace that with a JNDI lookup, we need to set the
>> destinationResolver property of the JmsComponent bean with a
>> JndiDestinationResolver bean (in camel-context.xml)
>> * Once that is done, writing jms:queue:sampleQueue becomes
>> equivalent to writing jms:queue:#0.0.1023
>>
>> And that's why I'm mentioning the destinationResolvers...
>>
>> Do you think I'm going in the wrong direction?
>>
>> Cheers
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>> Claus Ibsen a écrit :
>>
>>> On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
>>> <sa...@bull.net> wrote:
>>>
>>>
>>>> Hello
>>>>
>>>> After some tests, I have the impression that the real property to look
>>>> after
>>>> is the "destinationResolver" property. Do you think that's expected?
>>>>
>>>>
>>> Could you elaborate what you mean, eg. write some more?
>>> Which destinationResolver. I can not find destinationResolver in Camel.
>>>
>>>
>>>
>>>
>>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Camel supports defining endpoints so you can ref then using the id
instead of the actual uri.
<endpoint id="foo" uri="jms:qeue:a?disableReply=true"/>
And then you can ref the endpoint just as foo
from("foo").to("log:hello");
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Thu, Nov 20, 2008 at 1:32 PM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Hello
>
> Time for me to be more elaborate, then... :)
>
> When we're doing a Repository service, our aim is to link logical URLs to
> technical URLs.
>
> For example:
>
> * The logical URL reference:sampleTopic has as technical
> correspondent jms:topic:sampleTopic?disableReplyTo=true
> * Therefore, if the user writes reference:sampleTopic in its
> camel-context.xml file, CAMEL should act exactly as if
> jms:topic:sampleTopic?disableReplyTo=true was written
>
> What I've seen in CAMEL is that JNDI on JMS also does a similar job:
>
> * The default JMS implementation requires the JMS worker names to be
> written (for example, jms:queue:#0.0.1023)
> * To replace that with a JNDI lookup, we need to set the
> destinationResolver property of the JmsComponent bean with a
> JndiDestinationResolver bean (in camel-context.xml)
> * Once that is done, writing jms:queue:sampleQueue becomes
> equivalent to writing jms:queue:#0.0.1023
>
> And that's why I'm mentioning the destinationResolvers...
>
> Do you think I'm going in the wrong direction?
>
> Cheers
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Claus Ibsen a écrit :
>>
>> On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>
>>>
>>> Hello
>>>
>>> After some tests, I have the impression that the real property to look
>>> after
>>> is the "destinationResolver" property. Do you think that's expected?
>>>
>>
>> Could you elaborate what you mean, eg. write some more?
>> Which destinationResolver. I can not find destinationResolver in Camel.
>>
>>
>>
>>
>
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello again
I've actually found out that the Registry needs to be overriden in the
RouteBuilder.configure() method.
Getting closer... :)
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
S. Ali Tokmen a écrit :
> Hello
>
> Time for me to be more elaborate, then... :)
>
> When we're doing a Repository service, our aim is to link logical URLs
> to technical URLs.
>
> For example:
>
> * The logical URL reference:sampleTopic has as technical
> correspondent jms:topic:sampleTopic?disableReplyTo=true
> * Therefore, if the user writes reference:sampleTopic in its
> camel-context.xml file, CAMEL should act exactly as if
> jms:topic:sampleTopic?disableReplyTo=true was written
>
> What I've seen in CAMEL is that JNDI on JMS also does a similar job:
>
> * The default JMS implementation requires the JMS worker names to be
> written (for example, jms:queue:#0.0.1023)
> * To replace that with a JNDI lookup, we need to set the
> destinationResolver property of the JmsComponent bean with a
> JndiDestinationResolver bean (in camel-context.xml)
> * Once that is done, writing jms:queue:sampleQueue becomes
> equivalent to writing jms:queue:#0.0.1023
>
> And that's why I'm mentioning the destinationResolvers...
>
> Do you think I'm going in the wrong direction?
>
> Cheers
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>
> Claus Ibsen a écrit :
>> On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
>> <sa...@bull.net> wrote:
>>
>>> Hello
>>>
>>> After some tests, I have the impression that the real property to
>>> look after
>>> is the "destinationResolver" property. Do you think that's expected?
>>>
>>
>> Could you elaborate what you mean, eg. write some more?
>> Which destinationResolver. I can not find destinationResolver in Camel.
>>
>>
>>
>>
>
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello
Time for me to be more elaborate, then... :)
When we're doing a Repository service, our aim is to link logical URLs
to technical URLs.
For example:
* The logical URL reference:sampleTopic has as technical
correspondent jms:topic:sampleTopic?disableReplyTo=true
* Therefore, if the user writes reference:sampleTopic in its
camel-context.xml file, CAMEL should act exactly as if
jms:topic:sampleTopic?disableReplyTo=true was written
What I've seen in CAMEL is that JNDI on JMS also does a similar job:
* The default JMS implementation requires the JMS worker names to be
written (for example, jms:queue:#0.0.1023)
* To replace that with a JNDI lookup, we need to set the
destinationResolver property of the JmsComponent bean with a
JndiDestinationResolver bean (in camel-context.xml)
* Once that is done, writing jms:queue:sampleQueue becomes
equivalent to writing jms:queue:#0.0.1023
And that's why I'm mentioning the destinationResolvers...
Do you think I'm going in the wrong direction?
Cheers
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Hello
>>
>> After some tests, I have the impression that the real property to look after
>> is the "destinationResolver" property. Do you think that's expected?
>>
>
> Could you elaborate what you mean, eg. write some more?
> Which destinationResolver. I can not find destinationResolver in Camel.
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
On Thu, Nov 20, 2008 at 11:46 AM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Hello
>
> After some tests, I have the impression that the real property to look after
> is the "destinationResolver" property. Do you think that's expected?
Could you elaborate what you mean, eg. write some more?
Which destinationResolver. I can not find destinationResolver in Camel.
Re: Registry/Repository support in CAMEL
Posted by "S. Ali Tokmen" <sa...@bull.net>.
Hello
After some tests, I have the impression that the real property to look
after is the "destinationResolver" property. Do you think that's expected?
Cheers
S. Ali Tokmen
savas-ali.tokmen@bull.net
Office: +33 4 76 29 76 19
GSM: +33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Claus Ibsen a écrit :
> Hi
>
> This is really a question for James Strachan ;)
>
> You can check out the camel-guice component that he recently added it
> shows how it integrated with Guice and how camel uses the guice
> context for registry lookup.
> The DefaultCamelContext has a setRegistry(Registry) method you can
> call to inject your registry. I also think it has a setRegistry that
> support jndi out-of-the-box.
>
>
>
> /Claus Ibsen
> Apache Camel Committer
> Blog: http://davsclaus.blogspot.com/
>
>
>
> On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
> <sa...@bull.net> wrote:
>
>> Hello
>>
>> I'm currently working in integrating CAMEL into the JOnAS Application
>> Server. I had previously worked on Mule and I can tell you that integrating
>> CAMEL in an application server has been much easier and neater.
>>
>> When working with CAMEL, one functionality I've found missing is the
>> Registry/Repository support.
>>
>> So, I'm asking: has anyone tried linking CAMEL with any registry or
>> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>>
>> Cheers
>>
>> --
>>
>> S. Ali Tokmen
>> savas-ali.tokmen@bull.net
>>
>> Office: +33 4 76 29 76 19
>> GSM: +33 66 43 00 555
>>
>> Bull, Architect of an Open World TM
>> http://www.bull.com
>>
>>
>>
>>
>
>
>
>
Re: Registry/Repository support in CAMEL
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
This is really a question for James Strachan ;)
You can check out the camel-guice component that he recently added it
shows how it integrated with Guice and how camel uses the guice
context for registry lookup.
The DefaultCamelContext has a setRegistry(Registry) method you can
call to inject your registry. I also think it has a setRegistry that
support jndi out-of-the-box.
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
On Mon, Nov 17, 2008 at 4:27 PM, S. Ali Tokmen
<sa...@bull.net> wrote:
> Hello
>
> I'm currently working in integrating CAMEL into the JOnAS Application
> Server. I had previously worked on Mule and I can tell you that integrating
> CAMEL in an application server has been much easier and neater.
>
> When working with CAMEL, one functionality I've found missing is the
> Registry/Repository support.
>
> So, I'm asking: has anyone tried linking CAMEL with any registry or
> repository? (UDDI, Mule Galaxy, WSO2 Registry, ...)
>
> Cheers
>
> --
>
> S. Ali Tokmen
> savas-ali.tokmen@bull.net
>
> Office: +33 4 76 29 76 19
> GSM: +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>
>