I would do a couple of things here.

First, there is a version of Struts in the WebLogic core.  In order to
ensure that your app uses the version of Struts you need to, you'll need
to specify "prefer-web-inf-classes" in your weblogic.xml (set to true).

Second, there is never any need to independently deploy TLD files, OR
specify "taglib" elements in your "web.xml" file.  If your JSP specifies
the correct URI in the taglib directive (which is specified in the TLD
stored in the struts jar file), it will find the TLD in the deployed
taglib jar file.  It's always better to reduce the number of "moving
parts".  Similarly, if your taglib directive specifies the URI from the
embedded TLD, you also don't need the "taglib" elements in the web.xml
file.

> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Laurie Harper
> Sent: Friday, September 08, 2006 11:53 AM
> To: user@struts.apache.org
> Subject: Re: Problem while deploying on Weblogic
> 
> Asthana, Rahul wrote:
> > Hi All,
> > I am trying to deploy a struts 1.2.4  application on 
> WebLogic Server 8.1 SP3.
> > The application deploys correctly on tomcat.The exception I 
> am getting 
> > on Weblogic is this- Parsing of JSP File '/admin.jsp' failed:
> > /admin.jsp(3): Error in using tag library 
> > uri='/WEB-INF/struts-html.tld' prefix='html': The Tag class 
> 'org.apache.struts.taglib.html.CheckboxTag' has no setter 
> method corresponding to TLD declared attribute 'errorKey', 
> (JSP 1.1 spec, 5.4.1) probably occurred due to an error in 
> /admin.jsp line 3:
> > <%@ taglib uri="/WEB-INF/struts-html.tld" prefix="html" %>
> 
> My guess would be that the TLD files you have deployed are 
> out of sync with the version of Struts you're using. Make 
> sure they are the correct versions or, better yet, remove 
> them (and any references to them in web.xml), since the 
> container should find the right version bundled in struts.jar 
> that way.
> 
> L.
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

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

Reply via email to