This may not be relevant, but it’s something we struggled with FDS so I will share.
We had CF running on the machine, setup FDS and the built in JRun server. Made all the changes to the .xml files.
The java-dao examples worked well, but when we moved to CF, it started giving weird problems.
Specifically:
‘Error invoking fill method flex.data.adapters.javaadapter$fillmethod
exception is : java.socket exception: software cause connection abort: socket write error’
And this was because of some unmarshaling exception.
We went beating around the bush for four days.
Then figured that the problem was because we installed FDS in “C:\Program Files\Adobe\Flex Data Service” folder, instead of the default “c:\fds2”. Looks like it could not handle the spaces in the path.
When we moved the installation to the default folder, it started working.
This is due to a known JRun issue specific to JDK 1.4.x. The problem happens due to different handling of space char in JDK 1.4. Either follow the advice in the technote below or do not install the integrated JRun into a directory with spaces.
http://www.macromedia.com/go/4c7d1c1
Cheers,
Trevor