Jsp 1.2 tags in weblogic 5.1?

Is there any patch to get JSP 1.2 tags to work in weblogic 5.1? I'm
          itching to play with the new standardized tag library under
          development thats been released on the Sun site. Unfortunately my
          company is using weblogic 5.1 and is not planning on moving anytime
          soon. What exactly about JSP 1.2 tags would not workn in the 5.1
          server?

Mike,
          WLS 5.1 only supports JSP 1.1. There is no patch available to get JSP
          1.2 tags to work. WLS 6.1 includes some features for JSP 1.2. For
          specifics on what is supported see:
          http://e-docs.bea.com/wls/docs61/notes/new.html#1047732
          Regards,
          Velvet
          Mike Lomage wrote:
          > Is there any patch to get JSP 1.2 tags to work in weblogic 5.1? I'm
          > itching to play with the new standardized tag library under
          > development thats been released on the Sun site. Unfortunately my
          > company is using weblogic 5.1 and is not planning on moving anytime
          > soon. What exactly about JSP 1.2 tags would not workn in the 5.1
          > server?

Similar Messages

Problem compling JSP with struts tags on Weblogic 8.1

I have deployed a web application in Weblogic 8.1. However, I am facing a problem while the JSPs are getting compiled. The JSPs ahve taglib declarations referring to Struts tag library files that are present in WEB-INF folder.
Stacktrace:
C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\myserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209: cannot resolve symbol
probably occurred due to an error in /approve/approve_home.jsp line 53:
<logic:notPresent name="<%=JobBean.ID%>" scope="request">
C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\myserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209: cannot resolve symbol
symbol : variable EVAL_BODY_BUFFERED
location: interface javax.servlet.jsp.tagext.BodyTag
if (_int0 == BodyTag.EVAL_BODY_BUFFERED) { //[ /approve/approve_home.jsp; Line: 53]
I believe other people have also faced this issue with Weblogic8.1 and struts. Any solutions???
Thx
KP

KP,
Does this code run in the development environment but not in production? How
was this code compiled?
- john
"KP" <[email protected]> wrote in message
news:405b9b56$[email protected]..
I have deployed a web application in Weblogic 8.1. However, I am facing aproblem while the JSPs are getting compiled. The JSPs ahve taglib
declarations referring to Struts tag library files that are present in
WEB-INF folder.
Stacktrace:
C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\m
yserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209:
cannot resolve symbol
probably occurred due to an error in /approve/approve_home.jsp line 53:
<logic:notPresent name="<%=JobBean.ID%>" scope="request">
C:\java\bea\user_projects\domains\mydomain\.\myserver\.wlnotdelete\extract\m
yserver_epgonline_epgonline\jsp_servlet\_approve\__approve_home.java:209:
cannot resolve symbol
symbol : variable EVAL_BODY_BUFFERED
location: interface javax.servlet.jsp.tagext.BodyTag
if (_int0 == BodyTag.EVAL_BODY_BUFFERED) { //[/approve/approve_home.jsp; Line: 53]
>
I believe other people have also faced this issue with Weblogic8.1 andstruts. Any solutions???
>
Thx
KP

Custom JSP Tags for Weblogic

Hi,
          I have several questions regarding this topic:
          1) Does Weblogic 5.1 supports Custom Tags ? If so, are there any known
          problems ?
          2) Does Weblogic come with any tag libraries (for loops, if, etc) and where
          can I get them ?
          3) Are there any tag libraries out there (JRun, for example) that have been
          successfully run on Weblogic ?
          Any help would be much appreciated.
          Thanks,
          Jamie


