Many of you have asked me for the materials I used in my LCDS/BlazeDS hands-on sessions at MAX.
Here are the links:
- Lab instructions PDF (Powering Flex Applications with BlazeDS and Data Services)
- Lab files (including final solutions)
If you didn’t have a chance to attend, you should be able to use this as a BlazeDS/LCDS tutorial as well.
It was great to see all of you at MAX. I hope to see you next year in Los Angeles.
Christophe
Hi Christophe,
Is this the same as the session you did in amsterdam for the flex camp?
Are those files from flex camp online, if not can you put them, i’d love to see them, i really like the presentation and the demos you gave.
Thanks in advance,
Sidney
Hi Sidney,
It is similar to what I presented in Amsterdam… I will post the missing pieces in a few days.
Christophe
Very nice introduction. I ran into a small problem because I’m more familiar with Flex than Java: when trying to run exercise 4 my Java code wasn’t compiled because I didn’t know that I should convert to ‘src’ folder of the lcds-server project to a source folder (using right click on ‘src’, choose ‘Build path’ and then ‘Use as source folder’).
I got this error with the flexmaps:
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at com.yahoo.maps.api.copyright:
Is the swc out of date?
I can’t get exercise 4 to work. I get the folling error:
[RPC Fault faultString="Bad version number in .class file" faultCode="Server.Processing" faultDetail="null"]
at mx.rpc::AbstractInvoker/http://www.adobe.com/2006/flex/mx/internal::faultHandler()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\AbstractInvoker.as:220]
at mx.rpc::Responder/fault()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\Responder.as:53]
at mx.rpc::AsyncRequest/fault()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\rpc\AsyncRequest.as:103]
at NetConnectionMessageResponder/statusHandler()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\channels\NetConnectionChannel.as:569]
at mx.messaging::MessageResponder/status()[C:\autobuild\3.2.0\frameworks\projects\rpc\src\mx\messaging\MessageResponder.as:222]
The BaseDAO & ContactDAO classes have eclipse warning on the on all the List interfaces and quick fix recommends adding a type parameter.
Yes, I’m newbie.
Hi Christophe,
I’ve enjoyed your session at Max in SF and learned a lot. During your presentation you stated that you have a component/process that allows you to make LiveCycle DS aware of changes to database-dataset from external sources. We have an e-prescribing application that needs to interact with external information hubs. Our application server is CF 8. I hope you can point me to the direction of how to make the LCDS aware when a request or data comes from an external web server so that the message can be pushed to our application. Do you have to interact directly with the assembler?
Thank you
Yes, I’m newbie.
It is similar to what I presented in Amsterdam
Very nice introduction. I ran into a small problem because I’m more familiar with Flex than Java: when trying to run exercise 4 my Java code wasn’t compiled because I didn’t know that I should convert to ’src’ folder of the lcds-server project to a source folder (using right click on ’src’, choose ‘Build path’ and then ‘Use as source folder’).
nice info for all bloggers thanks editor
Hello
The exercice 4, 5 doesn’t work, Iget this problem in Alert Show PopUp, ” type insync.dao.ContactDAO” not found
I convert the folder src in lcds-server to a source folder but always Iget the same error
any idea ???
Do you have to interact directly with the assembler?
eskişehir kiralık daireler resimli kiralık daire ilanları.