camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Karlsen <davidkarl...@gmail.com>
Subject Re: [jira] [Issue Comment Edited] (CAMEL-4164) A camel component for ISO8583 protocol
Date Sun, 27 Jan 2013 15:39:39 GMT
We have a need for such functionality at work.
But it would need to use a business-friendly license.
Would also need support for packed EBCDIC format.
Could possible chip in on this if that was the case.

2013/1/27 Christian Müller <christian.mueller@gmail.com>:
> I think creating "only" a data format for this kind of functionality is the
> right thing instead of creating a "full blown" Camel component.
>
> We COULD add this new data format to Camel, if you want to donate the Camel
> data format. But, ...
>
> What concerns me a bit is, that you are the only one member of the isotypes
> project Camel will than depend on. Not a big or diverse community... But it
> also makes no sense for me to add this code to Camel (if you want to donate
> this code too).
> We will see what the others users/contributors/comitters/PMC members are
> thinking about it...
>
> Best,
> Christian
>
> On Fri, Jan 18, 2013 at 11:55 AM, sothach <phillips.roy@gmail.com> wrote:
>
>> I have been working to integrate ISO8583 messaging with Camel, and the
>> approach I have taken is to create a custom DataFormat, to perform message
>> marshaling/unmarshaling in a Camel route, rather than as a full-on
>> endpoint:
>> this separates the concerns of transformation and transport, in keeping
>> with
>> my understanding of the Camel/EIP philosophy. Transformed messages can then
>> be routed to MINA, Netty, a JMS queue or wherever, for transmission.
>>
>> To facilitate this, I have published an ISO8583 transformation library
>> under
>> an Apache-2 license:  http://code.google.com/p/isotypes/
>> <http://code.google.com/p/isotypes/>
>>
>> I have described how I think this can be best integrated with Camel here:
>> Camel Integration <http://code.google.com/p/isotypes/wiki/CamelIntegration
>> >
>> , but as a relative newcomer to Camel, would appreciate any
>> suggestions/comments from you guys. thx!
>>
>>
>> JIRA jira@apache.org wrote
>> > [
>> >
>> https://issues.apache.org/jira/browse/CAMEL-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059615#comment-13059615
>> > ]
>> >
>> > Richard Kettelerij edited comment on CAMEL-4164 at 7/4/11 9:19 PM:
>> > -------------------------------------------------------------------
>> >
>> > @Ashwin
>> > AGPL is not compatible with the Apache license. See
>> > http://www.apache.org/legal/3party.html, AGPL classifies as "Special
>> > exceptions to the GNU GPL". So if Lekan's contribution uses JPOS we can't
>> > host it at Apache.org, but we can host it a Apache-extras.org
>> > (http://code.google.com/a/apache-extras.org/p/camel-extra/).
>> >
>> > @Lekan,
>> > I've done a few Google searches and JPOS seems to be the most well-known
>> > open source ISO8583 implementation. Apart from this perfectly valid
>> > reason, are there other motivations for choosing JPOS? I've found this
>> > Apache licensed implementation for example:
>> > http://code.google.com/p/nucleus8583/.
>> >
>> > Edit: Gert beat me with his comment :)
>> >
>> >       was (Author: rkettelerij):
>> >     @Ashwin
>> > AGPL is not compatible with the Apache license. See
>> > http://www.apache.org/legal/3party.html, AGPL classifies as "Special
>> > exceptions to the GNU GPL". So if Lekan's contribution uses JPOS we can't
>> > host it at Apache.org, but we can host it a Apache-extras.org
>> > (http://code.google.com/a/apache-extras.org/p/camel-extra/).
>> >
>> > @Lekan,
>> > I've done a few Google searches and JPOS seems to be the most well-known
>> > open source ISO8583 implementation. Apart from this perfectly valid
>> > reason, are there other motivations for choosing JPOS? I've found this
>> > Apache licensed implementation for example:
>> > http://code.google.com/p/nucleus8583/.
>> >
>> >
>> >
>> >> A camel component for ISO8583 protocol
>> >> --------------------------------------
>> >>
>> >>                 Key: CAMEL-4164
>> >>                 URL: https://issues.apache.org/jira/browse/CAMEL-4164
>> >>             Project: Camel
>> >>          Issue Type: New Feature
>> >>            Reporter: Lekan Omotayo
>> >>              Labels: camel-iso,, camel-iso8583,
>> >>
>> >> A new component to interface with ISO8583 protocol. When started as a
>> >> consumer, it listens on a port, and when started as a producer, it
>> >> connects to a remote server. Let me know if this has been useful to you.
>> >
>> > --
>> > This message is automatically generated by JIRA.
>> > For more information on JIRA, see:
>> http://www.atlassian.com/software/jira
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/jira-Created-CAMEL-4164-A-camel-component-for-ISO8583-protocol-tp4537054p5725744.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>
>
>
> --



-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

Mime
View raw message