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 <hzbar...@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 >>> <christian.muel...@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/ >
