Any suggestions as to where I should start looking (source code or otherwise)
to understand how Wicket actually handles back button?
--
View this message in context:
http://old.nabble.com/What-happens-after-browser%27s-%27back%27-button--tp28149886p28179655.html
Sent from the Wicket - User maili
Hi,
thanks for the reply and the suggestion.
However I'm not sure it'll work (or else I'm misunderstanding what you're
suggesting). As you said yourself, 'when the user hits back wicket will pull
the old page instance from the pagemap and rerender it'. In my limited
testing it seemed that when h
Hi,
our first Wicket-based application is about to go into testing and I'm
feeling rather uncomfortable about the fact that I don't really
understand what happens when user uses browser's back button and then
submits some 'outdated' form. Can someone elaborate please on what
exactly happens when W
to true) and add a
> validator that fails when the flag is true
>
> Martijn
>
> On Fri, Mar 26, 2010 at 4:48 PM, Sergey Olefir
> wrote:
>>
>> Also on this subject -- if I want to prevent users from submitting wizard
>> (multi-page form) again via back butto
on at all
(e.g. show them the last 'normally' generated page if they submit anything
from the 'old' page), what would be the best way to achieve this?
Sergey Olefir wrote:
>
> Hi,
>
> I'm looking for a good source of information on Wicket's support for
&
Hi,
I'm looking for a good source of information on Wicket's support for
browser's back button and also on what happens when user opens a new
tab/window. I feel this is something I need to understand well before
we can deploy our first Wicket application in production.
I found this:
http://cwiki.
Hi,
for user interface reasons I want to use button on an otherwise
read-only page that would simply open another page (e.g. act just like
a link would). What would be the simplest way to achieve that
(including i18n)?
I'm currently using form like this:
Placeholder:
Execute
---
Form form
Hi,
is it possible to (easily) analyze HTML markup at runtime? More
specifically I'm thinking about implementing a component that will
examine its (or more realistically the markup of extending class)
markup to determine whether or not particular wicket:id is present.
Or, in other words, is it po
Thanks for the reply, Igor.
Indeed it was my own error -- there was a misconfiguration in our log4j
config which led to me simply not seeing error messages generated by Wicket
when serialization failed. It's only when I was shutting down the server,
the error message had enough severity to be see
Hi,
what is the current 'proper' way to debug serialization issues in Wicket?
My web search led me to two things:
- Wicket contains SerializableChecker class whose explicit purpose is
to assist in tracking down serialization issues.
- At some point it seems that in development mode Wicket used to
I'm not 100% sure what exactly is your issue, but have you taken a look at
subclasses of IFeedbackMessageFilter ? They allow filtering messages based
on component instance, for example. You will have to use reuseItems=true in
ListView though most likely.
Brad Grier wrote:
>
> I've written a dy
bgooren wrote:
>
> You gotta love Wicket for making it quite easy to do this stuff;
>
Actually I think in this particular case Wicket didn't make it 'easy' to do
what I needed to do. It would've been easy and logical if I could change
SharedResources method so it doesn't use class name in t
gBuffer;
import org.jasypt.encryption.pbe.StandardPBEStringEncryptor;
import org.jasypt.salt.ZeroSaltGenerator;
/**
* Version of standard {...@link WebRequestCodingStrategy} that encrypts FQNs
* (full qualified names of classes) in resource references.
*
* @author Sergey Olefir
*/
public class CryptWebRequestCodingS
I admit I didn't research in-depth what you've suggested, but from the
quoted piece it seems that your suggestion will find all subclasses of
ResourceReference. But to actually test that all resources are properly
mapped, it would be necessary to locate all invocations of the
ResourceReference co
Err, I guess I don't quite understand what you're proposing... My
understanding is that I need to know all class names that are used by
application as part of ResourceReference (and possibly something else too).
How would I scan for that?
Martijn Dashorst wrote:
>
> Create a unit test case tha
Thanks for heads up.
I guess it's back to hacking WebRequestCodingStrategy for me, the flag is
better than nothing, but I'm not eager in having application crash in
production because someone forgot to map something and somehow it slipped
past testing.
Antoine van Wel wrote:
>
> A flag has be
Thing is, I already toyed with WebRequestCodingStrategy -- specifically I
changed how resources are encoded by replacing URL path with URL parameter.
And I broke CSS/relative references in the process as I found out much later
:) (as you found out already in your another post ;))
Although if I d
I'm not sure if session invalidation will be carried out if server
stops/crashes. Although I think the session invalidation mechanism is still
the most reliable of all that was proposed (my personal first reaction was
"you can't do it reliably" -- although after reading the thread I have to
agree
As I briefly mentioned before, class aliases are, IMO, a terribly unreliable
thing to maintain. Every time someone comes up with new component that uses
resource reference they must not forget to go and register the alias for it.
I'm predicting a 100% probability that soon enough someone will fo
Thanks for the pointer, I was able to solve my problem with this information.
However I had to roll my own versions of ContextImage and
ContextPathGenerator -- because the ones supplied with Wicket appear to be
hardcoded to use 'src' attribute.
Maybe generic versions that are able to manipulate
He he, that was my old thread there :)
Thing is, I just recently discovered, that encoding resources as arguments
(rather than paths) completely breaks relative URLs discussed there:
http://old.nabble.com/How-to-'resolve'-URL-in-stylesheet--td27720293.html
(for the simple reason that browser stri
Hi,
out of the box Wicket generates urls for packaged resources that
contain fully-qualified class names, e.g.:
Now in accordance with our security policies we are not allowed to
expose internal application details -- and fully qualified class name
certainly fits that category.
On the other han
Hi,
in our application we need to make use of an applet. For the size and
logistics reasons I don't want to package the required applet jars
inside Java packages (that is unlike e.g. images and css that we do
package together with the components).
So, say, I'll package the jars under 'applet' web
*bonks self on the head*
Somehow I never realised that paths in CSS are resolved against CSS itself,
not the HTML page (being a total HTML noob and all it's not that
surprising). Thanks for the pointer Igor, I've been inventing problem where
there's none.
igor.vaynberg wrote:
>
> if you keep
Hi,
I'm wondering if it is possible to 'resolve' URLs in stylesheets so
that they would point to packaged resources? Or at least so that
they'll work regardless of what /context/ path application is using?
Specifically, if I want to use something like in CSS:
background-image: url(/images/corner.
Hi,
we are currently developing our first application with Wicket -- and
naturally we run into some problems/questions :)
One of the' frameworkish' things we've done is to create 'base page'
that we want to be able switch the look & feel (theme) depending on
the settings (e.g. depending on where/
26 matches
Mail list logo
