Juha Alatalo wrote:
Johan Compagner wrote:
Yes you have :). private final static IGetAndSet getGetAndSetter(String
exp, Class clz) has changed quite a lot.
Do you have a unit test that fails now that shouldn't that i can
add to
the PropertyResolverTest ?
No I
Could you please open a JIRA issue[1] for this and attach the test case?
Thanks,
Eelco
[1] http://issues.apache.org/jira/browse/WICKET
On 6/26/07, Juha Alatalo [EMAIL PROTECTED] wrote:
Juha Alatalo wrote:
Johan Compagner wrote:
Yes you have :). private final static IGetAndSet
https://issues.apache.org/jira/browse/WICKET-698
- Juha
Eelco Hillenius wrote:
Could you please open a JIRA issue[1] for this and attach the test case?
Thanks,
Eelco
[1] http://issues.apache.org/jira/browse/WICKET
On 6/26/07, Juha Alatalo [EMAIL PROTECTED] wrote:
Juha Alatalo
Eelco Hillenius wrote:
Thanks. I had blocked cookies on my test site for some reason. Why
cookies are needed in 1.3? In 1.2 that wasn't the case, was it?
It shouldn't be the case now either; links should always be rewritten
so that it includes the jsessionid if the cookie is not available
Juha Alatalo wrote:
Eelco Hillenius wrote:
Thanks. I had blocked cookies on my test site for some reason. Why
cookies are needed in 1.3? In 1.2 that wasn't the case, was it?
It shouldn't be the case now either; links should always be rewritten
so that it includes the jsessionid if the cookie
Yes you have :). private final static IGetAndSet getGetAndSetter(String
exp, Class clz) has changed quite a lot.
Do you have a unit test that fails now that shouldn't that i can add to
the PropertyResolverTest ?
No I don't.
is this exception now thrown then:
throw new
Johan Compagner wrote:
Yes you have :). private final static IGetAndSet getGetAndSetter(String
exp, Class clz) has changed quite a lot.
Do you have a unit test that fails now that shouldn't that i can
add to
the PropertyResolverTest ?
No I don't.
is
1)
If the model is List, PropertySolver doesn't try to find fields. We are
using vectors containing public fields. In 1.2.6 this was ok.
i dont know if we really changed the property resolver behavior like tis for
1.3
Do you have a unit test that fails now that shouldn't that i can add to the
Hi,
We are trying to start using wicket version 1.3 and encountered some
problems
1)
If the model is List, PropertySolver doesn't try to find fields. We are
using vectors containing public fields. In 1.2.6 this was ok.
2)
Pressing any button or link causes page expiration. It seems that
Johan Compagner wrote:
1)
If the model is List, PropertySolver doesn't try to find fields. We are
using vectors containing public fields. In 1.2.6 this was ok.
i dont know if we really changed the property resolver behavior like tis
for 1.3
Yes you have :). private final
Thanks. I had blocked cookies on my test site for some reason. Why
cookies are needed in 1.3? In 1.2 that wasn't the case, was it?
It shouldn't be the case now either; links should always be rewritten
so that it includes the jsessionid if the cookie is not available (the
actual rewriting is
11 matches
Mail list logo