+1 for M2 and a final release as soon as possible.
I also have no plans of adding anything to Wicket 10 before the release.
I would have deployed M1 to production already if my Jakarta migration
wasn't blocked by performance issues in Hibernate 6 ,)
Best,
Thomas
On Mon, Sep 11, 2023 at 3:30
We've been using Martin's solution with JQueryFileUpload for years and it
works great.
Best,
Thomas
On Mon, Jul 6, 2020 at 8:59 AM Maxim Solodovnik
wrote:
> Thanks a million :))
>
> On Mon, 6 Jul 2020 at 13:43, Martin Grigorov wrote:
>
> > On Sun, Jul 5, 2020 at 9:16 PM Sven Meier wrote:
>
Hi all,
I created two more tickets for potential improvements that showed up during
profiling:
- https://issues.apache.org/jira/projects/WICKET/issues/WICKET-6776
- https://issues.apache.org/jira/projects/WICKET/issues/WICKET-6780
Both are not urgent, because I was able to override the
Hi,
There are two options I'm aware of:
- You can use a session manager in your application server that stores your
session in the database. I.e. Tomcat's JDBC store.
- You can use Spring Session with a JDBC store
I recently implemented Spring Session for Wicket with Redis as a backing
store.
u, Apr 16, 2020 at 1:41 PM Thomas Heigl wrote:
>
> > Thanks Sven!
> >
> > I think the solution is good enough for now.
> >
> > Would it be possible to do a 9.0.0-M5.1 release for this? If so, I would
> > give it another try on production.
> >
>
&
e fun
> Sven
>
>
> On 12.04.20 20:41, Thomas Heigl wrote:
> > Hi Sven,
> >
> > I was thinking about this as well.
> >
> > SoftReferences worked well in my application. G1GC seems to start to
> evict
> > them when -XX:InitiatingHeapOccupancyPe
ructor which is a bad practice by
> itself, but this is the simplest solution.)
>
> What do you think?
>
> Sven
>
>
> On 12.04.20 10:34, Thomas Heigl wrote:
> > Hi Sven,
> >
> > That's good to hear! Please let me know when you have an implementati
implementation had so many special concepts and
> solutions, it's easy to miss one.
>
> A soft reference feature can easily be added/restored. I'm already
> checking where it fits best.
>
> Thanks for your thorough testing.
>
> Best regards
> Sven
>
>
>
rov
wrote:
> On Fri, Apr 10, 2020 at 4:01 PM Thomas Heigl wrote:
>
> > FYI: I deployed Wicket 9.0.0-M5 to production an hour ago. 100k requests
> > served and no issues so far.
> >
>
> Awesome!
> Thank you for testing it!
>
>
> >
> > Great work!
>
>
> > On Wed, 8 Apr 2020 at 15:41, Maxim Solodovnik
> wrote:
> >> OK
> >>
> >> Will start new release process in couple of hours
> >> Please stop me if you will find any blocker :)
> >>
> >> On Wed, 8 Apr 2020 at 14:36, Thomas Heigl wro
Hi Maxim,
It works for me now!
Thomas
On Wed, Apr 8, 2020 at 9:17 AM Maxim Solodovnik
wrote:
> Thanks a million!
>
> On Wed, 8 Apr 2020 at 14:10, Thomas Heigl wrote:
> >
> > Hi Maxim,
> >
> > I'm testing against the snapshot now. Will get back to you short
ase
> Could you please tell when can I start?
>
> On Wed, 8 Apr 2020 at 07:01, Maxim Solodovnik
> wrote:
> >
> > Hello Thomas,
> >
> > Please test M6-SNAPSHOT (so I don't have to release M5.2 :))))
> >
> > On Wed, 8 Apr 2020 at 02:39, Thomas Heigl wrote
Hi Maxim,
That would be great. I want to do some more extensive testing and then
deploy M5 into production. ;)
Thomas
On Tue, Apr 7, 2020 at 7:50 PM Maxim Solodovnik
wrote:
> I can pack another release
> later this week ...
>
> On Wed, 8 Apr 2020 at 00:48, Thomas Heigl wrote:
&g
n
> wicket-core.
>
> And SessionQuotaManagingDataStore$DelegatedPage must be serializable of
> course.
>
> I've pushed changes to wicketstuff master.
>
> Thanks
> Sven
>
>
> On 07.04.20 14:14, Thomas Heigl wrote:
> > And one more thing. There is now a
And one more thing. There is now a warning logged just before serialization:
WARN o.a.w.pageStore.AsynchronousPageStore: Delegated page store
> 'org.apache.wicket.pageStore.SerializingPageStore' can not be asynchronous
On Tue, Apr 7, 2020 at 2:09 PM Thomas Heigl wrote:
> The
The cause is the following MetaData entry in the session:
class
> org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$1=org.wicketstuff.datastores.common.SessionQuotaManagingDataStore$SizeLimitedData@4090594a
On Tue, Apr 7, 2020 at 1:59 PM Thomas Heigl wrote:
> Hi Sven,
>
dataStore) {
> final ISerializer pageSerializer = getFrameworkSettings().getSerializer();
> return new PerSessionPageStore(pageSerializer, dataStore,
> MAX_PAGES_CACHED_PER_SESSION);
> }
> protected IDataStore newDataStore() {
> final RedissonRedisCache redisCache = new
> Re
Hi Vit,
I'm using a utility class to encapsulate these use cases:
/** Utility class for interacting with {@link AjaxRequestTarget}s */
> public final class AjaxTarget {
> private AjaxTarget() {
> // utility class
> }
> /**
> * Checks if there is an active {@link AjaxRequestTarget}
> *
> *
Meier wrote:
> > Hi Thomas,
> >
> > I thought I covered that usecase, but I will have to take a look.
> >
> > Thanks for testing Wicket 9
> > Sven
> >
> > On 25.03.20 20:10, Thomas Heigl wrote:
> >> Maybe the same approach could be used
o construct the
> key.
>
> MetaData would do the job as well, but I'd prefer to not add more
> functionality unless really needed.
>
> Regards,
> Martin
>
> On Wed, Mar 25, 2020 at 6:30 PM Thomas Heigl wrote:
>
> > Hi all,
> >
> > I'd like to add metadata
Maybe the same approach could be used as for InSessionPageStore that can be
used as cache and a store:
https://github.com/apache/wicket/commit/894799e01227781be76886b2d1cdb2a424c812e0
On Wed, Mar 25, 2020 at 6:35 PM Thomas Heigl wrote:
> Hi all,
>
> I just merged our master in our
Hi all,
I just merged our master in our Wicket 9 branch and I ran into an issue:
Our current configuration with Wicket 8 looks like this:
PageStore = PerSessionPageStore
DataStore = RedisDataStore
So the page store keeps the last couple of pages of a session in memory and
Redis is used as a
Hi all,
I'd like to add metadata to websocket connections. For instance, which
events or channels a connection is subscribed to.
What do you think about adding MetaDataEntry[] metaData to connections
and setMetaData/getMetaData to IWebSocketConnection?
Best regards,
Thomas
, Feb 28, 2020 at 1:27 PM Thomas Heigl wrote:
> Hi Martin,
>
> I created https://github.com/apache/wicket/pull/411 with my suggested
> changes. Feedback would be greatly appreciated ;)
>
> Best regards,
>
> Thomas
>
> On Fri, Feb 28, 2020 at 10:14 AM Martin Grigorov
Hi all,
I created a ticket (https://issues.apache.org/jira/browse/WICKET-6761) and
a PR (https://github.com/apache/wicket/pull/417) for this.
Best,
Thomas
On Fri, Mar 20, 2020 at 12:14 PM Thomas Heigl wrote:
> Hi all,
>
> I'm currently implementing native websockets for my applica
Hi all,
I'm currently implementing native websockets for my application. I'm using
`WebSocketResource` because I don't need access to the page and do not want
my page to lock on websocket messages.
Everything works, but I encountered one issue: It is not possible to
support websocket connections
Hi Martin,
I created https://github.com/apache/wicket/pull/411 with my suggested
changes. Feedback would be greatly appreciated ;)
Best regards,
Thomas
On Fri, Feb 28, 2020 at 10:14 AM Martin Grigorov
wrote:
> On Thu, Feb 27, 2020 at 3:58 PM Thomas Heigl wrote:
>
> &g
h have been modified, i.e. their
> #setAttibute() has been called.
> In cluster mode there will be one HttpSession per server node, respectfully
> one Wicket Session instance per node, and one PageAccessSynchronizer per
> session per node.
> Using Wicket or not if you don't use sticky sessions
I created https://issues.apache.org/jira/projects/WICKET/issues/WICKET-6751
Feedback would be very welcome.
Best regards,
Thomas
On Thu, Feb 27, 2020 at 10:08 AM Thomas Heigl wrote:
> Hi all,
>
> I can confirm that my analysis was correct. I implemented a quic
, and unlockAllPages. The default lock manager
could hold the session-scoped locks collection and custom implementations
could provide their own locking mechanism.
I will create a JIRA issue for this.
Best regards,
Thomas
On Wed, Feb 26, 2020 at 8:17 PM Thomas Heigl wrote:
> Hi Sven,
>
> Thanks for
chronously serialized while another request is already coming in.
>
> Or maybe it is something different.
> Could you create a quickstart?
>
> Sven
>
> Am 25. Februar 2020 22:12:46 MEZ schrieb Thomas Heigl >:
> >Hi again,
> >
> >I
in the session?
Best,
Thomas
On Tue, Feb 25, 2020 at 8:25 PM Thomas Heigl wrote:
> Hi all,
>
> I'm currently experimenting with PerSessionPageStore as a second-level
> cache. We are moving our page store from memory (i.e. session) to Redis and
> keeping 1-2 pages per session in memory
Hi all,
I'm currently experimenting with PerSessionPageStore as a second-level
cache. We are moving our page store from memory (i.e. session) to Redis and
keeping 1-2 pages per session in memory speeds up ajax requests quite a bit
because network roundtrips and (de)serialization can be skipped
>
> Would you mind to elaborate on this a bit? What do you do in your forms?
> How do you handle state there? Do you use view models that are
> serializable? Do you keep state in local variables and propagate it to the
> domain object in every request after it is reloaded?
Sure.
We use
f that you
> didn't want/notice is being serialized... Perhaps we are doing something
> wrong...
>
>
> On Sun, Aug 4, 2019 at 11:35 AM Thomas Heigl wrote:
>
> > Hi Marios,
> >
> > I don't think there is a way to disable this behaviour but you have other
> >
d it hard to decide
> which of these could be extracted into a stand-alone component (e.g.
> resolving properties from the parents model.
>
> My question: Why don't you use a Panel instead, using different markup
> based on some condition?
>
> Have fun
> Sven
>
>
> On 27.0
Hi Marios,
I don't think there is a way to disable this behaviour but you have other
options:
- If you use IntelliJ, you can configure the "Local variable or parameter
can be final" inspection to raise an error instead of a warning (for
variables that are implicitly final)
- Checkstyle or
ner and adjust it for
my project but it contains a lot of logic that has to be duplicated like
message interpolation and markup stream parsing.
I'd be willing to provide a PR if someone in the development team has any
suggestions on how to approach this.
Best,
Thomas
On Thu, Jul 25, 2019 at
Can you show an example of solution now vs. solution after change, what are
> the benefits of such visibility change to your case? Maybe there is another
> way to accomplish your goal?
>
> **
> Martin
>
> ke 24. heinäk. 2019 klo 22.25 Thomas Heigl (tho...@umschalt.com)
> kirjoitti:
&
Hi all,
I'd like to create Wicket messages with child components programatically.
Currently, this is only possible by using the tag and
nesting components inside of it.
For most use cases this is sufficient, but I sometimes come across cases
where I'd like to programatically define the message
Or was the original version of `GaePageManagerProvider` with 2 sessions
stores actually correct with the first one acting as a non-serialized cache?
Best,
Thomas
On Tue, Apr 23, 2019 at 9:57 PM Thomas Heigl wrote:
> Hi Sven,
>
> This works, but now we do not have any in-memory cach
overrides.
Best,
Thomas
On Tue, Apr 23, 2019 at 8:39 PM Sven Meier wrote:
> Hi Thomas,
>
> you're right, I've changed it to single InSessionStore.
>
> Have fun
> Sven
>
> Am 23.04.19 um 09:06 schrieb Thomas Heigl:
> > Hi Sven,
> >
> > Thanks
Hi Sven,
I have some types of ajax behavior callback (timers, lazy-loading) that do
not really touch the page and I want to avoid serialization.
It's basically the same use case as the original ticket:
https://issues.apache.org/jira/browse/WICKET-5933
It would be great if we had some mechanism
vider.java
>
> Have fun
> Sven
>
>
> Am 22.04.19 um 18:47 schrieb Thomas Heigl:
> > Hi all,
> >
> > I just experimentally upgraded my application to 9.0.0-M1. Most things
> are
> > straight forward, but I'm struggling with replicating my current page
>
Hi all,
What is the equivalent of the following line in Wicket 9?
Session.get().getPageManager().untouch(content.getPage())
There is only `removePage` now, but it doesn't do the same thing as far as
I can see. Is it still possible to untouch pages in ajax requests so they
won't be serialized
Hi all,
I just experimentally upgraded my application to 9.0.0-M1. Most things are
straight forward, but I'm struggling with replicating my current page
manager configuration using the new API.
My current configuration for Wicket 8 looks like this:
setPageManagerProvider(new
added my src/main/resources folder to
> extraClassPath as you did.
>
> Maybe something missing in my WicketApplications' settings?
>
> Thanks for your support.
> Regards.
>
> On 2018/07/13 16:50:16, Thomas Heigl wrote:
> > Hi Francesco,
> >
> > I faced the sa
Hi Francesco,
I faced the same situation last week.
I wrote a Wicket plugin that clears the Localizer cache. It does not clear
the resource bundle cache because I use Spring's ReloadableResourceBundle,
but that should be very easy to add.
Configuration is a little more difficult than with
Hi Maxim,
Created https://issues.apache.org/jira/browse/WICKET-6560.
Thomas
On Sat, Jun 9, 2018 at 5:44 AM, Maxim Solodovnik
wrote:
> Sounds like these 2 comments worth JIRA
> Or Jira+PR ;))
>
> On Thu, Jun 7, 2018 at 9:45 PM, Thomas Heigl wrote:
> > Also the warning i
anceof Serializable == false)
Best,
Thomas
On Thu, Jun 7, 2018 at 4:25 PM, Thomas Heigl wrote:
> Hi all,
>
> After porting our app to Wicket 8, I'm getting these warnings on my test
> environment:
>
> WAR o.a.w.model.ChainingModel It is not a good idea to reference a
>
Hi all,
After porting our app to Wicket 8, I'm getting these warnings on my test
environment:
WAR o.a.w.model.ChainingModel It is not a good idea to reference a
> non-serializable instance in models directly as it may lead to
> serialization problems
The warning is OK, but it gives me
've fixed the problem. The setup currently used is discouraged and broken
> in
> m2e, but I don't feel like restructuring the whole thing to get rid of
> this
> test-jar.
>
> Emond
>
> On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote:
> > The culprit is:
>
The culprit is:
https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868b940d9be3a
On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl wrote:
> `mvn clean install` fails for me because no test-jar is built for the core
> module:
>
> [INFO] WiQuery Parent
gaaij wrote:
> Hi Thomas,
>
> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT. I
> did
> not do a release, as I cannot push to central. If you want to run your
> tests
> on some CI server, you probably have to push the artifacts to a local repo
> also.
&
? For now you can use a snapshot build. It works, but the UI API
> might
> > change a bit before the 8.0 release.
> >
> > Best regards,
> > Emond Papegaaij
> >
> > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl :
> > > Hi Ernesto,
> > >
> >
Great! Thanks Martin!
On Fri, Jun 1, 2018 at 5:44 PM, Martin Grigorov
wrote:
> On Fri, Jun 1, 2018, 18:35 Thomas Heigl wrote:
>
> > Hi Ernesto,
> >
> > I'm not sure how many people are still using it. But as I said, my
> project
> > heavily depends on it.
&g
, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
reier...@gmail.com> wrote:
> Hi,
>
> I do not know who is actually using this project. I use to contribute to it
> a few years ago. I haven't used it for ages..
>
> On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl wrote:
>
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could somebody
please cut a release of WiQuery compatible with the new version?
Our application still heavily relies on WiQuery and we can't move to Wicket
8 without it.
Best,
Thomas
gt;not sure whether that will work for you though, without understanding
> >why you called that internal API at all.
> >
> >Best regards
> >Sven
> >
> >Gesendet mit Blue
> >
> >Am 19. Feb. 2018, 11:22, um 11:22, Thomas Heigl <tho...@umschalt.com&
Hi all,
I upgraded my application from M8 to M9 yesterday and encountered 3 issues:
1. Current WiQuery version is not compatible with M9
It still depends on WicketEventJQueryResourceReference. It would be great
if someone could cut a milestone release for WiQuery as well, so I can do
further
?
On Thu, Jan 12, 2017 at 6:48 PM, Thomas Heigl <tho...@umschalt.com> wrote:
> Hi Martin,
>
> Yes, I tried that, but what happens is this:
>
> When a user clicks on the an an Ajax link on a page that is not in the
> application cache, the whole page gets refreshed
go...@apache.org>
wrote:
> Hi,
>
> You can setup a no-op IPageStore.
> This way there won't be a call to ISerializer#serialize(Object) at all.
>
> Martin Grigorov
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Jan 12, 2017 at 11:53 AM
I forgot to add:
We are using the HTML5 History API to push state to the (bookmarkable) URL,
so a page can be re-created with *all* state from the URL alone.
Thomas
On Thu, Jan 12, 2017 at 11:47 AM, Thomas Heigl <tho...@umschalt.com> wrote:
> Hi all,
>
> I'm looking for a so
Hi all,
I'm looking for a solution to avoid serialization of bookmarkable pages.
These are yesterday's metrics from an instrumented version of
Fast2WicketSerializer:
"WicketSerializer.deserialize" : {
> "count" : 4084,
> "max" : 0.0308421623,
> "mean" : 0.005861568417930906,
>
, Martin Grigorov <mgrigo...@apache.org>
wrote:
> Hi,
>
> On Mon, Mar 28, 2016 at 2:17 PM, Thomas Heigl <tho...@umschalt.com> wrote:
>
> > Hi all,
> >
> > I just finished upgrading a larger application from Wicket 6.21.0 to
> Wicket
> > 7.2.0. I enc
uff-core-6.21.0...wicketstuff-core-6.22.0
but there isn't anything related to serializer-fast except for the FST
dependency upgrade. I'll do some more investigating.
Best regards,
Thomas
On Mon, Mar 28, 2016 at 2:26 PM, Martin Grigorov <mgrigo...@apache.org>
wrote:
> Hi,
>
> O
Hi all,
I just finished upgrading a larger application from Wicket 6.21.0 to Wicket
7.2.0. I encountered 3 issues that more or less prevent me from pushing it
into production:
1. There seems to be an issue with whose children are
added during onConfigure and stateless checking.
Stateless
Hey all,
Recenty, probably after moving to Wicket 6.16, we see some strange behavior
for TextAreas.
We have been using a JavaScript library to limit the number of characters a
user can enter in a textbox for years. Now we started getting validation
exceptions on the server that the user entered
+1
We're also seeing these sporadically and a custom exception would help a
lot.
Thomas
On Jul 7, 2014 10:12 AM, Martin Grigorov mgrigo...@apache.org wrote:
Please create a ticket!
With a patch with the custom exception will make its processing even
faster!
Thank you!
Martin Grigorov
Hey all,
I just tried to upgrade to Wicket 6.13.0 because of the new JQuery version
packaged with it. It breaks some of our resource mounting functionality
that has been working since 1.4x and some package resources cannot be found
anymore. Have there been changes to resource mounting in this
it could be null.
Martin Grigorov
Wicket Training and Consulting
On Mon, Jan 13, 2014 at 3:02 PM, Thomas Heigl tho...@umschalt.com
wrote:
Hey all,
I just tried to upgrade to Wicket 6.13.0 because of the new JQuery
version
packaged with it. It breaks some of our resource mounting
Hey all,
After upgrading to Wicket 6.9.0 our ajax file upload started stalling and
on some machines even crashing IE8. Downgrading to 6.8.0 immediately fixed
the problem.
I verified that the issue is not related to the new jQuery version by
downgrading to Wicket 6.8.0 but setting the jQuery
, 2013 at 2:30 PM, Thomas Heigl tho...@umschalt.com wrote:
Hey all,
After upgrading to Wicket 6.9.0 our ajax file upload started stalling and
on some machines even crashing IE8. Downgrading to 6.8.0 immediately
fixed
the problem.
I verified that the issue is not related to the new jQuery
:
Please pack this code in a quickstart and attach it to a ticket.
What do you mean by crash exactly ? Does the process end with segfault or
what ?
On Tue, Jul 23, 2013 at 4:08 PM, Thomas Heigl tho...@umschalt.com wrote:
Hey Martin,
The example works fine.
I just tried to narrow
See https://issues.apache.org/jira/browse/WICKET-5283
On Tue, Jul 23, 2013 at 3:12 PM, Thomas Heigl tho...@umschalt.com wrote:
Please pack this code in a quickstart and attach it to a ticket.
I'll do that.
What do you mean by crash exactly ? Does the process end with segfault or
what
and so on).
Do you know https://github.com/scottjehl/Respond?
best,
Michael
Am 17.06.2013 um 17:30 schrieb Thomas Heigl tho...@umschalt.com:
Hey Michael,
but isn't it enough to send the correct cache headers + a calculated
filename that contains the hash of file?
I actually have
Hi all,
I was wondering if Wicket has a built-in mechanism for caching the
generated byte[] of package resources. I use concatenated resource bundles
that are compressed using the YUI CSS/JS compressors.
Using the default settings, compression is performed for every request that
does not have it
MessageDigestResourceVersion());
}
best,
Michael
Am 17.06.2013 um 15:21 schrieb Thomas Heigl tho...@umschalt.com:
Hi all,
I was wondering if Wicket has a built-in mechanism for caching the
generated byte[] of package resources. I use concatenated resource
bundles
that are compressed using
of the
application
resourceVersion = new CachingResourceVersion(new
MessageDigestResourceVersion());
}
best,
Michael
Am 17.06.2013 um 15:21 schrieb Thomas Heigl tho...@umschalt.com:
Hi all,
I was wondering if Wicket has a built-in mechanism for caching the
generated byte
Hey Guys,
Yesterday I upgraded our 6.6.0 app to 6.7.0 and my CI build broke
immediately with OOM (Heap Space) exceptions while running our
integration/smoke test suite. The suite renders all pages in the
application using WicketTester and uses the full Spring application context.
I tried
Hey Guys,
Thanks a lot for sharing your ideas. Maybe together we can find a smooth
way to integrate the two ;)
My plan for now is to create an abstract wicket page for angular apps that
renders basic HTML structure including menus, footers, meta tags etc. This
page also adds the basic angular JS
Java/Wicket stack. At least
that's my theory ;)
Thomas
On Wed, Feb 27, 2013 at 11:35 AM, Ernesto Reinaldo Barreiro
reier...@gmail.com wrote:
Hi Thomas,
We just posted at the same time:-)
On Wed, Feb 27, 2013 at 11:19 AM, Thomas Heigl tho...@umschalt.com
wrote:
Hey Guys,
Thanks a lot
Hey all,
I recently started a new project based on our existing Wicket
infrastructure. This infrastructure handles typical web application
requirements like registration, signup, authentication, user management
functionality and is very solid.
One of the main requirements of the new site we are
Hey Sekib,
Thanks a lot for your input!
In case anybody has a similar problem, I ended up solving it through an
AjaxCallListener with a little workaround. If the user confirms the alert,
I re-trigger a click on the link with additional data and check for that in
my precondition. This can be used
Hey All,
I noticed that setRequired(true) on ListMultipleChoice does not have an
effect anymore after upgrading to Wicket 6 from Wicket 1.5.7.
I think it might be a problem with the ajax library because the AJAX post
request looks like this (where 'tags' is my select multiple / field)
tags:null
Hey all,
I'm currently in the progress of migrating a largish Wicket 1.5 app to
Wicket 6.2. The only major problem I could not resolve so far are
precondition scripts with user input.
My old code looked like this:
@Override
public CharSequence postDecorateScript(Component component,
Hi Sam,
I wrote a custom MountedMapper for the project I'm currently working on.
All it does, is not rendering the page version info for pages. For all
other components it is still turned on. IMHO this mimics the pre-1.5
behavior. We've been using it in production for quite a while now and it
);
if (submittingComponent != null) {
submittingComponent.onSubmit();
}
break;
}
}
Cheers,
Thomas
On Wed, May 9, 2012 at 3:07 PM, Thomas Heigl tho...@umschalt.com wrote:
Hey Martin,
WICKET-3705 links to https://issues.apache.org/jira/browse/WICKET-1894
which says that this order
Hello,
Since Wicket 1.5.6, the UrlRender generates all URLs prefixed with ./
when using RequestCycle.get().urlFor(pageClass). The Problem is that for my
application's homepage the generated URL is ./. which does not really
make sense.
Is there any reason for doing this? What caused the change to
.
Before 1.5.6: some/relative/url
After 1.5.6: ./somerelative/url
Both are the same. The reason is
https://issues.apache.org/jira/browse/WICKET-4260
How exactly the home page is broken ? Do you have custom RequestMapper
for the home page ?
On Wed, May 9, 2012 at 11:56 AM, Thomas Heigl tho
I had the same problem. I solved it by using the transparent container as
markup provider for the fragment:
add(new MyFragment(fragmentId, getTransparentBodyContainer()))
It works, but is kind of awkward, as subclasses shouldn't really know about
transparent containers in the base class.
Thomas
Hello,
I notices a strange behavior after upgrading to Wicket 1.5. Nested forms
are submitted in a different order.
I have structures like this:
- Compound Form
-- Subform 1
-- Subform 2
-- Subform 3
- Submit Link/Button for Compound Form
In Wicket 1.4 the order of calls to onSubmit was
:24 PM, Martin Grigorov mgrigo...@apache.orgwrote:
On Wed, May 9, 2012 at 2:22 PM, Martin Grigorov mgrigo...@apache.org
wrote:
Hi Thomas,
On Wed, May 9, 2012 at 2:12 PM, Thomas Heigl tho...@umschalt.com
wrote:
Hello,
I notices a strange behavior after upgrading to Wicket 1.5. Nested
Hello,
I'm currently in the process of migrating a largish Wicket 1.4 application
to 1.5. When moving from 1.5.5 to 1.5.6 something related to feedback
messages breaks.
On all my stateless pages, feedback messages are not rendered anymore when
using:
@Override
protected void
Hey all,
I have a requirement where I'd like to create a Wicket Session outside of a
Wicket request:
My application runs stand-alone (no problem here) and as a Facebook
application. Facebook calls my REST authentication service with a user's
credentials if they open my application in facebook.
, David Berkman david.berk...@glu.comwrote:
Apache Shiro, and create a shiro version of WebSession. Then wicket can
ask for the Shio Session from the Http context, and you can get it
outside the context.
David
-Original Message-
From: Thomas Heigl [mailto:tho...@umschalt.com]
Sent
String[codeList.size()];
codeList.toArray(codes);
return new Roles(codes);
}
return NO_ROLES;
}
@Override
public void signOut () {
SecurityUtils.getSubject().logout();
super.signOut();
}
}
-Original Message-
From: Thomas Heigl [mailto:tho
Hey all,
I've just been investigating some performance problems indicated by Page
Speed. It reported that some of my resources did not send far future expiry
headers, although my default expiry and my expiry for all resources is set
to one year.
After some debugging, I found out that Wicket
upgrading.
You can always override headers set by Wicket by introducing your own
servlet filter which wraps WicketFilter and resets the headers after
WicketFilter returns, i.e. chain.doFilter() call in your filter.
On Mon, Sep 5, 2011 at 5:42 PM, Thomas Heigl tho...@umschalt.com wrote:
Hey all
99 matches
Mail list logo
