Marcin,
I couldn't reproduce the problem. Let me know if you find any more
details. For instance it would be helpful to match your app output
with query messages sent via HessianConnection. Per CVS example
connection logging can be configured via Log4J to output stuff like
this:
1637 [main] INFO
org.objectstyle.cayenne.remote.hessian.HessianConnection - ---
Message 10: Query
11976 [main] INFO
org.objectstyle.cayenne.remote.hessian.HessianConnection - ===
Message 10: Query done - took 339 ms.
Also try todays build (2006-4-13 - should be available within an hour
or two), as it fixes a number of things that can be possibly related
(such as CAY-503).
Sometime next week after B2 release I am planning to work on more
client examples. This way we'll have more regression cases available.
Andrus
On Apr 13, 2006, at 10:41 AM, Marcin Skladaniec wrote:
Hello
Yes, it is cayenne-1.2-dev-2006-4-11.
I'm sorry that I can't provide more info, but there is no Exception
thrown, the only symptom is that I'm getting a nulls where I should
get data.
I can add that I'm using an "wedge" class in between
PersistentObject and client entity classes. (Client superclass on
cayenne modeler form)
I have a question too. Is it important to use same entity classes
on client and server ?
I would like not to import the client entity classes to server, but
generate them separately. I'm using superclass and custom
dotemplates what causes that whole client jar has to be added to
server.
Aren't those classes treated as beans, so there is no real need to
have the same code on server and client ?
Regards
Marcin
