Connecting with the Gateway

If you're working with Adobe Managed Services and try to connect via Workbench using the Adobe LiveCycle Gateway, there's a chance that port 8443 will be in use and prevent you from connecting.  If that's the case and you're running IIS, you'll have to remove it's binding to 8443.  I should add that many other services could use this port such as Apache, JBoss, etc, but if you're on a Windows 7 box it's a likely culprit.

This can be done by opening Computer Management under Administrative Tools, expanding Services and Applications, clicking on Internet Information Services, clicking on Sites, then inspect which of your sites are binding to 8443 and remove them manually (Bindings under Edit Site when the site is selected).

Using hand cursors in the flex tree

Normally getting hand cursors to show on flex components involves setting useHandCursor="true", buttonMode="true", and mouseChildren="false". Sadly this blows up the tree as you aren't able to select anything.  The way around this is to set  useHandCursor="true" buttonMode="true" on your <mx:Tree/> component and then set super.mouseChildren = false in an itemRenderer like so:

package somepackage
{
import mx.controls.treeClasses.TreeItemRenderer;
import mx.controls.treeClasses.TreeListData;

public class ReportsTreeItemRenderer extends TreeItemRenderer
{
public function ReportsTreeItemRenderer()
{
super();
}

override public function set data(value:Object):void
{
super.data = value;

if( super.data )
{
super.mouseChildren = false;
if( TreeListData(listData).depth == 1 )
setStyle('fontWeight', 'bold');
else {
setStyle('fontWeight', 'normal');
}
}
}
}
}

DSC ClassNotFoundException

Quite often when deploying DSC's you'll see errors such as "Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: Map".
Quite often this is caused by not fully defined your input types such as <input-parameter name="credential" required="true" type="Map"> instead of <input-parameter name="credential" required="true" type="java.util.Map">.

DSC Deployment Issue

When using the LiveCycle Component tool as I've blogged about in the past, sometimes you'll run into class issues when deploying your dsc to either a LiveCycle 8.2 or ES2 server that looks like the following:
Caused by: java.lang.UnsupportedClassVersionError: Bad version number in .class file

What you can do to rectify this is to specify the version that your javac task is targeting like so:

<target name="compile" depends="prepare">
<javac destdir="${classes.dir}" classpathref="class.path" debug="on" deprecation="on" optimize="off" target="1.5">
<src path="${src.dir}"/>
</javac>
</target>