nobody has a solution?
On 1 Apr., 07:46, Johannes Stein johannes.st...@googlemail.com
wrote:
Hey folks,
thank you for your help.
I got it fixed. I missed to implement a zero-argument constructor in
Kontakt...
Damn... im so blind! But sometimes you need to have a night to rethink
on it
Well you know most sane people are asleep over here...
You could just use the Date constructor directly with those three
numbers - Date(year - 1900, month, date), which is what you then pass
on to the client through RPC. The DateTimeFormat class is intended
for client side use to substitute for
Hey,
ive got a problem and im searching for hours to find a solution.
My problem is the following:
I have a little RPC-Service which returns as a result a Domain-
Object (Own custom-class).
But this Domain-Object could not be serialized, though i have made
this Domain-class serializable with
Don't have a constructor with arguments, only use Set/Gets.
What's a Kontakt? Is that serializable?
Fix the constructor and verify Kontakt is serializable and it should
work.
On Mar 31, 10:43 am, Johannes Stein johannes.st...@googlemail.com
wrote:
Hey,
ive got a problem and im searching
What are the fields of the Kontakt class? Based on the error, one of
the fields under Domain is a JavaScriptObject, but nothing in your
Domain class above seems to be.
Also, you should just use the java.io.Serializable interface, not
gwt's IsSerializable.
--
You received this message because
I think it's fine to have constructors with arguments (so long as you also
have a zero-argument constructor), but, yes, Kontakt needs to be
serializable too.
kathrin
On Wed, Mar 31, 2010 at 2:41 PM, Sean slough...@gmail.com wrote:
Don't have a constructor with arguments, only use Set/Gets.
Hey folks,
thank you for your help.
I got it fixed. I missed to implement a zero-argument constructor in
Kontakt...
Damn... im so blind! But sometimes you need to have a night to rethink
on it again.
Okay, but there´s one new question.
In my database (dont know why it was designed this way) the
