About 3 years ago I wrote my first custom component for Adobe LiveCycle ES, a Twitter client, that allowed you to Tweet as part of a process orchestration. I’ve seen it crop up in quite a few demonstrations over time and find it to be a good example of how extensible Livecycle ES is. Until it broke. or rather, Twitter changed their authentication system to require oAuth, causing me to finally update the 3 year old code.
Times have changed for component development with LiveCycle. When I built the first version it involved manual creation of config file. Life is easy with the new LiveCycle Workbench ES Component Development Tool on Adobe Labs.
Here is the process I followed (Step 1-8 took less than 2 hours)
- Open Eclipse
- Stare at the screen for a minute
- Google “Twitter oAuth Java”
- Found “Scribe” and downloaded the library
- Ran the sample Java code within Eclipse and confirmed it worked
- Ran the LiveCycle Component Development Tool and created the wrapper project
- “Stole” pieces of the Scribe sample code for the Livecycle component.
- Deployed and tested the component in a process (it actually worked first go! Gasp!)
- Wrote some documentation -> http://220.127.116.11/blog/twitter-component-for-adobe-livecycle-es2-5/
Most of the time was spent futzing around trying to understand oAuth 2.0, so hopefully my docs above will make it easy to get the component up and running. The actual LiveCycle work took very little time.
Still to do
- Better error handling – Twitter codes are returned, but I’m assuming internet connectivity :-/
- More operations eg. direct tweet, reply etc
- Consider making a Facebook & Foursquare version
Any feature requests? If you use it (even for a demo) let me know!
Comments are closed.