I could break it down further but not in 2 1 file. I have coldspring
loading everything and then I have a decorator/service/gateway all
which derive from an Abstract Parent. I just tried it with another
object to see If I could replicate the issue and sure enough it did. I
know im doing something
So I got some time to finally look at this and I think I have found
the issue. When I save using the method I created in my
abstractDecorator I am having the issue.
cfset userTO = application.userService.get(form.userId)
!--- populate the user bean with our form props ---
OMG yeah that would do it ;o)
getTransferObject() returns the underlying TO.
The cache synchronisation would find that the object in cache is different
to the one you currently have, and try and resolve it.
Erk...
Glad you worked it out.
Mark
On Wed, Jul 1, 2009 at 6:13 AM, Dan Vega
Thanks for the help Mark!
On Jun 30, 5:43 pm, Mark Mandel mark.man...@gmail.com wrote:
OMG yeah that would do it ;o)
getTransferObject() returns the underlying TO.
The cache synchronisation would find that the object in cache is different
to the one you currently have, and try and resolve
Dan,
Can you break it down into a single index.cfm file, so it's a reproducible
test case?
Mark
On Sat, Jun 27, 2009 at 2:47 AM, Dan Vega danv...@gmail.com wrote:
Loaded via coldspring
cffunction name=onApplicationStart returnType=boolean
output=false
cfset
Loaded via coldspring
cffunction name=onApplicationStart returnType=boolean
output=false
cfset coldspringConfig =
/quickconnects/config/coldspring.xml
cfset application.coldspring = createObject('component',
Ok so I just don't understand the object cache. I will have to read up
on it. If I create a new object and then save that object to the
database everything works great. If I then try to get that object
again I am working with a tranfser object instead of my decorator. If
I were to re initialize
