The classes like JBossMessageProducer are only meant to map the *FAT* JMS api to a simpler sub-version.
You should not be putting real logic (and definitly not state) into that code otherwise it cannot be overridden/changed/optimized by different interceptor configuration. e.g.1. I want to store my transacted session on the server because I am a small handheld device. So I move most of the interceptors to the serverside. e.g.2. I want to do a work offline mode such that when I commit/send it actually stores the messages in a local store and a background thread does the real send to the server when I am connected. e.g.3. Some other use case I haven't thought about yet. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874018#3874018 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874018 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