As there seems to be general interest, a link would probably be a great
          help.
          Regards
          Daniel Hoppe
          -----Original Message-----
          From: Michael Girdley [mailto:[email protected]]
          Posted At: Friday, August 25, 2000 8:03 AM
          Posted To: jsp
          Conversation: Custom JSP Tags for Weblogic
          Subject: Re: Custom JSP Tags for Weblogic
          Please see the documentation:
          http://www.weblogic.com/docs51/resources.html
          Michael Girdley
          BEA Systems Inc
          "Jamie" <[email protected]> wrote in message
          news:[email protected]...
          > Update
          > =======
          >
          > Weblogic Portal has some Tag libraries. I've downloaded the trial
          version
          > of
          > the Weblogic Commerce Server. How do I get the tag libraries and use
          them
          > on WL 5.1 ?
          >
          > Answers to original post still wanted
          >
          > Thanks,
          >
          > Jamie
          >
          > Jamie <[email protected]> wrote in message
          > news:[email protected]...
          > > Hi,
          > >
          > > I have several questions regarding this topic:
          > >
          > > 1) Does Weblogic 5.1 supports Custom Tags ? If so, are there any
          known
          > > problems ?
          > >
          > > 2) Does Weblogic come with any tag libraries (for loops, if, etc)
          and
          > where
          > > can I get them ?
          > >
          > > 3) Are there any tag libraries out there (JRun, for example) that
          have
          > been
          > > successfully run on Weblogic ?
          > >
          > >
          > > Any help would be much appreciated.
          > >
          > > Thanks,
          > >
          > > Jamie
          > >
          > >
          >
          >

[weblogic-9.1] JSP 2.0 tag file gets compiled but not reloaded

I am trying to use a JSP 2.0 tag file on weblogic 9.1. Everything works as expected until I reload the page after changing the tag file. Consider the following files, simple.jsp and simple.tag:
h5. /simple.jsp
<%@ page language="java" %>
<%@ taglib prefix="sandbox" tagdir="/WEB-INF/tags" %>
<html>
<body>
This output comes from the jsp.
<sandbox:simple>
</sandbox:simple>
</body>
</html>h5. /WEB-INF/tags/simple.tag
<%@ tag language="java" %>
<div>This output comes from a tag file
</div>The output of a call to simple.jsp is:
<html><head>
</head><body>
This output comes from the JSP.
<div>This output comes from a tag file</div>
</body></html>So far, so good. Now I change the content of simple.tag to
<%@ tag language="java" %>
<div>This output comes from *simple.tag*<div>On a new call to simple.jsp,
1. Weblogic notices that the file has been changed,
2. generates the TagHandler .java file
3. compiles the .java file
But the new class file seems not to be loaded by weblogic; the resulting HTML does not change. It is not a browser cache issue, as I can see Javelin compilation errors. E.g., changing the tag file content to
<%@ tag language="j" %>
<div>This output comes from simple.tag</div>leads to the following (expected) error:
Compilation of JSP File '/sandbox/simple.jsp' failed:
simple.tag:1:18: "j" is not a valid setting for the language attribute.
<%@ tag language="j" %>
^-^
Changes to the .jsp file are reflected in the HTML output.
Am I missing something? Is there any flag I have to set in my weblogic configuration?

You are right in saying that decoding has nothing to
do with rendering per se.I will go even further than Erik did, and dispute this statement.
Consider that you are generating an <input> tag for a text field. Among other things, you have to generate a "name" attribute. Who decides what to put there? The renderer that actually created the markup.
The "renderer" really does
two completely different things. But both should
nevertheless be separate from the component
implementation itself. You could still have the
renderer doing the decoding part, which arguably would
rarely change, and somehow delegate the actual
rendering to an implementation in a tag file.Whether you implement decoding in a separate class or inside the component, what request parameter name do you look for? It is not reasonable to assume that ALL possible renderers will choose the same parameter name ... hence, decoding and encoding are inextricably linked (the code doing the decoding has to know what kind of markup the code doing the encoding actually created). In JavaServer Faces, the current APIs create that linkage by requiring that the decode and encode be done by the same class (either the component, if you are not delegating, or the renderer if you are).
Craig

JSP in custom tag attributes...

Sirs,
          A very nice feature from a development perspective, would be the ability
          to use JSP code within custom tags. Say I have a page on which I wish
          to give all the information on a widget. Say further that I have
          implemented a tag that writes out all the info of a widget as HTML
          table. I would like to write something like this:
          <mytaglib:widgetTag widgetID="<%=request.getParameter("widget_id")%>"
          />
          As far as I know, in the current implementation of custom taglibs this
          does not seem to be possible. Instead you end up writing something like
          this:
          <mytaglib:widgetTag>
          <mytaglib:getWidget><%=request.getParameter("widget_id")%>"</mytaglib:getWidget>
          <mytaglib:displayWidget />
          </mytaglib:widgetTag>
          Which is much more like a scripting language than a heirarchical XML .
          Now, I could always just use the request object within the tag helper
          classes, but this gives up flexibility and can introduce security
          issues, and it also makes the tags much more difficult to work with...
          In short, we should push for JSP evaluation of tag attributes. Weblogic
          could leap ahead of other app servers in this area (making up for the
          custom tag performance issues, to be solve in sp6) and Sun would, once
          again, follow Weblogic's lead and rewrite the standard to include this
          functionality.
          Regards,
          Carson Gross


