David Jencks wrote: > 1. Why is it lame to tell you to make this into a session bean so you can > use xdoclet to generate the tx attribute tags? Maybe it's obvious, but I'm > not getting it.
It is a unit test test under JUnit it has nothing to do with ejbs. I can manage the tx by hand I just rather do it declarativly. Anyway, I am thinking outside the ejb box (not everything will be an ejb). > 2. If you still don't want a session bean, when the ejb and mbean > interceptor stacks are unified you should be able to use the tx attribute > interceptor in front of an mbean, thus providing at least the specific > functionality you are talking about without modifying your class at all, > just using an xml descriptor. That is what I am talking about, but instead of having a separate xml file it is embedded into the class. David, take a second lean back and think about what you could do with this system. It is very powerful, but MS popularized it first I am sure the didn't invent it; they never invent anything new. -dain _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
