i have been following this field for some time , it looks to me as if web services is in a mess in terms of number of specs and duplication of standards--e.g (i found jax rpc as a spec much more cryptic than any of the main line j2ee specs because of cross references to so many other specs: soap/wsdl/saaj/jaxm/jaxr/jaxb/ and the list goes on)
In this scenario this link from msdn does provide some clarity on where we are going-- but isnt it only MS perspective Consider this : following consortiums communities are driving the specs 1.w3c 2.oasis 3.JCP through java communicty 4.microsoft /ibm/bea with others //i am sure there are more Would n't it be a better idea to first filter out competing specs...and then come out with a road map. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3859917#3859917 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3859917 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
