> I think you're talking about giving people something more like > asynchronous method invocations (one-way) than traditional MOM style > messages, right?
I am talking about propagation of TX with async calls, yes. > An asynch. invocation on the other hand, ought to take the > transaction > with it, but I think you want a different programming model than the > JMS overhead crap (look up three object in JNDI, call three > factories, > sacrifies three virgin goats...) I wouldn't care if it were LOL > implemented on the same infrastructure as JBossMQ, but I'd > really want > a more light-weight programming model - like an asynchronous Aspect > for the target object, or something... Yes lite-version of the specs would be a powerful thing to have, keep an eye open when we are done with the basic AOP framework. marcf ------------------------------------------------------- This SF.NET email is sponsored by: Thawte.com Understand how to protect your customers personal information by implementing SSL on your Apache Web Server. Click here to get our FREE Thawte Apache Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
