I'm having the exact same problem using BlazeDS on the server side, fwiw. Creating the service picks up all the service methods and data types. However, subsequent changes to data types aren't recognized. My only work-around is to delete the service and re-create it. Gets somewhat tedious as the projec grows, as all data management and paging config then has to be re-done, type for type. This bug is still there for me in FB4 release version.
I'm having this problem as well. The only thing I found after hours of searching on the web is this topic.
Is there allready a possible solution I haven't found yet?
I found a quicker way to update then delete en recreate.
If you update the php service class and you hit refresh the changes are recognized by flash builder.
Now you select the getAll method and configure the return type.
Select auto detect. Hit next. Select 'Use an excisting data type'. Select the right datatype in the dropdown and hit finish.
That's all. It would be nice if FB could update the generated services itself when you make changes to the DB scheme. But doing it this way makes it ok form me.
with FB4 and wsdl going to microsoft servers i have had no luck with any refresh or getAll. For any changes to the schema I have to delete the services and valueObjects in FB4 / Package Explorer. Then go back to Data / connect to data service / wsdl and bring in a wsdl with a slightly different name even tho like I said i just clobbered the service from FB4.
This is because somehow in some cache or someplace fb4 thinks the service is still there.
so for instance i was pointing to http://dbsvr/greeter?wsdl .... i would regen the wcf service with a slightly different name such as greeter02?wsdl then as I type that in the URI fb4 thinks it is not already in the project and allows its import. whereas if i tried greeter again fb4 would bark and not allow it as it would say the service is already present !
make sure you keep a copy of your subclass source code that you modified that derives from *super* in services so you can cut and paste it in.
the whole thing takes about 5 min now for each change which is certainly better than flirting with coding against the *super* classes.
the whole microsoft wcf and FB4 scenario is becoming quite smooth for those of us who only know MSFT on the back end such as C# and msft sql server / stored procs as opposed to you LAMP stack fellows