What kind of errors are you seeing in the .jspf files?
It might be helpful to know that jspf files are generally not aware of the context that they may be used in. So if it references a variable that is declared in a JSP you know the fragment will be included in, the fragment is unaware of this and will generate problems from that.
> Hi David,
> What kind of errors are you seeing in the .jspf files?
There are two errors, each repeated:-
The function fn:substring is undefined Tail.jspf
/project/WebContent/WEB-INF/jsp line 14 JSP Problem
Type mismatch: cannot convert from boolean to String Head.jspf
/project/WebContent/WEB-INF/jsp line 95 JSP Problem
(Sorry that has wrapped rather badly).
Wherever they are used they work properly. In the first case it is accurate
to say that fn:substring is not defined in this file, as it happens it is
defined in the second file. In the second case when it compiles properly
it works, so I guess it is because it is undefined.
But I thought the point of the validation and the fragment files was that
only complete files (with their includes) should be checked, and the
fragments left along.
Do you have the preference unchecked for "Validate JSP fragments"? This is under Window > Preferences and then under Web > JSP Files > Validation. Once this option is disabled, doing a full validation should remove the problems.