SA_DS Datasource for Solution Accelerators

The documentation for the LiveCycle SA's don't specify anything other than creating the SA_DS data source when using WebSphere for WebLogic. This data source name has already been added to the common building block and will automatically 'pickup' when LiveCycle is restarted. Here's the error message that you'll see if it hasn't been created.

[9/23/10 15:27:02:565 EDT] 000000aa RegisteredRes E WTRN0062E: An illegal attempt to use multiple resources that have only one-phase capability has occurred within a global transaction.

[9/23/10 15:27:02:573 EDT] 000000aa LocalTransact E J2CA0030E: Method enlist caught com.ibm.ws.Transaction.IllegalResourceIn2PCTransactionException: Illegal attempt to enlist multiple 1PC XAResources at com.ibm.ws.Transaction.JTA.RegisteredResources.enlistResource(RegisteredResources.java:416)

Eligibility Expressions in SNC

One of the pieces of functionality that's called out in the Selection and Capture Building Block for Adobe LiveCycle is that you can leverage processes to perform the eligibility expression. Normally eligibility expressions are done using a jspl syntax such as ${(state=='CA')} but obviously this can only be so robust. Here's an example of the EligibilityExpressionTO that you'll need to define in your beans.xml:

<bean class="com.adobe.solutions.snc.transfer.EligibilityExpressionTO" id="someId">
<property name="expressionType" value="LCService"/>
<property name="operationName" value="invoke"/>
<property name="serviceName" value="YourProcessName"/>
<property name="name" value="someName"/>
</bean>

Scrolling ViewStack Contents

I ran into an interesting issue with a Flex app today as I couldn't constrain the contents of a viewstack properly. I ultimately wanted a scrollbar to appear if it's contents were larger than what the parent would allow. To enable this properly, the children all had height of 100%, the viewstack had a height of 100%, and the key setting was to give a minHeight of 50 or something small to the viewstack itself.

I also tried using resizeToContent which is great, but it still wouldn't allow the viewstack to get very short until I put the minHeight in.

LiveCycle Workbench ES Component Development Tool on Helios

The new LiveCycle Workbench ES Component Development Tool for creating DSC's works just fine with the Eclipse Helios (3.6) for Java EE Developers edition. If you start with Helios you can skip past the requirements for EMF, GEF, and WTP and simply install the archive that you can download from Adobe Labs.

It's a nice tool to get you started with component development.

Crossdomain for LiveCycle

I've been asked this question numerous times so I figured I would post it here. When you need to deploy a crossdomain.xml file for a LiveCycle install running JBoss, you'll have to dump it in the following location:

C:\Adobe\LiveCycle8.2\jboss\server\all\deploy\jbossweb-tomcat55.sar\ROOT.war

Compc not found...

I was setting up another project today and I ran into an odd issue with compc in my ant tasks. Here is the error that I was getting:

compile:
[compc] java.lang.NoClassDefFoundError: flex2/tools/Compc
[compc] Caused by: java.lang.ClassNotFoundException: flex2.tools.Compc
[compc] at java.net.URLClassLoader$1.run(Unknown Source)
[compc] at java.security.AccessController.doPrivileged(Native Method)
[compc] at java.net.URLClassLoader.findClass(Unknown Source)
[compc] at java.lang.ClassLoader.loadClass(Unknown Source)
[compc] at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
[compc] at java.lang.ClassLoader.loadClass(Unknown Source)
[compc] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[compc] Could not find the main class: flex2.tools.Compc. Program will exit.
[compc] Exception in thread "main"

BUILD FAILED
D:\xx\xx\xx\build.xml:91: compc task failed.

This was the actual location of my flex_sdk:

C:\Program Files\Adobe\Adobe Flash Builder 4 Plug-in (2)\sdks\3.2.0.3958

Oddly enough, I tried all sorts of different combinations to reproduce this in another location to no avail. After digging through the following posts I moved the sdk to the root of my drive and that seemed to do the trick.

For more reading:
http://bugs.adobe.com/jira/browse/SDK-13003
https://bugs.adobe.com/jira/browse/SDK-13602