Carson,
          Perhaps the problem is that you are treating custom tags like one would
          construct an imperative language. I have never had to put Java or use beans
          or %= or even parameters to tags into a JSP because of custom tags.
          The real problem is writing/packaging/maintaining all those tags; sure could
          use a tool that did just that ;-)
          Peace,
          Cameron Purdy
          [email protected]
          http://www.tangosol.com
          WebLogic Consulting Available
          "Carson Gross" <[email protected]> wrote in message
          news:[email protected]...
          > Sirs,
          >
          > A very nice feature from a development perspective, would be the ability
          > to use JSP code within custom tags. Say I have a page on which I wish
          > to give all the information on a widget. Say further that I have
          > implemented a tag that writes out all the info of a widget as HTML
          > table. I would like to write something like this:
          >
          > <mytaglib:widgetTag widgetID="<%=request.getParameter("widget_id")%>"
          > />
          >
          > As far as I know, in the current implementation of custom taglibs this
          > does not seem to be possible. Instead you end up writing something like
          > this:
          >
          > <mytaglib:widgetTag>
          >
          >
          <mytaglib:getWidget><%=request.getParameter("widget_id")%>"</mytaglib:getWid
          get>
          >
          > <mytaglib:displayWidget />
          > </mytaglib:widgetTag>
          >
          > Which is much more like a scripting language than a heirarchical XML .
          > Now, I could always just use the request object within the tag helper
          > classes, but this gives up flexibility and can introduce security
          > issues, and it also makes the tags much more difficult to work with...
          >
          > In short, we should push for JSP evaluation of tag attributes. Weblogic
          > could leap ahead of other app servers in this area (making up for the
          > custom tag performance issues, to be solve in sp6) and Sun would, once
          > again, follow Weblogic's lead and rewrite the standard to include this
          > functionality.
          >
          > Regards,
          > Carson Gross
          >

Support for jsp:include page tag

Is there a support for the jsp:include page tag ?
I get an exception when trying to include jsp's
Thanks

Hi
I use a page with a one column template
I print a JSP that include another JSP using <jsp:include page="my_shopping_cart.jsp"
flush="true"/>
i get this exception :
java.lang.IllegalStateException: Can not set buffer size after writing data. at
com.bea.portlet.container.HttpServletResponseImpl.setBufferSize(HttpServletResponseImpl.java:179)
at weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:66) at
weblogic.servlet.jsp.PageContextImpl.(PageContextImpl.java:105) at weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:37)
at jsp_servlet._portlets._oci.__my_shopping_cart._jspService(my_shopping_cart.jsp)
at com.bea.portlet.jsp.PortletJspBase.service(PortletJspBase.java:110) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
at weblogic.servlet.jsp.PageContextImpl.include(PageContextImpl.java:155) at jsp_servlet._portlets._oci.__oci._jspService(oci.jsp:209)
at com.bea.portlet.jsp.PortletJspBase.service(PortletJspBase.java:110) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
at com.bea.portlet.container.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:98)
at com.cgi.poc.jsr168.MyAccountsPortlet.doView(MyAccountsPortlet.java:107) at
javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:208) at javax.portlet.GenericPortlet.render(GenericPortlet.java:137)
at com.bea.portlet.container.PortletStub.render(PortletStub.java:370) at com.bea.portlet.container.AppContainer.renderStub(AppContainer.java:501)
at com.bea.portlet.container.AppContainer.invokeRender(AppContainer.java:436)
at com.bea.portlet.server.PortletHttpServer.invoke(PortletHttpServer.java:218)
at com.bea.portlet.server.PortletHttpServer.process(PortletHttpServer.java:162)
at com.bea.portlet.server.PortletHttpServer.doGet(PortletHttpServer.java:119)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
at com.bea.netuix.servlets.controls.content.JavaPortletContent.fireRender(JavaPortletContent.java:246)
at com.bea.netuix.servlets.controls.content.JavaPortletContent.renderInternal(JavaPortletContent.java:146)
at com.bea.netuix.servlets.controls.content.JavaPortletContent.beginRender(JavaPortletContent.java:108)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:424) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:427)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172) at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:95)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:380) at com.bea.netuix.nf.UIControl.render(UIControl.java:580)
at com.bea.netuix.servlets.controls.PresentationContext.render(PresentationContext.java:341)
at com.bea.netuix.servlets.util.RenderToolkit.renderChild(RenderToolkit.java:123)
at com.bea.netuix.servlets.jsp.taglib.RenderChild.doStartTag(RenderChild.java:58)
at jsp_servlet._framework._skeletons._bellca.__gridlayout._jspService(gridlayout.jsp:29)
at com.bea.portlet.jsp.PortletJspBase.service(PortletJspBase.java:110) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:101)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:597)
at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:409)
at com.bea.netuix.servlets.controls.JspRenderer.renderAlt(JspRenderer.java:187)
at com.bea.netuix.servlets.controls.JspRenderer.beginRender(JspRenderer.java:90)
at com.bea.netuix.nf.ControlLifecycle$7.visit(ControlLifecycle.java:420) at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:427)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursiveRender(ControlTreeWalker.java:436)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:172) at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:220)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:158) at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:363)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:207) at com.bea.netuix.servlets.manager.PortalServlet.service(PortalServlet.java:584)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28) at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at com.bea.p13n.servlets.PortalServletFilter.doFilter(PortalServletFilter.java:313)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6316)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118) at
weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3622)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2569)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Subbu Allamaraju <[email protected]> wrote:
Could you please post more details of the exceptions?
Thanks
Subbu
Carl Samson said the following on 12/09/2003 01:15 PM:
Is there a support for the jsp:include page tag ?
I get an exception when trying to include jsp's
Thanks

