Bingo!Thank you a lot. - PaoloOn 7/4/06, smallufo [EMAIL PROTECTED] wrote:
Eclipse 3.2Project - Properties - Java Compiler - Building - Enable projectspecific settings - Output folder - Filtered Resourcesremove *.htmldone!
Using Tomcat but need to do more? Need to support web services, security?
You get the error because you are using CompoundPropertyModel and has
the security manager in tomcat turned on.
CompoundPropertyModel uses introspection to set / get properties and for
doing that, it needs to run with permission
java.lang.reflect.ReflectPermission suppressAccessChecks
You can
Thank you very much, Johan. I failed to mention that I'm still on
Wicket-1.1.1. Is there a way to do this with
Wicket-1.1.1?
- Johannes
Johan Compagner wrote:
remote address can be get from the http request (of the WebRequest
from the RequestCycle)
The snoop servlet does this
yes just get the real http request (just cast the wicket.Request to WebRequest and get the HttpRequest from it)On 7/5/06, Johannes Fahrenkrug
[EMAIL PROTECTED] wrote:Thank you very much, Johan. I failed to mention that I'm still on
Wicket-1.1.1. Is there a way to do this withWicket-1.1.1?-
Johan,
thanks a lot. For anyone who was following this, here's how I'm getting
the IP of the client now:
HttpServletRequest httpRequest =
((ServletWebRequest)getRequest()).getHttpServletRequest();
System.out.println(httpRequest.getRemoteAddr());
- Johannes
Johan Compagner wrote:
yes
this is from RequestCycle:
private final void processEventsAndRespond()
{
// Use any synchronization lock provided by the target
Object lock = getRequestTarget().getLock(this);
if (lock != null)
{
Ittay Dror wrote:
this is from RequestCycle:
private final void processEventsAndRespond()
{
// Use any synchronization lock provided by the target
Object lock = getRequestTarget().getLock(this);
if (lock != null)
{
thanks for the quick response.
is there any way around it? what happens if i don't lock?
Matej Knopp wrote:
Ittay Dror wrote:
this is from RequestCycle:
private final void processEventsAndRespond()
{
// Use any synchronization lock provided by the target
I'm testing an app I just finished and is currently running on JBoss
on Sun's Glassfish (SJAS 9.0) to test compatibility and see if it's a
viable option going forward w/ our enterprise efforts.
I seem to be having an issue w/ storing objects in session. Wicket
runs fine until I utilize the
Caused by: java.io.NotSerializableException:com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegateat java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075)
looks like a bug in sun's impl of ejbs?-IgorOn 7/5/06, Vincent Jenks [EMAIL PROTECTED]
wrote:I'm testing an app I
I am using the RadioChoice class in Wicket 1.2
import wicket.markup.html.form.*;
RadioChoice radio = new RadioChoice(choice);
ListString choices = new ArrayListString();
choices.add(a);
choices.add(b);
choices.add(c);
radio.setModel(new
You could just set the option in your model.
Jeremy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean
Sullivan
Sent: Wednesday, July 05, 2006 2:31 PM
To: wicket-user@lists.sourceforge.net
Subject: [Wicket-user] RadioChoice, default selection
I am
I need some help with the following scenario.I have a form and when a user is halfway through it, there is a button which leads to another page. The user enters values in that second page and then goes back to the first one. The user should be allowed to continue entering values and the original
I don't know, I would believe that if I weren't able to make a
Stateful bean and use it exactly how I did in Wicket, outside of this
project.
I setup a test project and their stateful/stateless beans work
flawlessly when tested against JSP/Servletsthe problem arises w/
Wicket + SFSB on
well, the problem might be that it is serialized by wicket itself.
this is done because you have the logger set to debug to help identify
things you put into session that might not be serializable. maybe the
container doesnt serialize the same way so when the container does it
its not a problem,
That's kind of what I was thinking...and afraid of myself - that
Glassfish isn't playing nicely w/ Wicket when attempting to serialize
- otherwise the error doesn't make much sense.
I'm building a little test-app to demonstrate right now.
If this is the case, what can be done to work around it,
the stuff in session is only serialized because you have the logger
set to debug, if you turn that off it should be fine.
-Igor
On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's kind of what I was thinking...and afraid of myself - that
Glassfish isn't playing nicely w/ Wicket when
Doesn't setDefaultFormProcessing(false) work for you? The values should
be preserved even if model is not update. At least if you're using
wicket 1.2 or newer.
-Matej
Alexei Sokolov wrote:
I need some help with the following scenario.
I have a form and when a user is halfway through it,
I'm not entirely sure what you meant by having the logger set to
debug...but I'll assume that you meant I was missing this from
web.xml?...
init-param
param-nameconfiguration/param-name
param-valueDEPLOYMENT/param-value
Yeah, the raw input is always updated, so getInput will give the
updated value, and it is also used to set the output value of form
components.
Eelco
On 7/5/06, Matej Knopp [EMAIL PROTECTED] wrote:
Doesn't setDefaultFormProcessing(false) work for you? The values should
be preserved even if
well, serialization error happens here:
at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java:62)
if you go there you will see:
// Do some extra profiling/ debugging. This can be a great help
// just for testing whether your webbapp will behave when using
// session
how do you make youre logoutpage?If that is made in a form request or link then by default we do a redirect after postso the logout page is redirected to instead of directly rendered.johan
On 7/5/06, Mark George [EMAIL PROTECTED] wrote:
Thanks Johan.@SuppressWarnings(serial)public class LogoutPage
if you don't lock then pages and sessions must take care of that they are not thread safecurrently wicket is for the most part (99%) thread safe.Maybe we could loose it a bit and say we only sync around the active page.
But then if you hold a page in another page. And set that as a respond then we
can you make a bug report for this?On 7/5/06, Adam Smyczek [EMAIL PROTECTED] wrote:
Hi All,I am getting a StringIndexOutOfBoundsException when I changeselection in a DropDownChoise component that haswantOnSelectionChangedNotifications set to true. It looks like it isrelated to
Alright, I stuck a log4j.properties into my src folder, rebuilt,
redeployed - still get the same exception...here's my properties file
(copied from wicket-examples):
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
i dont know, but if the stack trace is exactly the same then log4j
still thinks debug level is enabled on that package.
-Igor
On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Alright, I stuck a log4j.properties into my src folder, rebuilt,
redeployed - still get the same exception...here's
Thanks. I changed my implementation:
radio.setModel(new Model(a));
This is a whole lot simpler than the CompoundPropertyModel approach that
I was using.
(BTW, my form has only input field: the radio choice)
Sean
Levy, Jeremy wrote:
You could just set the option in your model.
Johan Compagner wrote:
if you don't lock then pages and sessions must take care of that they
are not thread safe
currently wicket is for the most part (99%) thread safe.
Maybe we could loose it a bit and say we only sync around the active page.
But then if you hold a page in another
How can I implement a way switch over to https?
Depending on how the user navigates I need to swich over to https from
a form submit. Every time I try a different way to implement this
transparently I receive Caused by: wicket.WicketRuntimeException:
Already redirecting to '/app/Checkout'.
29 matches
Mail list logo