On 2010-10-04 21.38, Paul Merlin wrote:
Following what Niclas answered to Stanislav question about many paralled Qi4j apps, only the underlying indexer repository (sail) is causing me problems.
Because Sesame NativeRepository is not designed to allow multiple processes to own the underlying files at the same time.
I use servlets in other projects and it's working flawlessly. In the project that caused me a headhache last friday the Qi4j app is behind stateless session beans facades (ejb). Because I want to use the filesystem based sail repository I reworked my ejb integration so there's now only one Qi4j app accessing it but it has drawbacks specifics to the ejb world. I should have given more context to my question.
Yes, it is much trickier to get it right in EJB, since there's no good way (that I know of) to get singletons. You can create a static instance in a SSB, but that's not "proper".
Does this mean that if we use 'out of the jvm' stores and index (entitystore- rest, entitystore-sql, rdbms based sail repository or indexing-sql) we'll be able to run many paralled Qi4j apps ?
Yes, pretty much. But then you probably need to cache locally, and consider cache-invalidation etc.
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
