i have this problem too
i never see that before .
if you resolve this problem please share it.
I just finished working through the ""cvc-elt.1" issue with a customer. It turned out not to be his FlashBuilder, eclipse or modeler plugins. The issue was that his project was deploying to an lcds3 beta 1 war file that was then running on lcds 3 beta 3 (the 10/05/2009 distro). We were able to see this by checking the META-INF/MANIFEST.MF should show a build of 126.96.36.199266. Placing his project into a lcds 3 beta 3 WAR resolved the issue.
Make sure your projects point to the current release of BlazeDS and all deployed WAR files are the current build.
Nightly builds 188.8.131.5230 and up fix this - found through http://sujitreddyg.wordpress.com/2009/06/01/building-flex-application-for-blazeds-remoting -service-using-flash-builder-4/ looking there it seems you already found the answer.
I'm just getting started with Flash Builder 4 and BlazeDS and I'm having this same issue. I have installed the FlashBuilder 4 beta 2 Build 253292, and Blaze 4 ( blazeds-turnkey-184.108.40.20641 ). I have also installed the livecycle_dataservices3_modelerplugin_100509. Upon clicking Data-Connect to data/service and then Blazeds, I can see my DAO object listed. However, if I select it I receive the dreaded error. Now if I code in the remote object manually, in the .mxml file and run it, all works just fine. It's only while trying to use the object within Flashbuilder that I have the problem. I see lots of ideas kicked around for this, and it seems that various solutions have worked for different users. Can somebody put together a 'cookbook' of just exactly how to set things up to make this work?
i have this error in my computer but i am just install in another computer and it's works.
when i reinstall my windows it's work .
We have a known issue around this.
Please refer to https://bugs.adobe.com/jira/browse/FB-23479
We are unable to reproduce the issue though.
Would it be possible to upgrade to a latest pre-release version of Flash Builder and then try the workflow?
To get access for pre-release builds please mail to rkrishna AT adobe DOT com.
Recent reportings of this issue have been due to out of synch combinations of lcds server versus modeler plugins. The same issue would occur with BlazeDS.
As suggested, I installed the latest Blaze 4 trunk release(blazeds-turnkey-220.127.116.1192) and also the latest FB (flex_sdk_18.104.22.16803) release on Thursday. Subsequently the message went away and things worked ok. Today (Monday) the problem has returned. I have not changed any versions since Thursday, so I do not understand why it has stopped working.
We are currently working on a fix for this issue and expect to have it available shortly (meaning next several months.)
Adobe LCDS QE