Hi Magnus, I don't know how to say it :-)
Cactus v2 works *exactly* in the same manner than Cactus v1. So if there's something you can do in Cactus v1 you can do it in Cactus v2 (actually you can even do more with v2 because it's a strict superset AFAIK). Some more information. Whenever an advice is applied it is applied in the location it captures. So if you catch your servlet your advice code will run in your servlet. Let me know what is not clear in my v2 architecture blog post and I'll be happy to explain it in more details. Alternatively feel free to skype me and I can explain it verbally. Thanks -Vincent > -----Original Message----- > From: Magnus Grimsell [mailto:[EMAIL PROTECTED] > Sent: mardi 7 juin 2005 18:56 > To: Cactus Developers List > Subject: RE: cactus v2 > > > If there's no way inside the server then this portion of code > > will never be > > called and hence you don't need to test it! :-) > > > > This EJB will usually be called by a Servlet or some MDB > > or... So you'll > > intercept using the same principle as it is currently done > > with Cactus. > > Sure, most server services can be called or rather triggered remotely. > However, I can > see the need for services that has no remote api and is only triggered via > timers inside > the server. > > More importantly one could be developing a reusable component with no > remote api. The component > will later on be invoked by servlets or MDB:s for instance. When > developing our component we > want to focus on that and write integration tests for it without having to > bother about the > parts of the system that will be invoking it. These part may not yet > exist. > I would still argue its a valid integration test since it tests the > component running in its container > working against a real database. > > One of the main reasons we are using Cactus today is the ability to run > the actual test on the server > within the servlet that Cactus provides for us. From within the servlet we > can insantiate server components > like local session EJB:s and run integration tests on them. It seems to me > that it will be much more > cumbersome to write these kind of test with the new architecture. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
