Originally posted by Roland Barcia:
Are you precompiling JSP files?
Yes, I am. But, as Kyle mentioned, this is not the issue. The errors are validation errors.
Originally posted by Kyle Brown:
You should be able to do that by creating a tasks filter that only displays errors in a particular working set that does NOT contain that folder, but contains the rest of your project. No guarantees that this will work, but it's certainly worth a try.
Kyle
Hi Kyle!
Thanks for the tip. I don't know why I did not think of that.
I don't want any type of validation to be done idealy on the files, but your tip is what I was lookig for.
Oh yes, I meant validation errors and not compile errors. Sorry for the confusion. Sometimes, you think something but you write something else.
For now, renaming the jsp fragments to .asp works great for both WSAD and Dreamweaver. No other extension works so well for both. WSAD performs no validation check on the .asp files and Dreamweaver renders the includes appropriately.
All the fragments in question are translation time includes. They are part of a few Dreamweaver templates I have developed.
Thanks guys!
[ May 12, 2004: Message edited by: Brahim Bakayoko ]
SCJP, SCWCD, SCBCD, IBM CSD WebSphere v5, <br />A+, MCP 2000 and 2000 server, CST, and few incompleted certification tracks.<br /> <br />Ivory Coast<br /> <br />Analyze your web Request/Response @ <a href="http://webtools.servehttp.com" target="_blank" rel="nofollow">http://webtools.servehttp.com</a> down for a while...