Figured it out... the sample I had found at some point used label instead of
span
Changing it to span seems to have it working in all browsers now.
..darcy
--
View this message in context:
Hi,
Is it possible not to render a component for security issues.
I know i can use IAuthorizationStrategy for this but i want to to it manually
I don't need just setVisible(false), i really need not to render that
component.
I don't know which method to override. Below code gives error.
Am 11.08.2011 11:59, schrieb Lurtz Nazgul:
Hi,
Is it possible not to render a component for security issues.
I know i can use IAuthorizationStrategy for this but i want to to it manually
I don't need just setVisible(false), i really need not to render that component.
I don't know which
org.apache.wicket.Component.setVisibilityAllowed(boolean) is for that purpose.
if component.isVisibleInHierachy() returns false then the component is
not rendered.
What exactly is the problem with setVisible(false) ?
On Thu, Aug 11, 2011 at 12:59 PM, Lurtz Nazgul lu...@ymail.com wrote:
Hi,
Is
setVisible(false) , actually renders component but disables it via style sheet
like
input type=input value=name style=display:none
I don't want that.
I will try isVisibleInHierachy now.
Thanks.
From: Martin Grigorov mgrigo...@apache.org
To:
setVisible(false) , actually renders component but disables it via style sheet
Isn't that the case only when you use setOutputPlaceholderTag(true)? For other
cases, nothing is output AFAIK.
- Tor Iver
-
To unsubscribe,
On Thu, Aug 11, 2011 at 1:42 PM, Wilhelmsen Tor Iver toriv...@arrive.no wrote:
setVisible(false) , actually renders component but disables it via style
sheet
Isn't that the case only when you use setOutputPlaceholderTag(true)? For
other cases, nothing is output AFAIK.
true
- Tor Iver
Problem is solved now:
i extract the application-relative-path with:
String path = Strings.stripJSessionId(request.getRequestURI());
the trick is to overwrite method onComponentTag(ComponentTag tag) of class
ResourceLink and prepend the application -relative path so i end up with
e.g.:
Igor: thank you for your reply and your solution. Could you please discuss
this case with other developers and let me know what they think? In my
opinion framework should make my job easier not force me to do workarounds
to get what I need. Just a thought.
Martin: thank you :D
Kind regards
Hi,
i've added a domain model globally to my session.
A form for editing this data is provided on page A. On this i have 2
submit buttons. One with setDefaultFormProcessing false (to previous
page) and one with true (to next step).
If i press the main submit (next step | dfp = true) then
Shouldn't you be submitting that button anyway? dfp = true
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 10:44 AM, Mike Mander wicket-m...@gmx.de wrote:
Hi,
i've added a domain model globally to my session.
A form for editing this data is provided on page
When I set the *setRequired(true)* in a CheckGroup and Override the
*onValidate* of the Form, calling *updateFormComponentModels();* to update
the Models, a NullPointerException occurs in CheckGroup.updateModel.
This only occurs when setRequired is setted to true, not happening when not
setted or
Are you calling super.onValidate() ?
And I think before updating the models, all components must be visitted.
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 11:39 AM, delta lsgpimen...@gmail.com wrote:
When I set the *setRequired(true)* in a CheckGroup and
Yeap, I'm calling ;)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/CheckGroup-updateModel-setrequired-Bug-tp3736032p3736067.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To
Am 11.08.2011 16:36, schrieb Bruno Borges:
Shouldn't you be submitting that button anyway? dfp = true
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 10:44 AM, Mike Manderwicket-m...@gmx.de wrote:
Hi,
i've added a domain model globally to my session.
A
I think that's a case for using Border.
http://wicket.apache.org/apidocs/1.4/org/apache/wicket/markup/html/border/Border.html
You may check the migration of Border behaviour in 1.5 at
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-RemovedmagicfromBorderComponent
You want to go back to another page without having to fill the form, but you
also don't want to lose data you typed in in the previous screen? Seems
weird to me.
Have you considered to add Ajax update behaviour? onBlur of components, you
could update the model of each component.
*Bruno Borges*
Hmmm, the error only occurs when no CheckBox in the CheckGroup is marked, but
considering this scenario the super.onValidate() should complain about I
don't have any CheckBox marked in a CheckGroup with serRequired(true),
that's not what happening. And since this validation don't exists, when
Hmmm, the error only occurs when no CheckBox in the CheckGroup is marked, but
considering this scenario the super.onValidate() should complain about I
don't have any CheckBox marked in a CheckGroup with serRequired(true),
that's not what happening. And since this validation don't exists, when
Is that Wicket 1.5 RC5.1 ?
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:00 PM, delta lsgpimen...@gmail.com wrote:
Hmmm, the error only occurs when no CheckBox in the CheckGroup is marked,
but
considering this scenario the super.onValidate() should
It's 1.4.15
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/CheckGroup-updateModel-setrequired-Bug-tp3736032p3736109.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To
Am 11.08.2011 16:54, schrieb Bruno Borges:
You want to go back to another page without having to fill the form, but you
also don't want to lose data you typed in in the previous screen? Seems
weird to me.
Have you considered to add Ajax update behaviour? onBlur of components, you
could update
I have a five step static Wicket Wizard which works great for the most part. I
am running on Wicket 1.4.13.
I am seeing some odd behavior and stepping through a debugger hasn't yielded
any causes so I am reaching out to the forum for help.
If I navigate through the wizard by pressing the Next
Could you test your app with 1.4.18 ?
Just in case...
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:04 PM, delta lsgpimen...@gmail.com wrote:
It's 1.4.15
--
View this message in context:
In your GoBack button's submit method (dpf = false), call
form.updateFormComponentModels()
*Bruno Borges *
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:08 PM, Mike Mander wicket-m...@gmx.de wrote:
Am 11.08.2011 16:54, schrieb Bruno Borges:
You want to go back to
Is possible using reuseManager, but you need to keep reference to it somewhere.
http://apache-wicket.1842946.n4.nabble.com/Check-box-loses-checked-state-after-error-td1855690.html
**
Martin
2011/8/11 Bruno Borges bruno.bor...@gmail.com:
In your GoBack button's submit method (dpf = false), call
Models must be updated anyway, and that's solved with
form.updateFormComponentModels()
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:21 PM, Martin Makundi
martin.maku...@koodaripalvelut.com wrote:
Is possible using reuseManager, but you need to keep
On Thu, Aug 11, 2011 at 4:35 AM, armandoxxx armando@dropchop.com wrote:
Igor: thank you for your reply and your solution. Could you please discuss
this case with other developers and let me know what they think?
this is the place where the developers discuss things. if any of them
want to
why are you calling updatemodels() from inside onvalidate()? this is
what happens anyways if validation passes. i am guessing your code
does not check if the form is valid before calling updatemodels()
which causes the error you are describing since you are forcing a
model update for a component
Isn't this correct?
onInitialize() {
super.onInitialize();
... // whatever I put here would be the same as overriding
onAfterInitialize();
}
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 12:35 PM, Igor Vaynberg igor.vaynb...@gmail.comwrote:
On Thu, Aug
No, if you don't want to update models, you can use reusemanager. It
retains the raw unsubmitted values in rawInput fields.
**
Martin
2011/8/11 Bruno Borges bruno.bor...@gmail.com:
Models must be updated anyway, and that's solved with
form.updateFormComponentModels()
*Bruno Borges*
I'm doing that to force the Models to update, since when I receive a validate
error, like when I dont fill a required field, the checkgroup in the page
loose the ckeckboxes marked, so I update the models and the marked
checkboxes come back (So the user dont have to mark all over again just
because
I can't, we must work with this version, because of the company.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/CheckGroup-updateModel-setrequired-Bug-tp3736032p3736594.html
Sent from the Users forum mailing list archive at Nabble.com.
I just realized that onInitialize() isn't the 'initialize' of
traditional frameworks that I thought it was: The style of
initialization that occurs in the lifecycle after instance construction
has completed and the call to the constructors has returned.
onInitialize appears to be called while
this is true only for page#oninitialize() which is called at the time
the first add(component) is called. it remains like this for backwards
compatbility with the first introduction of #oninitialize(). in 1.5
this has been changed so that oninitialize() is called after the page
is constructed.
this is true only for page#oninitialize() which is called at the time
the first add(component) is called. it remains like this for backwards
compatbility with the first introduction of #oninitialize().
Ahuh!
In 1.5 this has been changed so that oninitialize() is called after
the page is
Even if you can't upgrade the production version its worth testing it
against the newer version of Wicket to see if the bug is resolved.
On Thu, Aug 11, 2011 at 12:43 PM, delta lsgpimen...@gmail.com wrote:
I can't, we must work with this version, because of the company.
--
View this message
Hello,
Following the release of wicket 1.4.18 I have cut a matching
wicketstuff-core release.
The artifacts have been promoted and should be synced into the maven
central repository with in a 2-3 hours.
They can be retrieved like this:
dependency
groupIdorg.wicketstuff/groupId
Mike, excelent job!!
Thank you very much.
*Bruno Borges*
www.brunoborges.com.br
+55 21 76727099
On Thu, Aug 11, 2011 at 10:56 PM, Michael O'Cleirigh
michael.ocleir...@rivulet.ca wrote:
Hello,
Following the release of wicket 1.4.18 I have cut a matching
wicketstuff-core release.
The
Hi Jeremy,
did you find a solution as we've had the problem for a long time now
and more and more people are reporting it as they move over to FF and
Chrome?
On Tue, Jan 25, 2011 at 3:39 AM, Jeremy Thomerson
jer...@wickettraining.com wrote:
Perhaps this thread will help:
just to say we still have this issue and its getting more and more
worse as people are moving to FF and Chrome.
We have no idea how to solve as we cannot reproduce it consistently.
On Mon, Dec 13, 2010 at 8:41 PM, Wayne W waynemailingli...@gmail.com wrote:
Hello everyone,
I thought you might
Hi all,
I've digged into PackageMapper and CryptoMapper trying to achieve a
Mapper based on user defined URLs, but honestly, it is not easy (at least
for me).
The goal is to provide access to pages in package com.mysite.profile
(pages: Guests, Messages, Wall, Home, etc) through a root path
if you create a quickstart that people can play with you will get a
lot more responses...
-igor
On Thu, Aug 11, 2011 at 10:38 PM, Bruno Borges bruno.bor...@gmail.com wrote:
Hi all,
I've digged into PackageMapper and CryptoMapper trying to achieve a
Mapper based on user defined URLs, but
@IGor: I figured it out .. no need for new features.
@Bruno: if you cann onAfterInitialize() in onInitialize() you can't be sure
all components on the page we're
initialized()
Regards
Armando
--
View this message in context:
44 matches
Mail list logo
