Hello all,
this question is not directed solely at Wicket, but extends beyond that to web
app architecture and best practices.
I have been working mostly with the open-session-in-view pattern and Wicket's
loadable detachable models backed with Hibernate or similar ORM for my
applications.
Hi all,
I have a datatable and need to make it more accessible for screenreaders.
I am using an AbstractColumn and setting the getHeader and populateItem
methods with the contents.
In a particular row I want to change the markup of the cells from TD to TH,
as they are header type content. Is
Hi,
I'm working on a 'themeable' (does this word exist ?) application were
some string resources differ based on the currently active user's theme.
Since (at least during development) each user can freely switch between
different themes, I need Wicket to not cache these string resources.
I
Hello,
I have added certain custom url mapping and rewriting to show the language
tag in the url before mounted pages, which was working really well during
development mode, however in deployment mode, the application does not start
at all. I get an exception:
Problem accessing /gymwatch/login.
Urbani, Edmund wrote
I don't think I am the only one running into these kinds of issues, so I'd
like
to hear which patterns other developers apply or what they consider best
practices.
Would like to hear the same. I've attempted to work through this in the
most Wicket-way I know how.
The
Hi,
it's a little bit finicky, but it can be done:
DataTable dataTable = new DefaultDataTableContact,
String(table, columns, new SortableContactDataProvider(), 8) {
protected ItemIColumnContact, String newCellItem(final
String id, final int index, final
Hi,
Wicket includes the session's style when generating the cache key*. Why
don't you use this to identify your current 'theme'? Then theme-specific
string resources should work out-of-the-box.
Have fun
Sven
*See Localizer#getCacheKey()
On 18.06.2015 16:39, Tobias Gierke wrote:
Hi,
I'm
Hi,
It looks like a build problem. Maybe you have an older version of
wicket-core.jar in your classpath in production.
The method is definitely there [1]
1.
Also see Localizer#clearCache() [1]
When changing the theme use getApplication().getLocalizer().clearCache()
1.
https://github.com/apache/wicket/blob/edcbd4e849378a5aba9ee2d5e4f954bce904af52/wicket-core/src/main/java/org/apache/wicket/Localizer.java#L90
Martin Grigorov
Freelancer. Available for