Hi Sebastien,
The problem is that Request#getQueryParameters() is about - parameters in
the query string.
And "/mypage/${param}" uses parameter in the path.
Both of these are GET parameters but they are different.
To get the correct values you should use something like:
IRequestHandler handler
Hi Martin,
Thank you very much for this explanation and suggestion!
As you said, both are GET parameters (and actually, both are accessible
thought page-parameters), so from a user point of view it is strange that
one is not considered as a "request parameter".
Consider a user, who used to get
Hi,
Could you reproduce the issue in a quickstart application with 620.0?
About POST-GET: this looks to me like ONE_PASS_RENDER vs.
REDIRECT_TO_BUFFER render strategy. See IRequestCycleSettings.
Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
Thanks for the response Martin, good to know this is fixed in v7 (and
the workaround for v6).
On 21/05/14 14:08, Martin Grigorov wrote:
Hi,
This is fixed in Wicket 7.x. We didn't apply the fix to 6.x because it is a
behavior change.
You can read the current parameters in #onConfigure() with
Hi,
This is fixed in Wicket 7.x. We didn't apply the fix to 6.x because it is a
behavior change.
You can read the current parameters in #onConfigure() with
getRequestCycle().getRequest().getRequestParameters() and override with
them the page's parameters (page.getPageParameters())
Martin
Hi,
On Wed, May 14, 2014 at 4:11 PM, NickMoutsios nickmouts...@gmail.comwrote:
Hi,
I have a shared resource, DynamicImageResource, to serve images from the
database given some parameters.
The URL looks like this (coming from tinymce where it encodes the
ampersand):
Hi,
You need to use BookmarkablePageLink (BPL) instead of Link to have a nice
looking urls for the links themselves.
With your approach the link url will be
'./req?4-2.ILinkListener-[...]-7-linkanchor'
and when clicked it will make a redirect to /req/post/1
With BPL the link url will be
Hey Martin,
It's not about 'nice urls' as such, but with the Link-component, the
page doesn't redirect to /req/post/1. The redirection worked fine in
1.4.x, but in 1.6.x, it didn't work anymore. Dunno exactly why, but
all the links redirected to /post/62, not using/reading the
PageParameters. For
ListStringValue liSVs = params.getValues([Param name]);
if ((liSVs != null) !liSVs.isEmpty())
{
StringValue svValue = liSVs.get(0);
String sValue = svValue.toOptionalString();
...
}
you can just do
if(params.getNamedKeys().contains(parameter_name))
{
String svValue =
Hi
And you can even leave away the
if(params.getNamedKeys().contains(parameter_name))
and just do:
StringValue param = params.get(param); // or use an index if you wish
if (!param.isEmpty()) {
... param.toString() ...
}
Matt
On 2011-11-23 12:17, vineet semwal wrote:
ListStringValue
ha yes just checked out the source ,thanks :)
On Wed, Nov 23, 2011 at 5:46 PM, Matthias Keller
matthias.kel...@ergon.ch wrote:
Hi
And you can even leave away the
if(params.getNamedKeys().contains(parameter_name))
and just do:
StringValue param = params.get(param); // or use an index if
Thanks for your comments, Guys.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/PageParameters-in-1-5-a-sanity-check-request-tp4099136p4099956.html
Sent from the Users forum mailing list archive at Nabble.com.
new MyPage(bean);
On Mon, Aug 29, 2011 at 5:01 PM, eugenebalt eugeneb...@yahoo.com wrote:
I need to construct a page from a bean object. Ideally, I'd pass a custom
Object to
PageParameters params = new PageParameters();
params.add(bean, bean);
but it's not letting me do that... only
Good catch!
Please create a ticket.
On Wed, Jul 13, 2011 at 5:46 PM, Fabio Cechinel Veronez
fabio.vero...@gmail.com wrote:
Hello all,
I was in doubt whether this message should be sent to user or dev list
so following http://wicket.apache.org/help/email.html page
recommendation I'm sending
Fixed with https://issues.apache.org/jira/browse/WICKET-3896
On Wed, Jul 13, 2011 at 5:48 PM, Martin Grigorov mgrigo...@apache.org wrote:
Good catch!
Please create a ticket.
On Wed, Jul 13, 2011 at 5:46 PM, Fabio Cechinel Veronez
fabio.vero...@gmail.com wrote:
Hello all,
I was in doubt
I can only suggest you to use Wicket 1.5.
In current trunk MountedMapper supports all of this - named, indexed
and optional parameters.
See
http://svn.apache.org/viewvc/wicket/trunk/wicket-core/src/test/java/org/apache/wicket/request/mapper/MountedMapperTest.java?view=markup
for examples
On Thu,
Thank you for the tip Martin.
Sorry to ask silly question, but where can I find API for 1.5-M3? I found
this
http://www.jarvana.com/jarvana/view/org/apache/wicket/wicket/1.5-M3/wicket-1.5-M3-javadoc.jar!/index.html
but
it is missing some classes like for example PageParameters. Or it is best to
Download the jar from Maven repos.
Latest version is RC3, not M3.
On Thu, May 5, 2011 at 11:17 AM, Peter Miklosko peter.b...@gmail.com wrote:
Thank you for the tip Martin.
Sorry to ask silly question, but where can I find API for 1.5-M3? I found
this
I downloaded RC3, but even after building API from source (mvn
javadoc:javadoc) when I open documentation in wicket-core/target/site/apidoc
there is no
package parameters inside org.apache.wicket.request.mapper and because of
that no PageParameters class documentation.
Any suggestions?
Peter
On
it is in wicket-request.jar
On Thu, May 5, 2011 at 1:47 PM, Peter Miklosko peter.b...@gmail.com wrote:
I downloaded RC3, but even after building API from source (mvn
javadoc:javadoc) when I open documentation in wicket-core/target/site/apidoc
there is no
package parameters inside
God damn it so complicated... ;)
Thank you for all your help Martin!
Peter
On 5 May 2011 12:51, Martin Grigorov mgrigo...@apache.org wrote:
it is in wicket-request.jar
On Thu, May 5, 2011 at 1:47 PM, Peter Miklosko peter.b...@gmail.com
wrote:
I downloaded RC3, but even after building API
Using Maven/Ivy/Gradle/Buildr/... helps a lot these days ;-)
On Thu, May 5, 2011 at 1:54 PM, Peter Miklosko peter.b...@gmail.com wrote:
God damn it so complicated... ;)
Thank you for all your help Martin!
Peter
On 5 May 2011 12:51, Martin Grigorov mgrigo...@apache.org wrote:
it is in
Isn't my question clear or just nobody wants to get into mud of long
explanation?
Peter
On 4 May 2011 16:04, Peter Miklosko peter.b...@gmail.com wrote:
We are using MixedParamUrlCodingStrategy to create user/SEO friendly URLs
for booking website. The booking can have two different types as
Hi,
the parameter value (a ConfigurastionUser in your case) is converted
to a String using
toString(). Are you sure that you want to pass in that object and not
an ID of it?
Bert
On Wed, Dec 9, 2009 at 12:57, Eyal Golan egola...@gmail.com wrote:
Hi,
I have a BookmarkablePageLink that I set
OK. I understand.
Yes, I prefer passing it as an object.
So I switched the page LinkAttributesPage to have a constructor that accepts
the OBJECTS I need.
If I ever need it with URL, then I'll add the PageParameters and will get
the objects by keys.
Thanks,
Eyal Golan
egola...@gmail.com
Visit:
I really want to know how to encode-decode params in new PageParamters() calls.
Do I need to use WicketURLEncoder and WicketURLDecoder?
If so, how?
-- Tony
On Tue, Nov 24, 2009 at 1:56 PM, Anton Veretennikov
anton.veretenni...@gmail.com wrote:
Hi!
Sorry for simple question.
Do we need
This has been fixed in the trunk as far as I know. I brought it up
and even filed a JIRA I believe. It burned me too. :)
On Thu, Apr 2, 2009 at 11:40 AM, francisco treacy
francisco.tre...@gmail.com wrote:
i presume this has changed as of 1.4-rc2:
/**
* @see
yup, WICKET-2162.
i confirm this has been reverted in trunk. thanks :)
francisco
2009/4/2 James Carman jcar...@carmanconsulting.com:
This has been fixed in the trunk as far as I know. I brought it up
and even filed a JIRA I believe. It burned me too. :)
On Thu, Apr 2, 2009 at 11:40 AM,
Please file a JIRA and add your attachments there. Reply back to this post
with a link to the JIRA. This prevents things from being lost in a very
active mailing list.
--
Jeremy Thomerson
http://www.wickettraining.com
On Mon, Mar 16, 2009 at 10:11 AM, Brad Fritz
Jeremy and others,
On Mon, Mar 16, 2009 at 03:51:18PM -0500, Jeremy Thomerson wrote:
Please file a JIRA and add your attachments there. Reply back to
this post with a link to the JIRA. This prevents things from being
lost in a very active mailing list.
Done:
This is what the 1.2 javadoc says about it:
protected WebPage(PageParameters parameters)
Constructor which receives wrapped query string parameters for a
request. Having this constructor public means that your page is
'bookmarkable' and hence can be called/ created from anywhere. For
Hi Nino,
I don't link to the verification page from inside the application
itself. Instead, the link is send in an email to the user when he
changes his email adress. When they click the link, the page is opened.
In a lot of cases the users are still logged in on the application,
meaning
Hi Rik
Im not sure about this, it's been some months(if not years) since i've
touched 1.2.x. How are you linking to verification page when logged in,
for me it looks like you are not using pageparameters at all but instead
just instantiate the page with an other constructor..
Rik Overvelde
Basically, the code that executes is:
public ValidatePage(PageParameters parameters)
{
super(Valideren gegevens);
String code = parameters.getString(code);
If I put a breakpoint right after this, I already get the incorrect
code. The page that I use extends a page that
IIRC You should pass in the page parameters all the way down to the Wicket page:
super(parameters, Valideren gegevens)
Martijn
On Mon, Nov 3, 2008 at 8:41 AM, Rik Overvelde [EMAIL PROTECTED] wrote:
Basically, the code that executes is:
public ValidatePage(PageParameters parameters)
{
Strange, but as you said you had the idea that it could be a bug. But it
still strikes me a bit strange that the page are redirected, and results
in an modifified link.. Could you provide a cut out of the code?
Otherwise the idea with the servlet should be fine, I think you can
enable shared
Thats what I was thinking, too, when I read Uwes post. I did not look at
Wicket 1.4 yet, but had assumed that PageParameters should always be String to
String maps, because this is what they are in HTTP.
But then again, wicket is not strictly HTTP, and when you look at the javadoc
comment for
wicket provides convinience methods for working with strings, eg a
method to automatically convert a string to an int so you dont have
to. likewise it will automatically convert all objects you put into it
to a string.
-igor
On Mon, Aug 11, 2008 at 7:36 AM, Lutz Müller [EMAIL PROTECTED] wrote:
ok... that make sense to me.
The primary then should be String, String but maybe overload it so
that nothing legacy breaks.
I think the String, ? will help, but I also think that being
specific about what it holds is important... otherwise its trying to
be too smart and I might get a
then, unfortunately, you have to perform the conversion yourself all
the time, which is quiet annoying.
-igor
On Mon, Aug 11, 2008 at 8:24 AM, Brill Pappin [EMAIL PROTECTED] wrote:
ok... that make sense to me.
The primary then should be String, String but maybe overload it so that
nothing
Oh I wouldn't take out the convenience methods... but the base should
not be String,Object :)
Start with String, String then add any convenience methods from there.
I agree that manual conversion would be a bit of a pain, but most
people would only do it once if that was the only option
I agree on the generics front... however are not the params supposed
to be strings?
or do they represent request parameters as well as page attributes?
If they are representing both, maybe they should be separated.
- Brill
On 8-Aug-08, at 12:59 PM, Uwe Schäfer wrote:
ok, maybe there was
Igor Vaynberg schrieb:
done for now
thx again.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ok, maybe there was too much K and V in my last mail ;)
I´ll try another way round:
wouldn´t it be nice to be able to use smth like that ?
MapString, Integer map =...
PageParameters p = new PageParameters(map);
So if you agree, please switch from
public PageParameters(final MapString, Object
done for now
-igor
2008/8/8 Uwe Schäfer [EMAIL PROTECTED]:
ok, maybe there was too much K and V in my last mail ;)
I´ll try another way round:
wouldn´t it be nice to be able to use smth like that ?
MapString, Integer map =...
PageParameters p = new PageParameters(map);
So if you agree,
What is the likelihood that we can get this patch included in the next 1.4
milestone?
Again, I'll repeat my offer to submit it myself if given commit access. I
updated the JIRA issue with the API javadoc to show what I added.
-Doug
Doug Donohoe wrote:
I created
I will look at it this weekend
On 5/9/08, Doug Donohoe [EMAIL PROTECTED] wrote:
What is the likelihood that we can get this patch included in the next 1.4
milestone?
Again, I'll repeat my offer to submit it myself if given commit access. I
updated the JIRA issue with the API javadoc to
Hi,
You can best file an RFE in JIRA for things like this. The list is
primarily for questions and discussions, and adding it to JIRA will at
least make sure it stays on the list of things to look at.
Cheers,
Eelco
On Thu, Apr 24, 2008 at 3:00 PM, Doug Donohoe [EMAIL PROTECTED] wrote:
Hi
I created https://issues.apache.org/jira/browse/WICKET-1596 and submitted a
patch with test cases. I'd be happy to commit if given commit access if
that is easier.
Perhaps my work on wicketstuff-annotation demonstrates my attention to
detail in code and documentation.
Thanks,
-Doug
Eelco
Hi Ulf,
You use non iso8859-1 characters in the Java file. That is fine as long
as you are sure you safe the file in UTF-8.
Nowadays you should be allowed to use UTF-8 in URLs. But don't count on
it too much yet. Edvin's solution looks safer.
However, since you said that the problem only
If you use tomcat then you must set the encoding of the url as a
special property before tomcat uses urf8 for the url part.
On 1/22/08, palun [EMAIL PROTECTED] wrote:
(I´m sorry if this is the wrong forum for this kind of question. If so,
please direct me.)
Here´s my problem:
I set a page
params.put(str, åäö);
setResponsePage(MyPage.class, params);
But on MyPage the string is displayed as åäö !!?
You are sending non-ASCII characters so maybe you could URLEncode the
characters before sending them?
params.put(str, URLEncoder.encode(åäö, UTF-8));
And then get
52 matches
Mail list logo
