Current state of art: Inline Enclosure does not work properly when using wicket:extend and wicket:child
Hi, I refer the https://issues.apache.org/jira/browse/WICKET-3947 and ask is there any new fix (idea on fix) for this bug or is the mentioned workaround the best way to live with it? BR T.G.
about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
Websphere, i am currently testing our product in a war deployment with the latest wicket 1.4 code But i am still bumping against this with Websphere 8.0.2 was it really fixed? Do i need a setting somehow? It is really weird for example if this is the url http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/solution/RadioTest we send ../../?wicketurl which is correct because we should get: http://jcompagner-pc:9080/servoy/servoy-webclient/?wicketurl but what i get: http://jcompagner-pc:9080/?wicketurl weird thing is if i do this: http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/solution/RadioTest/a/b we send: ../../../../?wicketurl and then it works! But if i then play with it a bit http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/solution/RadioTest/a/b and then force that this is send: ../../../?wicketurl i get: http://jcompagner-pc:9080/servoy/servoy-webclient/solutions/?wicketurl so that is still correct, there is 1 less removed.. But now i remove another one: ../../?wicketurl then i get this: http://jcompagner-pc:9080/?wicketurl ??? so now it seems to only use the servlet path/context again! if i kill another: ../?wicketurl http://jcompagner-pc:9080/servoy/?wicketurl so it seems that if the relative url has context/servletpath up dirs (so 1 or 2 ../) then it sees it as the context/servletpath thing and if it is more so i have 3 times ../ it sees it as the whole url!! Is Websphere trying to be to smart??
Re: about webshere and relative url redirects: https://issues.apache.org/jira/browse/WICKET-3258
2012/2/6 Johan Compagner jcompag...@gmail.com: Websphere, i am currently testing our product in a war deployment with the latest wicket 1.4 code But i am still bumping against this with Websphere 8.0.2 was it really fixed? Do i need a setting somehow? I have been struggling with Websphere 6.1 for quite some time, and eventually sorted out the glitches and made it run wicket apps smoothly. There have been several so called custom properties to be set and several patches to be applied (which eventally ended up being part of FPs). Will give you complete details as soon as I gather them when I get to the office. There might have been something that relates to your particular case I thought it was only the company I work for that uses crappy WebSphere ;) and everyone else use decent application servers. regz, /dd -- /* Spelin donut mader if iz ina coment */
