So, I've started to figure out which of our components tries to access our
Model in #onInitialize. It ended up that almost every component does. This
means, that I have to re-write all these components which might be very time
consuming. I'm wondering why a request with a redirect has to
It is necessary to detect whether a page is stateful before redirecting
to it.
Sven
On 07/15/2013 10:53 AM, Dirk Forchel wrote:
So, I've started to figure out which of our components tries to access our
Model in #onInitialize. It ended up that almost every component does. This
means, that I
So one of your components tries to access its model in #onInitialize(),
which now may be called *after* #onRequestHandlerExecuted() was called.
Try to move this logic into #onConfigure().
Sven
On 07/12/2013 06:34 AM, Dirk Forchel wrote:
We've added a TransactionRequestCycleListener (extends
We've added a TransactionRequestCycleListener (extends
AbstractRequestCycleListener). This class handles transactions mainly like
this:
@Override
public void onRequestHandlerResolved(final RequestCycle cycle, final
IRequestHandler handler)
{
LOGGER.debug( start transaction --- +
How does your application handle transactions?
What does org.foo.model.Model#currentTransaction() look like?
Sven
On 07/10/2013 06:46 AM, Dirk Forchel wrote:
Unfortunately not. It's not that easy to create a quickstart without using
all the additional stuff we're currently using. I think of
I've a question regarding this issue
https://issues.apache.org/jira/browse/WICKET-5083 and
Commit:34f43642195058f375d161dbb7cec58b40711423. This commit changed the
behavior of our application (I used git:bisect to pinpoint the changes
made). From this revision on, our application does not behave
Hi Dirk,
initialization may now be triggered when asking a page for
#isPageStateless(), this is done to be sure to catch stateful components
added lately in #onInitialize().
RequestAdapter#commitRequest() detaches the page first before testing
statefulness:
try
To be honest, I'm a bit confused. I reckon this has to do with the redirect
from http://localhost:8080/ to http://localhost:8080/de/home. If I call de
URL http://localhost:8080/de/home directly all works as expected and no
exception is thrown. By the way my Home page is stateless and bookmarkable.
Can you create a quickstart so we can address this confusion?
Sven
On 07/09/2013 01:33 PM, Dirk Forchel wrote:
To be honest, I'm a bit confused. I reckon this has to do with the redirect
from http://localhost:8080/ to http://localhost:8080/de/home. If I call de
URL
Unfortunately not. It's not that easy to create a quickstart without using
all the additional stuff we're currently using. I think of our persistence
framework etc.
--
View this message in context:
10 matches
Mail list logo
