Hi Simon, > "multiple conversations in parallel on the same Service from > one client". > Can I just check that this is a requirement in you scenario. > I'm imagining that the effect you want is to have multiple > ongoing crawl actions associated with a particular type of > crawler. Sound right? Also what is the scope of the crawler > controller component. Is it composite scoped?
Yes, this is exactly what I want to achieve. The scope of the Controller is COMPOSITE. > In the factory approach you suggest, would there be a factory > for each type of crawler. So you would have an injected > reference to get the factory reference from the multiplicity > of factory references and then the factory would be > responsible for having multiple conversations with the crawler. > This would work I think but it doesn't sounds quite right. I > probably don't quite understand the scenario properly. Can > you say a little more about the the interactions between the > crawler controller and the crawlers themselves. The idea is that a Controller has 1..n references to concrete Crawlers, e.g. a FilesystemCrawler and a WebCrawler. The Controller initiates crawls of Datasources (e.g. C:\folder or http://someserver.org) and receives the crawled objects from the Crawler and processes them. It should be possible to crawl multiple Datasources with the same Crawler instance in parallel. In the Controller there is a seperate thread for each crawled datasource (programmed manually). On the Crawler side one needs something similar (either sepereate threads or multiple instances) and for simplicity I wanted to make use of SCA Conversations to take care of this. Am I mis-using the Conversation feature ? > (the real answer of course is for us to fix the JIRA;-) Well, of course this would be ideal, but I need a solution (or at least a workaround) for now. Implementing my own conversation handling seems to be lots of overhead if the Jira is fixed somtime. Bye, Daniel
