Re: Getting Page Expired in Glassfish but not in Jetty
Hi, Check that session cookies are not mixed up between the application servers. I had PageExpired exceptions when testing the same application on the very same browser with WebLogic and Tomcat, and that was caused by that both servers are using the JSESSIONID cookie, but with different paths, so actually there was two JSESSIONID cookies appearing in the browser. And because wrong cookie was picked up the session was always recreated, which was causing PageExpired exceptions. The easy solution was to configure WebLogic to use an other cookie name, and after that everything worked fine. For testing just clear the cookies in your browser before/when switching between app servers. Cheers, Zoltan Early Morning írta: Well yes, ideally, but it is easier to not use such a heavy appserver when developing, so we make do with an internal QA deployment on Glassfish :) In any case, I was more wondering about the differences between how appservers handle wicket page versions and the like, since I'd like to understand why such differences exist. In any case, I'll check for serialization errors first. Thanks! Regards, Ces On Thu, Dec 10, 2009 at 5:52 AM, b...@actrix.gen.nz wrote: Hi, It is usually easier to have identical development and production platforms. If then you get an error as you describe, you usually catch it in development before it reaches production. So why don't you develop with GlassFish? Bernard On Thu, 10 Dec 2009 02:36:49 +0800, you wrote: Hi all, Currently I have a problem with my application wherein when I press the Back button of the browser and navigate to a new page, I get a Page Expired error consistently. However, this only happens when my application is deployed in Glassfish, but not when I run it using Jetty. Any suggestions for what I should check? Related to that, I also experienced an error wherein there was a target.add(form) in the onSubmit method of the button, which caused an Exception in Glassfish whenever the feedback panel within the form was added because the page could not be constructed; however In Jetty, the same code caused no errors. The fix (removing target.add(form)) was simple enough, but I was hoping someone could enlighten me regarding how different appservers handle wicket page versions, etc. Is there a resource I can look up for this? Thanks! Regards, Ces - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Date Picker in Editable TreeTable in IE7 and IE8
Hi,
Try to play with z-index css value; increase it, and it should bring the
calendar control above the other parts of the table. We are also using
the YUI calendar widget inside a table, see this page on JavaForge:
http://www.javaforge.com/proj/tracker/submitNew.do?tracker_id=5407.
(Sorry guys for showing a struts page here ;-).
The calendar markup is wrapped in a span
class=calOuterContainer.../span. The relevan css is:
/* relative puts the calendar where the container is on screen */
.calOuterContainer {
position: relative;
z-index:20;
/* holy hack for IE6 scrollbar bug on relative positioned controller
see: http://www.positioniseverything.net/explorer/unscrollable.html
*/
height: 1%;
}
I hope that helps,
Zoltan
John MacEnri írta:
Rolling my own seems like a pretty heavyweight solution. The control for the
most part is fine. (Though the lack of any year change ability is a
significant drawback)
What I'm trying to find out is whether anyone else is having any trouble
with the YUI datepicker in IE7 or IE8 when used within a Table or TreeTable.
Thanks
John
2009/10/10 Igor Vaynberg igor.vaynb...@gmail.com
you can always roll your own datepicker if the YUI one does not work
properly.
-igor
On Fri, Oct 9, 2009 at 5:13 PM, John MacEnri john.mace...@gmail.com
wrote:
Hi,
I'm new to Wicket this week, so not familiar with the expected format or
structure of emails to this mailing list.
I picked Wicket after trawling around for a framework that would enable
UI
programming on the Web make sense again. It's been an absolute pleasure
so
far. Compared to the pain I've felt for some time now battling with web
application frameworks where most of the code of the applications was in
XML, JS, JSP etc. etc. and a light sprinkling of actual Java, the
elegance
of Wicket as a natural UI programming environment makes everything seem
possible and even enjoyable again. Thanks.
But, (there always is a but:-) ), I'm struggling with an issue I've hit
with
the DatePicker and can't seem to resolve it.
I'm using Wicket 1.4.1.
I used the Editable TreeTable example from the Wicket site as a starter
for
the very small app I needed to write.
Rather than just text editable columns though, I'm making them more type
specific, so one of them is for Dates and shows a DateTextField and a
DatePicker.
The app is working fine in Firefox but the DatePicker is always caught
behind the rows above and below when I run the app in IE7 or 8.
The attached screen snippets show the difference. I've dug deep into the
css
and used the developer tools in IE8 which give you something akin to
Firebug
but couldn't find any css change would fix it.
Is there a way to fix this or an alternative date picker?
Thanks
John
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
