Tak wrote: > > Hello, > We recently moved to WebLogic and and I'm seeing an error message > deploying the example page for the request taglib. The same example works > wonderfully in Tomcat. In reading this list, it seems that WL is a bit more > stringent about what you can and can't do. > > The datetime taglib works ok, it looks like WebLogic is whining about the > looping constructs that use that try and use the jspGetProperty to reference > the taglib. > > However, I can't seem to see what sort of deployment problem I'm running > into. Any pointers? To me it looks like WebLogic is not spec compliant. It seems to require a <jsp:useBean> action to define each bean used by <jsp:getProperty> actions in the same page. That is *not* a requirement, according to the JSP 1.1 spec. The spec only says that the name attribute in <jsp:getProperty> must be the name of a bean created by some other action in the page, using the <jsp:useBean> action as an example. In this case it's created by the <req:cookies> action, and that should work equally fine. I suggest you report this as a bug to BEA. It's the only way we will ever get the vendors to implement the spec correctly, and get the promise of vendor independent applications. Hans > ---------------------------- > Error message: > ---------------------------- > > Parsing of JSP File '/pages/request.jsp' failed: > > /pages/request.jsp(18): oatmeal is not defined as bean > probably occurred due to an error in /pages/request.jsp line 18: > Cookie name: <jsp:getProperty name="oatmeal" property="name"/> > > ---------------------------- > here's the JSP page, fresh from CVS --- request.jsp - > ---------------------------- > > <%@ taglib uri="http://jakarta.apache.org/taglibs/request" prefix="req" %> > > Cookies received with request: > <req:cookies id="oatmeal"> > > Cookie name: <jsp:getProperty name="oatmeal" property="name"/> > Comment: <jsp:getProperty name="oatmeal" property="comment"/> > Domain: <jsp:getProperty name="oatmeal" property="domain"/> > MaxAge: <jsp:getProperty name="oatmeal" property="maxAge"/> > Path: <jsp:getProperty name="oatmeal" property="path"/> > Secure: <jsp:getProperty name="oatmeal" property="secure"/> > Value: <jsp:getProperty name="oatmeal" property="value"/> > Version: <jsp:getProperty name="oatmeal" property="version"/> > </req:cookies> > > ---------------------------- > Here's my web.xml deployment file as stored in myApp/WEB-INF/web.xml > ---------------------------- > > web.xml - > <taglib> > <taglib-uri>http://jakarta.apache.org/taglibs/request</taglib-uri> > <taglib-location>/WEB-INF/request.tld</taglib-location> > </taglib> > > ---------------------------- > It appears that the CookiesTag.java is placing the ID in pageContext, and the > TEI file looks like it's got the ID structure in place. > ---------------------------- > > doStartTag(...) { > ... > pageContext.setAttribute(id,this,PageContext.PAGE_SCOPE); > ... > } > > ---------------------------- > and > ---------------------------- > > new VariableInfo(data.getAttributeString("id"), > "org.apache.taglibs.request.CookiesTag", > true, > VariableInfo.NESTED > ), > > ---------------------------- > Even the BEA docs say this should be supported. > ---------------------------- > > http://edocs.bea.com/wls/docs60/taglib/handler.html#359297 > > Dynamically Named Scripting Variables > [ text snipped ] > > ---------------------------- > > And it works in Tomcat. So that makes me think it's a deployment issue, but > I can't find it. What am I missing? > > -tak > > -- Hans Bergsten [EMAIL PROTECTED] Gefion Software http://www.gefionsoftware.com Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com