This content has been marked as final. Show 4 replies
I am getting the same error > I Guess no one has posted the solution for this
i'm having the same problem... can't find the solution anywhere. hope this will be resolved soon.
I was having this same problem and spent most of this afternoon tracking it down. It seems the problem arises from the fact that the factory instance doesn't touch the fill, sync, etc methods. For some reason, flex interprets not using certain properties of a ConfigMap object as a fatal however which seems a little odd.
In this case though, it is correct because the sync and fill methods actually aren't getting set on the underlying java adapter. This isn't a problem if you use the the Assembler approach, but it is if you obviously.
I found two fixes one is to get the data adapter for the current instance in the SpringFactoryInstance constructor and initiliaze it with the properties ConfigMap so it will set its syncMethodProperty and the fill-method to its fillMethodProperties list. This prevents the properties from showing up in the unused properties of the ConfigMap and so the error is no longer called and the adapter is configured.
The other option is to upgrade two Lifecyle Data Services (FDS 2.5). It seems to be fixed there.
Did you able to define multiple fill methods and implement in assembler after changing the SpringFactory class?
I removed the fill config. and I am using the default fill method and everything works fine. Hopefully this problem is fixed in LCDS to allow multiple fill method configuration.