I think this is addressed in the 7.4 <c:import> section of the JSTL 1.0 Spec. There's an explanation of how errors are handled for internal vs. external resources. Give it a look and see if it helps.

James Watkin wrote:

There seems to be an inconsistent behavior in the way <c:import> throws errors for non-existent files. When the <c:import> url attribute is an in-context-jsp (like pageHeader.jsp) that doesn't exist, no error is thrown. However, when the url attribute is a "file:" that doesn't exist, an error is thrown. Can anyone confirm, or explain this behavior?

I'm using the following pattern:

<c:catch var="importError">
    <c:import url="${param.pageURL}"/>
</c:catch>
<c:if test="${not empty importError}">
    <c:out value="${importError.message}"/>
</c:if>

Thank you.

- Jim

______________________________
James Watkin
ACIS Software Development
The Anderson School at UCLA
[EMAIL PROTECTED]
Voice: 1-310-825-5030
  Fax: 1-310-825-4835
______________________________

-- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to