Steven, I am having been experimenting with ServiceMix for about 2 weeks and I agree with points raised by you. Most of documentation work is IN PROGRESS because of which newbies like me find it difficult to understand things quickly. Posting queries in the forum helps but not all questions get answered making things difficult. Like Terry said the best way to understand ServiceMix is going through the code but is tough if we have less time.
Pradeep Steven wrote: > > > Although I agree in general, the problem is I simply don't have time to > read someone else's code to learn how to use their product. I work in an > office where SOA is being considered and I'm just trying to put together a > small example of how ServiceMix could be used. From my newbie > perspective, if you haven't been in the SOA/messaging game for a while, > all of the info out there is written from a point of view of the reader > knowing what's going on - which I don't. ;-) > > Luckily, the ServiceMix examples all work as expected once you get past a > couple of hurdles (proxy servers, ant and proxy servers, etc. etc.). The > best example I've found thus far is the rss-binding example. It's close > to what I want to do. This brings up another thing I've notice, there > doesn't seem to be an info on how to use ServiceMix as a solution to a > problem. For instance, as a newbie to ServiceMix I don't yet understand > what I need to configure or build myself to get a stock quote from a > service (via http) every five minutes, then cache those results, then > allow clients to request the lastest results from the cache. I know I > could use the quartz and http components, but what else? How do I cache > the results. What do I need to provide in terms of custom components, > etc. Unless you've been involved with ServiceMix for a while, this kind > of solutions based info just isn't found - or at least, I can't find it. > Seems like a good oportunity for someone to write a book: "Real World > ServiceMix Solutions" Any takers? > > > > > Terry wrote: >> >>> No one seems willing to share >>> "how" they learned what they learned. >> >> Well, one of the neat things about ServiceMix is that big chunks of it >> are written using ServiceMix, so by looking at the source you get lots >> of examples of how to deal with all the basic patterns. Also, by >> following the example of the ServiceMix unit tests, you can build your >> own unit test suite to determine the behaviour of the container in >> situations that you can't find direct examples for. >> >> Terry >> >> > > -- View this message in context: http://www.nabble.com/Hello-World-tf2087343.html#a6308135 Sent from the ServiceMix - User forum at Nabble.com.
