We are using javacvs for Unix. It is GUI similar Wincvs, you can select "binary file"
option.
Damien Joldersma wrote:
> hahahah isn't that just the way these really annoying problems are? After
> working on this problem for like 2 days, and finally getting frustrated
> enough to write a letter, I solved it about 20 min after I wrote the letter.
>
> So just incase anyone else out there runs in to this problem be advised:
>
> "cvs add -kb" is WAY cooler for binary files than just "cvs add"!
>
> The problem was that the struts.jar file was checked into cvs on a linux box
> with out the -kb flag, then checked out with wincvs on the windows box, thus
> windows replaced all the newlines with carragie returns/line feed garbage
> and corrupted the file. So! Be warned, becareful when putting binary files
> into CVS!
>
> -Damien Joldersma
>
> -----Original Message-----
> From: Damien Joldersma [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 14, 2001 3:58 PM
> To: [EMAIL PROTECTED]
> Subject: Unable to open taglibrary /WEB-INF/tlds/struts-bean.tld : null
>
> Hello,
>
> We just started writing an application with tomcat and struts. Our
> developers are developing on both windows and linux. We're running into a
> problem on the windows side of things with the taglibrary jazz.
>
> The problem is namely that tomcat is upset and is throwing an exception when
> we make a call to loading the taglib:
>
> <%@ taglib uri="/WEB-INF/tlds/struts-bean.tld" prefix="bean" %>
>
> This line throws the following exception:
>
> org.apache.jasper.compiler.CompileException: <path snipped>/globals.jsp(5,0)
> Unable to open taglibrary /WEB-INF/tlds/struts-bean.tld : null
> at
> org.apache.jasper.compiler.JspParseEventListener.handleDirective(JspParseEve
> ntListener.java, Compiled Code)
> at
> org.apache.jasper.compiler.DelegatingListener.handleDirective(DelegatingList
> ener.java:116)
> at org.apache.jasper.compiler.Parser$Directive.accept(Parser.java, Compiled
> Code)
> at org.apache.jasper.compiler.Parser.parse(Parser.java, Compiled Code)
> at org.apache.jasper.compiler.Parser.parse(Parser.java:1042)
> at org.apache.jasper.compiler.Parser.parse(Parser.java:1038)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java, Compiled
> Code)
> at org.apache.jasper.servlet.JspServlet.doLoadJSP(JspServlet.java:462)
> at
> org.apache.jasper.servlet.JasperLoader12.loadJSP(JasperLoader12.java:146)
> at org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:433)
> at
> org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspSe
> rvlet.java:152)
> at
> org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja
> va:164)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java, Compiled
> Code)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
> at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404)
> at org.apache.tomcat.core.Handler.service(Handler.java:286)
> at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372)
> at
> org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79
> 7)
> at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743)
> at
> org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC
> onnectionHandler.java:210)
> at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java,
> Compiled Code)
> at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java,
> Compiled Code)
> at java.lang.Thread.run(Thread.java:479)
>
> We are using tomcat 3.2 and Struts 1.0.
>
> The same code and war file work fine under linux.
>
> It looks like there is some problem with the windows configuration. I've
> gone over the web.xml and have been unable to locate any problems
> (obviously!). Here is the relavent bit from web.xml
>
> <web-app>
> servlet
> servelt-mapping
> welcome-file-list
>
> <taglib>
> <taglib-uri>/WEB-INF/tlds/struts-bean.tld</taglib-uri>
> <taglib-location>/WEB-INF/tlds/struts-bean.tld</taglib-location>
> </taglib>
> </web-app>
>
> If I move the file out of the way, the error changes properly to one where
> the system cannot find the file specified, so I know it's finding the file.
> I thought it may have been like a case where newline/carrage return
> corruption and replaced it with a fresh tld from the struts zip file
> distribution, no luck.
>
> Does anyone know where the error is being thrown? Where can I track down
> what error is supposed to being thrown? Has anyone run into a null error
> while trying to open a taglib?
>
> Thanks in advance for any help!
>
> -Damien Joldersma