Error while running JSP with custom tag

I am trying to run a jsp with a tag and I am getting the following error when I run the jsp:
"Unable to open taglibrary /WEB-INF/jsp/mytaglib.tld : Parse Error in the tag library descriptor: External parameter entity "%(DOCTYPE);" has characters after markup."
I have no idea what this is, can anyone help me here?
tx
-AB

Its difficult to tell without looking at your TLD file i.e. mytaglib.tld
However, a guess is that you may be refering to an invalid or otherwise corrupted DTD from your TLD.
Check that out.
The official DTD for TLDs in JSP 1.1 is http://java.sun.com/j2ee/dtds/web-jsptaglibrary_1_1.dtd
and the official DTD for TLDs in JSP 1.2 is http://java.sun.com/dtd/web-jsptaglibrary_1_2.dtd

JSP : Tiles Error �tag.getAsString� : component context is not defined

JSP : Tiles Error �tag.getAsString� : component context is not defined
I�m working with Struts 1.1 and Tiles, under Tomcat 5.0.16
My application works fine using Struts 1.1 alone, however, when attempting to run the application in a �Tiles� environment, I get an error:
�
javax.servlet.jsp.JspException: Error - tag.getAsString : component context is not defined. Check tag syntax
�
I have �defined� this in my �tiles-defs.xml� file, and as far as I can tell, everything else is configured properly (I have looked over the included Struts document examples, and others on the web, and I seem to have everything configured identically).
What am I missing???
I have created a series of �mostly� empty JSP files, for simplicity sake.
JSP FILES:
-     header.jsp
-     footer.jsp
-     menu.jsp
-     rootLayout.jsp
-     user.jsp
-     show_user.jsp
-     error.jsp
-     defaultContentPage.jsp
All JSP files contain:
<%@ taglib uri="/WEB-INF/lib/struts-tiles.tld" prefix="tiles" %>
and
�
<title>
<tiles:getAsString name="title"/>
</title>
�
My �tiles-defs.xml�: =================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE tiles-definitions PUBLIC
"-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
<tiles-definitions>

<definition name=".root.layout" path="/jsp/rootLayout.jsp" >
<put name="title" value="Default title"/>
<put name="header" value="/jsp/header.jsp"/>
<put name="menu" value="/jsp/menu.jsp"/>
<put name="content" value="/jsp/defaultContentPage.jsp"/>
<put name="footer" value="/jsp/footer.jsp"/>
</definition>


<definition name=".view.user" extends=".root.layout">
<put name="title" value="Welcome to the User Form."/>
<put name="content" value="/jsp/user.jsp"/>
</definition >

<definition name=".view.save" extends=".root.layout">
<put name="title" value="Welcome to the Show User Form."/>
<put name="content" value="/jsp/show_user.jsp"/>
</definition >

