The first workaround we ended up using was something like:
public class SafeWicketFilter extends WicketFilter {
private boolean
initWasAlreadyCalledSoYouShouldNotDoThisYouStupidGlassfish = false;
@Override
public void init(FilterConfig filterConfig) throws
Thanks for sharing this information Attila!
The folks at Glassfish suggested I use URIs as well.
I created WICKET-3867 to change URLs to URIs.
On 04/07/2011 1:48 AM, Attila Király wrote:
Using java.net.URL in Set-s and Map-s is a no-no. Wicket should use
java.net.URI instead. See [1] for an
Hi,
On Sun, Jul 3, 2011 at 12:35 AM, Bertrand Guay-Paquet
ber...@step.polymtl.ca wrote:
Thanks for your answer Harald. I had taken a look at that bug as well, but
this is not my case. I don't even have to access a web page to see the
initialization problem.
Filter.init() is called at deploy
Hi Martin,
I wanted to make my message shorter, but I should have posted the whole
thing to avoid the confusion. You are right that a set is returned and
not a list of course. However, here is what is actually returned by the
method:
Hi,
This behavior explains the problem.
Since when you face this problem ? I remember tickets from you since
at least Wicket 1.5-RC1. Did you upgrade to newer version of Glassfish
or did you introduce .ear/lib recently ?
On Sun, Jul 3, 2011 at 6:47 PM, Bertrand Guay-Paquet
ber...@step.polymtl.ca
Hi,
I have very recently transitioned from Embedded Jetty (single WAR) to
Java EE 6 and EAR-based deployment (Glassfish v3.1). I started being
able to see actual Wicket pages with EJB beans late last week and I only
tried deploying my application on Glassfish.
Since this is a new project,
I created an issue with Glassfish:
http://java.net/jira/browse/GLASSFISH-16942
Here is a workaround I use in the meantime :
public class CustomClassResolver implements IClassResolver {
private DefaultClassResolver classResolver = new
DefaultClassResolver();
@Override
public Class?
Using java.net.URL in Set-s and Map-s is a no-no. Wicket should use
java.net.URI instead. See [1] for an example.
Attila
[1] More Joy of Sets example with URL from Google Tech Talks:
http://www.youtube.com/watch?v=wDN_EYUvUq0#t=9m58s
2011/7/3 Bertrand Guay-Paquet ber...@step.polymtl.ca
When
Thanks for your answer Harald. I had taken a look at that bug as well,
but this is not my case. I don't even have to access a web page to see
the initialization problem.
Wicket logs show the following on startup:
INFO: init: DevUtils DebugBar Initializer
INFO: init: DevUtils DebugBar
Hello,
I am deploying a Wicket 1.5 application inside an EAR on Glassfish 3.1.
I noticed that the debug bar was doubled at the top of the browser
window (2 full debug bars). After investigation, the problem is that
WicketFIlter.init() is being called twice each time I start the server.
This
Am 01.07.2011 18:30, schrieb Bertrand Guay-Paquet:
Hello,
I am deploying a Wicket 1.5 application inside an EAR on Glassfish 3.1.
I noticed that the debug bar was doubled at the top of the browser
window (2 full debug bars). After investigation, the problem is that
WicketFIlter.init() is being
11 matches
Mail list logo
