You can also try at http://wicketstuff.org/wicket14/ajax/choice
I just updated it to 1.4.18.
On Thu, Aug 25, 2011 at 10:21 PM, Pedro Santos pedros...@gmail.com wrote:
Hi Palmer, it is possible related to
https://issues.apache.org/jira/browse/WICKET-3820 , upgrade to 1.4.18
2011/8/25 PALMER,
I'm using the SignInPanel on my web application and it works quite well. The
only thing I want to change are the error message which got rendered to the
feedback panel when no login or password is entered.
The error message is not really nice at is contains the internal name of the
text field
No I'm not doing any ajax on this page.
I got it somehow working that the feedback panel show info messages form the
ActionPanels constructor but the error messages after the delete button was
pressed are still not shown.
--
View this message in context:
I finally solved my problem perhaps it's not the best way but it works for
me.
After digging in the sources of the SignInPanel I figured out the following.
setRequired() is always called in the constructor of a PasswortTextField.
setRequired() is a method of the FormComponent class which has
enable DEBUG logging of Localizer class and you'll see what resource
keys are attempted
this way you'll see that you can use myFormComponentId.Required=
and it will be used just for the component with id
myFormComponentId, all other will still use 'Required'.
On Fri, Aug 26, 2011 at 3:18 PM,
A great, that's even better!
Thanks!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/How-to-override-SignInPanel-s-error-messages-tp3770610p3770720.html
Sent from the Users forum mailing list archive at Nabble.com.
I think you must set your page as error page.
Make that change and try again.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri, Aug 26, 2011 at 1:27 AM, Scott Reed sr...@avacoda.com wrote:
A created my own PageExpiredErrorPage. There is a button that is supposed
to take the user
We are running a couple of products on 1.5 and are having no problems.
I'd say go ahead and migrate now. Then you'll probably be ready for
when 1.5 are released depending on project complexity. Although afaik
it was not so hard to go from 1.4 - 1.5 will be a little harder going
from 1.3 to 1.5..
There are few articles about the new request processing architecture
and mounting of pages and resources at http://wicketinaction.com.
I'm planning to add another for the new event mechanism soon.
On Wed, Aug 24, 2011 at 7:34 PM, Fabian Schwarzer
fabian.schwar...@gmx.de wrote:
Hi!
Does anyone
My apologies. I am reposting this without the distracting pseudo-formatting.
I created my own PageExpiredErrorPage. There is a button that is
supposed to take the user to the login page so they can log in (just
like the button on the default page-expired error page). /
/
When the user first
Thanks, Bruno. I added isErrorPage() just in case. The docs just say
This can help the framework prevent infinite failure loops. That's
also not mentioned in Wicket in Action which says creating an error
page is no different than creating a normal page.
Scott
On 8/26/2011 9:15 AM, Bruno
actually #isErrorPage() is not used in current 1.5, so WIA is correct
On Fri, Aug 26, 2011 at 6:15 PM, Scott Reed sr...@avacoda.com wrote:
Thanks, Bruno. I added isErrorPage() just in case. The docs just say This
can help the framework prevent infinite failure loops. That's also not
mentioned
can we remove it then?
-igor
On Fri, Aug 26, 2011 at 8:19 AM, Martin Grigorov mgrigo...@apache.org wrote:
actually #isErrorPage() is not used in current 1.5, so WIA is correct
On Fri, Aug 26, 2011 at 6:15 PM, Scott Reed sr...@avacoda.com wrote:
Thanks, Bruno. I added isErrorPage() just in
I tried this on IRC first, but it seems that everybody is busy over
there so i thought i'd try it here :)
It seems that in wicket 1.5, the only way to let 2 Pages (for example, a
page in a modal window + the page that opened that modal window)
communicate with each other (call each others
I found that replacing add(linkHomePage( homeLink )) with my code
below works. Can anyone explain?
Thanks,
Scorr
void addHomeBtn( String id, MarkupContainer parent, final WebPage page )
{
final AbstractDefaultAjaxBehavior homeBehavior = new
AbstractDefaultAjaxBehavior()
{
Hi again,
Just to add to this that the following will work for pages with parameters:
@Override
protected void onSelectionChanged(Locale newSelection) {
super.onSelectionChanged(newSelection);
// the following tells wicket to instantiate a new page using
the current
for 1.6 - yes, I think. unless we find it useful for something
On Fri, Aug 26, 2011 at 6:54 PM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
can we remove it then?
-igor
On Fri, Aug 26, 2011 at 8:19 AM, Martin Grigorov mgrigo...@apache.org wrote:
actually #isErrorPage() is not used in
But still, why isn't Scott's case working?
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fri, Aug 26, 2011 at 5:12 PM, Martin Grigorov mgrigo...@apache.orgwrote:
for 1.6 - yes, I think. unless we find it useful for something
On Fri, Aug 26, 2011 at 6:54 PM, Igor Vaynberg
Hi,
(I was pretty sure I could find an answer to my question by searching
the list archives and the Wicket Jira, but didn't. But if there's an
answer somewhere already and I just missed it, I apologize and would
be very happy if I was pointed to it.)
Is the visitChildren method of
the way it works makes sense to me...
-igor
On Fri, Aug 26, 2011 at 3:24 PM, Mika Viljanen mika.vilja...@iki.fi wrote:
Hi,
(I was pretty sure I could find an answer to my question by searching
the list archives and the Wicket Jira, but didn't. But if there's an
answer somewhere already and
Is it possible to open a modal window after file upload completion.
Even though I'm using the AJAX file upload which shows the progress bar
the submit handler doesn't contain a 'target' parameter required to
bring up a modal.
protected void onSubmit()
{
final FileUpload upload =
21 matches
Mail list logo
