Hello Johan i test whatyou say with tomcat-5 and observer the same results
if i change my page encoding to "UTF-8" firefox status bar prints ok
all characters
I think that the correct is overload PageParamters put and putAll and
make here the codification work in this way PageParameters are allwa
Hello again
I solved my problem calling
java.net.URLencoder.ecode(paramValue,"ISO-8859-1");
before setting a parameter
Why you create a class for encoding parameters if there is one in JDK ?
i think i´ll extend BookmarkableLink and overload setParam to make
this by default
thanks for your tim
maybe i don´t understand how this work
but other example that fail using bookmarkableLink is
myBookMakableLink.setParameter("nodePath","/%");
the generated url is
http://localhost:8080/app?bookmarkablePage=TestPage&nodePath=/
the url that i expect
http://localhost:8080/app?bookmarkablePage=Te
soory for the empty message
this is the correct url the bad include a +- simbol that i can print here
http://localhost:8080/app?bookmarkablePage=TestPage&nodePath=Coru%F1a
On 10/8/05, pepone pepone <[EMAIL PROTECTED]> wrote:
> On 10/8/05, pepone pepone <[EMAIL PROTECTED]> wrote:
> > Yes what you s
On 10/8/05, pepone pepone <[EMAIL PROTECTED]> wrote:
> Yes what you say is correct Johan
>
> but the problem is the next
>
> i create a bookMarkable link
>
> a call setParameter("nodePath","/c++");
>
> and the url for this bookmarkable link is
> http://localhost:8080/app?bookmarkablePage=TestPage&n
Yes what you say is correct Johan
but the problem is the next
i create a bookMarkable link
a call setParameter("nodePath","/c++");
and the url for this bookmarkable link is
http://localhost:8080/app?bookmarkablePage=TestPage&name=c
and the correct url must be
http://localhost:8080/app?bookmark
thats because that is not really a bug
this url:
http://localhost:8080/app?bookmarkablePage=TestPage&name=c+a
does have the right effect now in wicket.
you get 'c a'
because a plus is a space in an url.
So if we add a param like 'a+b" in a bookmarkable page then we should convert it to
'c%2b
Haha, seems that Johan closed that bug :)
Eelco
On 10/8/05, pepone pepone <[EMAIL PROTECTED]> wrote:
> Ok I made a bug report same weeks ago and same body close it but the
> problem is still the same
>
> here is the link to the bug
> https://sourceforge.net/tracker/index.php?func=detail&aid=12955
Ok I made a bug report same weeks ago and same body close it but the
problem is still the same
here is the link to the bug
https://sourceforge.net/tracker/index.php?func=detail&aid=1295506&group_id=119783&atid=684975
must i open a new one??
I don´t know if unscaped is a servlet container job. wh
make a bug report for these things.
Is unescaping not a job for the servlet container itself?
On 10/8/05, pepone pepone <[EMAIL PROTECTED]> wrote:
Hello allI have a problem with bookmarkable links and use same especialcharacters no only '+' that i mentioned in my previous message 'ñ' isnot escaped
Hello all
I have a problem with bookmarkable links and use same especial
characters no only '+' that i mentioned in my previous message 'ñ' is
not escaped because bookmarkable links escape parameters using
wicket.util.string.String.escapeMarkup(param,false,false);
by colling this method not espac
Hello this issue continues to fail with wicket-1.1.rc2
any body in wicket see this as a problem?
On 9/25/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
> #: Johan Compagner changed the world a bit at a time by saying on 9/25/2005
> 12:17 PM :#
> > i don't know about %20
> > i hate thise thing
#: Johan Compagner changed the world a bit at a time by saying on 9/25/2005
12:17 PM :#
i don't know about %20
i hate thise things in urls + is much better readable
So if we are going to do that (encode it)
Then my vote is + for ' '
and %2b for '+'
Johan but this shouldn't be a standard wa
+ is not translated by us
The url you have in youre browser still does have the +
it is the servlet spec that makes ' ' from +
But as i said we can encode this this to %2b and then make ' ' a '+'On 9/25/05, pepone pepone <[EMAIL PROTECTED]
> wrote:I view that this bug is closed but i think problem
i don't know about %20
i hate thise things in urls + is much better readable
So if we are going to do that (encode it)
Then my vote is + for ' '
and %2b for '+'
On 9/25/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
#: pepone pepone changed the world a bit at a time by saying on 9/25/2005 12:
#: pepone pepone changed the world a bit at a time by saying on 9/25/2005
12:26 AM :#
I view that this bug is closed but i think problem is still the same
i try to explain it better
if i use PageParameters class to buil the parameters i think that the
class must
translate the simbol + to the
I view that this bug is closed but i think problem is still the same
i try to explain it better
if i use PageParameters class to buil the parameters i think that the
class must
translate the simbol + to the corect 2B Hex encoding
currently the '+' is translate to ' '
and ' ' is tranlate to '%20
i can reproduce this bug with 1.1.rc1 and open a bug
here is the link
https://sourceforge.net/tracker/index.php?func=detail&aid=1295506&group_id=119783&atid=684975
On 9/19/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
> #: Johan Compagner changed the world a bit at a time by saying on 9/19/200
#: Johan Compagner changed the world a bit at a time by saying on 9/19/2005
3:18 PM :#
i don't think locale has much to do about it.
It is not char encoding. It is url encoding.
Yep, absolutely. I wasn't talking about char encoding :-). I was looking for
URL.encode/decode calls.
./alex
--
i don't think locale has much to do about it.
It is not char encoding. It is url encoding.
On 9/19/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
#: Johan Compagner changed the world a bit at a time by saying on 9/19/2005 1:48 PM :#> if this is still the case in RC1 then please open a bugreport>
#: Johan Compagner changed the world a bit at a time by saying on 9/19/2005
1:48 PM :#
if this is still the case in RC1 then please open a bugreport
We have to encode all the params, but i think we did something in that area
so check RC1 first.
When firstly answering this, I was looking f
Thanks Johan i try rc1 today and them open a bug,
can the locale of my page influece this inssue?
On 9/19/05, Johan Compagner <[EMAIL PROTECTED]> wrote:
> if this is still the case in RC1 then please open a bugreport
> We have to encode all the params, but i think we did something in that area
>
if this is still the case in RC1 then please open a bugreport
We have to encode all the params, but i think we did something in that area so check RC1 first.
On 9/18/05, Alexandru Popescu <[EMAIL PROTECTED]> wrote:
#: pepone pepone changed the world a bit at a time by saying on 9/18/2005 7:53 PM :
#: pepone pepone changed the world a bit at a time by saying on 9/18/2005 7:53
PM :#
Hello boys
I think that this is a bug in wicket currently i testing with 1.1.b4 i
try later to update to rc1
the problem is that if i use a parameter like
myBookMarkableLink.setParam("name","c++");
later in
Hello boys
I think that this is a bug in wicket currently i testing with 1.1.b4 i
try later to update to rc1
the problem is that if i use a parameter like
myBookMarkableLink.setParam("name","c++");
later in the class i get the param via
String param=getRequest().getParam("name);
param value i
25 matches
Mail list logo
