I started with Servicemix about a month back and servicemix has been great for
me. I am sure most of us are evaluating Servicemix in our own companies and
need quicker results that we can share with team and executives. Maybe this
could help some beginners like me.
1. Buy ourself a book on EIP. The patterns described by Hohpe and Woolf got me
off with things that I thought I knew but didnt know how to use them. Ofcourse
reading the JBI specs is mandatory.
2. Though the servicemix examples are great to learn, if you are looking for a
near real world example, I thought the Grocery demo that comes with FUSE is a
great great one. I learnt most things about writing my own components, invoking
internal and external services, packaging SUs and SAs, using servicemix
components. I favoured this slightly when compared to the classic loan broker
example.
3. Personally I thought FUSE has a great management console. Ofcourse the same
information can be found using the servicemix-console. Either way, it helps a
lot in understanding the messaging.
4. One of the difficult part is tracing a message flow between components.
Wiretaps and traces are great but I followed one of the threads in this forum
to write an exchange listener and just log all exchanges between components. My
implementation is rudimentary but works great for debugging. Its also on
Servicemix's "Ideas" list so you can hope a better support in the long run.
5. Servicemix tooling is great if your using maven. I had my own set of
problems but most problems went away once I built servicemix from source. Since
then I update my servicemix source to see if issues are fixed before I spend
too much time on it. The servicemix support has been very responsive in
providing answers and I am sure a lot of them will agree with it.
6. I struggled with calling external web services and I followed steps
mentioned in "External webservices binding (the answer)" by Alessio D'Innocenti
on this forum. (sorry dont have the links ready with me but please search these
on the maillist). Once I got how to use consumer and provider endpoints,
invoking them was a breeze. The Saaj binding didnt work but the provider
endpoints are a way to go.
7. Classpath and library incompatibilities are a pain. You can either add all
dependencies in your SU or copy them to your lib folder and revisit it once you
have a basic understanding of how things are. Again the servicemix maven plugin
is great to package your SAs.
There are plenty of other things to be improved but I will not abandon it yet.
I am no expert but hope this helps some of us.
Regards
Kiran
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 9/14/2006 5:45 AM
To: [email protected]
Cc: [email protected]
Subject: Re: Hello World
Any chance of a chapter on how you package up say a MyPojo service into
a
JBI install file and why it should go into the install dir rather than
the
deploy dir and so on.
As the current docs are not clear to a simpleton like myself!
Regards Rick
Terry Cox <[EMAIL PROTECTED]>
14/09/2006 16:27
Please respond to servicemix-users
To: [email protected]
cc:
Subject: Re: Hello World
> Seems like a good oportunity for
> someone to write a book: "Real World ServiceMix Solutions" Any
> takers?
Well, I am working on the book, so I'll let you know, but in the
meantime, I think you will find that once you actually start to use the
framework, the documentation provided and the questions addressed via
the forum are more than enough to get a team of developers up to speed
very quickly.
Terry
Direct Line Group Limited, registered in England
with number 2811437, registered office 3 Edridge
Road, Croydon, Surrey CR9 1AG. The following
companies are members of the Direct Line Group:
Direct Line Insurance plc, Direct Line Life
Insurance Company Limited, Direct Line Unit
Trusts Limited and Direct Line Financial Services
Limited, all of which are authorised and regulated
by the Financial Services Authority. All are
members of The Royal Bank of Scotland Group.
This email is intended for the addressee only and
may contain confidential, proprietary or legally
privileged information. If you are not the
intended recipient of this email you should
notify us immediately and delete it. You should
not copy, print, distribute, disclose or use any
part of it. We reserve the right to monitor and
record all electronic communications through our
networks. We cannot accept any liability for
viruses transmitted via this e-mail once it has
left our networks.
***************************************************************
The information in this email is confidential and may be
legally privileged. It is intended solely for the addressee. If
you have received this communication in error, please contact
the sender immediately, return the original message to the
sender, and delete the material from your computer. Thank you.
***************************************************************
