:) In the else branch for when the type is not null.
final IConverter converter =
getConverter(getType());
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: Friday, September 07, 2012 3:00 PM
To: users@wicket.apache.org
Subject: Re: Migration to 1.5: 'X'
> As you must have figured it out by now if you do not specify a type for the
> form field then Wicket converts the input via
> FormComponet#convertValue(getInputAsArray()) which is what your code hits
> and the type passed to it is not Object.class but rather String[].
I just opened a new thread w
ate a quick start so that we can all
reproduce your problem on our own to better help you?
~ Thank you,
Paul Bors
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: Friday, September 07, 2012 2:09 PM
To: users@wicket.apache.org
Subject: Re: Migration to 1.5: 'X
> // Via generics
Paul, I am not seeing this comment in the actual code. I am assuming
that you added this comment to clarify something for me, but I am not
getting it.
> Thus if you use generics your problem would most likely go away
Are you saying that Wicket has a different code path for models
day, September 06, 2012 6:13 PM
To: users@wicket.apache.org
Subject: Re: Migration to 1.5: 'X' is not a valid Serializable
> Besides calling #setType() do you actually use generics with your
> models and components?
Sorry, don't quite understand the question. I am not cal
> Besides calling #setType() do you actually use generics with your models and
> components?
Sorry, don't quite understand the question. I am not calling setType()
hence the problems with type detection in Wicket. Why is it important
if I use generics if they are only compile-time syntactic sugar?
-wicket-14.html#MigratingtoWicke
t1.4-Modelchanges
~ Thank you
Paul Bors
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: Thursday, September 06, 2012 5:18 PM
To: users@wicket.apache.org
Subject: Re: Migration to 1.5: 'X' is not a valid Serializable
The fi
The fix for this is the same as for the "X is not a valid
Serializable", specifically: new
EditableLabel(..).setType(String.class)
Is there anybody who thinks that requiring setType(..) call on all
components which models don't resolve to a supported type is huge
problem?
Can this be fixed in 1.5
I just ran into another problem with type resolution. In fact, it
looks like a bug in org.apache.wicket.util.lang.Objects#convertValue.
The call convertValue(nonNullNonArrayValue, Object.class) will always
return null if nonNullNonArrayValue is a value that is not null and
not an array!
Is that a
see this:
http://apache-wicket.1842946.n4.nabble.com/Wicket-1-5-ListMultipleChoice-add-Serializable-values-td4585991.html#a4586026
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Migration-to-1-5-X-is-not-a-valid-Serializable-tp4651757p4651764.html
Sent from the User
10 matches
Mail list logo