- This topic has 1 reply, 2 voices, and was last updated 16 years, 1 month ago by
.
-
Posts
-
I’m not sure whether to post here or on the ‘Bugs’ forum. I’m using the Visual JSP Designer a lot but my frustration with it is it doesn’t really show properly how the pages are going to look like. The main cause of this is that it only properly resolves resources that are specified by a relative path, i.e. ../common/MyJSP.jsp and doesn’t recognize resources with a fully specified path, i.e. /context-path/common/MyJSP.jsp
This is so for JSP include statements and link statements. There’s an obvious problem using relative paths because when you have some JSP pieces that are reused a lot it depends on the directory location of the including page whether it will actually work when compiled or not. Same problem with style-sheets. And of course you only find out after deployment.
So I was hoping to hear whether we can look forward to supporting fully qualified paths in the visual designers any time? It would really help a lot.
Another thing I noticed is that the visual designer does at least attempt to include files included with the <%@include> statements but doesn’t do it when it’s specified as <jsp:include> I’m not even going to get started about tiles…
Mark
Mark,
Can you create a sample project that would help me replicate the issues you have pointed out and send it across so that I can attach it along with the bug report that I would be filing for the dev team. You can hit the “pm” button at the bottom of my post and send me the project.Thank you for your help.
