"[EMAIL PROTECTED]" wrote : Not really correct. | | For example, if I call a Seam component via RMI, Seam can set up an event context and application contect for me. It just cant do a session or conversation context because RMI can't propagate conversation or session ids. I am specifically trying to understand, what it takes to "propagate conversation or session ids". Imagine using Seam from a calender-driven scheduler (no UI, no HTTP, no ExternalContext, everything is the same JVM). Do I create a custom implementation of Context? Or do I use ServerConversationContext with a custom implementation of Session?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3947323#3947323 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3947323 ------------------------------------------------------- All the advantages of Linux Managed Hosting--Without the Cost and Risk! Fully trained technicians. The highest number of Red Hat certifications in the hosting industry. Fanatical Support. Click to learn more http://sel.as-us.falkag.net/sel?cmd=lnk&kid=107521&bid=248729&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
