yes, the messages are a bit cryptic for sureWicketMessage: No get method defined for class: class java.lang.Integer_expression_: idwhat it says is that it is looking to evaluate _expression_ "id" on the Integer class. so your property model is pointing to the wrong object.
-IgorOn 8/3/06, Gwyn Evan
On 03/08/06, Pierre-Yves Saumont <[EMAIL PROTECTED]> wrote:
> (I was using autoboxing, which it seems Wicket is not aware of).
Wicket 1.* deliberately doesn't make use of any JDK 1.5 features, in
order to support JDK 1.4, so while you can use JDK 1.5 features, you
need to be aware of this sort of
I followed your first advice and finally figure what it was (I was using
autoboxing, which it seems Wicket is not aware of). The problem was
difficult to find because it interfered with another problem (added a DO
and forgot to implement Serializable).
One should never make several changes with
or your propertyOGNL is wrong. You are welcome to share some code with the problem.FrankOn 8/3/06, Frank Bille <
[EMAIL PROTECTED]> wrote:It's due to invalid use of *PropertyModel. The POJO you use doesn't have a get method for the property defined.
FrankOn 8/3/06, Pierre-Yves Saumont
<[EMAIL PROT
It's due to invalid use of *PropertyModel. The POJO you use doesn't have a get method for the property defined.FrankOn 8/3/06, Pierre-Yves Saumont
<[EMAIL PROTECTED]> wrote:Hello,Wicket's error message are generally full of useful details, but this
one is a bit more tricky :WicketMessage: No get m
Hello,
Wicket's error message are generally full of useful details, but this
one is a bit more tricky :
WicketMessage: No get method defined for class: class java.lang.Integer
expression: id
It does not say anything about where the problem happens. As I had
several classes that had ids of typ
