<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://apache.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>From the Editor</title>
 <link>http://apache.sys-con.com/</link>
 <description>Latest articles from From the Editor</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Sun, 29 Nov 2009 10:30:37 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Debugging Both Flex and Tomcat Java Programs in Eclipse</title>
 <link>http://apache.sys-con.com/node/458994</link>
 <description>If you use Adobe Flex Web applications that connect to Plain Old Java Objects on the server side, chances are you use a popular, robust, and freely available server called Apache Tomcat. If you use Eclipse-based Flex Builder, you can smoothly debug both Flex and Java code without leaving Eclipse. Flex Builder debugger does not need any special configuration. But we need to add a couple of parameters to the startup routine of Tomcat so it&#039;ll engage the Java Platform Debugger Architecture (JPDA), which will allow other applications attach to JVM that runs Tomcat and debug deployed Java classes remotely.&lt;p&gt;&lt;a href=&quot;http://apache.sys-con.com/node/458994&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 14 Nov 2007 08:15:00 EST</pubDate>
 <guid isPermaLink="true">http://apache.sys-con.com/node/458994</guid>
</item>
</channel>
</rss>
