[Wicket-user] invalid XHTML
Hi all, I tried to validate the following HTML code in http://validator.w3.org/ but received validation errors. Does anyone know what is the correct namespace declaration? Input HTML: == !DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; html xmlns=http://www.w3.org/1999/xhtml; xmlns:wicket=http://wicket.sourceforge.net/; xml:lang=en lang=en /html Validation Results: == Error /Line 6 column 19/: there is no attribute xmlns:wicket. | xmlns:wicket=**http://wicket.sourceforge.net/; | Thanks Nili Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] too much synchronization in wicket?
anyone care to comment?
just to reiterate the problem: if i work with two windows/tabs, pointing to the
same wicket app, and in one i do some lengthy operation, then in the other i
cannot work. i'm not sure if this is the case, but if i want to build a flicker
like site, then i can't browse the site while uploading images
ittay
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 page. And set that as a respond
then we can have again
threaded access to that page that is get from a 'pool'
johan
On 7/5/06, *Ittay Dror* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
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
Object lock = getRequestTarget().getLock(this);
if (lock != null)
{
synchronized (lock)
{
doProcessEventsAndRespond(processor);
}
}
else
{
doProcessEventsAndRespond(processor);
}
}
this is from BookmarkablePageRequestTarget:
/**
* @see wicket.IRequestTarget#getLock(RequestCycle)
*/
public Object getLock(RequestCycle requestCycle)
{
// we need to lock when we are not redirecting,
i.e. we are
// actually rendering the page
return !requestCycle.getRedirect() ?
requestCycle.getSession() : null;
}
as far as i could see, requestCycle.getSession() returns a
Session from the HttpSession
this means that if i open two tabs to a wicket application, and
in one i do some lengthy operation, and then try to load an
unrelated page in the other, it will be stuck, right?
right.
-Matej
ittay
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make
your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
===
Ittay Dror,
Chief architect, openQRM TL,
RD, Qlusters Inc.
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
+972-3-6081994 Fax: +972-3-6081841
http://www.openQRM.org
- Keeps your Data-Center Up and Running
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
===
Ittay Dror,
Chief architect, openQRM TL,
RD, Qlusters Inc.
[EMAIL PROTECTED]
+972-3-6081994 Fax: +972-3-6081841
Re: [Wicket-user] RadioChoice, default selection
This is not what Jeremy meant I think. I've written a blog entry on this subject: http://www.jroller.com/page/dashorst?entry=wicket_goodie_selecting_a_value I'll try to incorporate the example into our documentation at a later stage (writing a blog entry is soo much easier) Martijn On 05 Jul 2006 17:23:21 -0700, Sean Sullivan [EMAIL PROTECTED] wrote: 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. Jeremy -Original Message- Subject: [Wicket-user] RadioChoice, default selection 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 CompoundPropertyModel(this)); radio.setChoices(choices); When the page is displayed to the user, I want the a option to be selected by default. How can I do this with RadioChoice? I'm looking for a Java method like this: radio.setSelection(0); Cheers, Sean Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Download Wicket 1.2 now! Write Ajax applications without touching JavaScript! -- http://wicketframework.org Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] form processing
It is of course assumed that you return to the specific page instance instead of a new instance. So give the originating instance to the popup or new page, and when you are ready to return, set that specific instance as the response page. Martijn On 7/5/06, Eelco Hillenius [EMAIL PROTECTED] wrote: 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 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, 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 entered values should be preserved. What's the best way to implement such a scenario? If I use submit button with default form processing than validation fails, if I disable default form processing than my model is not populated (which is correct, because it can be inconsistent because the form was not completely filled out before user was redirected to another page). Thank you, Alex Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user -- Download Wicket 1.2 now! Write Ajax applications without touching JavaScript! -- http://wicketframework.org Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] too much synchronization in wicket?
I can say that current synchronization policy of wicket seems to me too
coarse grained.
But having no synchronization at it would be very easy to achieve
inconsistent internal state. There's no easy way around this right now.
There was a thread about this lately, maybe you'll find something there.
-Matej
Ittay Dror wrote:
anyone care to comment?
just to reiterate the problem: if i work with two windows/tabs, pointing to
the same wicket app, and in one i do some lengthy operation, then in the
other i cannot work. i'm not sure if this is the case, but if i want to build
a flicker like site, then i can't browse the site while uploading images
ittay
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 page. And set that as a respond
then we can have again
threaded access to that page that is get from a 'pool'
johan
On 7/5/06, *Ittay Dror* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
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
Object lock = getRequestTarget().getLock(this);
if (lock != null)
{
synchronized (lock)
{
doProcessEventsAndRespond(processor);
}
}
else
{
doProcessEventsAndRespond(processor);
}
}
this is from BookmarkablePageRequestTarget:
/**
* @see wicket.IRequestTarget#getLock(RequestCycle)
*/
public Object getLock(RequestCycle requestCycle)
{
// we need to lock when we are not redirecting,
i.e. we are
// actually rendering the page
return !requestCycle.getRedirect() ?
requestCycle.getSession() : null;
}
as far as i could see, requestCycle.getSession() returns a
Session from the HttpSession
this means that if i open two tabs to a wicket application, and
in one i do some lengthy operation, and then try to load an
unrelated page in the other, it will be stuck, right?
right.
-Matej
ittay
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make
your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
===
Ittay Dror,
Chief architect, openQRM TL,
RD, Qlusters Inc.
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
+972-3-6081994 Fax: +972-3-6081841
http://www.openQRM.org
- Keeps your Data-Center Up and Running
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
Re: [Wicket-user] too much synchronization in wicket?
As Matej already said that will be to difficutl internally in wicket (for example the rendering of a page and another thread setting stuff like new components)And for the developer code itself. Threading is one of the most difficult things there is in programming, there are so many loopholes.
So we could syn around a page (that is pretty much already in) so that you can have multiply pages accessed at once. Then only the wicket session objectmust be taken care of. But that is also now already the case because there are situations like
session.attach/detach or if you have your own request cyclethat access the session. Then a session can be accessed by multiply threads.johanOn 7/6/06,
Ittay Dror [EMAIL PROTECTED] wrote:
anyone care to comment?just to reiterate the problem: if i work with two windows/tabs, pointing to the same wicket app, and in one i do some lengthy operation, then in the other i cannot work. i'm not sure if this is the case, but if i want to build a flicker like site, then i can't browse the site while uploading images
ittayJohan 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 page. And set that as a respond then we can have again threaded access to that page that is get from a 'pool'
johan On 7/5/06, *Ittay Dror* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
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 Object lock = getRequestTarget().getLock(this);
if (lock != null) { synchronized (lock) {
doProcessEventsAndRespond(processor); } } else {
doProcessEventsAndRespond(processor); } } this is from BookmarkablePageRequestTarget:
/*** @see wicket.IRequestTarget#getLock(RequestCycle)*/ public Object getLock(RequestCycle requestCycle)
{ // we need to lock when we are not redirecting, i.e. we are // actually rendering the page return !requestCycle.getRedirect() ?
requestCycle.getSession() : null; } as far as i could see, requestCycle.getSession() returns a Session from the HttpSession
this means that if i open two tabs to a wicket application, and in one i do some lengthy operation, and then try to load an unrelated page in the other, it will be stuck, right?
right. -Matej ittay Using Tomcat but need to do more? Need to support web services,
security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___
Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:
Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
-- === Ittay Dror, Chief architect, openQRM TL, RD, Qlusters Inc. [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] +972-3-6081994 Fax: +972-3-6081841 http://www.openQRM.org - Keeps your Data-Center Up and Running
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server
v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___
Wicket-user mailing list Wicket-user@lists.sourceforge.net mailto:Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server
v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___ Wicket-user mailing list
Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user--===
Ittay Dror,Chief architect, openQRM TL,RD, Qlusters Inc.[EMAIL PROTECTED]+972-3-6081994 Fax: +972-3-6081841http://www.openQRM.org
- Keeps your Data-Center Up and RunningUsing Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server
v.1.0.1 based
Re: [Wicket-user] SSL
Redirect to a full url or use an ExternalLink (pointing to your own site but then with ssl)Do that redirect with a IRequestTarget.I don't know how you do it now but doing a redirect should always be donethrough request targets. johanOn 7/6/06, Joe Toth [EMAIL PROTECTED] wrote: How can I implement a way switch over to https?Depending on how the user navigates I need to swich over to https froma form submit.Every time I try a different way to implement thistransparently I receive Caused by: wicket.WicketRuntimeException:Already redirecting to '/app/Checkout'. Cannot redirect more thanonceAt first I tried to annotate a class with @RequiredSSL and created anew IResponseStrategy that would test if the request was secure, if not, WebResponse.redirect to the https version of the requested url.Second I tried to do the same in the constructor of my Base Class forall my pages and throw an AbortException, but I had the same problem. Any ideas?Also, are there any plans to add a https feature in 2.0 core or extensions?Thanks!Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimohttp://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___Wicket-user mailing listWicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] too much synchronization in wicket?
Especially if you have a user object retrieved from the database using
Hibernate in your sessoin, that will not work when handling multpile
requests.
A hibernate object can only be attached to one hibernate session at a
time. It is a very convenient and useful programming paradigm to put
such objects in your session and have them attach/detach with each
request.
We have seen *a lot* of problems with multiple requests arriving at
the same time for the same session when the synchronization lock was
relaxed. I'm not pro loosening this without a decent test case
ensuring that we don't open up a box of pandorra. Until we have unit
tests in place for testing this behavior, I'm against opening our
synchronization.
In my opinion the most significant advantages over Tapestry is the
fact that we don't require you to pay (much) attention to
synchronization issues. For most web applications out there, this is
not a problem: the 90% usecase of Wicket. For the other 10% we should
be careful not to create problems or impose specific optimization
strategies as a default on the other 90%.
Martijn
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
As Matej already said that will be to difficutl internally in wicket (for
example the rendering of a page and another thread setting stuff like new
components)
And for the developer code itself. Threading is one of the most difficult
things there is in programming, there are so many loopholes.
So we could syn around a page (that is pretty much already in) so that you
can have multiply pages accessed at once. Then only the wicket session
object
must be taken care of. But that is also now already the case because there
are situations like session.attach/detach or if you have your own request
cycle
that access the session. Then a session can be accessed by multiply threads.
johan
On 7/6/06, Ittay Dror [EMAIL PROTECTED] wrote:
anyone care to comment?
just to reiterate the problem: if i work with two windows/tabs, pointing
to the same wicket app, and in one i do some lengthy operation, then in the
other i cannot work. i'm not sure if this is the case, but if i want to
build a flicker like site, then i can't browse the site while uploading
images
ittay
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 page. And set that as a respond
then we can have again
threaded access to that page that is get from a 'pool'
johan
On 7/5/06, *Ittay Dror* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
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
Object lock =
getRequestTarget().getLock(this);
if (lock != null)
{
synchronized (lock)
{
doProcessEventsAndRespond(processor);
}
}
else
{
doProcessEventsAndRespond(processor);
}
}
this is from BookmarkablePageRequestTarget:
/**
* @see wicket.IRequestTarget#getLock(RequestCycle)
*/
public Object getLock(RequestCycle requestCycle)
{
// we need to lock when we are not redirecting,
i.e. we are
// actually rendering the page
return !requestCycle.getRedirect() ?
requestCycle.getSession() : null;
}
as far as i could see, requestCycle.getSession() returns a
Session from the HttpSession
this means that if i open two tabs to a wicket application, and
in one i do some lengthy operation, and then try to load an
unrelated page in the other, it will be stuck, right?
right.
-Matej
ittay
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make
your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
Re: [Wicket-user] too much synchronization in wicket?
the thing is that an application in the 90% group may evolve into the 10%
group. it may be a simple thing such as a new report, pdf generation, file
upload or anything else. it seems easy to add to your application, but then you
discover that it influences all of it. and, there's no way out.
even if wicket provides a way out, but it will mean rewriting all existing
pages, it may mean a huge amount of work.
ittay
Martijn Dashorst wrote:
Especially if you have a user object retrieved from the database using
Hibernate in your sessoin, that will not work when handling multpile
requests.
A hibernate object can only be attached to one hibernate session at a
time. It is a very convenient and useful programming paradigm to put
such objects in your session and have them attach/detach with each
request.
We have seen *a lot* of problems with multiple requests arriving at
the same time for the same session when the synchronization lock was
relaxed. I'm not pro loosening this without a decent test case
ensuring that we don't open up a box of pandorra. Until we have unit
tests in place for testing this behavior, I'm against opening our
synchronization.
In my opinion the most significant advantages over Tapestry is the
fact that we don't require you to pay (much) attention to
synchronization issues. For most web applications out there, this is
not a problem: the 90% usecase of Wicket. For the other 10% we should
be careful not to create problems or impose specific optimization
strategies as a default on the other 90%.
Martijn
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
As Matej already said that will be to difficutl internally in wicket (for
example the rendering of a page and another thread setting stuff like new
components)
And for the developer code itself. Threading is one of the most difficult
things there is in programming, there are so many loopholes.
So we could syn around a page (that is pretty much already in) so that you
can have multiply pages accessed at once. Then only the wicket session
object
must be taken care of. But that is also now already the case because there
are situations like session.attach/detach or if you have your own request
cycle
that access the session. Then a session can be accessed by multiply threads.
johan
On 7/6/06, Ittay Dror [EMAIL PROTECTED] wrote:
anyone care to comment?
just to reiterate the problem: if i work with two windows/tabs, pointing
to the same wicket app, and in one i do some lengthy operation, then in the
other i cannot work. i'm not sure if this is the case, but if i want to
build a flicker like site, then i can't browse the site while uploading
images
ittay
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 page. And set that as a respond
then we can have again
threaded access to that page that is get from a 'pool'
johan
On 7/5/06, *Ittay Dror* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
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
Object lock =
getRequestTarget().getLock(this);
if (lock != null)
{
synchronized (lock)
{
doProcessEventsAndRespond(processor);
}
}
else
{
doProcessEventsAndRespond(processor);
}
}
this is from BookmarkablePageRequestTarget:
/**
* @see wicket.IRequestTarget#getLock(RequestCycle)
*/
public Object getLock(RequestCycle requestCycle)
{
// we need to lock when we are not redirecting,
i.e. we are
// actually rendering the page
return !requestCycle.getRedirect() ?
requestCycle.getSession() : null;
}
as far as i could see, requestCycle.getSession() returns a
Session from the HttpSession
this means that if i open two tabs to a wicket application, and
in one i do some lengthy operation, and then try to load an
unrelated page in the other, it will be stuck, right?
right.
-Matej
ittay
Using Tomcat but need to do more? Need to support web services,
Re: [Wicket-user] too much synchronization in wicket?
pdf generation and that kind of stuff should be done in a seperate thread.Else you could have browser just time out your request. And with an ajax call/progress bar it is also much nicer.FileUpload would be a thing that we can optimze (if that is not already the case or something like that) that the pure upload doesn't block the session yet.
But i guess if you want you can go around the session syncjust make your own RequestTarget resolver (IRequestTargetResolverStrategy) and don't return a session sync.On 7/6/06,
Ittay Dror [EMAIL PROTECTED] wrote:
the thing is that an application in the 90% group may evolve into the 10% group. it may be a simple thing such as a new report, pdf generation, file upload or anything else. it seems easy to add to your application, but then you discover that it influences all of it. and, there's no way out.
even if wicket provides a way out, but it will mean rewriting all existing pages, it may mean a huge amount of work.ittayMartijn Dashorst wrote: Especially if you have a user object retrieved from the database using
Hibernate in your sessoin, that will not work when handling multpile requests. A hibernate object can only be attached to one hibernate session at a time. It is a very convenient and useful programming paradigm to put
such objects in your session and have them attach/detach with each request. We have seen *a lot* of problems with multiple requests arriving at the same time for the same session when the synchronization lock was
relaxed. I'm not pro loosening this without a decent test case ensuring that we don't open up a box of pandorra. Until we have unit tests in place for testing this behavior, I'm against opening our
synchronization. In my opinion the most significant advantages over Tapestry is the fact that we don't require you to pay (much) attention to synchronization issues. For most web applications out there, this is
not a problem: the 90% usecase of Wicket. For the other 10% we should be careful not to create problems or impose specific optimization strategies as a default on the other 90%. Martijn
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: As Matej already said that will be to difficutl internally in wicket (for example the rendering of a page and another thread setting stuff like new
components) And for the developer code itself. Threading is one of the most difficult things there is in programming, there are so many loopholes. So we could syn around a page (that is pretty much already in) so that you
can have multiply pages accessed at once. Then only the wicket session object must be taken care of. But that is also now already the case because there are situations like
session.attach/detach or if you have your own request cycle that access the session. Then a session can be accessed by multiply threads. johan
On 7/6/06, Ittay Dror [EMAIL PROTECTED] wrote: anyone care to comment? just to reiterate the problem: if i work with two windows/tabs, pointing
to the same wicket app, and in one i do some lengthy operation, then in the other i cannot work. i'm not sure if this is the case, but if i want to build a flicker like site, then i can't browse the site while uploading
images ittay 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 page. And set that as a respond
then we can have again threaded access to that page that is get from a 'pool' johan On 7/5/06, *Ittay Dror*
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: 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 Object lock = getRequestTarget().getLock(this); if (lock != null) {
synchronized (lock) { doProcessEventsAndRespond(processor);
} } else {
doProcessEventsAndRespond(processor); } }
this is from BookmarkablePageRequestTarget:/*** @see wicket.IRequestTarget#getLock(RequestCycle)*/
public Object getLock(RequestCycle requestCycle) { // we need to lock when we are not redirecting,
i.e. we are // actually rendering the page return !requestCycle.getRedirect() ?
requestCycle.getSession() : null; } as far as i could see, requestCycle.getSession
() returns a Session from the HttpSession this means that if i open two tabs to a wicket application, and in one i do some lengthy operation, and then try to load an
unrelated page in the other, it will be stuck, right? right. -Matej
ittay Using Tomcat but need to do more? Need to support web services,
security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server
v.1.0.1 based on Apache Geronimo
[Wicket-user] Images to button
Hi All I want to add external images to button . Regards Gangadhar Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Creating a component / dynamic casting / implicit casting
Hi Im currently working on a component that consists of a dropdown list and two listbox's, lb1 and lb2. This is pretty simple to do. My issue isnt really a wicket one, but I guess it has relevance since this is something I need to solve to create my component. The hard part is that the contents of lb1 depends of the contents of the dropdown. So I looked towards java.lang.reflect(Reflection), wich lets me define a certain method to use. my constructor looks something like this dualForm_form(String id, ItemContainer drop, List DropList, ItemContainer myCont, Class myProvider, String sMethod) The things that regards reflect are these: myProvider, which is the class that I need to call sMethod, which is the name of the method that I need to call To keep stuff simple lets just assume that method bla only takes one parameter, the one which is provided by the onselectionchange method of my dropdown. The above things are fine. But I also need to provide an instanciated object of the Class myProvider. I thought that I would use the class Object to carry the object. But calling reflect gives an error that the method defined in sMethed does not exist, I guess this is because reflection is looking in the object Class and not the true class which carries the method? What should I do instead? As said earlier, this has nothing to do with wicket, but is very interresting when creating components that needs to update themselfes. -Regards Nino winmail.datUsing Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
[Wicket-user] Master-details form
I'm using wicket to developer a budget application. I've a classic Master-Details data entry form and relative POJOs. For example
public class Order { private Long id;
private Data date; private Float amout;
private Float tax; private ListOrderItem items;
} public class OrderItem {
private Long id;
private String description; private Integer qty;
private Float unitPrice;}Customer is requesting to handle all order data entry using only one form.
How to handle that using Wicket? For example suppose I want to edit an existing order: which is the best approch to display data-entry fields for each OrderItem
element in 'items' collection?Thank you for helping.Paolo
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Again, I did this at home on my Gentoo box in a separate project...and got the same result. My log4j.properties: logger.wicket.protocol.http=INFO The exception stack: wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.zambizzi.finances.ui.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update(Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach(RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run(WorkerThread.java:75) Caused by: java.io.NotSerializableException: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java:56) ... 33 more If I make a reference to the SFSB and do *not* place it into Wicket's session state - there are no problems (but of course this is useless)... What else can I do? This is a real jam for me as my boss has expressed interest in replacing JBoss w/ Glassfish and the one EJB3 app we've written so far makes heavy use of a single SFSB. Thanks again! Igor Vaynberg wrote: 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 my properties file (copied from wicket-examples):
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
My problem w/ that is; the application is done and I can't go back through and re-work it to get something working that already works on another container. This application runs well on JBoss's EJB3 implemenation w/o that kind of tweaking. However, going forward, JBoss probably isn't an option for us. I suppose I can post @ the Glassfish forums to see what they think. Meanwhile, how can I get debug logging disabled in order to eliminate that possibility? On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: This discussion is completely about getting the debug logging disabled. But even if that is done. Then you still could have a problem because for example in 2.0 we store the pages to disk. this will fail then. It is much better for you to look why it is not serializeable or of you can wrap something around it like a serializeable proxy (just like our spring intergration) johan On 7/6/06, V. Jenks [EMAIL PROTECTED] wrote: Again, I did this at home on my Gentoo box in a separate project...and got the same result. My log4j.properties: logger.wicket.protocol.http=INFO The exception stack: wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.zambizzi.finances.ui.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update (Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach(RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked (ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java :287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run (WorkerThread.java:75) Caused by: java.io.NotSerializableException: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1081) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) at java.io.ObjectOutputStream.writeOrdinaryObject (ObjectOutputStream.java:1290) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) at
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) looks like a bug in sun's impl of ejbs? -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 overridden ISessionFactory to store objects - then I start getting exceptions like this: ** StandardWrapperValve[ProductCatalogApp]: Servlet.service() for servlet ProductCatalogApp threw exception wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.myapp.ui.admin.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute (HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update(Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach(RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet (WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService (ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service (CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(ProcessorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked(ProcessorTask.java :574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorTask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(ReadTask.java:287) at com.sun.enterprise.web.connector.grizzly.ReadTask.doTask(ReadTask.java:212) at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:252) at com.sun.enterprise.web.connector.grizzly.WorkerThread.run (WorkerThread.java:75) Caused by: java.io.NotSerializableException:
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
On Thursday, 06 July 2006 09:16 am, Vincent Jenks escreveu: My problem w/ that is; the application is done and I can't go back through and re-work it to get something working that already works on another container. This application runs well on JBoss's EJB3 implemenation w/o that kind of tweaking. However, going forward, JBoss probably isn't an option for us. I suppose I can post @ the Glassfish forums to see what they think. Meanwhile, how can I get debug logging disabled in order to eliminate that possibility? I don't know if this will help, but you might try something like this: Logger logger = Logger.getLogger( org.springframework ); logger.setLevel( Level.ERROR ); but replace org.springframework with your class's FQN. Do this in your Application. Then you might be able to see that with this manually set to error you do or don't get this issue. Then you can at least be assured of that. Or... you can print out the logging level. Once you know for sure what level it is getting set to, you can then investigate further. If it's not getting set to the level you want to, you might have to set some breakpoints in the log4j code. On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: This discussion is completely about getting the debug logging disabled. But even if that is done. Then you still could have a problem because for example in 2.0 we store the pages to disk. this will fail then. It is much better for you to look why it is not serializeable or of you can wrap something around it like a serializeable proxy (just like our spring intergration) johan On 7/6/06, V. Jenks [EMAIL PROTECTED] wrote: Again, I did this at home on my Gentoo box in a separate project...and got the same result. My log4j.properties: logger.wicket.protocol.http=INFO The exception stack: wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.zambizzi.finances.ui.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute(HttpSessionStore.java: 62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update (Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach(RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService(Applicatio nFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke (StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java: 566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:53 6) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardCont extValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve .java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java: 566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java: 566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline .java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.j ava:137) at org.apache.catalina.core.StandardPipeline.doInvoke (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:53 6) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:231) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.invokeAdapter(Proc essorTask.java:667) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.processNonBlocked (ProcessorTask.java:574) at com.sun.enterprise.web.connector.grizzly.ProcessorTask.process(ProcessorT ask.java:844) at com.sun.enterprise.web.connector.grizzly.ReadTask.executeProcessorTask(Re
Re: [Wicket-user] Images to button
What do you mean? Like the entire button is just your image or that you both have text and an icon? Try taking a look at: http://wicket.sourceforge.net/apidocs/wicket/markup/html/form/ImageButton.html Regards Frank On Thu, 2006-07-06 at 16:00 +0530, [EMAIL PROTECTED] wrote: Hi All I want to add external images to button . Regards Gangadhar Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Well, this was the first app I've ever built w/ EJB technology of *any* version...it's sort of a pilot app for future in-house effortsso far it's worked out great. So, correct me if I'm wrong but it's my understanding that if I do not store the stub to the interface of the stateful bean in an HTTP session - I may lose the reference to that bean the next time I call it. So, I'm calling the stateful bean and storing a reference to it in http session so I can recall that exact instance back from the server later. This is how it was done in the app that is currently running in production on JBoss. On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote: Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) looks like a bug in sun's impl of ejbs? -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 overridden ISessionFactory to store objects - then I start getting exceptions like this: ** StandardWrapperValve[ProductCatalogApp]: Servlet.service() for servlet ProductCatalogApp threw exception wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.myapp.ui.admin.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute (HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update(Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach(RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet (WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService (ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at org.apache.catalina.core.StandardContextValve.invoke (StandardContextValve.java:179) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.WebPipeline.invoke(WebPipeline.java:73) at org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:182) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at com.sun.enterprise.web.VirtualServerPipeline.invoke(VirtualServerPipeline.java:120) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:137) at org.apache.catalina.core.StandardPipeline.doInvoke (StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:939) at org.apache.coyote.tomcat5.CoyoteAdapter.service (CoyoteAdapter.java:231) at
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
OK, I've created a small test-app in Netbeans where I'm using a Wicket page and have overridden ISessionFactory in the app class to create a session. I have a page where I call the stateful bean, create it and store it in session if it's non-existent, and supply a link to clear the bean from session. When first calling the page - when the stub is first stored in session, the page fails. If I re-visit the page the values have actually been stored...amazingly enough...and the page does not fail but displays the values in session. I can click the link, clear it, and start the whole process over again and it is consistent. So that begs the question - would I be safe supressing the exception in the custom session class where I'm storing the bean stub? Or, is it possible that I'm not getting the correct reference to the bean due to the serialization failure? If someone wants a copy of my little test app - I'd be happy to send it along. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Well, this was the first app I've ever built w/ EJB technology of *any* version...it's sort of a pilot app for future in-house effortsso far it's worked out great. So, correct me if I'm wrong but it's my understanding that if I do not store the stub to the interface of the stateful bean in an HTTP session - I may lose the reference to that bean the next time I call it. So, I'm calling the stateful bean and storing a reference to it in http session so I can recall that exact instance back from the server later. This is how it was done in the app that is currently running in production on JBoss. On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote: Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1075) looks like a bug in sun's impl of ejbs? -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 overridden ISessionFactory to store objects - then I start getting exceptions like this: ** StandardWrapperValve[ProductCatalogApp]: Servlet.service() for servlet ProductCatalogApp threw exception wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.myapp.ui.admin.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute (HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update(Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach(RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet (WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService (ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
that it just works is logical. It is just a test we try to serialize it sothat you get a warning if that is not possible because of a non serializeable object.On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: OK, I've created a small test-app in Netbeans where I'm using a Wicketpage and have overridden ISessionFactory in the app class to create asession.I have a page where I call the stateful bean, create it andstore it in session if it's non-existent, and supply a link to clear the bean from session.When first calling the page - when the stub is first stored insession, the page fails.If I re-visit the page the values haveactually been stored...amazingly enough...and the page does not fail but displays the values in session.I can click the link, clear it,and start the whole process over again and it is consistent.So that begs the question - would I be safe supressing the exceptionin the custom session class where I'm storing the bean stub?Or, is it possible that I'm not getting the correct reference to the bean dueto the serialization failure?If someone wants a copy of my little test app - I'd be happy to send it along.On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Well, this was the first app I've ever built w/ EJB technology of *any* version...it's sort of a pilot app for future in-house effortsso far it's worked out great. So, correct me if I'm wrong but it's my understanding that if I do not store the stub to the interface of the stateful bean in an HTTP session - I may lose the reference to that bean the next time I call it. So, I'm calling the stateful bean and storing a reference to it in http session so I can recall that exact instance back from the server later.This is how it was done in the app that is currently running in production on JBoss. On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote: Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1075) looks like a bug in sun's impl of ejbs? -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 overridden ISessionFactory to store objects - then I start getting exceptions like this: ** StandardWrapperValve[ProductCatalogApp]: Servlet.service() for servlet ProductCatalogApp threw exception wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.myapp.ui.admin.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute (HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update(Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach (RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet (WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.catalina.core.ApplicationFilterChain.servletService ( ApplicationFilterChain.java:397) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:278) at org.apache.catalina.core.StandardPipeline.doInvoke(StandardPipeline.java:566) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:536) at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:240) at
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Excellent, I'll move forward then and see how it goes...thanks! On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: that it just works is logical. It is just a test we try to serialize it so that you get a warning if that is not possible because of a non serializeable object. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: OK, I've created a small test-app in Netbeans where I'm using a Wicket page and have overridden ISessionFactory in the app class to create a session. I have a page where I call the stateful bean, create it and store it in session if it's non-existent, and supply a link to clear the bean from session. When first calling the page - when the stub is first stored in session, the page fails. If I re-visit the page the values have actually been stored...amazingly enough...and the page does not fail but displays the values in session. I can click the link, clear it, and start the whole process over again and it is consistent. So that begs the question - would I be safe supressing the exception in the custom session class where I'm storing the bean stub? Or, is it possible that I'm not getting the correct reference to the bean due to the serialization failure? If someone wants a copy of my little test app - I'd be happy to send it along. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Well, this was the first app I've ever built w/ EJB technology of *any* version...it's sort of a pilot app for future in-house effortsso far it's worked out great. So, correct me if I'm wrong but it's my understanding that if I do not store the stub to the interface of the stateful bean in an HTTP session - I may lose the reference to that bean the next time I call it. So, I'm calling the stateful bean and storing a reference to it in http session so I can recall that exact instance back from the server later. This is how it was done in the app that is currently running in production on JBoss. On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote: Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1075) looks like a bug in sun's impl of ejbs? -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 overridden ISessionFactory to store objects - then I start getting exceptions like this: ** StandardWrapperValve[ProductCatalogApp]: Servlet.service() for servlet ProductCatalogApp threw exception wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class: com.myapp.ui.admin.UserSession at wicket.protocol.http.HttpSessionStore.setAttribute (HttpSessionStore.java:62) at wicket.Session.setAttribute(Session.java:914) at wicket.Session.update(Session.java:938) at wicket.protocol.http.WebSession.update(WebSession.java:116) at wicket.RequestCycle.detach (RequestCycle.java:818) at wicket.RequestCycle.steps(RequestCycle.java:1052) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet (WicketServlet.java:215) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
For whatever reason, I'm unable to supress this exception in the storefront application (where I really need it.) I've tried wrapping a try/catch around the assignment and retrieval of the SFSB stub in the custom Session class...I can't pull the bean data up w/o the exception occuring, it would seem. So again, is there a way to turn logging debugging off so the test doesn't happen at all...so I can quit trying to find work-arounds? Even if my error supression did work, it's not a very elegant solution - it might be better if the serialization wasn't being tested at all. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Excellent, I'll move forward then and see how it goes...thanks! On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: that it just works is logical. It is just a test we try to serialize it so that you get a warning if that is not possible because of a non serializeable object. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: OK, I've created a small test-app in Netbeans where I'm using a Wicket page and have overridden ISessionFactory in the app class to create a session. I have a page where I call the stateful bean, create it and store it in session if it's non-existent, and supply a link to clear the bean from session. When first calling the page - when the stub is first stored in session, the page fails. If I re-visit the page the values have actually been stored...amazingly enough...and the page does not fail but displays the values in session. I can click the link, clear it, and start the whole process over again and it is consistent. So that begs the question - would I be safe supressing the exception in the custom session class where I'm storing the bean stub? Or, is it possible that I'm not getting the correct reference to the bean due to the serialization failure? If someone wants a copy of my little test app - I'd be happy to send it along. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Well, this was the first app I've ever built w/ EJB technology of *any* version...it's sort of a pilot app for future in-house effortsso far it's worked out great. So, correct me if I'm wrong but it's my understanding that if I do not store the stub to the interface of the stateful bean in an HTTP session - I may lose the reference to that bean the next time I call it. So, I'm calling the stateful bean and storing a reference to it in http session so I can recall that exact instance back from the server later. This is how it was done in the app that is currently running in production on JBoss. On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote: Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1075) looks like a bug in sun's impl of ejbs? -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 overridden ISessionFactory to store objects - then I start getting exceptions like this: ** StandardWrapperValve[ProductCatalogApp]: Servlet.service() for servlet ProductCatalogApp threw exception wicket.WicketRuntimeException: Internal error cloning object. Make sure all dependent objects implement Serializable. Class:
Re: [Wicket-user] too much synchronization in wicket?
i agree with johan,the web is based around processing a lot of short lived requests. if you have something that takes a long time do it in a separate thread with some kind of notification. now what we may need is support for long-running tasks that makes implementing them and their notifications trivial. rfe/patches are welcome.
-IgorOn 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
pdf generation and that kind of stuff should be done in a seperate thread.Else you could have browser just time out your request. And with an ajax call/progress bar it is also much nicer.FileUpload would be a thing that we can optimze (if that is not already the case or something like that) that the pure upload doesn't block the session yet.
But i guess if you want you can go around the session syncjust make your own RequestTarget resolver (IRequestTargetResolverStrategy) and don't return a session sync.
On 7/6/06,
Ittay Dror [EMAIL PROTECTED] wrote:
the thing is that an application in the 90% group may evolve into the 10% group. it may be a simple thing such as a new report, pdf generation, file upload or anything else. it seems easy to add to your application, but then you discover that it influences all of it. and, there's no way out.
even if wicket provides a way out, but it will mean rewriting all existing pages, it may mean a huge amount of work.ittayMartijn Dashorst wrote: Especially if you have a user object retrieved from the database using
Hibernate in your sessoin, that will not work when handling multpile requests. A hibernate object can only be attached to one hibernate session at a time. It is a very convenient and useful programming paradigm to put
such objects in your session and have them attach/detach with each request. We have seen *a lot* of problems with multiple requests arriving at the same time for the same session when the synchronization lock was
relaxed. I'm not pro loosening this without a decent test case ensuring that we don't open up a box of pandorra. Until we have unit tests in place for testing this behavior, I'm against opening our
synchronization. In my opinion the most significant advantages over Tapestry is the fact that we don't require you to pay (much) attention to synchronization issues. For most web applications out there, this is
not a problem: the 90% usecase of Wicket. For the other 10% we should be careful not to create problems or impose specific optimization strategies as a default on the other 90%. Martijn
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: As Matej already said that will be to difficutl internally in wicket (for
example the rendering of a page and another thread setting stuff like new
components) And for the developer code itself. Threading is one of the most difficult things there is in programming, there are so many loopholes. So we could syn around a page (that is pretty much already in) so that you
can have multiply pages accessed at once. Then only the wicket session object must be taken care of. But that is also now already the case because there are situations like
session.attach/detach or if you have your own request cycle that access the session. Then a session can be accessed by multiply threads. johan
On 7/6/06, Ittay Dror [EMAIL PROTECTED] wrote: anyone care to comment?
just to reiterate the problem: if i work with two windows/tabs, pointing
to the same wicket app, and in one i do some lengthy operation, then in the other i cannot work. i'm not sure if this is the case, but if i want to build a flicker like site, then i can't browse the site while uploading
images ittay 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 page. And set that as a respond
then we can have again threaded access to that page that is get from a 'pool' johan On 7/5/06, *Ittay Dror*
[EMAIL PROTECTED] mailto:
[EMAIL PROTECTED] wrote: 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 Object lock = getRequestTarget().getLock(this); if (lock != null) {
synchronized (lock) { doProcessEventsAndRespond(processor);
} } else {
doProcessEventsAndRespond(processor); } }
this is from BookmarkablePageRequestTarget:/*** @see wicket.IRequestTarget#getLock(RequestCycle)*/
public Object getLock(RequestCycle requestCycle) { // we need to lock when we are not redirecting,
i.e. we are // actually rendering the page return !requestCycle.getRedirect() ?
requestCycle.getSession() : null; } as far as i could see, requestCycle.getSession
() returns a Session from the HttpSession this means that if i open two tabs to a wicket
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
That's where I put it - nothing changed so you're obviously right...it won't make a difference anyways. Hmm...this is bad...this puts me in a rough spot as I have no idea how to use a spring like proxy and am not at all familiar w/ Springand in effect I'd have no idea how to do this in Wicket or what it would involve. It's obviously going to involve me reworking a bunch of my existing code just to move to another container...which shouldn't have been the case. On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you are doing it fine, you just have to find a location for log4j.properties where glassfish will pick it up. usually it is in war/web-inf/classes -Igor On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: For whatever reason, I'm unable to supress this exception in the storefront application (where I really need it.) I've tried wrapping a try/catch around the assignment and retrieval of the SFSB stub in the custom Session class...I can't pull the bean data up w/o the exception occuring, it would seem. So again, is there a way to turn logging debugging off so the test doesn't happen at all...so I can quit trying to find work-arounds? Even if my error supression did work, it's not a very elegant solution - it might be better if the serialization wasn't being tested at all. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Excellent, I'll move forward then and see how it goes...thanks! On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote: that it just works is logical. It is just a test we try to serialize it so that you get a warning if that is not possible because of a non serializeable object. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: OK, I've created a small test-app in Netbeans where I'm using a Wicket page and have overridden ISessionFactory in the app class to create a session. I have a page where I call the stateful bean, create it and store it in session if it's non-existent, and supply a link to clear the bean from session. When first calling the page - when the stub is first stored in session, the page fails. If I re-visit the page the values have actually been stored...amazingly enough...and the page does not fail but displays the values in session. I can click the link, clear it, and start the whole process over again and it is consistent. So that begs the question - would I be safe supressing the exception in the custom session class where I'm storing the bean stub? Or, is it possible that I'm not getting the correct reference to the bean due to the serialization failure? If someone wants a copy of my little test app - I'd be happy to send it along. On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote: Well, this was the first app I've ever built w/ EJB technology of *any* version...it's sort of a pilot app for future in-house effortsso far it's worked out great. So, correct me if I'm wrong but it's my understanding that if I do not store the stub to the interface of the stateful bean in an HTTP session - I may lose the reference to that bean the next time I call it. So, I'm calling the stateful bean and storing a reference to it in http session so I can recall that exact instance back from the server later. This is how it was done in the app that is currently running in production on JBoss. On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote: Anyway, I don't really understand, why is the ejb object actually being serialized. Do you store your service objects in session? -Matej Igor Vaynberg wrote: 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, but when wicket does it it is a problem. -Igor On 7/5/06, Vincent Jenks [EMAIL PROTECTED] wrote: 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 Glassfish. On 7/5/06, Igor Vaynberg [EMAIL PROTECTED] wrote: Caused by: java.io.NotSerializableExcepti on: com.sun.ejb.containers.EJBLocalObjectInvocationHandlerDelegate at java.io.ObjectOutputStream.writeObject0 (ObjectOutputStream.java:1075)
Re: [Wicket-user] Creating a component / dynamic casting / implicit casting
why not use models, see how the ajax dropdown example works.-IgorOn 7/6/06, Nino Wael [EMAIL PROTECTED] wrote:I solved the problem by requiring a interface instead of the object. But that means that, every where my component are used the user needs to implement the interface. That doesnt seem to be a really nice solution. The thing I need are for you guys(developers of wicket) to extend the propertymodel class so that it can take parameters also instead of just calling setters and getters... :)-regards Nino -Original Message-From: [EMAIL PROTECTED] on behalf of Nino WaelSent: Thu 06-07-2006 14:01To: wicket-user@lists.sourceforge.netCc:Subject:Creating a component / dynamic casting / implicit castingHiIm currently working on a component that consists of a dropdown list and two listbox's, lb1 and lb2. This is pretty simple to do. My issue isnt really a wicket one, but I guess it has relevance since this is something I need to solve to create my component. The hard part is that the contents of lb1 depends of the contents of the dropdown. So I looked towards java.lang.reflect(Reflection), wich lets me define a certain method to use.my constructor looks something like this dualForm_form(String id, ItemContainer drop, List DropList, ItemContainer myCont, Class myProvider, String sMethod)The things that regards reflect are these: myProvider, which is the class that I need to call sMethod, which is the name of the method that I need to callTo keep stuff simple lets just assume that method bla only takes one parameter, the one which is provided by the onselectionchange method of my dropdown. The above things are fine. But I also need to provide an instanciated object of the Class myProvider. I thought that I would use the class Object to carry the object. But calling reflect gives an error that the method defined in sMethed does not exist, I guess this is because reflection is looking in the object Class and not the true class which carries the method? What should I do instead? As said earlier, this has nothing to do with wicket, but is very interresting when creating components that needs to update themselfes.-Regards NinoUsing Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___Wicket-user mailing list Wicket-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Images to button
That, or just use a SubmitLink coupled to a a tag with an img tag embedded. Or use CSS. Eelco On 7/6/06, Frank Bille Jensen [EMAIL PROTECTED] wrote: What do you mean? Like the entire button is just your image or that you both have text and an icon? Try taking a look at: http://wicket.sourceforge.net/apidocs/wicket/markup/html/form/ImageButton.html Regards Frank On Thu, 2006-07-06 at 16:00 +0530, [EMAIL PROTECTED] wrote: Hi All I want to add external images to button . Regards Gangadhar Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant solution
- it might be better if the serialization wasn't being tested at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not getting the correct reference to the
bean
due
to the serialization failure?
If someone wants a copy of my little test app - I'd be happy to
send
it
along.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Well, this was the first app I've ever built w/ EJB technology
of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if
I do
not
store the stub to the interface of the stateful bean in an
HTTP
session - I may lose the reference to that bean the next time
I
call
it.
So, I'm calling the stateful bean and storing a reference to
it in
http session so I can recall that exact instance back from the
server
later. This is how it was done in the app that is currently
running
in production on JBoss.
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Anyway, I don't really understand, why is the ejb object
actually
being
serialized. Do you store your service objects in session?
-Matej
Igor Vaynberg wrote:
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
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
It must be in the wrong place somehow, if glassfish doesn't pick it
up. You should try to figure out how Glassfish works with commons
logging. Typically there is logging configuration for the whole
application server, and then for specific web applications. Not all
containers behave the same unfortunately (had to write a JBoss plugin
to let it pick up application specific logging for a project some two
years ago)
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant solution
- it might be better if the serialization wasn't being tested at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not getting the correct reference to the
bean
due
to the serialization failure?
If someone wants a copy of my little test app - I'd be happy to
send
it
along.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Well, this was the first app I've ever built w/ EJB technology
of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if
I do
not
store the stub to the interface of the stateful bean in an
HTTP
session - I may lose the reference to that bean the next time
I
call
it.
So, I'm calling the stateful bean and storing a reference to
it in
http session so I can recall that exact instance back from the
server
later. This is how it was done in the app that is
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant solution
- it might be better if the serialization wasn't being tested at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not getting the correct reference to the
bean
due
to the serialization failure?
If someone wants a copy of my little test app - I'd be happy to
send
it
along.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Well, this was the first app I've ever built w/ EJB technology
of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if
I do
not
store the stub to the interface of the stateful bean in an
HTTP
session - I may lose the reference to that bean the next time
I
call
it.
So, I'm calling the stateful bean and storing a reference to
it in
http session so I can recall that exact instance back from the
server
later. This is how it was done in the app that is currently
running
in production on JBoss.
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Anyway, I don't really understand, why is the ejb object
actually
being
serialized. Do you store your service objects in session?
-Matej
Igor Vaynberg wrote:
well,
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Wicket uses commons-logging. I wonder whether glassfish doesn't have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant solution
- it might be better if the serialization wasn't being tested at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not getting the correct reference to the
bean
due
to the serialization failure?
If someone wants a copy of my little test app - I'd be happy to
send
it
along.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Well, this was the first app I've ever built w/ EJB technology
of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if
I do
not
store the stub to the interface of the stateful bean in an
HTTP
session - I may lose the reference to that bean the next time
I
call
it.
So, I'm calling the stateful bean and storing a reference to
it in
http session so I can recall that exact instance back from the
server
later. This is how it was done in the app that is currently
running
in production on JBoss.
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Anyway, I don't really understand, why is the ejb object
actually
being
serialized. Do you store your service objects in session?
-Matej
Igor Vaynberg wrote:
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, but when wicket does it it is a
problem.
-Igor
On 7/5/06, Vincent Jenks [EMAIL
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it is a
requirement for using Hibernate as the persistence engine. I put the
log4j.properties in there w/ the suggested entries and restarted...the
error is the same - didn't work.
I tried deploying log4j in my war's /lib folder and packaging
log4j.properties in there...made no difference...I can't get the
exception message to change.
ugh :(
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Wicket uses commons-logging. I wonder whether glassfish doesn't have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant solution
- it might be better if the serialization wasn't being tested at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not getting the correct reference to the
bean
due
to the serialization failure?
If someone wants a copy of my little test app - I'd be happy to
send
it
along.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Well, this was the first app I've ever built w/ EJB technology
of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if
I do
not
store the stub to the interface of the stateful bean in an
HTTP
session - I may lose the reference to that bean the next time
I
call
it.
So, I'm calling the stateful bean and storing a reference to
it in
http session so I can recall that exact instance back from the
server
later. This is how it was done in the app that is
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Did you try asking around on the glassfish list/ IRC channel (if they have one)?
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it is a
requirement for using Hibernate as the persistence engine. I put the
log4j.properties in there w/ the suggested entries and restarted...the
error is the same - didn't work.
I tried deploying log4j in my war's /lib folder and packaging
log4j.properties in there...made no difference...I can't get the
exception message to change.
ugh :(
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Wicket uses commons-logging. I wonder whether glassfish doesn't have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant
solution
- it might be better if the serialization wasn't being tested at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not getting the correct reference to the
bean
due
to the serialization failure?
If someone wants a copy of my little test app - I'd be happy to
send
it
along.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Well, this was the first app I've ever built w/ EJB technology
of
*any* version...it's sort of a pilot app for future in-house
effortsso far it's worked out great.
So, correct me if I'm wrong but it's my understanding that if
I do
not
store the stub to the interface of the stateful bean in an
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
At 8:30 this morning...it's now 2:30pm here and I was the *last*
person to post to this forum at all...which is weird...it's normally
pretty busy.
http://forums.java.net/jive/thread.jspa?threadID=16673tstart=0
This is the first time I haven't gotten an answer to my problem on the
same day...they're *almost* as good as you guys! :)
On 7/6/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Did you try asking around on the glassfish list/ IRC channel (if they have
one)?
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it is a
requirement for using Hibernate as the persistence engine. I put the
log4j.properties in there w/ the suggested entries and restarted...the
error is the same - didn't work.
I tried deploying log4j in my war's /lib folder and packaging
log4j.properties in there...made no difference...I can't get the
exception message to change.
ugh :(
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Wicket uses commons-logging. I wonder whether glassfish doesn't have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p - %-26.26c{1} -
%m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously
right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no idea
how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in Wicket or
what it would involve. It's obviously going to involve me reworking
a
bunch of my existing code just to move to another container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in
war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in the
storefront application (where I really need it.) I've tried
wrapping
a try/catch around the assignment and retrieval of the SFSB stub in
the custom Session class...I can't pull the bean data up w/o the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the test
doesn't happen at all...so I can quit trying to find work-arounds?
Even if my error supression did work, it's not a very elegant
solution
- it might be better if the serialization wasn't being tested at
all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm using a
Wicket
page and have overridden ISessionFactory in the app class to
create
a
session. I have a page where I call the stateful bean, create
it
and
store it in session if it's non-existent, and supply a link to
clear
the bean from session.
When first calling the page - when the stub is first stored in
session, the page fails. If I re-visit the page the values have
actually been stored...amazingly enough...and the page does not
fail
but displays the values in session. I can click the link, clear
it,
and start the whole process over again and it is consistent.
So that begs the question - would I be safe supressing the
exception
in the custom session class where I'm storing the bean stub?
Or, is
it possible that I'm not
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
OK, checked it out and I made my changebut bare w/ me...I'm almost
completely unfamiliar w/ Ant and I figured that'd be the easiest way
to build it?
So, how do I build this sucker?
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
well, if it comes down to it just check out wicket, remove that portion of
code, and deploy it that way
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
At 8:30 this morning...it's now 2:30pm here and I was the *last*
person to post to this forum at all...which is weird...it's normally
pretty busy.
http://forums.java.net/jive/thread.jspa?threadID=16673tstart=0
This is the first time I haven't gotten an answer to my problem on the
same day...they're *almost* as good as you guys! :)
On 7/6/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Did you try asking around on the glassfish list/ IRC channel (if they
have one)?
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it is a
requirement for using Hibernate as the persistence engine. I put the
log4j.properties in there w/ the suggested entries and restarted...the
error is the same - didn't work.
I tried deploying log4j in my war's /lib folder and packaging
log4j.properties in there...made no difference...I can't get the
exception message to change.
ugh :(
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Wicket uses commons-logging. I wonder whether glassfish doesn't have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p -
%-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously
right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have no
idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in
Wicket or
what it would involve. It's obviously going to involve me
reworking a
bunch of my existing code just to move to another
container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location for
log4j.properties
where glassfish will pick it up. usually it is in
war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
For whatever reason, I'm unable to supress this exception in
the
storefront application (where I really need it.) I've tried
wrapping
a try/catch around the assignment and retrieval of the SFSB
stub in
the custom Session class...I can't pull the bean data up w/o
the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so the
test
doesn't happen at all...so I can quit trying to find
work-arounds?
Even if my error supression did work, it's not a very elegant
solution
- it might be better if the serialization wasn't being tested
at all.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
Excellent, I'll move forward then and see how it
goes...thanks!
On 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:
that it just works is logical. It is just a test we try to
serialize
it so
that you get a warning if that is not possible because of a
non
serializeable object.
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, I've created a small test-app in Netbeans where I'm
using a
Wicket
page and have overridden ISessionFactory in the app class
to
create
a
session. I have a page where I call the stateful bean,
create
it
and
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
I've heard of it but am not familiar...I'll look into it.
I was going to make a lib project in eclipse or netbeans and build it
that way but realized there's probably a pile of dependencies I don't
have...won't that be an issue even w/ maven?
All the lib folders only contain clover
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
naaah use maven2
make the change in the src folder
type mvn package and you will have a .jar ready in the target dir
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
OK, checked it out and I made my changebut bare w/ me...I'm almost
completely unfamiliar w/ Ant and I figured that'd be the easiest way
to build it?
So, how do I build this sucker?
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
well, if it comes down to it just check out wicket, remove that portion
of
code, and deploy it that way
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
At 8:30 this morning...it's now 2:30pm here and I was the *last*
person to post to this forum at all...which is weird...it's normally
pretty busy.
http://forums.java.net/jive/thread.jspa?threadID=16673tstart=0
This is the first time I haven't gotten an answer to my problem on the
same day...they're *almost* as good as you guys! :)
On 7/6/06, Eelco Hillenius [EMAIL PROTECTED] wrote:
Did you try asking around on the glassfish list/ IRC channel (if
they
have one)?
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
I have no idea...but I'm lost at this point. I have both
commons-logging and log4j in the glassfish/lib folder because it
is a
requirement for using Hibernate as the persistence engine. I put
the
log4j.properties in there w/ the suggested entries and
restarted...the
error is the same - didn't work.
I tried deploying log4j in my war's /lib folder and packaging
log4j.properties in there...made no difference...I can't get the
exception message to change.
ugh :(
On 7/6/06, Matej Knopp [EMAIL PROTECTED] wrote:
Wicket uses commons-logging. I wonder whether glassfish doesn't
have
it's own weird logger factory, just like jetty does.
-Matej
Eelco Hillenius wrote:
In fact log4j.logger.wicket=INFO should be enough.
Eelco
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
log4j.debug=false
log4j.rootLogger=INFO
log4j.logger.org=INFO
log4j.logger.com=INFO
log4j.logger.net=INFO
log4j.logger.nl=INFO
log4j.logger.wicket=INFO
log4j.logger.wicket.protocol.http.HttpSessionStore=INFO
log4j.logger.org.apache.catalina.cluster=INFO
log4j.logger.wicket.version=INFO
log4j.logger.wicket.RequestCycle=INFO
logger.wicket.protocol.http=INFO
log4j.appender.Stdout=org.apache.log4j.ConsoleAppender
log4j.appender.Stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.Stdout.layout.conversionPattern=%-5p -
%-26.26c{1} - %m\n
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
paste your complete log4j.properties file
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED] wrote:
That's where I put it - nothing changed so you're obviously
right...it
won't make a difference anyways.
Hmm...this is bad...this puts me in a rough spot as I have
no
idea how
to use a spring like proxy and am not at all familiar w/
Springand in effect I'd have no idea how to do this in
Wicket or
what it would involve. It's obviously going to involve me
reworking a
bunch of my existing code just to move to another
container...which
shouldn't have been the case.
On 7/6/06, Igor Vaynberg [EMAIL PROTECTED] wrote:
you are doing it fine, you just have to find a location
for
log4j.properties
where glassfish will pick it up. usually it is in
war/web-inf/classes
-Igor
On 7/6/06, Vincent Jenks [EMAIL PROTECTED]
wrote:
For whatever reason, I'm unable to supress this exception
in
the
storefront application (where I really need it.) I've
tried
wrapping
a try/catch around the assignment and retrieval of the
SFSB
stub in
the custom Session class...I can't pull the bean data up
w/o
the
exception occuring, it would seem.
So again, is there a way to turn logging debugging off so
the
test
doesn't happen at all...so I can quit trying to find
work-arounds?
Even if my error supression did work, it's not a very
elegant
solution
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
On 06/07/06, Igor Vaynberg [EMAIL PROTECTED] wrote: so there are people out there not using log4j? :) I'm quite taken with Simple Log, myself! [https://simple-log.dev.java.net/] (It includes an CommonsLoggingAdapter for use with clogging.) /Gwyn Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] Testing Wicket 1.2 on Glassfish b48
Why would you want to make logging easy? :) If SUN had just adopted Log4J instead of IBM's kit like the whole world besides IBM asked them to do, we wouldn't have been in this mess. Eelco On 7/6/06, Gwyn Evans [EMAIL PROTECTED] wrote: On 06/07/06, Igor Vaynberg [EMAIL PROTECTED] wrote: so there are people out there not using log4j? :) I'm quite taken with Simple Log, myself! [https://simple-log.dev.java.net/] (It includes an CommonsLoggingAdapter for use with clogging.) /Gwyn Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
Re: [Wicket-user] SSL
Weird...I'm only getting the error in Jetty 6 (Beta17). wicket.WicketRuntimeException: Internal Error: Could not render error page class wicket.markup.html.pages.InternalErrorPage at wicket.request.compound.DefaultExceptionResponseStrategy.respond (DefaultExceptionResponseStrategy.java:109) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:76) at wicket.RequestCycle.step(RequestCycle.java :1000) at wicket.RequestCycle.steps(RequestCycle.java:1034) at wicket.RequestCycle.request(RequestCycle.java:453) at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:215) at javax.servlet.http.HttpServlet.service (HttpServlet.java:747) at javax.servlet.http.HttpServlet.service(HttpServlet.java:860) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:423) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter (ServletHandler.java:966) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:174) at org.springframework.web.filter.OncePerRequestFilter.doFilter (OncePerRequestFilter.java:77) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:957) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:353) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:226) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:567) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java :126) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:119) at org.mortbay.jetty.Server.handle(Server.java:248) at org.mortbay.jetty.HttpConnection.handlerRequest(HttpConnection.java :360) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:614) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:487) at org.mortbay.jetty.HttpParser.parseAvailable (HttpParser.java:197) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:288) at org.mortbay.jetty.nio.SelectChannelConnector$HttpChannelEndPoint.run(SelectChannelConnector.java:805) at org.mortbay.thread.BoundedThreadPool$PoolThread.run (BoundedThreadPool.java:475)Caused by: wicket.WicketRuntimeException: Already redirecting to 'https://localhost:8443/app'. Cannot redirect more than once at wicket.protocol.http.BufferedWebResponse.redirect (BufferedWebResponse.java:92) at wicket.protocol.http.WebRequestCycle.redirectTo(WebRequestCycle.java:225) at wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:60) at wicket.request.compound.DefaultResponseStrategy.respond (DefaultResponseStrategy.java:49) at wicket.request.compound.AbstractCompoundRequestCycleProcessor.respond(AbstractCompoundRequestCycleProcessor.java:66) at wicket.RequestCycle.respond(RequestCycle.java:905) at wicket.RequestCycle.step(RequestCycle.java:975) ... 23 moreOn 7/6/06, Johan Compagner [EMAIL PROTECTED] wrote:Redirect to a full url or use an ExternalLink (pointing to your own site but then with ssl)Do that redirect with a IRequestTarget.I don't know how you do it now but doing a redirect should always be donethrough request targets. johanOn 7/6/06, Joe Toth [EMAIL PROTECTED] wrote: How can I implement a way switch over to https?Depending on how the user navigates I need to swich over to https froma form submit.Every time I try a different way to implement thistransparently I receive Caused by: wicket.WicketRuntimeException:Already redirecting to '/app/Checkout'. Cannot redirect more thanonceAt first I tried to annotate a class with @RequiredSSL and created anew IResponseStrategy that would test if the request was secure, if not, WebResponse.redirect to the https version of the requested url.Second I tried to do the same in the constructor of my Base Class forall my pages and throw an AbortException, but I had the same problem. Any ideas?Also, are there any plans to add a https feature in 2.0 core or extensions?Thanks!Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___Wicket-user mailing listWicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web services, security?Get stuff done quickly with pre-integrated technology to make your job easierDownload IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___Wicket-user mailing listWicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user Using Tomcat but need to do more? Need to support web
[Wicket-user] I require Ajax TextArea
Dear users,
I have a situation where I need to get a value from a text area without
submitting the form. To do this I think Ajax is the perfect candidate,
but I cant get the value. How do I get that value from Ajax? Thanks for
the help in advance. I am using the following code:
import wicket.ajax.AjaxEventBehavior;
import wicket.ajax.AjaxRequestTarget;
import wicket.ajax.markup.html.AjaxFallbackLink;
import wicket.markup.html.WebPage;
import wicket.markup.html.form.Form;
import wicket.markup.html.form.TextArea;
import wicket.model.Model;
public class AutherizationPageSample extends WebPage{
private static final long serialVersionUID = 1887L;
SampleTextArea area;
String areaModel = Imran M Yousuf;
public AutherizationPageSample(){
area = new SampleTextArea(area);
area.setModel(new Model(areaModel));
AjaxFallbackLink link = new AjaxFallbackLink (link){
private static final long serialVersionUID = 9001L;
@Override
public void onClick(AjaxRequestTarget arg0) {
// TODO Auto-generated method stub
System.out.println(Value: + area.getValue());
System.out.println(Has Raw: + area.hasRawInput());
System.out.println(Raw In: + area.getRawInput());
System.out.println(Model Str: +
area.getModelObjectAsString());
System.out.println(Model Obj: +
area.getModelObject());
System.out.println(Latest: + area.getLatest());
}
};
add(new SampleForm(form));
add(link);
}
public class SampleForm extends Form{
private static final long serialVersionUID = 1011L;
public SampleForm(String arg0) {
super(arg0);
add(area);
}
public void onSubmit(){
System.out.println(Area Value: + area.getValue());
}
}
public class SampleTextArea extends TextArea{
private String latestText;
public SampleTextArea(String arg0) {
super(arg0);
add(new AjaxEventBehavior(onchange){
@Override
protected void onEvent(AjaxRequestTarget target) {
System.out.println(Changed +
getComponent().getModelObject());
}
});
}
public String getLatest(){
return Latest;
}
public String getLatestText(){
return latestText;
}
}
}
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
