* Herman Bovens:
...WEB-INF/lib/wicket-1.3.0-incubating-SNAPSHOT-javadoc.jar!/org/apache/wicket/markup
Loading Wicket templates from the Javadocs won't help much.
I don't think it's a good idea to put the javadocs in
Jean-Baptiste Quenot-3 wrote:
...WEB-INF/lib/wicket-1.3.0-incubating-SNAPSHOT-javadoc.jar!/org/apache/wicket/markup
Loading Wicket templates from the Javadocs won't help much.
I don't think it's a good idea to put
Jean-Baptiste Quenot-3 wrote:
* Herman Bovens:
tdIDnbsp;input wicket:id=username type=text name=j_username
id=j_username size=24 tabindex=1//td
tdPaswoordnbsp;input wicket:id=password type=password
name=j_password id=j_password size=24 tabindex=2//td
Obviously adding the name
* Herman Bovens:
OK thanks, the IllegalBlockSizeException is gone now (strange:
if I add the name attribute again, it stays gone?), but
the MarkupExceptions remain.
Well I guess markup errors are pretty understandable as they state
precisely which component does not match. For
Jean-Baptiste Quenot-3 wrote:
* Herman Bovens:
OK thanks, the IllegalBlockSizeException is gone now (strange:
if I add the name attribute again, it stays gone?), but
the MarkupExceptions remain.
Well I guess markup errors are pretty understandable as they state
precisely
I would say the simple signin page is the closest match.
This is my panel's HTML file:
html xmlns:wicket
body
wicket:panel
form wicket:id=signInForm name=signInForm
table
* Herman Bovens:
tdIDnbsp;input wicket:id=username type=text name=j_username
id=j_username size=24 tabindex=1//td
tdPaswoordnbsp;input wicket:id=password type=password
name=j_password id=j_password size=24 tabindex=2//td
Obviously adding the name attribute on the password field is
causing
When I omit the panel that has the password field (a simple subclass from
SignInPanel) from the page, there are no errors anymore. Obviously, I need
the SignInPanel. It worked fine with version 1.2. Any ideas?
Herman Bovens wrote:
Hi,
I'm getting errors when deploying my application,
* Herman Bovens:
When I omit the panel that has the password field (a simple
subclass from SignInPanel) from the page, there are no errors
anymore. Obviously, I need the SignInPanel. It worked fine
with version 1.2. Any ideas?
Providing the relevant code snippet would
Hi,
I'm getting errors when deploying my application, which I have just migrated
from wicket 1.2 to 1.3.
The first one is this:
00:52:22,421 ERROR [PasswordTextField] Problem applying encryption; go on
without for now
org.apache.wicket.WicketRuntimeException: Unable to decrypt the text
'[EMAIL
10 matches
Mail list logo
