Re: wicket on Weblogic 10.3.1
Dear All, Solved now; describing the solutin now for future if anybody suffers from the same; the page expired exceptions are caused by the JSESSIONID, which got mixed up with the Tomcat's JSESSIONID. The best option is to use a different cookie with WebLogic when testing the same app on WebLogic and Tomcat. Just put this to weblogic.xml: session-descriptor cookie-nameWEBLOGIC_JSESSION_ID/cookie-name /session-descriptor Cheers, Zoltan zoltan luspai wrote: Dear All, Thanks for the help so far; one of my problem was indeed a misconfig in the dns (hosts file), funny that tomcat worked that way. The next problem was -solved now- that the ajax requests did not work at all, because weblogic is always adding index.jsp into the ajax urls, so they will look like /contextpath/index.jsp?wicket:interface=... instead of the correct /cb/?wicket:interface=:. This happens because the wicket filter is mounted on /* and there is no welcome-file-list in the web.xml. The fix is to add this to web.xml: welcome-file-list welcome-file//welcome-file /welcome-file-list Now, my problem is that the ajax calls always respond with page-expired exception. Any hints on that? Thanks, Zoltan Edward Zarecor wrote: When you start up what ports and addresses does Weblogic say it's listening on: grep for is now listening I'd recommend capturing the headers with live headers or something similar and seeing what differs between access via localhost and 127.0.0.1. That those differ suggests a DNS/hosts issue to me. Ed. On Tue, Nov 24, 2009 at 9:06 AM, zoltan luspai zlus...@gmail.com wrote: I'm going directly to weblogic, which is running locally all configured to default, it is all on the same host, no apache and no proxies in between. Z Edward Zarecor wrote: Are you using Apache with the Weblogic plugin? If so, do you see the same behavior if you go directly against Weblogic? Can you confirm that subsequent requests are actually being handled by the app server? I ask because we've seen cases where URL mangling caused requests that should have mapped to our wicket app not being properly proxied by the Weblogic plugin. The result was an Apache error as it couldn't handle the request itself and wasn't forwarding it. Ed. On Tue, Nov 24, 2009 at 4:11 AM, zoltan luspai zlus...@gmail.com wrote: Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - 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 - 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: wicket on Weblogic 10.3.1
Dear All, Thanks for the help so far; one of my problem was indeed a misconfig in the dns (hosts file), funny that tomcat worked that way. The next problem was -solved now- that the ajax requests did not work at all, because weblogic is always adding index.jsp into the ajax urls, so they will look like /contextpath/index.jsp?wicket:interface=... instead of the correct /cb/?wicket:interface=:. This happens because the wicket filter is mounted on /* and there is no welcome-file-list in the web.xml. The fix is to add this to web.xml: welcome-file-list welcome-file//welcome-file /welcome-file-list Now, my problem is that the ajax calls always respond with page-expired exception. Any hints on that? Thanks, Zoltan Edward Zarecor wrote: When you start up what ports and addresses does Weblogic say it's listening on: grep for is now listening I'd recommend capturing the headers with live headers or something similar and seeing what differs between access via localhost and 127.0.0.1. That those differ suggests a DNS/hosts issue to me. Ed. On Tue, Nov 24, 2009 at 9:06 AM, zoltan luspai zlus...@gmail.com wrote: I'm going directly to weblogic, which is running locally all configured to default, it is all on the same host, no apache and no proxies in between. Z Edward Zarecor wrote: Are you using Apache with the Weblogic plugin? If so, do you see the same behavior if you go directly against Weblogic? Can you confirm that subsequent requests are actually being handled by the app server? I ask because we've seen cases where URL mangling caused requests that should have mapped to our wicket app not being properly proxied by the Weblogic plugin. The result was an Apache error as it couldn't handle the request itself and wasn't forwarding it. Ed. On Tue, Nov 24, 2009 at 4:11 AM, zoltan luspai zlus...@gmail.com wrote: Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - 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 - 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
wicket on Weblogic 10.3.1
Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket on Weblogic 10.3.1
We've had no problems on our implementation. Even session replication works as expected. What is your stack? Are you doing stick sessions? Have you enabled session replication? -- View this message in context: http://old.nabble.com/wicket-on-Weblogic-10.3.1-tp26492655p26495578.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket on Weblogic 10.3.1
Are you using Apache with the Weblogic plugin? If so, do you see the same behavior if you go directly against Weblogic? Can you confirm that subsequent requests are actually being handled by the app server? I ask because we've seen cases where URL mangling caused requests that should have mapped to our wicket app not being properly proxied by the Weblogic plugin. The result was an Apache error as it couldn't handle the request itself and wasn't forwarding it. Ed. On Tue, Nov 24, 2009 at 4:11 AM, zoltan luspai zlus...@gmail.com wrote: Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - 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: wicket on Weblogic 10.3.1
Hi, Nothing fancy like that; no replication, just a simple localhost installation for development and testing. The stack is a bit of a weird mix, mostly legacy jsp/struts pages, decorated using sitemesh, plus few wicket pages yet also decorated by sitemesh (plus some hacking to include jsp fragments; don't ask ;-). What I see now that if I use the http://localhost:7001/x; url then any POST request will just fail, for example validation of some component is not called, but if I use the ip address like http://127.0.0.1/x; urls then it is just fine. Any hints on that? The same stuff is fine with tomcat. Btw; I'm on linux and localhost corretly resolves to 127.0.0.1. Cheers ( and sorry if that goes off-topic ) Zoltan Doug Leeper wrote: We've had no problems on our implementation. Even session replication works as expected. What is your stack? Are you doing stick sessions? Have you enabled session replication? - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket on Weblogic 10.3.1
I'm going directly to weblogic, which is running locally all configured to default, it is all on the same host, no apache and no proxies in between. Z Edward Zarecor wrote: Are you using Apache with the Weblogic plugin? If so, do you see the same behavior if you go directly against Weblogic? Can you confirm that subsequent requests are actually being handled by the app server? I ask because we've seen cases where URL mangling caused requests that should have mapped to our wicket app not being properly proxied by the Weblogic plugin. The result was an Apache error as it couldn't handle the request itself and wasn't forwarding it. Ed. On Tue, Nov 24, 2009 at 4:11 AM, zoltan luspai zlus...@gmail.com wrote: Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - 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
Re: wicket on Weblogic 10.3.1
Hmmm...a very strange stack indeed so I won't ask ;-) So urls with 127.0.0.1 work...correct? but if you initially access via localhost it doesn't? Do you have WL configured as a named virtual server by chance? Are you seeing generated urls being bounced back and forth between localhost and 127.0.0.1 when you access via localhost? If so, this may cause your session information to be lost when bouncing back/forth as 'domain name' (i believe) is used for your session key (via cookies). You can't access cookies from a different domain. -- View this message in context: http://old.nabble.com/wicket-on-Weblogic-10.3.1-tp26492655p26498557.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket on Weblogic 10.3.1
try taking sitemesh out of the picture and see if that helps. i remember postings on this list a long time ago about sitemesh messing up wicket. -igor On Tue, Nov 24, 2009 at 6:00 AM, zoltan luspai zlus...@gmail.com wrote: Hi, Nothing fancy like that; no replication, just a simple localhost installation for development and testing. The stack is a bit of a weird mix, mostly legacy jsp/struts pages, decorated using sitemesh, plus few wicket pages yet also decorated by sitemesh (plus some hacking to include jsp fragments; don't ask ;-). What I see now that if I use the http://localhost:7001/x; url then any POST request will just fail, for example validation of some component is not called, but if I use the ip address like http://127.0.0.1/x; urls then it is just fine. Any hints on that? The same stuff is fine with tomcat. Btw; I'm on linux and localhost corretly resolves to 127.0.0.1. Cheers ( and sorry if that goes off-topic ) Zoltan Doug Leeper wrote: We've had no problems on our implementation. Even session replication works as expected. What is your stack? Are you doing stick sessions? Have you enabled session replication? - 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: wicket on Weblogic 10.3.1
I am running two Wicket applications on WebLogic 10.3 on a Unix machine in a bank. One application is based on Wicket 1.3.7, the other application is based on Wicket 1.4.3. So far, everything is running fine. Best regards, giovanni Resources are limited, Imagination is unlimited. From: zoltan luspai zlus...@gmail.com To: users@wicket.apache.org Sent: Tue, November 24, 2009 10:11:51 AM Subject: wicket on Weblogic 10.3.1 Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket on Weblogic 10.3.1
When you start up what ports and addresses does Weblogic say it's listening on: grep for is now listening I'd recommend capturing the headers with live headers or something similar and seeing what differs between access via localhost and 127.0.0.1. That those differ suggests a DNS/hosts issue to me. Ed. On Tue, Nov 24, 2009 at 9:06 AM, zoltan luspai zlus...@gmail.com wrote: I'm going directly to weblogic, which is running locally all configured to default, it is all on the same host, no apache and no proxies in between. Z Edward Zarecor wrote: Are you using Apache with the Weblogic plugin? If so, do you see the same behavior if you go directly against Weblogic? Can you confirm that subsequent requests are actually being handled by the app server? I ask because we've seen cases where URL mangling caused requests that should have mapped to our wicket app not being properly proxied by the Weblogic plugin. The result was an Apache error as it couldn't handle the request itself and wasn't forwarding it. Ed. On Tue, Nov 24, 2009 at 4:11 AM, zoltan luspai zlus...@gmail.com wrote: Hi All, Anybody has experience with wicket running on Weblogic 10.3.1? Any hints about? I'm having some problem with that wicket pages does not seem to handle page events properly, for example the first render of the page is fine, but if I click on a button that does not seem to go to the next page. Sorry for being foggy here; the thing is being investigated now... Thanks, Zoltan - 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 - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
