Igor, it seems the 1.4 snapshot in the maven repository still contains 1.5
code.
I built wicket from sources locally. When I tested the project against that
build I found yet another problem. Attempt to submit the form (no matter
what value the default processing flag has) led to response with
the problem is that trunk did not have version numbers updated so it
was building as 1.4 for a while. this has been fixed so latest
snapshots should be properly built out of branch.
-igor
On Sat, Sep 19, 2009 at 10:50 PM, Vladimir K koval...@gmail.com wrote:
The latest 1.4 snapshot does not
The latest 1.4 snapshot does not define IComponentBorder interface in
addition to disappeared form component persistence.
Is it supposed that 1.4.2 breaks compatibility with 1.4.1?
I see the only way to check the fix in wicket-ajax.js - mix it into wicket
1.4.1 jar.
Vladimir K wrote:
I
Igor, thanks for the fix.
I tried to compile against 1.4.2-20090916 and obtained two compilation
errors. Now FormComponent does not contain method setPersistent() and Page
does not contain method removePersistedFormData().
What API should be used instead?
Vladimir K wrote:
Igor, could you
You have to use 1.4.x branch.
trunk is for 1.5. form persistence is removed only in trunk
El vie, 18-09-2009 a las 05:32 -0700, Vladimir K escribió:
Igor, thanks for the fix.
I tried to compile against 1.4.2-20090916 and obtained two compilation
errors. Now FormComponent does not contain
I use 1.4-snapshot from
http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.4-SNAPSHOT/
martin-g wrote:
You have to use 1.4.x branch.
trunk is for 1.5. form persistence is removed only in trunk
El vie, 18-09-2009 a las 05:32 -0700, Vladimir K escribió:
Igor, thanks for
Igor, could you plan it for 1.4.2?
Vladimir K wrote:
done
https://issues.apache.org/jira/browse/WICKET-2463
Vladimir K wrote:
sure
igor.vaynberg wrote:
i guess create a quickstart and attach it to a jira issue. when i
tested buttons, while developing the feature, it
done
https://issues.apache.org/jira/browse/WICKET-2463
Vladimir K wrote:
sure
igor.vaynberg wrote:
i guess create a quickstart and attach it to a jira issue. when i
tested buttons, while developing the feature, it seemed to work fine.
-igor
On Wed, Sep 9, 2009 at 10:40 PM,
this bit of javascript:
if (submitButton != null) { s += Wicket.Form.encode(submitButton) + =1; }
is needed because we do perform a custom form serialization - really
just constructing the query string - that we submit back to server via
ajax. the multipart handling performs a regular post into
it is attached to the input tag as follows:
form wicket:id=actionForm
enctype='multipart/form-data'
div class=buttonBox
input wicket:id=cancelAction
type=submit
i guess create a quickstart and attach it to a jira issue. when i
tested buttons, while developing the feature, it seemed to work fine.
-igor
On Wed, Sep 9, 2009 at 10:40 PM, Vladimir K koval...@gmail.com wrote:
it is attached to the input tag as follows:
form
sure
igor.vaynberg wrote:
i guess create a quickstart and attach it to a jira issue. when i
tested buttons, while developing the feature, it seemed to work fine.
-igor
On Wed, Sep 9, 2009 at 10:40 PM, Vladimir K koval...@gmail.com wrote:
it is attached to the input tag as follows:
12 matches
Mail list logo
