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 We
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 the
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
are limited, Imagination is unlimited.
From: zoltan luspai
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&#
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 wrote:
> Hi,
>
>
> Nothing fancy like that; no replication, just a simple localhost
> installation
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
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 Weblogi
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 f
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
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
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 n
11 matches
Mail list logo
