Comments on: A Dirt-Simple Web Service http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/ Wed, 25 Nov 2009 03:01:12 +0000 http://wordpress.org/?v=wordpress-mu-1.0 by: Peter O'Brien http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/#comment-363 Thu, 18 Jan 2007 15:16:24 +0000 http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/#comment-363 One of the key potential benefits of JAX-WS to software component developers is that it provides a certain degree of platform indpendance. It is clear that it does not go far enough though because of the amount of additional container specif annotations that are out there. The next step after this Dirt Simple Web Service would be to go through the process of deploying on Glassfish, etc. One of the key potential benefits of JAX-WS to software component developers is that it provides a certain degree of platform indpendance. It is clear that it does not go far enough though because of the amount of additional container specif annotations that are out there.

The next step after this Dirt Simple Web Service would be to go through the process of deploying on Glassfish, etc.

]]> by: siva http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/#comment-362 Thu, 28 Dec 2006 11:45:19 +0000 http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/#comment-362 This example does not explain how to deploy. Do we need to create war file? any other xml files are required etc... This example does not explain how to deploy.
Do we need to create war file? any other xml files are
required etc…

]]> by: Jack Webb http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/#comment-361 Thu, 21 Dec 2006 19:14:57 +0000 http://tssblog.blogs.techtarget.com/2006/12/14/a-dirt-simple-web-service/#comment-361 From TSS.com on a Dirt-Simple Web Service Re-Posted by: By Jack Vaughan Interop with "dirt simple" web services have never been an issue. Maybe so 2 or more years ago, but current (Java) web service stacks have matured to an extent that interop between "dirt simple" web services that are essentially Basic Profile 1.1 compliant is not an issue for simple (interop) scenarios. However, start passing complex types, graphs of complex types, arrays of complex types, nulls and you get to see that different Java web service stacks behave quite differently at [runtime]. Throw in WS-Security, WS-ReliableMessaging and some other assorted WS-* standards and you're almost guaranteed to run into a whole lot of interop headaches. - K. Subramanian From TSS.com on a Dirt-Simple Web Service
Re-Posted by: By Jack Vaughan

Interop with “dirt simple” web services have never been an issue. Maybe so 2 or more years ago, but current (Java) web service stacks have matured to an extent that interop between “dirt simple” web services that are essentially Basic Profile 1.1 compliant is not an issue for simple (interop) scenarios.

However, start passing complex types, graphs of complex types, arrays of complex types, nulls and you get to see that different Java web service stacks behave quite differently at [runtime].

Throw in WS-Security, WS-ReliableMessaging and some other assorted WS-* standards and you’re almost guaranteed to run into a whole lot of interop headaches. - K. Subramanian

]]>