<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: RIA + SOA: The Next Episode</title>
	<atom:link href="http://www.appcelerant.com/ria-soa-the-next-episode.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.appcelerant.com/ria-soa-the-next-episode.html</link>
	<description>Appcelerator blog focused on helping you build your next killer mobile, desktop and web based applications</description>
	<lastBuildDate>Fri, 05 Mar 2010 22:30:26 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Amro Mousa</title>
		<link>http://www.appcelerant.com/ria-soa-the-next-episode.html/comment-page-1#comment-385</link>
		<dc:creator>Amro Mousa</dc:creator>
		<pubDate>Tue, 01 Apr 2008 17:38:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.appcelerant.com/ria-soa-the-next-episode.html#comment-385</guid>
		<description>One can also step through the code client side (in firebug for example) if one is clever about how they structure their code (that is setup listeners for debugging in standalone javascript files).

Also, one can debug their Java service code by using the usual tools (that is remote debugging using eclipse and tomcat, for example).</description>
		<content:encoded><![CDATA[<p>One can also step through the code client side (in firebug for example) if one is clever about how they structure their code (that is setup listeners for debugging in standalone javascript files).</p>
<p>Also, one can debug their Java service code by using the usual tools (that is remote debugging using eclipse and tomcat, for example).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nolan Wright</title>
		<link>http://www.appcelerant.com/ria-soa-the-next-episode.html/comment-page-1#comment-301</link>
		<dc:creator>Nolan Wright</dc:creator>
		<pubDate>Tue, 11 Mar 2008 01:44:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.appcelerant.com/ria-soa-the-next-episode.html#comment-301</guid>
		<description>HI Joe,

There are a few options for debugging.

1) we have a URL parameter: debug=1 that will print out everything that&#039;s going on related to your application and our RIA framework.
&lt;br/&gt;
2) You can use Firebug (in Firefox) to see messages going back and forth between the UI and its services (including message contents).  It&#039;s also good for general client-side debugging.
&lt;br/&gt;
3) You can also add generic logging for your messages in the UI via our script widget.  It would look something like this:
&lt;br/&gt;
This logs all messages that are sent to and received from remote listeners (services):
&lt;br/&gt;
&lt;app:script on=&quot;r:~.* then execute&quot;&gt;
	Logger.info(&quot;Received remote message type: &quot; + this.type + &#039; data: &#039; + this.data);
&lt;/app:script&gt;
&lt;br/&gt;
This logs all messages that are sent to and received from local listeners	:
&lt;br/&gt;
&lt;app:script on=&quot;l:~.* then execute&quot;&gt;
	Logger.info(&quot;Received local message type: &quot; + this.type + &#039; data: &#039; + this.data);
&lt;/app:script&gt;
&lt;br/&gt;
The DWR/Prototype combo is certainly a viable option.  We actually bundle Prototype with Appcelerator, so you can use it.  We can also work with JQuery.  

We are trying to offer developers an alternative to the piecemeal approach to building RIA + SOA applications.  Ultimately, I believe a fully integrated platform will win out; it&#039;s just a question of which one.

Thanks for your comment!</description>
		<content:encoded><![CDATA[<p>HI Joe,</p>
<p>There are a few options for debugging.</p>
<p>1) we have a URL parameter: debug=1 that will print out everything that&#8217;s going on related to your application and our RIA framework.<br />
<br />
2) You can use Firebug (in Firefox) to see messages going back and forth between the UI and its services (including message contents).  It&#8217;s also good for general client-side debugging.<br />
<br />
3) You can also add generic logging for your messages in the UI via our script widget.  It would look something like this:<br />
<br />
This logs all messages that are sent to and received from remote listeners (services):<br />
<br />
&lt;app:script on=&#8221;r:~.* then execute&#8221;&gt;<br />
	Logger.info(&#8221;Received remote message type: &#8221; + this.type + &#8216; data: &#8216; + this.data);<br />
&lt;/app:script&gt;<br />
<br />
This logs all messages that are sent to and received from local listeners	:<br />
<br />
&lt;app:script on=&#8221;l:~.* then execute&#8221;&gt;<br />
	Logger.info(&#8221;Received local message type: &#8221; + this.type + &#8216; data: &#8216; + this.data);<br />
&lt;/app:script&gt;<br />
<br />
The DWR/Prototype combo is certainly a viable option.  We actually bundle Prototype with Appcelerator, so you can use it.  We can also work with JQuery.  </p>
<p>We are trying to offer developers an alternative to the piecemeal approach to building RIA + SOA applications.  Ultimately, I believe a fully integrated platform will win out; it&#8217;s just a question of which one.</p>
<p>Thanks for your comment!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.appcelerant.com/ria-soa-the-next-episode.html/comment-page-1#comment-300</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Tue, 11 Mar 2008 01:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.appcelerant.com/ria-soa-the-next-episode.html#comment-300</guid>
		<description>Well damn, I pasted in the pre-escaped stuff.  On the client-side snippet pretend there is a  tag wrapped around the JS functions, and then 2 comboboxes.</description>
		<content:encoded><![CDATA[<p>Well damn, I pasted in the pre-escaped stuff.  On the client-side snippet pretend there is a  tag wrapped around the JS functions, and then 2 comboboxes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe</title>
		<link>http://www.appcelerant.com/ria-soa-the-next-episode.html/comment-page-1#comment-299</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Tue, 11 Mar 2008 01:08:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.appcelerant.com/ria-soa-the-next-episode.html#comment-299</guid>
		<description>How does the debugging end of things work out with those tight strings of text?  Does it get &quot;compiled&quot; into Javascript that can be pretty cleanly stepped through on the client-side?  Genuinely curious.

I am a pretty big fan of the prototype/dwr combo.  That would look like this on the client side (hopefully the code renders alright):



    function changeOne(){
        dwr.updateOne($(&quot;comboOne&quot;).value, {callback: newTwo});
    }
    
    function newTwo(newOptions){
        util.addOptions($(&quot;comboTwo&quot;), newOptions, &quot;value&quot;, &quot;text&quot;);
    }






Its a few more characters (I could have packed it all in tight certainly) but super clear at a glance and really clean to debug on both ends.

The server side then looks like this:


@RemoteProxy(name = &quot;dwr&quot;)
public class DwrController{
    
    @RemoteMethod
    public List updateOne(String value){
        return myManager.getNewOptions(value);    
    }
}


It is indeed Java-only, but a nice combo if working in that environment.  I think Prototype makes Javascript rather fun to work with.</description>
		<content:encoded><![CDATA[<p>How does the debugging end of things work out with those tight strings of text?  Does it get &#8220;compiled&#8221; into Javascript that can be pretty cleanly stepped through on the client-side?  Genuinely curious.</p>
<p>I am a pretty big fan of the prototype/dwr combo.  That would look like this on the client side (hopefully the code renders alright):</p>
<p>    function changeOne(){<br />
        dwr.updateOne($(&#8221;comboOne&#8221;).value, {callback: newTwo});<br />
    }</p>
<p>    function newTwo(newOptions){<br />
        util.addOptions($(&#8221;comboTwo&#8221;), newOptions, &#8220;value&#8221;, &#8220;text&#8221;);<br />
    }</p>
<p>Its a few more characters (I could have packed it all in tight certainly) but super clear at a glance and really clean to debug on both ends.</p>
<p>The server side then looks like this:</p>
<p>@RemoteProxy(name = &#8220;dwr&#8221;)<br />
public class DwrController{</p>
<p>    @RemoteMethod<br />
    public List updateOne(String value){<br />
        return myManager.getNewOptions(value);<br />
    }<br />
}</p>
<p>It is indeed Java-only, but a nice combo if working in that environment.  I think Prototype makes Javascript rather fun to work with.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
