Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-06 Thread cknafl
I am trying some hacks now to get the application work well and I am looking forward to just have wicket in my application :) I don't even know why overriding getDefaultNameSpace(){ return "";} doesn't work. The resources js or css cannot be found anymore, so the will be searched in "/wicket/wicke

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-04 Thread Martin Grigorov
On Tue, Dec 4, 2012 at 10:29 AM, cknafl wrote: > I am currently overwriting getNamespace(). But that is really dirty. When I > make this method to return "" everytime, then my css, js and so on cannot > be > found anymore, that I added with renderHead(..). > So I implemented an if-else logic: > i

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-04 Thread cknafl
I am currently overwriting getNamespace(). But that is really dirty. When I make this method to return "" everytime, then my css, js and so on cannot be found anymore, that I added with renderHead(..). So I implemented an if-else logic: if(path.contains("resource") return "wicket"; ... Can you

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-04 Thread Martin Grigorov
On Tue, Dec 4, 2012 at 9:58 AM, cknafl wrote: > Could be a possibility. I am trying it right now, I have to overwrite > newUrlRenderer in RequestCycle but how do I set my own RequestCycle? > > What I do not understand is that this behavior changed from wicket1.4 to > wicket6. > I'm not sure that

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-04 Thread cknafl
Could be a possibility. I am trying it right now, I have to overwrite newUrlRenderer in RequestCycle but how do I set my own RequestCycle? What I do not understand is that this behavior changed from wicket1.4 to wicket6. When I call a page with mountpath(value="bla") then I get a URL like http://

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-03 Thread Martin Grigorov
Well, Wicket has no idea that you use Struts and even less where are the pages managed by Struts. What about the approach with UrlRenderer#renderContextRelativeUrl() ? On Mon, Dec 3, 2012 at 3:10 PM, cknafl wrote: > Yeah, that is working but that's in fact also a workaround. > > I don't want t

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-12-03 Thread cknafl
Yeah, that is working but that's in fact also a workaround. I don't want to mount all my pages. Or do I understand something wrong... My webapp has a login and should not have any mountpaths... (except of Loginpage itself). Kind Regards Christoph -- View this message in context: http://apache

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-11-30 Thread Martin Grigorov
https://issues.apache.org/jira/browse/WICKET-4870 It seems the problem is still unresolved. You have asked the same in a ticket. Did you try my proposals ? On Fri, Nov 30, 2012 at 2:04 PM, cknafl wrote: > I found nothing with struts and wicket... :( > > Maybe somebody knows the other topic, wh

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-11-30 Thread cknafl
I found nothing with struts and wicket... :( Maybe somebody knows the other topic, where the problem is solved? Or maybe somone could post the solution here again :) Regards Christoph -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Wicket-and-Struts-together-have-a

Re: Wicket and Struts together have a problem when not adding mountpath to the Wicket-Page

2012-11-30 Thread Martin Grigorov
I believe this question has been asked few weeks ago and we found the solution, no ? On Fri, Nov 30, 2012 at 9:07 AM, cknafl wrote: > Hi! > > We are having two frameworks for one project (wicket 1.4 and struts). Was > no > problem until now. > We want to migrate the whole client to wicket 6.2.