Indeed, the best support you get for the standard WS4EE technology. The wiki explains in detail the server and client programming model.
It tells you how to create service endpoints from POJO and SLSB and how to access remote web services from all sorts of J2EE components. Your concern about SAAJ I don't understand. SAAJ is mainly interfaces and jboss-saaj is an implementation of those interfaces and factory methods. The only reason not to use jboss-saaj is when you want to completely replace the jboss WS support with some other technology, which probably is not trivial. I have heared of people using JWSDP inside jboss, but then of course you loose the standard WS4EE deployment functionality and you are back to propriatory (unportable) code. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3858513#3858513 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3858513 ------------------------------------------------------- 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://productguide.itmanagersjournal.com/ _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
