Bug 224117 - JSP validator doesn't count coda and prelude tags
Summary: JSP validator doesn't count coda and prelude tags
Status: CLOSED DUPLICATE of bug 147098
Alias: None
Product: WTP Source Editing
Classification: WebTools
Component: jst.jsp (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: jst.jsp CLA
QA Contact: Nitin Dahyabhai CLA
URL: CSN 381248 2008
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2008-03-26 11:03 EDT by Stefan Dimov CLA
Modified: 2012-02-19 01:14 EST (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Dimov CLA 2008-03-26 11:03:34 EDT
If someone tries to build some JSF application she/he may want to use PRELUDE and CODA files to make headers and footers for all of her/his pages. This is achieved by adding some thing like this (more complex operations may also be used) into web.xml file:

    <jsp-property-group>
      <description>JSP configuration of all the JSP's </description>
      <url-pattern>*.jsp</url-pattern>
      <include-prelude>/common-jsps/prelude.jspf</include-prelude>
      <include-coda>/common-jsps/coda.jspf</include-coda>
    </jsp-property-group>

   When using these files as headers and footers for JSF/JSP pages, it's correct that the PRELUDE contains all taglib imports plus opening <HTML> and <BODY> tags while the CODA contains ending </BODY> and </HTML> tags. This means that you do NOT place these tag into your JSP/JSF pages.

    The problem is that Eclipse gives compile errors on just about every page! On the PRELUDE file - because the <HTML> and <BODY> tags are not ended; on the CODA file - because the </BODY> and </HTML> tags exist without the opening tags; on all other pages because they do not have the required imports for the JSP/JSF elements (these are in the PRELUDE file).

    It would be good if the JSP validator takes into account all the PRELUDE and CODA files included and avoid annoying and unnecessary errors.
Comment 1 Raghunathan Srinivasan CLA 2008-03-26 11:41:56 EDT
This looks like a JSP issue. Copying Nitin.
Comment 2 Radoslav Tsiklovski CLA 2009-07-21 09:17:26 EDT
Could the fix be targeted for WTP 3.1.1?
Comment 3 Mike Youngstrom CLA 2010-07-14 16:46:55 EDT
I'm experiencing this issue as well....would be great to have a fix.
Comment 4 Yury Kats CLA 2010-07-15 18:12:48 EDT
This looks misplaced in JSF product. Like comment 1 suggests, this appears to be a general JSP issue.
Comment 5 Raghunathan Srinivasan CLA 2010-07-16 14:18:54 EDT
Moving it to the right component
Comment 6 Nitin Dahyabhai CLA 2012-01-03 07:48:33 EST
Stefan, do you have an example project showing this that you can attach (and that we can be turn into a test)?
Comment 7 Nitin Dahyabhai CLA 2012-02-19 01:14:53 EST

*** This bug has been marked as a duplicate of bug 147098 ***