Actually, we hear you loud and clear. We are currently working on the next version of LiveCycle ES and one of the main focus areas is usability of Workbench, Designer and Flex Builder around building LiveCycle applications. We will be hosting a beta later this summer, I will be posting details about the beta on this forum once we are closer to that date.
We have made A LOT of changes in the property pages and have dramatically simplified the steps required to render and submit forms.
I totally agree with you in regards to the Java APIs. However, we have not targeted the Java API to improve usability in the next release. Actually, we strongly believe that Rich Internet Applications is a major differentiator for LiveCycle ES. To that end, we have also dramatically improved the integration of Flex Builder and LiveCycle ES. For example, we have automated the generation of data type handling classes and proxy classes to communicate with a LiveCycle ES server. Unfortunately, this does not help you in the Java API scenario. Maybe, we could create a sample Java framework that would provide helper classes that you could use?
Thanks for the reply. I think LiveCycle has a lot of potential, but a streamlined interface would really help.
As to the Java API, some sort of helper classes for the Java classes would probably do. You could leave all the current classes as is and simply add a simplified layer that calls the current classes but would return simplified values.
I noticed that there is a set of helper classes on riaforge, do those essentially try to accomplish this?
One more nice feature would be to have datasource configuration through the adminui. I had to figure out how to add datasources to JBoss in the xml file for this. Then I had to read that you have to add the java:/ in front of the datasource name in the JDBC node in Workbench. Took a little time to figure it all out.