Thanks for the help Mark!
On Jun 30, 5:43 pm, Mark Mandel 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 it.
>
> Erk...
>
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 wrote:
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.
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
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 wrote:
>
> Loaded via coldspring
>
> output="false">
>
> "/quickconnects/config/coldspring.xml">
> 'coldspring.beans
Loaded via coldspring
I have an abstract service
Dan,
Can you post what your doing in the userService.get().. I got() a
feeling that your doing something nefarious in there since that is
where your user object is coming from..
How is the service accessing transfer.. I mean are you using
coldspring to setup transfer or are you creating it somew
I just have a simple user form that you fill out and then submit it.
When it submits I get the user based on the id. On the very 1st pass
through it works fine and the user is saved (that code is not here).
When I go back in and edit the user and save the data that user object
is now a general tra
Dan, no matter if you get() or new() it should always be a decorator, if you
have defined one (get() calls new() to get a new object to populate).
Can you provide a code sample to show what you are doing?
Mark
On Fri, Jun 26, 2009 at 5:48 AM, Dan Vega wrote:
>
> Ok so I just don't understand t
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 my
10 matches
Mail list logo
