On 5/18/05, Knut Wannheden <[EMAIL PROTECTED]> wrote: > I'm afraid I don't quite understand what you mean by first and second > "kind of data bits". If you'd like more than one of your > implementations to somehow react to a call of a service method you > should investigate the hivemind.lib.ChainFactory and > hivemind.lib.PipelineFactory service implementation factories. See > online docs and > http://howardlewisship.com/blog/2004/06/new-in-hivemind-pipelineservice.html > and http://howardlewisship.com/blog/2005/01/hivemind-in-chains.html.
Well, probably I've to dig more on this since my feeling is I'm missing something :) Anyway, my apps have to work this way: Data comes in with some kind of events, JMS test/xml messages, then data is going to be parsed and processed by the main dispatch class which read a portion of the message and decide where to forward the rest of the data (payload), here is where I've to decide which service and also which implementation of that service to use. Let's say data should be delivered firstly based on the type of data which let me choose the service then to choose the implementation to use i look at the provider/producer of the data itself, all this information are wrapped inside a portion of the jms message. I could say that: every type of data i could receive needs an hivemind service and every producer of that data i want to support needs an implementation of that service. > Well you certainly only need to declare every one of the possible > combinations in one hivemodule.xml. But you're free to spread the > declarations across multiple hivemodule.xml files. If you can use > StrategyFactory, ChainFactory, or PipelineFactory then you might end > up with far less services or at least many private services. Probably you're right, I've looked at the ChainFactory model and I've felt very comfortable with it, it's sounds really good :) Probably using ChainFactory, in my case, let me have less services defined (the exact number of data type i wish to support), so i could construct various .jar modules one per service, which probably is the cleaner solution, one service one hivemind-jar-module ... Does this still sounds good ? Thanks very much for your time, you were more then helpful! -- Massimo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
