Jsp:include problem in custom tag

Question

I call <jsp:include page="emailbody.jsp" /> within a custom tag(in a file
          caller.jsp), which does emailing.
          When I invoke caller.jsp from browser, I do get the output(body of the
          email) on the browser screen, but not the output is not send as the body of
          the email.
          When I use static include namely, <@include file="emailbody.jsp" />, the
          output is directed to the body of the email.
          The above means, for a static jsp include file, it is parsed and included in
          the body-evaluation of the custom tag.
          For a dynamic include file, it is NOT parsed and NOT included in the
          body-evaluation of the custome tag.
          The reason could be, How Weblogic loads classes for custom-tag for dynamic
          include files.
          Can anybody at BEA throw loght on this and the solution.
          Thanks in advance.
          Chandra
          

Answer 1

Well I found out jsp:include is not supported inside custom tags for JSP
          spec 1.1.
          This was stated in section 5.4.5 of spec 1.1.
          May be in future spec 1.2.
          Thanks
          Chandra
          "Cameron Purdy" <[email protected]> wrote in message
          news:[email protected]...
          > Have you sent this to [email protected]?
          >
          > It sounds serious.
          >
          > Peace,
          >
          > --
          > Cameron Purdy
          > Tangosol, Inc.
          > http://www.tangosol.com
          > +1.617.623.5782
          > WebLogic Consulting Available
          >
          >
          > "matthew mcclain" <[email protected]> wrote in message
          > news:[email protected]...
          > > I have run into the same problem.
          > > I'm certain it's because CustomTags have their own buffer and
          > > jsp:include or pageContext.include() or requestDispatcher.include()
          > > all bypass the buffer and write to the underlying stream.
          > >
          > > I attempted to define jspx:include by wrapping the response object
          > > which is sent to requestDispatcher.include and then wrapping the
          > > OutputStream returned from the response with a stream which
          > > writes to the "out" of the pageContext for my tag.
          > >
          > > Unfortunately, I get a class cast exception because weblogic expects
          > > it's own class to be there as a ServletOutputStream:
          > >
          > > java.lang.ClassCastException:
          com.allmystuff.wif.IncludeServletResponse$1
          > > at
          > >
          >
          weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
          > > l.java:202)
          > > at
          > >
          >
          weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImp
          > > l.java:172)
          > > at com.allmystuff.wif.Include.doStartTag(Include.java:37)
          > >
          > > So any chance, jsp:include will get fixed?
          > >
          > > Thanks,
          > > Matthew McClain
          > > [email protected]
          > >
          > >
          > > "chandra" <[email protected]> wrote in message
          > > news:[email protected]...
          > > > I call <jsp:include page="emailbody.jsp" /> within a custom tag(in a
          > file
          > > > caller.jsp), which does emailing.
          > > > When I invoke caller.jsp from browser, I do get the output(body of the
          > > > email) on the browser screen, but not the output is not send as the
          body
          > > of
          > > > the email.
          > > > When I use static include namely, <@include file="emailbody.jsp" />,
          the
          > > > output is directed to the body of the email.
          > > >
          > > > The above means, for a static jsp include file, it is parsed and
          > included
          > > in
          > > > the body-evaluation of the custom tag.
          > > > For a dynamic include file, it is NOT parsed and NOT included in the
          > > > body-evaluation of the custome tag.
          > > > The reason could be, How Weblogic loads classes for custom-tag for
          > dynamic
          > > > include files.
          > > > Can anybody at BEA throw loght on this and the solution.
          > > > Thanks in advance.
          > > > Chandra
          > > >
          > > >
          > >
          > >
          >
          >