Vincent Massol wrote:
have the same basic structure (startup, deploy, test, shutdown). It should be possible to formalize those steps in the IContainerProvider interface without the danger of having an API that hinders integration with some containers. I.e., the requirements are already well known.Yes, you are right, if we stay at high level tasks like deploy/start/stop/etc. What I am concerned with is the link between the steps which are harder to bridge if you change technology.
I'm not sure I understand... :-P
I've taken a brief look at JSR 88 (107 is JCACHE?) and I don't see how it fits Cactus very well... it's only about deployment AFAICT, but the more complex tasks Cactus has to perform are setting up (in a temp directory, of course) and starting/stopping the container.Actually, I agree with all that you say :-). I'm only concerned about providing a working plugin ASAP and if the Ant integration works, I believe it is the fastest way. I am 200% ok to start doing a proper JSR107 interface and start afterwards. Or if you're interested you could work on that. Again, the more help we have the more ideas we can try!
--
Christopher Lenz
/=/ cmlenz at gmx.de
--
To unsubscribe, e-mail: <mailto:cactus-dev-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:cactus-dev-help@;jakarta.apache.org>