<definition name=".view.error" extends=".root.layout">
<put name="title" value="Error Message."/>
<put name="content" value="/jsp/error.jsp"/>
</definition >
</tiles-definitions>
My �struts-config.xml�: ==============================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE struts-config PUBLIC
"-//Apache Software Foundation//DTD Struts Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/struts-config_1_1.dtd">
<struts-config>

<form-beans>
<form-bean name="userForm" type="biz.seamrog.strutstest.model.state.UserForm"/>
</form-beans>

<action-mappings>


<action path="/user"
forward=".view.user">
</action>


<action path="/save"
type="biz.seamrog.strutstest.model.logic.SaveAction"
name="userForm" scope="request"
input="/jsp/user.jsp">
<forward name="success" path=".view.show_user"/>
<forward name="failure" path=".view.error"/>
</action>
</action-mappings>

<global-forwards>

<forward name="user" path=".view.user"/>
<forward name="show_user" path=".view.show_user"/>
<forward name="error" path=".view.error"/>
<forward name="cssBase" path="/stylesheets/common.css"/>
</global-forwards>


<plug-in className="org.apache.struts.tiles.TilesPlugin" >
<set-property property="definitions-config" value="/WEB-INF/tiles-defs.xml"/>
<set-property property="definitions-parser-validate" value="true" />
<set-property property="moduleAware" value="true" />
</plug-in>
</struts-config>
My �web.xml�: =====================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC '-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN' 'http://java.sun.com/dtd/web-app_2_3.dtd'>
<web-app>
<servlet>


<servlet-name>MyController</servlet-name>
<servlet-class>org.apache.struts.action.ActionServlet</servlet-class>

<init-param>
<param-name>config</param-name>
<param-value>/WEB-INF/struts-config.xml</param-value>
</init-param>

<init-param>
<param-name>definitions-config</param-name>
<param-value>/WEB-INF/tiles-defs.xml</param-value>
</init-param>

<init-param>
<param-name>application</param-name>
<param-value>ApplicationResource</param-value>
</init-param>

<load-on-startup>5</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>MyController</servlet-name>
<url-pattern>*.do</url-pattern>
</servlet-mapping>

<welcome-file-list>
<welcome-file>/jsp/user.jsp</welcome-file>
</welcome-file-list>

<taglib>
<taglib-uri>/WEB-INF/lib/struts-bean.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/struts-bean.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/lib/struts-html.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/struts-html.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/lib/struts-logic.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/struts-logic.tld</taglib-location>
</taglib>
<taglib>
<taglib-uri>/WEB-INF/lib/struts-tiles.tld</taglib-uri>
<taglib-location>/WEB-INF/lib/struts-tiles.tld</taglib-location>
</taglib>
</web-app>
My �rootLayout.jsp�: ================================================
<%@page contentType="text/html"%>
<%@ taglib uri="/WEB-INF/lib/struts-tiles.tld" prefix="tiles" %>
<html>
<header>
<title>
<tiles:getAsString name="title" />
</title>
<body>
<tiles:get name="header"/>
<tiles:get name="menu"/> <tiles:get name="content"/>
<tiles:get name="footer"/>
</body>
</html>

I found an entry in the Mail Archive for Struts. I got it working. My working code is below. You need to in the base JSP import the header and put the 'title' out to it.
tiles:def file:
<!DOCTYPE tiles-definitions PUBLIC
"-//Apache Software Foundation//DTD Tiles Configuration 1.1//EN"
"http://jakarta.apache.org/struts/dtds/tiles-config_1_1.dtd">
<tiles-definitions>
<definition name=".petstore.Base" path="/common/petstorecommon.jsp">
<put name="title" value ="${title}"/>
<put name="header" value="/common/header.jsp"/>
<put name="message" value="/common/message.jsp"/>
<put name="content" value="${content}"/>
<put name="navbar" value="/common/navbar.jsp"/>
</definition>
<definition name="petstore.Login" extends=".petstore.Base" >
<put name="title" value="Login Page" />
<put name="content" value="/Logon.jsp"/>
<put name="test1" value="test1value"/>
</definition>
base tile def:
<%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles"%>
<%@ page contentType="text/html;charset=windows-1252"%>
<html:html>
<head>
<html:base/>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<title>pet store common (jsp)</title>
</head>
<body>
<tiles:insert attribute="header">
<%-- both of these attributes are accessible from header.jsp It works!!! --%>
<tiles:put name="title" beanName="title" beanScope="tile" />
<tiles:put name="test1" beanName="test1" beanScope="tile" />
</tiles:insert>
<%-- <tiles:get name="header" /> --%>
<tiles:get name="message" />
<tiles:get name="content" />
<tiles:get name="navbar" />
</body>
</html:html>
Getting access to the title value in the header.jsp file:
<%@ taglib uri="/WEB-INF/struts-bean.tld" prefix="bean"%>
<%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html"%>
<%@ taglib uri="/WEB-INF/struts-logic.tld" prefix="logic"%>
<%@ taglib uri="/WEB-INF/struts-tiles.tld" prefix="tiles"%>
<html>
<head>
<tiles:getAsString name="title" />
<tiles:getAsString name="test1" />
</head>
<body>
</body>
</html>

