Finally…A Working LCDS Development Environment!

I think (and hope) that I finally have a working, stable environment for LiveCycle Data Services development. In my previous attempts, I have been plagued by Out of Memory errors (Eclipse 3.3 + Flex Builder 3 beta 2), strange “Unknown” problems (Eclipse 3.3 + Flex Builder 2), and missing plug-ins (Flex Builder 3 beta 2 stand alone).

My current approach is based on a great article titled Eclipse WTP + JBoss + Flex Builder + FDS Dev Environment Tutorial. In this case, the developer built his environment using slightly older versions of the tooling than I preferred, so I took a stab at building the environment with the following:

You might notice that Eclipse WTP and JBoss are not the latest and greatest as of this writing (in the case of Eclipse WTP, the latest is 2.0.1 and JBoss is 4.2.2). I made both of these choices for a reason. First, I had trouble running WTP 2 (built on Eclipse 3.3) with Flex Builder 3b2 earlier, so I wanted to avoid it initially. As for JBoss, the aforementioned tutorial points out that the Eclipse plug-in associated with the 4.2 version is a memory and CPU hog – a problem I had with my earlier trials also.

I am not going to go into full detail on set-up and configuration of the development environment here, because the development environment tutorial does a tremendous job there. Instead, I will point out a few, albeit minor, differences as well as a few key points:

  • I installed my environment at “C:\LCDSEnv,” so pathes listed below will differ from the tutorial.
  • Memory setting changes are a must for both Eclipse and JBoss:
  • Eclipse (C:\LCDSEnv\eclipseWTP\eclipse.ini)

    -vmargs
    -Xms256m
    -Xmx512m
    -XX:MaxPermSize=256m
    -XX:PermSize=128m

  • JBoss (C:\LCDSEnv\jboss\bin\run.bat):

    set JAVA_OPTS=%JAVA_OPTS% -Xms256m -Xmx740m

  • Utilize Peter Martin’s plugin instead of building your application based on the sample WAR file provided by LCDS.
  • Do not deploy “flex.war” from the LCDS installation to your appication server (I found a tutorial that stated otherwise and all this will do is cause a port conflict and unnecessary headaches).

Now that I have a working environment, I can start to integrate my previously built Java application (Spring + Hibernate + FDS) with my Flex frontend. I will document my efforts in future posts.

References

Advertisements

6 Comments on “Finally…A Working LCDS Development Environment!”

  1. […] November 1, 2007 Update: Creating the Skeleton for a New LCDS Application Posted by josh under Flex   First, the good news…my LCDS development environment and server have been running since yesterday afternoon (15+ hours) without a failure yet.  If you missed the set-up, check my earlier post Finally…A Working LCDS Development Environment. […]

  2. thosmos says:

    That link to Peter’s eclipse plugin doesn’t work anymore and I can’t find it when I google for it. Can you make that available or suggest an alternative method?

  3. josh says:

    @thosmos – It seems that Peter’s blog is either down or no longer available. You can find the plug-in on the Adobe Flex Exchange as well:

    http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&extid=1035666

  4. Jerome says:

    Hi,
    I would like to know if the Peter Martin plugin is still needed with flex builder 3 beta 3 or flex builder 3 can do the same (generate a J2EE project with flex inetgrated)?
    Thanks.

  5. codecraig says:

    Do you happen to have the notes for that tutorial (http://brianmriley.com/blog/?p=59) …the site is gone!

  6. josh says:

    @codecraig – sorry, I don’t have any details from that post…you might try searching for a cached version on Google