You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Christian Müller <ch...@gmail.com> on 2012/01/14 13:44:47 UTC
Do Apache Camel needs a SAP integration?
Hello list!
One year ago I was thinking about "Do Apache Camel needs a SAP
integration?".
Last week I got an announcement from Mulesoft and their SAP integration
[1]. And now I'm thinking about it again: Do Apache Camel needs a SAP
integration? Did you already missed this integration?
I'm highly interested in your opinion.
[1] http://www.mulesoft.com/sap-integration
Best,
Christian
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
Hello Thomas!
I'm interested in it. I would like to have a camel-sap component at Camel
extra [1] what is not the case at present.
If your camel-sap component use the SAP JCo library, I think this will not
be an option because we cannot (we are not allowed to) add the JCo
dependency in any Maven repository. But in any way, it would be cool if you
share your solution with the community.
[1] http://code.google.com/a/apache-extras.org/p/camel-extra/
Best,
Christian
On Fri, Nov 9, 2012 at 3:41 PM, Thomas Weinschenk <
thomas.weinschenk@infoserve.endress.com> wrote:
> Hello guys,
>
> I also created a Camel SAP component based on the JCo a while ago. I used
> the readXML and writeXML functionality of the JCo instead. In my opinion
> this fits much more to the way Camel is working. By simply passing and
> receiving XML file you can use a lot of Camel features like Content Based
> Routers, JAXB, XSLT for mapping and on and on. In the end it is a slightly
> different approach how to communicate with a SAP system.
>
> Is there an interest for a 2nd SAP Component?
>
> Cheers,
> Thomas
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5722408.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Re: Do Apache Camel needs a SAP integration?
Posted by Thomas Weinschenk <th...@infoserve.endress.com>.
Hi Christian,
I figured out that with JCo 3 SAP removed the readXml function. In the
meanwhile I added my own XMLReader to do the same.
I am waiting for confirmation from my company that I am allowed to publish
the code…should not be an issue. Once I got the confirmation I will include
the licensing information (ASL for the non SAP part) and a small
documentation and publish it at github.
I am not sure if I am able to publish all test cases as a SAP system is
needed to run the tests.
Furthermore the SAP license problem is really a pity.
Regards,
Thomas
--
View this message in context: http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5723009.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Thomas,
I am also interested in the component. Perhaps you can put it to github.
Make sure to put licensing information into your code so people know
what they may do with it.
Christian
On 11/09/2012 03:41 PM, Thomas Weinschenk wrote:
> Hello guys,
>
> I also created a Camel SAP component based on the JCo a while ago. I used
> the readXML and writeXML functionality of the JCo instead. In my opinion
> this fits much more to the way Camel is working. By simply passing and
> receiving XML file you can use a lot of Camel features like Content Based
> Routers, JAXB, XSLT for mapping and on and on. In the end it is a slightly
> different approach how to communicate with a SAP system.
>
> Is there an interest for a 2nd SAP Component?
>
> Cheers,
> Thomas
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5722408.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Do Apache Camel needs a SAP integration?
Posted by sekaijin <je...@sap.aphp.fr>.
Hi,
I've me to writed a camel-sap component based on JCO 3
it use xml based data to send and recive RFC SAP IDOCS
the consumer fix some headers from EDI_DC40 segment like idoc_type
The messageId is fixed with the idoc number
A+JYT
--
View this message in context: http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5723144.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Do Apache Camel needs a SAP integration?
Posted by Thomas Weinschenk <th...@infoserve.endress.com>.
Hello guys,
I also created a Camel SAP component based on the JCo a while ago. I used
the readXML and writeXML functionality of the JCo instead. In my opinion
this fits much more to the way Camel is working. By simply passing and
receiving XML file you can use a lot of Camel features like Content Based
Routers, JAXB, XSLT for mapping and on and on. In the end it is a slightly
different approach how to communicate with a SAP system.
Is there an interest for a 2nd SAP Component?
Cheers,
Thomas
--
View this message in context: http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5722408.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Do Apache Camel needs a SAP integration?
Posted by Björn Bength <bj...@gmail.com>.
Hi
I could do that later, but cant you just pull it off of github?
The component is still used by our client and i havent got any complaints
so far.
Thanks to the great hibersap :)
Im also interested in what a component working with xml and jco directly
would bring to the table.
(Im not an sap expert)
On Saturday, November 10, 2012, Christian Müller wrote:
> Hello Björn!
>
> I created a new issue at Camel extra [1] to track this. Could you please
> attach your camel-sap component as zip to this issue!? Then I can pick it
> up and work on an initial version.
>
> [1]
> http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=31
>
> Best,
> Christian
>
> On Wed, Jan 18, 2012 at 2:02 PM, Björn Bength <bjorn.bength@gmail.com<javascript:_e({}, 'cvml', 'bjorn.bength@gmail.com');>
> > wrote:
>
>> Hello
>>
>> After some adjustments to make the code shareable, I just pushed the
>> camel-hibersap component to GitHub.
>> You can find it at https://github.com/bjoben/camel-hibersap
>>
>> I realized that the actual camel part of it is very small and does not
>> include transaction or proper thread pool support yet.
>> However, similar component is used by our client and works very well
>> in our camel integration code (based on ServiceMix).
>>
>> It compiles as an osgi bundle and embeds JCo and hibersap libraries,
>> neither which i'm redistributing.
>> Therefore you have to compile it yourself, after installing JCo and
>> hibersap into you own maven repo.
>> (This is very well documented in the hibersap documentation)
>>
>> You can use it as it is, or treat it like an example from which to
>> base a better component.
>> I don't have an SAP server at hand, so I can't make it better right now.
>> Also, the unit tests use a real SAP server, so they are disabled for
>> now, and should be made into an integration test suit,
>> but they are the best example of how to use this component. So have a
>> look at those. They are very simple but demonstrates usage very well.
>> More examples can be found at the hibersap site.
>>
>>
>> Regards
>> Björn
>>
>>
>>
>>
>> On Mon, Jan 16, 2012 at 10:16 AM, Guillaume Yziquel
>> <guillaume.yziquel@crossing-tech.com <javascript:_e({}, 'cvml',
>> 'guillaume.yziquel@crossing-tech.com');>> wrote:
>> > Le Saturday 14 Jan 2012 à 15:37:38 (+0100), Björn Bength a écrit :
>> >> Hi
>> >>
>> >> At our client (a bank) in Sweden, we created a camel component that
>> >> integrated their SAP server.
>> >> It can only call BAPI functions right now but it uses JCo of course,
>> >> and Hibersap which allows to annotate java beans just send it through
>> >> to the camel endpoint. All this on ServiceMix where we made the
>> >> camel-SAP (with jco) component OSGi firendly.
>> >>
>> >> It worked so well that those SAP guys we worked with told us that they
>> >> never before had an integration project that actually worked on _the
>> >> first_ test transaction.
>> >>
>> >> Unfortunatly hibersap is LGPL but it really (really) makes working
>> >> with Jco sooo much easier.
>> >> And just maybe hibersap can convert it's license, but from another
>> >> thread (MongoDB) I got the feeling that all of you like to have a
>> >> "native" camel component in all cases.
>> >>
>> >> My intention was to put this on GitHub though, but I never took time
>> to do so.
>> >> I could share the parts I wrote if someone is interested, and call it
>> >> camel-hibersap.
>> >>
>> >> Regards
>> >> Björn
>> >
>> > I guess it would be quite nice to put such a Camel Component on Github.
>> > Please feel free to do so and keep us updated.
>> >
>> > --
>> > Guillaume Yziquel
>>
>
>
>
> --
>
>
>
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
Hello Björn!
I created a new issue at Camel extra [1] to track this. Could you please
attach your camel-sap component as zip to this issue!? Then I can pick it
up and work on an initial version.
[1]
http://code.google.com/a/apache-extras.org/p/camel-extra/issues/detail?id=31
Best,
Christian
On Wed, Jan 18, 2012 at 2:02 PM, Björn Bength <bj...@gmail.com>wrote:
> Hello
>
> After some adjustments to make the code shareable, I just pushed the
> camel-hibersap component to GitHub.
> You can find it at https://github.com/bjoben/camel-hibersap
>
> I realized that the actual camel part of it is very small and does not
> include transaction or proper thread pool support yet.
> However, similar component is used by our client and works very well
> in our camel integration code (based on ServiceMix).
>
> It compiles as an osgi bundle and embeds JCo and hibersap libraries,
> neither which i'm redistributing.
> Therefore you have to compile it yourself, after installing JCo and
> hibersap into you own maven repo.
> (This is very well documented in the hibersap documentation)
>
> You can use it as it is, or treat it like an example from which to
> base a better component.
> I don't have an SAP server at hand, so I can't make it better right now.
> Also, the unit tests use a real SAP server, so they are disabled for
> now, and should be made into an integration test suit,
> but they are the best example of how to use this component. So have a
> look at those. They are very simple but demonstrates usage very well.
> More examples can be found at the hibersap site.
>
>
> Regards
> Björn
>
>
>
>
> On Mon, Jan 16, 2012 at 10:16 AM, Guillaume Yziquel
> <gu...@crossing-tech.com> wrote:
> > Le Saturday 14 Jan 2012 à 15:37:38 (+0100), Björn Bength a écrit :
> >> Hi
> >>
> >> At our client (a bank) in Sweden, we created a camel component that
> >> integrated their SAP server.
> >> It can only call BAPI functions right now but it uses JCo of course,
> >> and Hibersap which allows to annotate java beans just send it through
> >> to the camel endpoint. All this on ServiceMix where we made the
> >> camel-SAP (with jco) component OSGi firendly.
> >>
> >> It worked so well that those SAP guys we worked with told us that they
> >> never before had an integration project that actually worked on _the
> >> first_ test transaction.
> >>
> >> Unfortunatly hibersap is LGPL but it really (really) makes working
> >> with Jco sooo much easier.
> >> And just maybe hibersap can convert it's license, but from another
> >> thread (MongoDB) I got the feeling that all of you like to have a
> >> "native" camel component in all cases.
> >>
> >> My intention was to put this on GitHub though, but I never took time to
> do so.
> >> I could share the parts I wrote if someone is interested, and call it
> >> camel-hibersap.
> >>
> >> Regards
> >> Björn
> >
> > I guess it would be quite nice to put such a Camel Component on Github.
> > Please feel free to do so and keep us updated.
> >
> > --
> > Guillaume Yziquel
>
--
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
Hello Carsten!
Any news about the licensing stuff of Hibersap? It looks like you still use
the GNU LESSER GENERAL PUBLIC LICENSE [1].
[1] http://hibersap.sourceforge.net/hibersap-1.0/license.html
Best,
Christian
On Fri, Jan 20, 2012 at 9:27 AM, cerker <ca...@akquinet.de> wrote:
> Björn, thanks a lot for sharing your camel-hibersap component. I only just
> started playing around with camel and liked it very much. Now there is a
> good reason to take a deeper look.
>
> It's good to hear that Hibersap helped you with your project. Regarding the
> license, I think there should be no problems to combine libraries that are
> under the Apache license and ones under LGPL (at least in their current
> versions). We initially liked the idea of a copyleft license and LGPL is
> the
> one most widely used. After all, I am not a lawyer and the big disadvantage
> of LGPL is that nobody seems to fully understand it and things are open to
> interpretation. Anyway, I'll have a talk with some people in my company who
> have a deeper understanding of OS licenses and we'll rethink the
> licensing....
>
> If you got any questions feel free to contact me via email or use the
> Hibersap forums or issue tracker on Sourceforge.
>
> Best Regards,
> Carsten
> (Founder of the Hibersap project)
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5159788.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Re: Do Apache Camel needs a SAP integration?
Posted by Fernando Ribeiro <we...@fernandoribeiro.eti.br>.
The most important thing here is that the component is published, be it in
camel-extra or in a separate project. Licensing has long prevented
integration products to be as complete as they could. Thanks for sharing.
On Jan 20, 2012 9:01 AM, "Björn Bength" <bj...@gmail.com> wrote:
> I think GPLv3 software may include Apache licensed software but not
> the other way around.
> however, I think it's ok to use 3 party librarys, but not including or
> distributing with it.
>
> http://www.apache.org/legal/3party.html#transition
>
> LGPL
> The LGPL v2.1 is ineligible from being a Category B license (a
> category that includes the MPL, CPL, EPL, and CDDL) primarily due to
> the restrictions it places on larger works, violating the third
> license criterion. Therefore, LGPL v2.1-licensed works must not be
> included in Apache products, although they may be listed as system
> requirements or distributed elsewhere as optional works.
>
> Björn
>
>
>
>
>
> On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten
> <Ca...@akquinet.de> wrote:
> > Hi Christian,
> >
> > yes, a colleague who is Apache member just explained it to me.
> >
> > We are discussing about switching to ASL 2.0 with the next version.
> >
> > Regards,
> > Carsten
> >
> >
> >
> > Am 20.01.2012 um 10:36 schrieb Christian Schneider:
> >
> >> Hi Carsten,
> >>
> >> you migth want to take a look at the Apache license policies:
> >> http://www.apache.org/legal/3party.html
> >>
> >> LGPL is listed as excluded so it may not be used as a dependency of an
> apache product (as far as I understand).
> >> I am not sure why it can´t be used but I guess some lawyer has helped
> with that policy.
> >>
> >> Christian
> >>
> >>
> >> Am 20.01.2012 09:27, schrieb cerker:
> >>> Björn, thanks a lot for sharing your camel-hibersap component. I only
> just
> >>> started playing around with camel and liked it very much. Now there is
> a
> >>> good reason to take a deeper look.
> >>>
> >>> It's good to hear that Hibersap helped you with your project.
> Regarding the
> >>> license, I think there should be no problems to combine libraries that
> are
> >>> under the Apache license and ones under LGPL (at least in their current
> >>> versions). We initially liked the idea of a copyleft license and LGPL
> is the
> >>> one most widely used. After all, I am not a lawyer and the big
> disadvantage
> >>> of LGPL is that nobody seems to fully understand it and things are
> open to
> >>> interpretation. Anyway, I'll have a talk with some people in my
> company who
> >>> have a deeper understanding of OS licenses and we'll rethink the
> >>> licensing....
> >>>
> >>> If you got any questions feel free to contact me via email or use the
> >>> Hibersap forums or issue tracker on Sourceforge.
> >>>
> >>> Best Regards,
> >>> Carsten
> >>> (Founder of the Hibersap project)
> >>>
> >>> -
> >>
> >> --
> >> Christian Schneider
> >> http://www.liquid-reality.de
> >>
> >> Open Source Architect
> >> Talend Application Integration Division http://www.talend.com
> >>
> >
>
Re: Do Apache Camel needs a SAP integration?
Posted by Björn Bength <bj...@gmail.com>.
I think GPLv3 software may include Apache licensed software but not
the other way around.
however, I think it's ok to use 3 party librarys, but not including or
distributing with it.
http://www.apache.org/legal/3party.html#transition
LGPL
The LGPL v2.1 is ineligible from being a Category B license (a
category that includes the MPL, CPL, EPL, and CDDL) primarily due to
the restrictions it places on larger works, violating the third
license criterion. Therefore, LGPL v2.1-licensed works must not be
included in Apache products, although they may be listed as system
requirements or distributed elsewhere as optional works.
Björn
On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten
<Ca...@akquinet.de> wrote:
> Hi Christian,
>
> yes, a colleague who is Apache member just explained it to me.
>
> We are discussing about switching to ASL 2.0 with the next version.
>
> Regards,
> Carsten
>
>
>
> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>
>> Hi Carsten,
>>
>> you migth want to take a look at the Apache license policies:
>> http://www.apache.org/legal/3party.html
>>
>> LGPL is listed as excluded so it may not be used as a dependency of an apache product (as far as I understand).
>> I am not sure why it can´t be used but I guess some lawyer has helped with that policy.
>>
>> Christian
>>
>>
>> Am 20.01.2012 09:27, schrieb cerker:
>>> Björn, thanks a lot for sharing your camel-hibersap component. I only just
>>> started playing around with camel and liked it very much. Now there is a
>>> good reason to take a deeper look.
>>>
>>> It's good to hear that Hibersap helped you with your project. Regarding the
>>> license, I think there should be no problems to combine libraries that are
>>> under the Apache license and ones under LGPL (at least in their current
>>> versions). We initially liked the idea of a copyleft license and LGPL is the
>>> one most widely used. After all, I am not a lawyer and the big disadvantage
>>> of LGPL is that nobody seems to fully understand it and things are open to
>>> interpretation. Anyway, I'll have a talk with some people in my company who
>>> have a deeper understanding of OS licenses and we'll rethink the
>>> licensing....
>>>
>>> If you got any questions feel free to contact me via email or use the
>>> Hibersap forums or issue tracker on Sourceforge.
>>>
>>> Best Regards,
>>> Carsten
>>> (Founder of the Hibersap project)
>>>
>>> -
>>
>> --
>> Christian Schneider
>> http://www.liquid-reality.de
>>
>> Open Source Architect
>> Talend Application Integration Division http://www.talend.com
>>
>
Re: Do Apache Camel needs a SAP integration?
Posted by Hadrian Zbarcea <hz...@gmail.com>.
Yes, it can and it's probably the best option.
Hadrian
On 03/05/2012 05:47 PM, Romain Manni-Bucau wrote:
> Hi,
>
> can't it be added to the google project creating a repo in the source
> repository?
>
> - Romain
>
>
> 2012/3/5 Christian Müller<ch...@gmail.com>
>
>> I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to an
>> ASF maven repository. Without it, we cannot build this component. Because
>> of this, I see no way to host this component at camel-extra. :-(
>>
>> Best,
>> Christian
>>
>> On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller<
>> christian.mueller@gmail.com> wrote:
>>
>>> +1
>>> This will make a few things easier for us and for our users.
>>> Of course, we can host this component in camel-extra on googlecode, but
>> we
>>> often ignore/forget these components (the last version is 2.8.0). And I
>>> think many of our users don't know that we also host some components
>>> because of license reasons on camel-extra.
>>>
>>> I will checkout the code from github and play with it a bit...
>>>
>>> @Björn: If you are the owner of this contribution, could you please open
>> a
>>> JIRA for this new component and attach it (don't forget to grant the
>> Apache
>>> license). Than we could put it into camel-extra and start to work to
>>> improve this component. And if Hibersap is licensed with a compatible
>>> license, we can move it into our repo at Apache.
>>>
>>> Best,
>>> Christian
>>>
>>> On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten<
>>> Carsten.Erker@akquinet.de> wrote:
>>>
>>>> Hi Christian,
>>>>
>>>> yes, a colleague who is Apache member just explained it to me.
>>>>
>>>> We are discussing about switching to ASL 2.0 with the next version.
>>>>
>>>> Regards,
>>>> Carsten
>>>>
>>>>
>>>>
>>>> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>>>>
>>>>> Hi Carsten,
>>>>>
>>>>> you migth want to take a look at the Apache license policies:
>>>>> http://www.apache.org/legal/3party.html
>>>>>
>>>>> LGPL is listed as excluded so it may not be used as a dependency of an
>>>> apache product (as far as I understand).
>>>>> I am not sure why it can´t be used but I guess some lawyer has helped
>>>> with that policy.
>>>>>
>>>>> Christian
>>>>>
>>>>>
>>>>> Am 20.01.2012 09:27, schrieb cerker:
>>>>>> Björn, thanks a lot for sharing your camel-hibersap component. I only
>>>> just
>>>>>> started playing around with camel and liked it very much. Now there
>> is
>>>> a
>>>>>> good reason to take a deeper look.
>>>>>>
>>>>>> It's good to hear that Hibersap helped you with your project.
>>>> Regarding the
>>>>>> license, I think there should be no problems to combine libraries
>> that
>>>> are
>>>>>> under the Apache license and ones under LGPL (at least in their
>> current
>>>>>> versions). We initially liked the idea of a copyleft license and LGPL
>>>> is the
>>>>>> one most widely used. After all, I am not a lawyer and the big
>>>> disadvantage
>>>>>> of LGPL is that nobody seems to fully understand it and things are
>>>> open to
>>>>>> interpretation. Anyway, I'll have a talk with some people in my
>>>> company who
>>>>>> have a deeper understanding of OS licenses and we'll rethink the
>>>>>> licensing....
>>>>>>
>>>>>> If you got any questions feel free to contact me via email or use the
>>>>>> Hibersap forums or issue tracker on Sourceforge.
>>>>>>
>>>>>> Best Regards,
>>>>>> Carsten
>>>>>> (Founder of the Hibersap project)
>>>>>>
>>>>>> -
>>>>>
>>>>> --
>>>>> Christian Schneider
>>>>> http://www.liquid-reality.de
>>>>>
>>>>> Open Source Architect
>>>>> Talend Application Integration Division http://www.talend.com
>>>>>
>>>>
>>>>
>>>
>>
>
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
Re: Do Apache Camel needs a SAP integration?
Posted by Hadrian Zbarcea <hz...@gmail.com>.
I don't think hosting at the asf is an option (if that's what you meant)
but Romain's proposal works and is imho the best option.
Hadrian
On 03/15/2012 07:52 PM, Christian Müller wrote:
> I opened the JIRA to track this [1].
> I will also check with legal what possibilities we have to host the needed
> dependency but not to include it. I would like to run/build the component
> as all others and use mocks to test it.
>
> [1] https://issues.apache.org/jira/browse/CAMEL-5094
>
> Best,
> Christian
>
> 2012/3/6 Björn Bength<bj...@gmail.com>
>
>> Hi
>>
>> I forgot to open a JIRA for this.
>> But what do you mean? No, we can't add the dependencies to a repo, but
>> we can refer to a doc that describes what to do to add it to one's
>> local repo.
>> Maybe we can't include the component into camel-extra and have people
>> build the entire stack of camel-extra components without messing with
>> these jars, but there has to be a way of dealing with this sort of
>> problems too, right?
>>
>> camel-manual-extra project :-)
>> Or just use the project camel-hibersap from github and follow the
>> instructions.
>>
>> regards.
>> Björn
>>
>>
>> On Mon, Mar 5, 2012 at 11:47 PM, Romain Manni-Bucau
>> <rm...@gmail.com> wrote:
>>> Hi,
>>>
>>> can't it be added to the google project creating a repo in the source
>>> repository?
>>>
>>> - Romain
>>>
>>>
>>> 2012/3/5 Christian Müller<ch...@gmail.com>
>>>
>>>> I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to
>> an
>>>> ASF maven repository. Without it, we cannot build this component.
>> Because
>>>> of this, I see no way to host this component at camel-extra. :-(
>>>>
>>>> Best,
>>>> Christian
>>>>
>>>> On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller<
>>>> christian.mueller@gmail.com> wrote:
>>>>
>>>>> +1
>>>>> This will make a few things easier for us and for our users.
>>>>> Of course, we can host this component in camel-extra on googlecode,
>> but
>>>> we
>>>>> often ignore/forget these components (the last version is 2.8.0). And
>> I
>>>>> think many of our users don't know that we also host some components
>>>>> because of license reasons on camel-extra.
>>>>>
>>>>> I will checkout the code from github and play with it a bit...
>>>>>
>>>>> @Björn: If you are the owner of this contribution, could you please
>> open
>>>> a
>>>>> JIRA for this new component and attach it (don't forget to grant the
>>>> Apache
>>>>> license). Than we could put it into camel-extra and start to work to
>>>>> improve this component. And if Hibersap is licensed with a compatible
>>>>> license, we can move it into our repo at Apache.
>>>>>
>>>>> Best,
>>>>> Christian
>>>>>
>>>>> On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten<
>>>>> Carsten.Erker@akquinet.de> wrote:
>>>>>
>>>>>> Hi Christian,
>>>>>>
>>>>>> yes, a colleague who is Apache member just explained it to me.
>>>>>>
>>>>>> We are discussing about switching to ASL 2.0 with the next version.
>>>>>>
>>>>>> Regards,
>>>>>> Carsten
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>>>>>>
>>>>>>> Hi Carsten,
>>>>>>>
>>>>>>> you migth want to take a look at the Apache license policies:
>>>>>>> http://www.apache.org/legal/3party.html
>>>>>>>
>>>>>>> LGPL is listed as excluded so it may not be used as a dependency
>> of an
>>>>>> apache product (as far as I understand).
>>>>>>> I am not sure why it can´t be used but I guess some lawyer has
>> helped
>>>>>> with that policy.
>>>>>>>
>>>>>>> Christian
>>>>>>>
>>>>>>>
>>>>>>> Am 20.01.2012 09:27, schrieb cerker:
>>>>>>>> Björn, thanks a lot for sharing your camel-hibersap component. I
>> only
>>>>>> just
>>>>>>>> started playing around with camel and liked it very much. Now
>> there
>>>> is
>>>>>> a
>>>>>>>> good reason to take a deeper look.
>>>>>>>>
>>>>>>>> It's good to hear that Hibersap helped you with your project.
>>>>>> Regarding the
>>>>>>>> license, I think there should be no problems to combine libraries
>>>> that
>>>>>> are
>>>>>>>> under the Apache license and ones under LGPL (at least in their
>>>> current
>>>>>>>> versions). We initially liked the idea of a copyleft license and
>> LGPL
>>>>>> is the
>>>>>>>> one most widely used. After all, I am not a lawyer and the big
>>>>>> disadvantage
>>>>>>>> of LGPL is that nobody seems to fully understand it and things are
>>>>>> open to
>>>>>>>> interpretation. Anyway, I'll have a talk with some people in my
>>>>>> company who
>>>>>>>> have a deeper understanding of OS licenses and we'll rethink the
>>>>>>>> licensing....
>>>>>>>>
>>>>>>>> If you got any questions feel free to contact me via email or use
>> the
>>>>>>>> Hibersap forums or issue tracker on Sourceforge.
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>> Carsten
>>>>>>>> (Founder of the Hibersap project)
>>>>>>>>
>>>>>>>> -
>>>>>>>
>>>>>>> --
>>>>>>> Christian Schneider
>>>>>>> http://www.liquid-reality.de
>>>>>>>
>>>>>>> Open Source Architect
>>>>>>> Talend Application Integration Division http://www.talend.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
I opened the JIRA to track this [1].
I will also check with legal what possibilities we have to host the needed
dependency but not to include it. I would like to run/build the component
as all others and use mocks to test it.
[1] https://issues.apache.org/jira/browse/CAMEL-5094
Best,
Christian
2012/3/6 Björn Bength <bj...@gmail.com>
> Hi
>
> I forgot to open a JIRA for this.
> But what do you mean? No, we can't add the dependencies to a repo, but
> we can refer to a doc that describes what to do to add it to one's
> local repo.
> Maybe we can't include the component into camel-extra and have people
> build the entire stack of camel-extra components without messing with
> these jars, but there has to be a way of dealing with this sort of
> problems too, right?
>
> camel-manual-extra project :-)
> Or just use the project camel-hibersap from github and follow the
> instructions.
>
> regards.
> Björn
>
>
> On Mon, Mar 5, 2012 at 11:47 PM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
> > Hi,
> >
> > can't it be added to the google project creating a repo in the source
> > repository?
> >
> > - Romain
> >
> >
> > 2012/3/5 Christian Müller <ch...@gmail.com>
> >
> >> I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to
> an
> >> ASF maven repository. Without it, we cannot build this component.
> Because
> >> of this, I see no way to host this component at camel-extra. :-(
> >>
> >> Best,
> >> Christian
> >>
> >> On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller <
> >> christian.mueller@gmail.com> wrote:
> >>
> >> > +1
> >> > This will make a few things easier for us and for our users.
> >> > Of course, we can host this component in camel-extra on googlecode,
> but
> >> we
> >> > often ignore/forget these components (the last version is 2.8.0). And
> I
> >> > think many of our users don't know that we also host some components
> >> > because of license reasons on camel-extra.
> >> >
> >> > I will checkout the code from github and play with it a bit...
> >> >
> >> > @Björn: If you are the owner of this contribution, could you please
> open
> >> a
> >> > JIRA for this new component and attach it (don't forget to grant the
> >> Apache
> >> > license). Than we could put it into camel-extra and start to work to
> >> > improve this component. And if Hibersap is licensed with a compatible
> >> > license, we can move it into our repo at Apache.
> >> >
> >> > Best,
> >> > Christian
> >> >
> >> > On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten <
> >> > Carsten.Erker@akquinet.de> wrote:
> >> >
> >> >> Hi Christian,
> >> >>
> >> >> yes, a colleague who is Apache member just explained it to me.
> >> >>
> >> >> We are discussing about switching to ASL 2.0 with the next version.
> >> >>
> >> >> Regards,
> >> >> Carsten
> >> >>
> >> >>
> >> >>
> >> >> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
> >> >>
> >> >> > Hi Carsten,
> >> >> >
> >> >> > you migth want to take a look at the Apache license policies:
> >> >> > http://www.apache.org/legal/3party.html
> >> >> >
> >> >> > LGPL is listed as excluded so it may not be used as a dependency
> of an
> >> >> apache product (as far as I understand).
> >> >> > I am not sure why it can´t be used but I guess some lawyer has
> helped
> >> >> with that policy.
> >> >> >
> >> >> > Christian
> >> >> >
> >> >> >
> >> >> > Am 20.01.2012 09:27, schrieb cerker:
> >> >> >> Björn, thanks a lot for sharing your camel-hibersap component. I
> only
> >> >> just
> >> >> >> started playing around with camel and liked it very much. Now
> there
> >> is
> >> >> a
> >> >> >> good reason to take a deeper look.
> >> >> >>
> >> >> >> It's good to hear that Hibersap helped you with your project.
> >> >> Regarding the
> >> >> >> license, I think there should be no problems to combine libraries
> >> that
> >> >> are
> >> >> >> under the Apache license and ones under LGPL (at least in their
> >> current
> >> >> >> versions). We initially liked the idea of a copyleft license and
> LGPL
> >> >> is the
> >> >> >> one most widely used. After all, I am not a lawyer and the big
> >> >> disadvantage
> >> >> >> of LGPL is that nobody seems to fully understand it and things are
> >> >> open to
> >> >> >> interpretation. Anyway, I'll have a talk with some people in my
> >> >> company who
> >> >> >> have a deeper understanding of OS licenses and we'll rethink the
> >> >> >> licensing....
> >> >> >>
> >> >> >> If you got any questions feel free to contact me via email or use
> the
> >> >> >> Hibersap forums or issue tracker on Sourceforge.
> >> >> >>
> >> >> >> Best Regards,
> >> >> >> Carsten
> >> >> >> (Founder of the Hibersap project)
> >> >> >>
> >> >> >> -
> >> >> >
> >> >> > --
> >> >> > Christian Schneider
> >> >> > http://www.liquid-reality.de
> >> >> >
> >> >> > Open Source Architect
> >> >> > Talend Application Integration Division http://www.talend.com
> >> >> >
> >> >>
> >> >>
> >> >
> >>
>
Re: Do Apache Camel needs a SAP integration?
Posted by Björn Bength <bj...@gmail.com>.
Hi
I forgot to open a JIRA for this.
But what do you mean? No, we can't add the dependencies to a repo, but
we can refer to a doc that describes what to do to add it to one's
local repo.
Maybe we can't include the component into camel-extra and have people
build the entire stack of camel-extra components without messing with
these jars, but there has to be a way of dealing with this sort of
problems too, right?
camel-manual-extra project :-)
Or just use the project camel-hibersap from github and follow the instructions.
regards.
Björn
On Mon, Mar 5, 2012 at 11:47 PM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> Hi,
>
> can't it be added to the google project creating a repo in the source
> repository?
>
> - Romain
>
>
> 2012/3/5 Christian Müller <ch...@gmail.com>
>
>> I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to an
>> ASF maven repository. Without it, we cannot build this component. Because
>> of this, I see no way to host this component at camel-extra. :-(
>>
>> Best,
>> Christian
>>
>> On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller <
>> christian.mueller@gmail.com> wrote:
>>
>> > +1
>> > This will make a few things easier for us and for our users.
>> > Of course, we can host this component in camel-extra on googlecode, but
>> we
>> > often ignore/forget these components (the last version is 2.8.0). And I
>> > think many of our users don't know that we also host some components
>> > because of license reasons on camel-extra.
>> >
>> > I will checkout the code from github and play with it a bit...
>> >
>> > @Björn: If you are the owner of this contribution, could you please open
>> a
>> > JIRA for this new component and attach it (don't forget to grant the
>> Apache
>> > license). Than we could put it into camel-extra and start to work to
>> > improve this component. And if Hibersap is licensed with a compatible
>> > license, we can move it into our repo at Apache.
>> >
>> > Best,
>> > Christian
>> >
>> > On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten <
>> > Carsten.Erker@akquinet.de> wrote:
>> >
>> >> Hi Christian,
>> >>
>> >> yes, a colleague who is Apache member just explained it to me.
>> >>
>> >> We are discussing about switching to ASL 2.0 with the next version.
>> >>
>> >> Regards,
>> >> Carsten
>> >>
>> >>
>> >>
>> >> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>> >>
>> >> > Hi Carsten,
>> >> >
>> >> > you migth want to take a look at the Apache license policies:
>> >> > http://www.apache.org/legal/3party.html
>> >> >
>> >> > LGPL is listed as excluded so it may not be used as a dependency of an
>> >> apache product (as far as I understand).
>> >> > I am not sure why it can´t be used but I guess some lawyer has helped
>> >> with that policy.
>> >> >
>> >> > Christian
>> >> >
>> >> >
>> >> > Am 20.01.2012 09:27, schrieb cerker:
>> >> >> Björn, thanks a lot for sharing your camel-hibersap component. I only
>> >> just
>> >> >> started playing around with camel and liked it very much. Now there
>> is
>> >> a
>> >> >> good reason to take a deeper look.
>> >> >>
>> >> >> It's good to hear that Hibersap helped you with your project.
>> >> Regarding the
>> >> >> license, I think there should be no problems to combine libraries
>> that
>> >> are
>> >> >> under the Apache license and ones under LGPL (at least in their
>> current
>> >> >> versions). We initially liked the idea of a copyleft license and LGPL
>> >> is the
>> >> >> one most widely used. After all, I am not a lawyer and the big
>> >> disadvantage
>> >> >> of LGPL is that nobody seems to fully understand it and things are
>> >> open to
>> >> >> interpretation. Anyway, I'll have a talk with some people in my
>> >> company who
>> >> >> have a deeper understanding of OS licenses and we'll rethink the
>> >> >> licensing....
>> >> >>
>> >> >> If you got any questions feel free to contact me via email or use the
>> >> >> Hibersap forums or issue tracker on Sourceforge.
>> >> >>
>> >> >> Best Regards,
>> >> >> Carsten
>> >> >> (Founder of the Hibersap project)
>> >> >>
>> >> >> -
>> >> >
>> >> > --
>> >> > Christian Schneider
>> >> > http://www.liquid-reality.de
>> >> >
>> >> > Open Source Architect
>> >> > Talend Application Integration Division http://www.talend.com
>> >> >
>> >>
>> >>
>> >
>>
Re: Do Apache Camel needs a SAP integration?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi,
can't it be added to the google project creating a repo in the source
repository?
- Romain
2012/3/5 Christian Müller <ch...@gmail.com>
> I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to an
> ASF maven repository. Without it, we cannot build this component. Because
> of this, I see no way to host this component at camel-extra. :-(
>
> Best,
> Christian
>
> On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller <
> christian.mueller@gmail.com> wrote:
>
> > +1
> > This will make a few things easier for us and for our users.
> > Of course, we can host this component in camel-extra on googlecode, but
> we
> > often ignore/forget these components (the last version is 2.8.0). And I
> > think many of our users don't know that we also host some components
> > because of license reasons on camel-extra.
> >
> > I will checkout the code from github and play with it a bit...
> >
> > @Björn: If you are the owner of this contribution, could you please open
> a
> > JIRA for this new component and attach it (don't forget to grant the
> Apache
> > license). Than we could put it into camel-extra and start to work to
> > improve this component. And if Hibersap is licensed with a compatible
> > license, we can move it into our repo at Apache.
> >
> > Best,
> > Christian
> >
> > On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten <
> > Carsten.Erker@akquinet.de> wrote:
> >
> >> Hi Christian,
> >>
> >> yes, a colleague who is Apache member just explained it to me.
> >>
> >> We are discussing about switching to ASL 2.0 with the next version.
> >>
> >> Regards,
> >> Carsten
> >>
> >>
> >>
> >> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
> >>
> >> > Hi Carsten,
> >> >
> >> > you migth want to take a look at the Apache license policies:
> >> > http://www.apache.org/legal/3party.html
> >> >
> >> > LGPL is listed as excluded so it may not be used as a dependency of an
> >> apache product (as far as I understand).
> >> > I am not sure why it can´t be used but I guess some lawyer has helped
> >> with that policy.
> >> >
> >> > Christian
> >> >
> >> >
> >> > Am 20.01.2012 09:27, schrieb cerker:
> >> >> Björn, thanks a lot for sharing your camel-hibersap component. I only
> >> just
> >> >> started playing around with camel and liked it very much. Now there
> is
> >> a
> >> >> good reason to take a deeper look.
> >> >>
> >> >> It's good to hear that Hibersap helped you with your project.
> >> Regarding the
> >> >> license, I think there should be no problems to combine libraries
> that
> >> are
> >> >> under the Apache license and ones under LGPL (at least in their
> current
> >> >> versions). We initially liked the idea of a copyleft license and LGPL
> >> is the
> >> >> one most widely used. After all, I am not a lawyer and the big
> >> disadvantage
> >> >> of LGPL is that nobody seems to fully understand it and things are
> >> open to
> >> >> interpretation. Anyway, I'll have a talk with some people in my
> >> company who
> >> >> have a deeper understanding of OS licenses and we'll rethink the
> >> >> licensing....
> >> >>
> >> >> If you got any questions feel free to contact me via email or use the
> >> >> Hibersap forums or issue tracker on Sourceforge.
> >> >>
> >> >> Best Regards,
> >> >> Carsten
> >> >> (Founder of the Hibersap project)
> >> >>
> >> >> -
> >> >
> >> > --
> >> > Christian Schneider
> >> > http://www.liquid-reality.de
> >> >
> >> > Open Source Architect
> >> > Talend Application Integration Division http://www.talend.com
> >> >
> >>
> >>
> >
>
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to an
ASF maven repository. Without it, we cannot build this component. Because
of this, I see no way to host this component at camel-extra. :-(
Best,
Christian
On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller <
christian.mueller@gmail.com> wrote:
> +1
> This will make a few things easier for us and for our users.
> Of course, we can host this component in camel-extra on googlecode, but we
> often ignore/forget these components (the last version is 2.8.0). And I
> think many of our users don't know that we also host some components
> because of license reasons on camel-extra.
>
> I will checkout the code from github and play with it a bit...
>
> @Björn: If you are the owner of this contribution, could you please open a
> JIRA for this new component and attach it (don't forget to grant the Apache
> license). Than we could put it into camel-extra and start to work to
> improve this component. And if Hibersap is licensed with a compatible
> license, we can move it into our repo at Apache.
>
> Best,
> Christian
>
> On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten <
> Carsten.Erker@akquinet.de> wrote:
>
>> Hi Christian,
>>
>> yes, a colleague who is Apache member just explained it to me.
>>
>> We are discussing about switching to ASL 2.0 with the next version.
>>
>> Regards,
>> Carsten
>>
>>
>>
>> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>>
>> > Hi Carsten,
>> >
>> > you migth want to take a look at the Apache license policies:
>> > http://www.apache.org/legal/3party.html
>> >
>> > LGPL is listed as excluded so it may not be used as a dependency of an
>> apache product (as far as I understand).
>> > I am not sure why it can´t be used but I guess some lawyer has helped
>> with that policy.
>> >
>> > Christian
>> >
>> >
>> > Am 20.01.2012 09:27, schrieb cerker:
>> >> Björn, thanks a lot for sharing your camel-hibersap component. I only
>> just
>> >> started playing around with camel and liked it very much. Now there is
>> a
>> >> good reason to take a deeper look.
>> >>
>> >> It's good to hear that Hibersap helped you with your project.
>> Regarding the
>> >> license, I think there should be no problems to combine libraries that
>> are
>> >> under the Apache license and ones under LGPL (at least in their current
>> >> versions). We initially liked the idea of a copyleft license and LGPL
>> is the
>> >> one most widely used. After all, I am not a lawyer and the big
>> disadvantage
>> >> of LGPL is that nobody seems to fully understand it and things are
>> open to
>> >> interpretation. Anyway, I'll have a talk with some people in my
>> company who
>> >> have a deeper understanding of OS licenses and we'll rethink the
>> >> licensing....
>> >>
>> >> If you got any questions feel free to contact me via email or use the
>> >> Hibersap forums or issue tracker on Sourceforge.
>> >>
>> >> Best Regards,
>> >> Carsten
>> >> (Founder of the Hibersap project)
>> >>
>> >> -
>> >
>> > --
>> > Christian Schneider
>> > http://www.liquid-reality.de
>> >
>> > Open Source Architect
>> > Talend Application Integration Division http://www.talend.com
>> >
>>
>>
>
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
+1
This will make a few things easier for us and for our users.
Of course, we can host this component in camel-extra on googlecode, but we
often ignore/forget these components (the last version is 2.8.0). And I
think many of our users don't know that we also host some components
because of license reasons on camel-extra.
I will checkout the code from github and play with it a bit...
@Björn: If you are the owner of this contribution, could you please open a
JIRA for this new component and attach it (don't forget to grant the Apache
license). Than we could put it into camel-extra and start to work to
improve this component. And if Hibersap is licensed with a compatible
license, we can move it into our repo at Apache.
Best,
Christian
On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten
<Ca...@akquinet.de>wrote:
> Hi Christian,
>
> yes, a colleague who is Apache member just explained it to me.
>
> We are discussing about switching to ASL 2.0 with the next version.
>
> Regards,
> Carsten
>
>
>
> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>
> > Hi Carsten,
> >
> > you migth want to take a look at the Apache license policies:
> > http://www.apache.org/legal/3party.html
> >
> > LGPL is listed as excluded so it may not be used as a dependency of an
> apache product (as far as I understand).
> > I am not sure why it can´t be used but I guess some lawyer has helped
> with that policy.
> >
> > Christian
> >
> >
> > Am 20.01.2012 09:27, schrieb cerker:
> >> Björn, thanks a lot for sharing your camel-hibersap component. I only
> just
> >> started playing around with camel and liked it very much. Now there is a
> >> good reason to take a deeper look.
> >>
> >> It's good to hear that Hibersap helped you with your project. Regarding
> the
> >> license, I think there should be no problems to combine libraries that
> are
> >> under the Apache license and ones under LGPL (at least in their current
> >> versions). We initially liked the idea of a copyleft license and LGPL
> is the
> >> one most widely used. After all, I am not a lawyer and the big
> disadvantage
> >> of LGPL is that nobody seems to fully understand it and things are open
> to
> >> interpretation. Anyway, I'll have a talk with some people in my company
> who
> >> have a deeper understanding of OS licenses and we'll rethink the
> >> licensing....
> >>
> >> If you got any questions feel free to contact me via email or use the
> >> Hibersap forums or issue tracker on Sourceforge.
> >>
> >> Best Regards,
> >> Carsten
> >> (Founder of the Hibersap project)
> >>
> >> -
> >
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Open Source Architect
> > Talend Application Integration Division http://www.talend.com
> >
>
>
Re: Do Apache Camel needs a SAP integration?
Posted by "Erker, Carsten" <Ca...@akquinet.de>.
Hi Christian,
yes, a colleague who is Apache member just explained it to me.
We are discussing about switching to ASL 2.0 with the next version.
Regards,
Carsten
Am 20.01.2012 um 10:36 schrieb Christian Schneider:
> Hi Carsten,
>
> you migth want to take a look at the Apache license policies:
> http://www.apache.org/legal/3party.html
>
> LGPL is listed as excluded so it may not be used as a dependency of an apache product (as far as I understand).
> I am not sure why it can´t be used but I guess some lawyer has helped with that policy.
>
> Christian
>
>
> Am 20.01.2012 09:27, schrieb cerker:
>> Björn, thanks a lot for sharing your camel-hibersap component. I only just
>> started playing around with camel and liked it very much. Now there is a
>> good reason to take a deeper look.
>>
>> It's good to hear that Hibersap helped you with your project. Regarding the
>> license, I think there should be no problems to combine libraries that are
>> under the Apache license and ones under LGPL (at least in their current
>> versions). We initially liked the idea of a copyleft license and LGPL is the
>> one most widely used. After all, I am not a lawyer and the big disadvantage
>> of LGPL is that nobody seems to fully understand it and things are open to
>> interpretation. Anyway, I'll have a talk with some people in my company who
>> have a deeper understanding of OS licenses and we'll rethink the
>> licensing....
>>
>> If you got any questions feel free to contact me via email or use the
>> Hibersap forums or issue tracker on Sourceforge.
>>
>> Best Regards,
>> Carsten
>> (Founder of the Hibersap project)
>>
>> -
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Carsten,
you migth want to take a look at the Apache license policies:
http://www.apache.org/legal/3party.html
LGPL is listed as excluded so it may not be used as a dependency of an
apache product (as far as I understand).
I am not sure why it can´t be used but I guess some lawyer has helped
with that policy.
Christian
Am 20.01.2012 09:27, schrieb cerker:
> Björn, thanks a lot for sharing your camel-hibersap component. I only just
> started playing around with camel and liked it very much. Now there is a
> good reason to take a deeper look.
>
> It's good to hear that Hibersap helped you with your project. Regarding the
> license, I think there should be no problems to combine libraries that are
> under the Apache license and ones under LGPL (at least in their current
> versions). We initially liked the idea of a copyleft license and LGPL is the
> one most widely used. After all, I am not a lawyer and the big disadvantage
> of LGPL is that nobody seems to fully understand it and things are open to
> interpretation. Anyway, I'll have a talk with some people in my company who
> have a deeper understanding of OS licenses and we'll rethink the
> licensing....
>
> If you got any questions feel free to contact me via email or use the
> Hibersap forums or issue tracker on Sourceforge.
>
> Best Regards,
> Carsten
> (Founder of the Hibersap project)
>
> -
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: Do Apache Camel needs a SAP integration?
Posted by cerker <ca...@akquinet.de>.
Björn, thanks a lot for sharing your camel-hibersap component. I only just
started playing around with camel and liked it very much. Now there is a
good reason to take a deeper look.
It's good to hear that Hibersap helped you with your project. Regarding the
license, I think there should be no problems to combine libraries that are
under the Apache license and ones under LGPL (at least in their current
versions). We initially liked the idea of a copyleft license and LGPL is the
one most widely used. After all, I am not a lawyer and the big disadvantage
of LGPL is that nobody seems to fully understand it and things are open to
interpretation. Anyway, I'll have a talk with some people in my company who
have a deeper understanding of OS licenses and we'll rethink the
licensing....
If you got any questions feel free to contact me via email or use the
Hibersap forums or issue tracker on Sourceforge.
Best Regards,
Carsten
(Founder of the Hibersap project)
--
View this message in context: http://camel.465427.n5.nabble.com/Do-Apache-Camel-needs-a-SAP-integration-tp5144926p5159788.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Do Apache Camel needs a SAP integration?
Posted by Björn Bength <bj...@gmail.com>.
Hello
After some adjustments to make the code shareable, I just pushed the
camel-hibersap component to GitHub.
You can find it at https://github.com/bjoben/camel-hibersap
I realized that the actual camel part of it is very small and does not
include transaction or proper thread pool support yet.
However, similar component is used by our client and works very well
in our camel integration code (based on ServiceMix).
It compiles as an osgi bundle and embeds JCo and hibersap libraries,
neither which i'm redistributing.
Therefore you have to compile it yourself, after installing JCo and
hibersap into you own maven repo.
(This is very well documented in the hibersap documentation)
You can use it as it is, or treat it like an example from which to
base a better component.
I don't have an SAP server at hand, so I can't make it better right now.
Also, the unit tests use a real SAP server, so they are disabled for
now, and should be made into an integration test suit,
but they are the best example of how to use this component. So have a
look at those. They are very simple but demonstrates usage very well.
More examples can be found at the hibersap site.
Regards
Björn
On Mon, Jan 16, 2012 at 10:16 AM, Guillaume Yziquel
<gu...@crossing-tech.com> wrote:
> Le Saturday 14 Jan 2012 à 15:37:38 (+0100), Björn Bength a écrit :
>> Hi
>>
>> At our client (a bank) in Sweden, we created a camel component that
>> integrated their SAP server.
>> It can only call BAPI functions right now but it uses JCo of course,
>> and Hibersap which allows to annotate java beans just send it through
>> to the camel endpoint. All this on ServiceMix where we made the
>> camel-SAP (with jco) component OSGi firendly.
>>
>> It worked so well that those SAP guys we worked with told us that they
>> never before had an integration project that actually worked on _the
>> first_ test transaction.
>>
>> Unfortunatly hibersap is LGPL but it really (really) makes working
>> with Jco sooo much easier.
>> And just maybe hibersap can convert it's license, but from another
>> thread (MongoDB) I got the feeling that all of you like to have a
>> "native" camel component in all cases.
>>
>> My intention was to put this on GitHub though, but I never took time to do so.
>> I could share the parts I wrote if someone is interested, and call it
>> camel-hibersap.
>>
>> Regards
>> Björn
>
> I guess it would be quite nice to put such a Camel Component on Github.
> Please feel free to do so and keep us updated.
>
> --
> Guillaume Yziquel
Re: Do Apache Camel needs a SAP integration?
Posted by Guillaume Yziquel <gu...@crossing-tech.com>.
Le Saturday 14 Jan 2012 à 15:37:38 (+0100), Björn Bength a écrit :
> Hi
>
> At our client (a bank) in Sweden, we created a camel component that
> integrated their SAP server.
> It can only call BAPI functions right now but it uses JCo of course,
> and Hibersap which allows to annotate java beans just send it through
> to the camel endpoint. All this on ServiceMix where we made the
> camel-SAP (with jco) component OSGi firendly.
>
> It worked so well that those SAP guys we worked with told us that they
> never before had an integration project that actually worked on _the
> first_ test transaction.
>
> Unfortunatly hibersap is LGPL but it really (really) makes working
> with Jco sooo much easier.
> And just maybe hibersap can convert it's license, but from another
> thread (MongoDB) I got the feeling that all of you like to have a
> "native" camel component in all cases.
>
> My intention was to put this on GitHub though, but I never took time to do so.
> I could share the parts I wrote if someone is interested, and call it
> camel-hibersap.
>
> Regards
> Björn
I guess it would be quite nice to put such a Camel Component on Github.
Please feel free to do so and keep us updated.
--
Guillaume Yziquel
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Müller <ch...@gmail.com>.
We cannot host such kind of component directly at Apache [1], but at
apache-extra on googlecode [2].
I could imagine this is an EE feature for which some users are looking for.
I will have a look at it in the next days...
And if you are the owner of the code, you may know we love contributions...
:-)
[1] http://www.apache.org/legal/3party.html
[2] http://code.google.com/a/apache-extras.org/p/camel-extra/?redir=1
Best,
Christian
On Sat, Jan 14, 2012 at 11:43 PM, Hadrian Zbarcea <hz...@gmail.com>wrote:
> That is correct. The owner of the code (which may not necessarily be the
> author!) can (re)license the work at any time under whatever terms he
> likes. If the work is relicensed, the previous licensing terms still apply
> to the old code.
>
> Cheers,
> Hadrian
>
>
>
> On 01/14/2012 11:47 AM, Christian Schneider wrote:
>
>> Hi Björn,
>>
>> sounds great. I am looking forward to it. I think you could dual license
>> your own code with apache and lgpl. Btw. there is camel-extra which holds
>> some camel components that are not fully apache licensed.
>> http://code.google.com/a/**apache-extras.org/p/camel-**extra/?redir=1<http://code.google.com/a/apache-extras.org/p/camel-extra/?redir=1>
>> So that case is not really uncommon.
>>
>> Christian
>>
>>
>> Am 14.01.2012 15:37, schrieb Björn Bength:
>>
>>> Hi
>>>
>>> At our client (a bank) in Sweden, we created a camel component that
>>> integrated their SAP server.
>>> It can only call BAPI functions right now but it uses JCo of course,
>>> and Hibersap which allows to annotate java beans just send it through
>>> to the camel endpoint. All this on ServiceMix where we made the
>>> camel-SAP (with jco) component OSGi firendly.
>>>
>>> It worked so well that those SAP guys we worked with told us that they
>>> never before had an integration project that actually worked on _the
>>> first_ test transaction.
>>>
>>> Unfortunatly hibersap is LGPL but it really (really) makes working
>>> with Jco sooo much easier.
>>> And just maybe hibersap can convert it's license, but from another
>>> thread (MongoDB) I got the feeling that all of you like to have a
>>> "native" camel component in all cases.
>>>
>>> My intention was to put this on GitHub though, but I never took time
>>> to do so.
>>> I could share the parts I wrote if someone is interested, and call it
>>> camel-hibersap.
>>>
>>> Regards
>>> Björn
>>>
>>>
>>>
>>> On Sat, Jan 14, 2012 at 1:44 PM, Christian Müller
>>> <ch...@gmail.com> wrote:
>>>
>>>> Hello list!
>>>>
>>>> One year ago I was thinking about "Do Apache Camel needs a SAP
>>>> integration?".
>>>>
>>>> Last week I got an announcement from Mulesoft and their SAP integration
>>>> [1]. And now I'm thinking about it again: Do Apache Camel needs a SAP
>>>> integration? Did you already missed this integration?
>>>>
>>>> I'm highly interested in your opinion.
>>>>
>>>> [1] http://www.mulesoft.com/sap-**integration<http://www.mulesoft.com/sap-integration>
>>>>
>>>> Best,
>>>> Christian
>>>>
>>>
>>
>>
> --
> Hadrian Zbarcea
> Principal Software Architect
> Talend, Inc
> http://coders.talend.com/
> http://camelbot.blogspot.com/
>
Re: Do Apache Camel needs a SAP integration?
Posted by Hadrian Zbarcea <hz...@gmail.com>.
That is correct. The owner of the code (which may not necessarily be the
author!) can (re)license the work at any time under whatever terms he
likes. If the work is relicensed, the previous licensing terms still
apply to the old code.
Cheers,
Hadrian
On 01/14/2012 11:47 AM, Christian Schneider wrote:
> Hi Björn,
>
> sounds great. I am looking forward to it. I think you could dual license
> your own code with apache and lgpl. Btw. there is camel-extra which holds
> some camel components that are not fully apache licensed.
> http://code.google.com/a/apache-extras.org/p/camel-extra/?redir=1
> So that case is not really uncommon.
>
> Christian
>
>
> Am 14.01.2012 15:37, schrieb Björn Bength:
>> Hi
>>
>> At our client (a bank) in Sweden, we created a camel component that
>> integrated their SAP server.
>> It can only call BAPI functions right now but it uses JCo of course,
>> and Hibersap which allows to annotate java beans just send it through
>> to the camel endpoint. All this on ServiceMix where we made the
>> camel-SAP (with jco) component OSGi firendly.
>>
>> It worked so well that those SAP guys we worked with told us that they
>> never before had an integration project that actually worked on _the
>> first_ test transaction.
>>
>> Unfortunatly hibersap is LGPL but it really (really) makes working
>> with Jco sooo much easier.
>> And just maybe hibersap can convert it's license, but from another
>> thread (MongoDB) I got the feeling that all of you like to have a
>> "native" camel component in all cases.
>>
>> My intention was to put this on GitHub though, but I never took time
>> to do so.
>> I could share the parts I wrote if someone is interested, and call it
>> camel-hibersap.
>>
>> Regards
>> Björn
>>
>>
>>
>> On Sat, Jan 14, 2012 at 1:44 PM, Christian Müller
>> <ch...@gmail.com> wrote:
>>> Hello list!
>>>
>>> One year ago I was thinking about "Do Apache Camel needs a SAP
>>> integration?".
>>>
>>> Last week I got an announcement from Mulesoft and their SAP integration
>>> [1]. And now I'm thinking about it again: Do Apache Camel needs a SAP
>>> integration? Did you already missed this integration?
>>>
>>> I'm highly interested in your opinion.
>>>
>>> [1] http://www.mulesoft.com/sap-integration
>>>
>>> Best,
>>> Christian
>
>
--
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/
Re: Do Apache Camel needs a SAP integration?
Posted by Christian Schneider <ch...@die-schneider.net>.
Hi Björn,
sounds great. I am looking forward to it. I think you could dual license
your own code with apache and lgpl. Btw. there is camel-extra which holds
some camel components that are not fully apache licensed.
http://code.google.com/a/apache-extras.org/p/camel-extra/?redir=1
So that case is not really uncommon.
Christian
Am 14.01.2012 15:37, schrieb Björn Bength:
> Hi
>
> At our client (a bank) in Sweden, we created a camel component that
> integrated their SAP server.
> It can only call BAPI functions right now but it uses JCo of course,
> and Hibersap which allows to annotate java beans just send it through
> to the camel endpoint. All this on ServiceMix where we made the
> camel-SAP (with jco) component OSGi firendly.
>
> It worked so well that those SAP guys we worked with told us that they
> never before had an integration project that actually worked on _the
> first_ test transaction.
>
> Unfortunatly hibersap is LGPL but it really (really) makes working
> with Jco sooo much easier.
> And just maybe hibersap can convert it's license, but from another
> thread (MongoDB) I got the feeling that all of you like to have a
> "native" camel component in all cases.
>
> My intention was to put this on GitHub though, but I never took time to do so.
> I could share the parts I wrote if someone is interested, and call it
> camel-hibersap.
>
> Regards
> Björn
>
>
>
> On Sat, Jan 14, 2012 at 1:44 PM, Christian Müller
> <ch...@gmail.com> wrote:
>> Hello list!
>>
>> One year ago I was thinking about "Do Apache Camel needs a SAP
>> integration?".
>>
>> Last week I got an announcement from Mulesoft and their SAP integration
>> [1]. And now I'm thinking about it again: Do Apache Camel needs a SAP
>> integration? Did you already missed this integration?
>>
>> I'm highly interested in your opinion.
>>
>> [1] http://www.mulesoft.com/sap-integration
>>
>> Best,
>> Christian
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
Re: Do Apache Camel needs a SAP integration?
Posted by Björn Bength <bj...@gmail.com>.
Hi
At our client (a bank) in Sweden, we created a camel component that
integrated their SAP server.
It can only call BAPI functions right now but it uses JCo of course,
and Hibersap which allows to annotate java beans just send it through
to the camel endpoint. All this on ServiceMix where we made the
camel-SAP (with jco) component OSGi firendly.
It worked so well that those SAP guys we worked with told us that they
never before had an integration project that actually worked on _the
first_ test transaction.
Unfortunatly hibersap is LGPL but it really (really) makes working
with Jco sooo much easier.
And just maybe hibersap can convert it's license, but from another
thread (MongoDB) I got the feeling that all of you like to have a
"native" camel component in all cases.
My intention was to put this on GitHub though, but I never took time to do so.
I could share the parts I wrote if someone is interested, and call it
camel-hibersap.
Regards
Björn
On Sat, Jan 14, 2012 at 1:44 PM, Christian Müller
<ch...@gmail.com> wrote:
> Hello list!
>
> One year ago I was thinking about "Do Apache Camel needs a SAP
> integration?".
>
> Last week I got an announcement from Mulesoft and their SAP integration
> [1]. And now I'm thinking about it again: Do Apache Camel needs a SAP
> integration? Did you already missed this integration?
>
> I'm highly interested in your opinion.
>
> [1] http://www.mulesoft.com/sap-integration
>
> Best,
> Christian