>Eclipse: Hidden Gems

>Every once in a while it’s good to turn over some rocks. Lately, I’ve been tossed into the world of SOA and Enterprise Integration Patterns. This lead me down an investigation of the Apache Camel project.

Camel is an interesting project in itself, as it can help wire together a lot of integration points. Half the time we spend is just hooking things together to move data from one place to another.
Link
In the investigation of camel, I came across the Eclipse STP EID project. However, it looks like it is on life support at the moment. However, I hope to help try and revive it a bit. The one thing I’m really interested in from the project is its visual designer.


Allow you to layout the Enterprise Integration Patterns visually that Camel can support. I suspect there is a lot of work to do since on the project Wiki, Oisin is practically begging for help:

* This little project is in URGENT NEED OF HELP!
* We are desperately seeking developers who can help take on open bugs
* We are desperately seeking developers to help refresh and add to the examples using our extension points.
* EID is not going to be part of the Galileo release as it will not build with EMF 2.5.
* Yes, EID is only available for the *Eclipse 3.4.x* stream

So as you can see. If you are looking to help resurrect a project, or get your feet wet. The STP EID project may be a great opportunity to help the community. Sounds like they really, really, need it.

Advertisements
This entry was posted in camel, eclipse, eid. Bookmark the permalink.

3 Responses to >Eclipse: Hidden Gems

  1. Scott Lewis says:

    >Hi Dave. For SOA OSGi/EF style + messaging/JMS integration please see http://eclipseecf.blogspot.com/. JMS provider at https://ecf2.osuosl.org/hudson/

  2. oisin says:

    >It would be very cool to get this up and running again, it was one that I thought had a lot of potential, but I made the error of not vetting the initial committers enough and they all vanished 😦 This project needs to be ported to 3.5 (and 3.6) and needs an architectural shake about. It was originally designed for a JBI target, where the graph model represented service units that were wired together. What I did was to refactor this a bit and put in JET 2 templates to generate Camel Spring XML configurations from the model. If I was to go back and do this again, I'd definitely forget about the JBI stuff entirely and just go for the Camel configuration directly :)It has been in the back of my mind that it would be a good project for when the Graphiti project comes online, to try out its capabilities.BTW let me know if you have questions, I'm sure I can remember some of this stuff!

  3. David Carver says:

    >@Oisin: You might want to tweet about it with the #camel tag. I did that and it was picked up and retweeted there. Closer work with the Apache Camel community would help give it better visibility.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s