I don't think it is a good idea to have multiple applications in one
war. Wicket stores static state in ThreadLocals (Application, Session,
etc.). All apps in the same war share the same ClassLoader and thus the
same static ThreadLocal instances. There might be circumstances when the
state some
I'd like to second Maartens point. Identical releases to Wicket itself
would mean that it always depends on Wicket. Independent releases would
not be possible. Bugs could not be fixed and new features could not be
added without a new Wicket release. This doesn't really make sense to me.
Reinha
This is the proper way to linking to our documentation.
The issue with the code blocks is something I'll take up with infra@
and see if there's something that can be done.
Martijn
On Wed, Aug 12, 2009 at 9:18 AM, Reinhard
Nägele wrote:
I just played around with that a bit. This
I just played around with that a bit. This seems to be a Confluence
problem. If you open the URL
http://cwiki.apache.org/WICKET/dropdownchoice-examples.html, you get
small text areas without proper styling. If you then edit the page and
cancel editing again, you are redirected to
http://cwiki.
You need to wait until your executor thread has finished. Then it might
work.
Future f = Executors.newSingleThreadExecutor().submit(new Runnable() {
@Override
public void run() {
try {
wb.write(out);
} catch (IOException e) {
MarkupUtils.handleUnexpected
How about this:
ByteArrayOutputStream baos = new ByteArrayOutputStream();
wb.write(baos);
InputStream is = new ByteArrayInputStream(baos.toByteArray());
Martin Makundi schrieb:
Hi!
I have a HSSF document which can be written to an output stream.
However, I want to stream it to the website vis
The same thing happened to me recently. I wanted to check out the
release tag and could not find it. I was already sort of surprised when
Igor mentioned he'd release from his private sandbox.
And now we have a 1.4.0 tag with a 1.4-SNAPSHOT in it and trunk which
still has 1.4-SNAPSHOT. That can
If you use slf4j 1.5.3 or newer, serialization should just work fine.
See http://www.slf4j.org/faq.html#declared_static
Reinhard
Jeremy Thomerson schrieb:
Your logger instances should either be transient or static - so that
they are not serialized.
--
Jeremy Thomerson
http://www.wickettraini
Given the fact that there is already wicket-jquery in wicketstoff-core,
I wonder how come it is simply possible to add another JQuery
integration to wicketstuff. What are the rules for adding stuff there?
Can committers just do whatever the like? Doesn't there have to be some
voting on the mail
