WS is indeed transport-agnostic. However, WSRP is not necessarily. Some methods on the required interfaces (initCookie for example on the Markup interface), explicitely need to set HTTP headers (when using the HTTP transport, that is).
This is indeed a Portal issue but since there used to be a means to retrieve the servlet request/response information and this doesn't exist anymore, I was wondering if something had replaced it that I had missed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3936671#3936671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3936671 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
