It just occured to me that cayenne remote object persistence might be
the key to a level of interoperability that I need in a very, very
heterogenous environent (i.e. my office) where people use Java, .net
and php, depending on the project, programmer and legacy code.
Is there any special reason
Actually clients written in other languages is one area that has a
huge potential. And this is something I'd really like to explore.
Current transport layer (Hessian) has support in many other
languages, also a standard WS interface is being developed as a
Summer of Code project. All this
Remote calls are done via a RemoteService interface (all low-level
details are handled by Hessian).
public interface RemoteService extends Remote {
RemoteSession establishSession() throws RemoteException;
RemoteSession establishSharedSession(String name) throws
RemoteException;
Looks like you have a HOLLOW object with a temporary ID? Strange...
Andrus
On Jul 5, 2006, at 3:20 PM, Mike Kienenberger wrote:
I'm not entirely certain what's changed between 1.2B2 and 1.2RC2, but
I'm now getting this error when I upgrade.
This is reading a property a newly-created data
Well, stepping through it in the debugger shows the state of the
object as new at this point with B2 but hollow with RC2. Guess I
need to track down what caused the persistent state change.
On 7/5/06, Andrus Adamchik [EMAIL PROTECTED] wrote:
Looks like you have a HOLLOW object with a
Well, I've been unable to track down exactly how this is happening.
Somehow, when my objects are unserialized and reattached to their
datacontexts on the following request, some of them are being changed
from NEW to HOLLOW in calls to localObjects().Under B2, the
objects never get attached
For what it's worth, the change in behavior happened between B2 and
B3. Versions B3, RC1, and RC2 all generate the same error.
The only thing in the release notes for B3 that looks relevent is
CAY-542 Re-registered objects lose their relationships
I'm guessing that the new recursive algorithm