JSPs using Custom Tag with Boolean attribute cannot compile

Hi,
In Oracle9iAS(9.0.3), a jsp using a tag extension, which has a Boolean attribute, caused the following compile error, although the jsp is valid in other web containers.
ERROR:
/opt/oracle/j2ee/home/application-deployments/simple/simple/persistence/_pages/_test.java:56: Method toBoolean(java.lang.Boolean) not found in class _test.
__jsp_taghandler_1.setExists( OracleJspRuntime.toBooleanObject( toBoolean( b)));
JSP:
<%@ page language="java" %>
<%@ page errorPage="error.jsp" %>
<%@ taglib prefix="jnpr" uri="/WEB-INF/testtag.tld" %>
<%
Boolean b = Boolean.valueOf("true");
%>
<jnpr:TestTag exists="<%= b%>"/>
The boolean value is <%= b %>
Tag Handler:
package defaultpak;
import javax.servlet.jsp.tagext.*;
import javax.servlet.jsp.*;
public class TestTag extends TagSupport{
private Boolean exists = null;
private java.lang.Boolean getExists() {
return exists;
public void setExists(java.lang.Boolean newExists) {
exists = newExists;
public int doStartTag() throws JspException {
return super.doStartTag();
Is this a known problem? Is there a way to get around this?
Thanks in advance.
Fred

This is a known issue with 903, fixed in coming 904.
In 903 the workaround is to use primitive type "boolean" instead of Object type "java.lang.Boolean" in user's getter and setter code for the taglib.
-Prasad

PageCheckSeconds (precompile jsp, stored in war file) (Weblogic 6.1)

Hi,
          I'm trying to stop the webserver from trying to recompile/check my jsp pages. I have set the pageCheckSeconds param to -1 but that doesn't seem to work. Looking at the weblogic.log file I get:
          [WebAppServletContext(601285,kcs,/kcs)] WorkflowServlet: init>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: init>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param verbose initialized to: true>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param packagePrefix initialized to: jsp_servlet>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param compilerclass initialized to: javac>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param srcCompiler initialized to weblogic.jspc>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param superclass initialized to weblogic.servlet.jsp.JspBase>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param workingDir initialized to: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param pageCheckSeconds initialized to: -1>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: initialization complete>
          [WebAppServletContext(601285,kcs,/kcs)] Generated java file: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs\jsp_servlet\__index.java>
          If I take out the jsp class files from the war file and set the param workingDir (weblogic.xml) to the directory where the jsp class files are located... it works. But now I have a packaging problem that I can easily solve by keeping the jsp class files within the war file. As you can see from the log messages above, the pageCheckSeconds value is set to -1... yet the checking occurred anyway. Is there a way to specify the name of the war file that is located within an EAR file using the workingDir param?
          Thanks
          David
          [att1.html]


You say: "If I take out the jsp class files from the war file and set the param workingDir (weblogic.xml) to the directory where the jsp class files are located... it works. "
          Did you get this to work in a cluster using admin/managed servers, or just with a single server?
          -Greg
          Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          www.oreilly.com/catalog/entjbeans3 or www.titan-books.com
          "David Kostiew" <[email protected]> wrote in message news:[email protected]...
          Hi,
          I'm trying to stop the webserver from trying to recompile/check my jsp pages. I have set the pageCheckSeconds param to -1 but that doesn't seem to work. Looking at the weblogic.log file I get:
          [WebAppServletContext(601285,kcs,/kcs)] WorkflowServlet: init>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: init>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param verbose initialized to: true>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param packagePrefix initialized to: jsp_servlet>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param compilerclass initialized to: javac>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param srcCompiler initialized to weblogic.jspc>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param superclass initialized to weblogic.servlet.jsp.JspBase>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param workingDir initialized to: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: param pageCheckSeconds initialized to: -1>
          [WebAppServletContext(601285,kcs,/kcs)] *.jsp: initialization complete>
          [WebAppServletContext(601285,kcs,/kcs)] Generated java file: C:\apps\bea\wlserver6.1\config\kces\applications\.wlnotdelete\wlap17684\WEB-INF\_tmp_war_kc_kc_kcs\jsp_servlet\__index.java>
          If I take out the jsp class files from the war file and set the param workingDir (weblogic.xml) to the directory where the jsp class files are located... it works. But now I have a packaging problem that I can easily solve by keeping the jsp class files within the war file. As you can see from the log messages above, the pageCheckSeconds value is set to -1... yet the checking occurred anyway. Is there a way to specify the name of the war file that is located within an EAR file using the workingDir param?
          Thanks
          David
          [att1.html]

Prob in working with jsp 2.0 tags fil

hi all
i am facing a prob working with jsp 2.0 tags files and hope to receive a possitive responce from your good self:-
<p>
how could i create a instance of a user defined class in a tags files .
<p>eg.
<tb:firsttag tableName="customer" className="createtable" packagename="package1">
<BR>
</tb:firsttag>
what code i have to write in tag file to create a object of class createtable </br>
thanks in advance, waiting for ur cooperation

I'm not sure I understand your question, but...
If you want to create a custom tag that will contain a body (data between the start and end tags) you will extend BodyTagSupport.
HTH.

Jsf 1s phase of life cycle how knows ths components of the jsp with jsf tag

i wish to know how faces servlet knows the jsp s view components while creaTI NG component tree at first request to input jsp which may have jsf tags.in the first phase faces servlet doesnot know input jsp with jsf tags what componnets it has. it is actually atthe response send or forward time which is the final phase when the tag ge executed and output is sent to client.i did understandin jsf life cycle in 1 st phase component tree is created at first request in 1 st phase .

Hi,
though a FacesContext holds the values used by a request, it doesn't mean it lives for as long as the request. The best explanation I found is from the JavaDocs
release
public abstract void release()
+Release any resources associated with this FacesContext instance. Faces implementations may choose to pool instances in the associated FacesContextFactory to avoid repeated object creation and garbage collection. After release() is called on a FacesContext instance (until the FacesContext instance has been recycled by the implementation for re-use), calling any other methods will cause an IllegalStateException to be thrown.+
The implementation must call setCurrentInstance(javax.faces.context.FacesContext) passing null to remove the association between this thread and this dead FacesContext instance.
Throws:
java.lang.IllegalStateException - if this method is called after this instance has been released
Frank

JSP 2.0 tags with JSF

Hi! I'm trying to mix jsf template with JSP 2.0 tag.
I almost did it, but still have some trouble.
MyForm.jspf:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib prefix="tmpl" tagdir="/WEB-INF/tags" %>
<tmpl:date bean="${MyForm}" property="date" />
date.tag
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ attribute name="bean" type="java.lang.Object" %>
<%@ attribute name="property" %>
<c:set var="form" value="${bean}" scope="session"/>
<c:set var="property" value="${property}" scope="session"/>
<f:subview id="time">
<h:inputText id="date" value="#{form[property]}">
<f:convertDateTime pattern="dd/MM/yyyy" />
</h:inputText>
because I have to use JSP EL (${MyForm}) to pass a parameter to the tag the managed bean is not initialized, submit fails for the first time, but works after the bean being initialized.
Again setting "property" to session scope otherwise it doesn't work, so I will have this during the session... I am lost in JSP EL/JSF EL context relation.
Does anyone use it???
Sincerely,
D.

I made a little improvement, but still have some questions...
MyForm.jspf:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ taglib prefix="tmpl" tagdir="/WEB-INF/tags" %>
<tmpl:date bean="ResidentAttentionForm" property="date" />
date.tag:
<%@ taglib uri="http://java.sun.com/jsp/jstl/core" prefix="c" %>
<%@ taglib uri="http://java.sun.com/jsp/jstl/fmt" prefix="fmt" %>
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
<%@ attribute name="bean" %>
<%@ attribute name="property" %>
<c:set var="bean" value="${bean}" scope="request"/>
<jsp:scriptlet>
javax.faces.context.FacesContext.getCurrentInstance().getApplication().getVariableResolver().resolveVariable(javax.faces.context.FacesContext.getCurrentInstance(), (String)request.getAttribute("bean"));
</jsp:scriptlet>
<c:set var="form" value="${sessionScope[bean]}" scope="session"/>
<c:set var="property" value="${property}" scope="session"/>
<f:subview id="time">
<h:inputText id="date" value="#{form[property]}">
<f:convertDateTime pattern="dd/MM/yyyy" />
</h:inputText>
The problem here:
1. how can I access from JSF EL to the tag attribute without passing it to the request??? (I've seen the question in the forum, but not the answer...)
2. Is there a way to initialize a bean with dynamic name (<c: set var="${name}"?
3. When we will have jsf 1.2 done? ;-) I know they said "with J2EE5", but it also has been said "J2EE5 - summer 2005" and now everyone is talking about 2006 (?). Why can't they make jsr for jsp 2.1 and jsf 1.2 before J2EE5?.
Sincerely,
D.

Unable to add Custom JSP 1.2 Tag Library to Project

I am trying to upgrade to a newer version of JDeveloper (10.1.3.0.4) but am having a problem with projects that use custom JSP tag libraries.
After converting the project (.jpr) files to the new version, I double click and go to "JSP Tag Libraries." When I click on "Add" to add a new JSP Tag library, only JSP version 1.1 libraries are shown, I cannot choose any JSP 1.2 tag libraries.
my TLD files are all JSP 1.2, so I am not quite sure why this isn't working in a newer JDeveloper after it has worked fine in the past. If I examine any JSP page that uses my taglibs, I see the following 2 kinds of error:
the line:
<%@ taglib uri="taglib.uri" prefix="mytag" %>
is underlined in red and says "the tag library taglib.uri is referenced, but not installed"
And for any lines that try to use the custom tag:
<mytag:dosomething>
there is a yellow/orange underline that says "no grammar available for namespace taglib.uri, contents of element dosomething cannot be validated"
Note that I can add the taglib JAR file under Tools > Manage Libraries, but I cannot add the JSP tag library to my project. Is there some sort of compatibility issue when transferring project files from an old version of JDeveloper?
Any help would be appreciated

Yes any new project I create I can specify JSP 1.2 or 2.0 with the wizard and it works fine.
But I don't want to re-create my entire project file again just to register my taglibs.
Here's the JSP related section in web.xml:

<taglib>
<taglib-uri>taglib.uri</taglib-uri>
<taglib-location>/WEB-INF/tlds/mytag.tld</taglib-location>
</taglib>
It's definately something in the project itself... but I am lost as to what it is.
Edit: nvm I fixed it. It was the web.xml. I had to change the line:
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
into
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
and it worked. Thanks.
Message was edited by:
user523020

How do I update JSPs without having to restart WebLogic?

How do I update JSPs without having to restart WebLogic? I have tried setting pageCheckSeconds to 0 in my weblogic.xml file. I have also tried setting Reload Period to 0 in the console. Please advise.


          Just bring up the Weblogic Console. Drill down to your webapp. De-select the Deploy
          option. Click on apply. Select the Deploy option and Click apply. Basically, Un-deploy
          and re-deploy your webapp.
          Later...
          - Wayne
          "cleve" <[email protected]> wrote:
          >which is here:
          >
          >http://e-docs.bea.com/wls/docs61////javadocs/weblogic/management/tools/WebAp
          >pComponentRefreshTool.html
          >
          >"Michael Young" <[email protected]> wrote in message
          >news:[email protected]..
          >> Try using the weblogic.refresh tool.
          >>
          >> regards,
          >> Michael
          >>
          >> Tony Nguyen wrote:
          >>
          >> > How do I update JSPs without having to restart WebLogic? I have tried
          >setting pageCheckSeconds to 0 in my weblogic.xml file. I have also tried
          >setting Reload Period to 0 in the console. Please advise.
          >>
          >> --
          >> Michael Young
          >> Developer Relations Engineer
          >> BEA Support
          >>
          >>
          >
          >

Jsp 1.2 tags in weblogic 5.1?

Similar Messages

Maybe you are looking for