Quoting Rickard Öberg <[email protected]>: > Ok, that sucks... hm... I don't particularly like the idea of > reinventing this wheel, but if their API is too screwed up then maybe > that's the best way to do it, with a fair share of "inspiration" going on.
To me there's no API, there's only some common interface for RAMJobStore that haz no really usefull feature and the JDBC based ones that shares code in JobStoreSupport. > What would be easiest: from scratch, or continue with JobStoreSupport? > Got gut feeling? I started something from scratch and things seems to go pretty well for now. Anyway, I'll push both to github in a dedicated repository so we can review it before it gets added to qi4j repositories, or not :) /Paul _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
