Hi Jochen, Right from the start, the Hivemind project has aimed to provide clear and concise instructions and information but as you also understand, this is of course not always possible. However, if you have some changes you'd like to contribute, I am quite confident such help is always welcome. I would suggest you create a JIRA for it, attach the changes you think see fit and someone will take a look and update the documentation to reflect this.
As for you questions relating to the "pipeline" - I am not sure this is a good fit to your problem - the pipeline is very similar to the interceptors in that it allows arbitrary implementations to slot in between the service interface and the actual implementation and the pipeline, as opposed to the interceptors, work with the service interface definition directly and have the exact same parameters defined by the service interface (plus the additional parameter being the next service in the pipeline to invoke). So, in short, the pipeline is a "more typed" version of the interceptor. I have used the pipeline quite effectively for validation of parameters and simple caching. The scenario you are describing sounds more like the Filters in the Servlet API - each filter gets invoked and they may pass parameters "down" the chain by adding data to the servlet request - does that match more what you have in mind? Cheers, Johan Jochen Zimmermann wrote: > Hello! > > Right now I get used to Hivemind and I am starting to like it very much :-) > > BUT .... I really think there is a massive lack of documentation. > I know (as I work for a software company myself) that writing > documentation is not really the favorite thing to do and I'm very happy > that my company has a own department doing this job, but on the other > hand: the coolest software is of no use if no one can use it :-) > And even if I found out a lot by myself right now it is frustrating to > trial and error for 3 hours (or more) just to find out how easy it is > done if you know how to do it (in a sense it is even more frustrating > than it would be if it would be hard to do ;-) > > The API help does not help me that much, because they don't really > describe how to do things in the context of the framework. > > If there is more documentation and I'm just to stupid to find it, please > point me to it!! > > Again, I like Hivemind very much already, I even would volunteer to > write some documentation. > What about the cookbook? I read in the newsgroup about it, but I could > not find it. > I don't know much about Hivemind right now, but as I hope to find out > more about it in the near future I could write about the things I learn > (and perhaps it is not to bad to describe it from a beginners point of > view), and if there would be a start, perhaps others would join in? > > But after that outburst of frustration (after trial and error the whole > afternoon) some questions: > > 1.: > At the moment I have three services, and I need them executed in a row. > > A -> give results to -> B -> give results to -> C > > Each of them is used (or at least could be used) alone from another > point of the application, so I want to keep them separated. > > I found something about pipelines in the net, but I could not find more > documentation on how to use them, I even did not found out if they are > really intended to do what I need here. > > 2.: > I tried to build my own "pipeline" using threaded services bundled > together in a "parent" service. > I got it working, but: after processing about 2500 objects that way I > get a java out of memory error. > After searching the internet a little more I found out that I should > clean up. > Can someone post me a little example of a threaded service including the > "clean up" part? > > Thanks a lot for your time again! > > Jochen > > > > > -- you too?
