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-name>WEBLOGIC_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
