Hey all, so I'm starting to play with Wicket and loving it, but I currently have a small pethate with the URL scheme used in the application.I realize the look of the URL shouldn't really matter, but I keep finding myself disliking it.
Currently my app shows a URL like:
Hi Mark,
if you are using wicket1.1 then your only choice is pretty much to use
a url rewriting filter to dress up the url. this is pretty easy to do.
there is a good filter here: http://tuckey.org/urlrewrite/
you can also add an alias to your page so it uses that in the url instead of fqn. but
Igor, cool - looks like that mounting option would suffice :) I just pulled out HEAD but see it uses Maven to build so I'm just gonna go install that.I assume any additional parameters passed via the traditional ?foo=barbar=foo scheme will be added to the PageParameters instance as well?
MarkOn
Hi, answers below
http://localhost:8081/quickstart/app?bookmarkablePage=com.theoryinpractice.testapp.pages.CommentsPage
Is there a way to get the app to resolve the above using something like:
http://localhost:8081/quickstart/app/page/Podcomments
or even
no, the additional parameters will not be added, in fact it will
probably cause an exception. this is because the part of the url after
the mount is processed by the page parameters encoder that is expecting
format (/param-name/param-value)*
its pretty easy to create an encoder that will process
oh and btw you can specify a page parameters encoder on per mount basis as well.
-Igor
On 12/3/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
no, the additional parameters will not be added, in fact it will
probably cause an exception. this is because the part of the url after
the mount is processed
I was about to ask that actually :)On 12/3/05, Igor Vaynberg [EMAIL PROTECTED] wrote:
oh and btw you can specify a page parameters encoder on per mount basis as well.
still the same problem then i am affraid.I have to control the visibilty if toat selectoption depending on what the model object is of the Select itself. (null or something)On 12/3/05,
Igor Vaynberg [EMAIL PROTECTED] wrote:
but a SelectOption is not in your collection - its a component. The whole
On Fri, 2 Dec 2005 22:51:05 +0100, Johan Compagner [EMAIL PROTECTED]
wrote:
Maybe we should build something that it is easier for models to version
themselfs. Like an interface IVersionable with a method Serializeable
getVersionData()
Which a model can implement. And then we don't store the
So pages with only bookmarkable links (and no other links) and no forms are not stored in the session?could be nice yes.Another thing i think of is having SingletonPage in the session. So that a bookmarkable link always goes to the same
page if there is already one there in the page mape (stored
I agree. I made the suggestion last month: http://sourceforge.net/mailarchive/message.php?msg_id=13756383I really like the architecture of Wicket although I have not used it much yet. The long url's is the one thing about Wicket that seemed would be a problem. It appears that the
The data provider is kept as the model because that is where the
sorting state lives and that needs to be versioned. I need to refactor
that out of the dataprovider looks like.
-IgorOn 12/3/05, Christian Essl [EMAIL PROTECTED] wrote:
On Fri, 2 Dec 2005 22:51:05 +0100, Johan Compagner [EMAIL
i dont really understand why this is a /problem/adding it yourself gives you options to add styles, your own text, etc.also most of the time i dont even want a select one message, i just want the box to default to the first choice. so when the page first renders the model is null and no options
Not only considering... we build it in! :)
There's a couple of things we are working on yet, which are stated in
the TODO doc in the niceurl example package. By looking at the commit
log (Juergen did some fresh commits), these issues are getting closer
to being fixed too.
Eelco
On 12/3/05, Jeff
I haven't taken a look at the latest code yet but I believe you simply
renamed the parameters to fixed single-character names (which I find
equally ugly). Is it possible for you to let us map parameter names to
arbitrary names we want? For example, I would alias bookmarkablePage to
page.
I haven't taken a look at the latest code yet
Well, please do that first before commenting :)
Eelco
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search
Perhaps next time you can be bothered to look at the code before saying that we did something ugly.-IgorOn 12/3/05, Gili
[EMAIL PROTECTED] wrote:I haven't taken a look at the latest code yet but I believe you simply
renamed the parameters to fixed single-character names (which I findequally
No problem. I was simply basing this on CVS diffs I saw on the mailing
list, so I didn't pull this out of the air. I'll check it out now.
Gili
Eelco Hillenius wrote:
I haven't taken a look at the latest code yet
Well, please do that first before commenting :)
Eelco
There you go, this is the CVS diff I was commenting on.
bookmarkablePage is replaced with 5.
Original Message
Subject: [Wicket-autocvs] wicket/src/java/wicket/protocol/http
WebResponseWithCryptedUrl.java,1.7,1.8
WebRequestWithCryptedUrl.java,1.10,1.11
Date: Sun, 20
this is for ENCRYPTED urls and has nothing to do with what we are discussing here.-IgorOn 12/3/05, Gili
[EMAIL PROTECTED] wrote: There you go, this is the CVS diff I was commenting on.
bookmarkablePage is replaced with 5. Original Message Subject: [Wicket-autocvs]
The data provider is kept as the model because that is where the sorting
state lives and that needs to be versioned. I need to refactor that out
of
the dataprovider looks like.
I see.
Maybe an interface ISortOrderProvider which is exactly like
ISortableDataProvider but does not extend
Where should I be looking in the new codebase for the clean URL code
you were discussing? It's not where I was expecting it.
Gili
Igor Vaynberg wrote:
this is for ENCRYPTED urls and has nothing to do with what we are
discussing here.
-Igor
On 12/3/05, *Gili* [EMAIL PROTECTED]
the problem im having is that something somewhere has to version this information. if i put it back into the dataprovider then we are back to square one. the problem is compounded by the fact that i want to add toolbars (like a filter toolbar). this means that the dataprovider has to be aware of
23 matches
Mail list logo
