We have been looking into multiple JSP enginges and we noticed that only OrionServer implements <jsp:include> in a way that makes sence. Most of other engines simply output the results of <jsp:include> directly to the ServletResponse output stream (as JSP 1.1 spec indicates). Orion, however, tends to honor the current nesting of BodyContext (multiple nested custom tags). I was wondering if this was an oversight, or by design. I hope this feature does not go way in favor of a "braindead" spec compliant implementation. Thanks. Sergio __________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/
