<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Stateful SOAP and beans</title>
	<link>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/</link>
	<description></description>
	<pubDate>Thu, 17 May 2012 03:36:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.0</generator>

	<item>
		<title>by: Mark</title>
		<link>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-453</link>
		<pubDate>Thu, 17 May 2007 18:04:18 +0000</pubDate>
		<guid>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-453</guid>
					<description>Soap is basically RPC and is not designed to be stateless. You need another protocol. I suggest taking a look at the EventHandler from Real Time Logic if you need to use a web-based communication link.
http://barracudaserver.com/brochures/EventHandler.html</description>
		<content:encoded><![CDATA[<p>Soap is basically RPC and is not designed to be stateless. You need another protocol. I suggest taking a look at the EventHandler from Real Time Logic if you need to use a web-based communication link.<br />
<a href='http://barracudaserver.com/brochures/EventHandler.html' rel='nofollow'>http://barracudaserver.com/brochures/EventHandler.html</a>
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: chan</title>
		<link>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-452</link>
		<pubDate>Thu, 17 May 2007 16:12:53 +0000</pubDate>
		<guid>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-452</guid>
					<description>The stateful web service support in the JAX-WS RI does NOT rely on HTTP,I think that the problem of stateful aspects must be managed by a specific web service that offers operations like:
openSession():Token;</description>
		<content:encoded><![CDATA[<p>The stateful web service support in the JAX-WS RI does NOT rely on HTTP,I think that the problem of stateful aspects must be managed by a specific web service that offers operations like:<br />
openSession():Token;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Anas</title>
		<link>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-451</link>
		<pubDate>Thu, 03 May 2007 20:50:22 +0000</pubDate>
		<guid>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-451</guid>
					<description>I think that the problem of stateful aspects must be managed by a specific web service that offers operations like:
openSession():Token;
refreshSession(token:Token):Token;
setParameter(key: Key, value: Object,token:Token);
getParameter(key: Key,token:Token):Object;
...
closeSession(token:Token);

The statefull aspect is not only a technical problem but either a functional problem.</description>
		<content:encoded><![CDATA[<p>I think that the problem of stateful aspects must be managed by a specific web service that offers operations like:<br />
openSession():Token;<br />
refreshSession(token:Token):Token;<br />
setParameter(key: Key, value: Object,token:Token);<br />
getParameter(key: Key,token:Token):Object;<br />
&#8230;<br />
closeSession(token:Token);</p>
<p>The statefull aspect is not only a technical problem but either a functional problem.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Scott Balmos</title>
		<link>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-450</link>
		<pubDate>Tue, 01 May 2007 02:58:13 +0000</pubDate>
		<guid>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-450</guid>
					<description>Hi Kohsuke. Nice to hear from you again. I haven't been around the Glassfish &#38;#38; JAXB / JAX-WS boards much lately. I had a feeling the SFWS support was transport-independent, being based on WS-Addressing. Thanks for that!

I'm kind of curious what form the EndpointReferences take if it's on a non-HTTP transport (such as JMS or SMTP)?</description>
		<content:encoded><![CDATA[<p>Hi Kohsuke. Nice to hear from you again. I haven&#8217;t been around the Glassfish &#38;#38; JAXB / JAX-WS boards much lately. I had a feeling the SFWS support was transport-independent, being based on WS-Addressing. Thanks for that!</p>
<p>I&#8217;m kind of curious what form the EndpointReferences take if it&#8217;s on a non-HTTP transport (such as JMS or SMTP)?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Kohsuke</title>
		<link>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-449</link>
		<pubDate>Sat, 28 Apr 2007 15:06:48 +0000</pubDate>
		<guid>http://tssblog.blogs.techtarget.com/2007/04/27/stateful-soap-and-beans/#comment-449</guid>
					<description>The stateful web service support in the JAX-WS RI does NOT rely on HTTP (for those of you who just want to do HTTP session, we offer @HttpSessionScope for that.) See http://weblogs.java.net/blog/kohsuke/archive/2006/10/stateful_web_se.html for more details.</description>
		<content:encoded><![CDATA[<p>The stateful web service support in the JAX-WS RI does NOT rely on HTTP (for those of you who just want to do HTTP session, we offer @HttpSessionScope for that.) See <a href='http://weblogs.java.net/blog/kohsuke/archive/2006/10/stateful_web_se.html' rel='nofollow'>http://weblogs.java.net/blog/kohsuke/archive/2006/10/stateful_web_se.html</a> for more details.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

