java.lang.SecurityException: sealing violation
Hi, I use tomcat 3.2 and try to read a xml file throught a servlet but i recieve this error : java.lang.Exception: Exception occurred: java.lang.SecurityException: sealing violation at lds.utils.XMLManager.loadXML(XMLManager.java:168) at lds.utils.XMLManager.loadXML(XMLManager.java:183) at lds.servlets.OdataControllerServlet.init(OdataControllerServlet.java:93) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) at org.apache.tomcat.core.Handler.init(Handler.java:215) at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) at org.apache.tomcat.core.Handler.service(Handler.java:254) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.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) any idee to help me Patrick PIERRA
java.lang.SecurityException: sealing violation?
Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy
java.lang.SecurityException: sealing violation - jBuilder4
I have been using jBuilder to develope servlets since JServ through Tomcat 3.2 and now with Catalina. This problem has never come up before ;) It seems that I am having some classpath issues. My jBuilder required libs include: Catalina libs (all jars under catalina home), a DB2 lib (jdbc driver), and the Orielly package (cos.jar). They are defined individually in jBuilders Required Libraries dialog. The Tomcat mail list archives indicate that this is a common problem, but I haven't seen a posting that has helped me. Has anyone overcome this problem? How? message: -- javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3240) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:278) at org.apache.catalina.core.StandardService.start(StandardService.java:368) at org.apache.catalina.core.StandardServer.start(StandardServer.java:473) at org.apache.catalina.startup.Catalina.start(Catalina.java:738) at org.apache.catalina.startup.Catalina.execute(Catalina.java:657) at org.apache.catalina.startup.Catalina.process(Catalina.java:178) at org.apache.catalina.startup.Catalina.main(Catalina.java:163) - Root Cause - java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:280) at java.net.URLClassLoader.access$100(URLClassLoader.java:60) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:234) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader.java:670) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:1088) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:987) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at org.apache.jasper.compiler.TldLocationsCache.processWebDotXml(TldLocationsCache.java:164) at org.apache.jasper.compiler.TldLocationsCache.(TldLocationsCache.java:138) at org.apache.jasper.EmbededServletOptions.(EmbededServletOptions.java:324) at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:265) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:833) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3240) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:278) at org.apache.catalina.core.StandardService.start(StandardService.java:368) at org.apache.catalina.core.StandardServer.start(StandardServer.java:473) at org.apache.catalina.startup.Catalina.start(Catalina.java:738) at org.apache.catalina.startup.Catalina.execute(Catalina.java:657) at org.apache.catalina.startup.Catalina.process(Catalina.java:178) at org.apache.catalina.startup.Catalina.main(Catalina.java:163) = - Best Regards, Raimee Stevens __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: java.lang.SecurityException: sealing violation
I am not sure but I belive this is because you are using the JAXP 1.1 libraries from the sun download site, those files does not work with TC4, you must use the jaxp.jar and crimson.jar files included with TC4 (in the jasper directory). Mikael - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 26, 2001 10:22 AM Subject: java.lang.SecurityException: sealing violation > Hi, > > I use tomcat 3.2 and try to read a xml file throught a servlet but i > recieve this error : > > java.lang.Exception: Exception occurred: java.lang.SecurityException: > sealing violation > at lds.utils.XMLManager.loadXML(XMLManager.java:168) > at lds.utils.XMLManager.loadXML(XMLManager.java:183) > at > lds.servlets.OdataControllerServlet.init(OdataControllerServlet.java:93) > at javax.servlet.GenericServlet.init(GenericServlet.java:258) > at > org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) > at org.apache.tomcat.core.Handler.init(Handler.java:215) > at > org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) > at org.apache.tomcat.core.Handler.service(Handler.java:254) > 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) > > any idee to help me > > Patrick PIERRA >
RE: java.lang.SecurityException: sealing violation?
as far as I know it means that you have a class name collision in two jars and one of them is sealed, I had a similar problem when using xml packages. Try to put jars foreign to tomcat in the begining of the classpath, or at the end... classpath reordering did it for me.. --V. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, July 13, 2001 11:46 AM To: [EMAIL PROTECTED] Subject: java.lang.SecurityException: sealing violation? Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ***
Re: java.lang.SecurityException: sealing violation?
Hi, Oh dear. TOMCAT IS A JAVA APPLICATION!!! The only time you should need to recompile it is if you want to use JSSE (For SSL) You might want to recompile mod_jk or the like, but thats completely different. You may be getting an error as you do not have the correct privileges to execute the commands in the script. (If it needs to access something from the JDK in Security) Why didn't tomcat work the first time??? Its all very well complaining about it but if you don't give precise details about OS/Tomcat/JDK versions and what happened then we can't help. Post exact details and I'll take a look. Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Friday 13 July 2001 18:45, you wrote: > Okay, I gave up on my tomcat installation. I wiped > everything clean and then got all the source in the > hopes that it might work better if I compiled > vs. dropping binaries. > > So, there are many confusing aspects of the > installation instructions regarding building the > source. Seems like maybe the docs don't match up with > the behavior of the current releases? > > Anyway, I plodded thru, I think I got everything > straight. BUT, when I run startup.sh, I get the > following: > > java.lang.SecurityException: sealing violation > > I followed the install instructions that came with the > JSSE from Sun. Have no idea what this error means. > > Can anyone help? > > Thanks. > > - Jeremy
RE: java.lang.SecurityException: sealing violation?
I had the same problem...with the nightly build. The milestone build was fine, however. No changes in code. I'd recommend going with m5 until this is fixed (Craig?). -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] e.org]On Behalf Of [EMAIL PROTECTED] Sent: Friday, July 13, 2001 7:46 PM To: [EMAIL PROTECTED] Subject: java.lang.SecurityException: sealing violation? Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy
Re: java.lang.SecurityException: sealing violation - jBuilder4
Catalina's Classpath: D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; D:\jBuilder\jdk1.3\jre\lib\i18n.jar; D:\jBuilder\jdk1.3\jre\lib\jaws.jar; D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; D:\jBuilder\jdk1.3\lib\dt.jar; D:\jBuilder\jdk1.3\lib\tools.jar" = - Best Regards, Raimee Stevens __ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: java.lang.SecurityException: sealing violation - jBuilder4
Tomcat 4 doesn't use the CLASSPATH variable. So, all the .jar files that aren't in the jakarta-tomcat directory will be ignored AFAIK. I did notice one thing that looks odd also. servlet.jar is normally found in common\lib, not server\lib. Not sure if that would make a difference. Jon - Original Message - From: "Raimee Stevens" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 06, 2001 1:01 PM Subject: Re: java.lang.SecurityException: sealing violation - jBuilder4 > Catalina's Classpath: > > D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; > > D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; > > D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; > > D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; > > D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; > D:\jBuilder\jdk1.3\jre\lib\i18n.jar; > D:\jBuilder\jdk1.3\jre\lib\jaws.jar; > D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; > D:\jBuilder\jdk1.3\lib\dt.jar; > D:\jBuilder\jdk1.3\lib\tools.jar" > > > = > - > Best Regards, > Raimee Stevens > > __ > Do You Yahoo!? > Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger > http://im.yahoo.com >
Re: java.lang.SecurityException: sealing violation - jBuilder4
That was - D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar - the api dist. not the one that ships with Tomcat. I took that one out believing that to be the cause of the name conflict. Apparently it wasn't. What was causing the problem was that I was loading Tomcat using the org.apache.catalina.startup.Catalina. I changed the main class to the org.apache.catalina.startup class and my problem went away as abruptly as it appeared. I really should have consulted the catalina.bat for the correct info, but I didn't. I had to learn the hard way :doRun if "%2" == "-security" goto doRunSecure %_RUNJAVA% %CATALINA_OPTS% -Dcatalina.home="%CATALINA_HOME%" org.apache.catalina.startup.Bootstrap %2 %3 %4 %5 %6 %7 %8 %9 start goto cleanup :doRunSecure %_RUNJAVA% %CATALINA_OPTS% -Djava.security.manager -Djava.security.policy=="%CATALINA_HOME%/conf/catalina.policy" -Dcatalina.home="%CATALINA_HOME%" org.apache.catalina.startup.Bootstrap %3 %4 %5 %6 %7 %8 %9 start goto cleanup The "org.apache.catalina.startup.Bootstrap" Class name is glaring. Also, Catalina does indeed use a classpath. And also from catalina.bat : set _CLASSPATH=%CLASSPATH% set _CP=%CP% ... rem - Set Up The Runtime Classpath set CP=%CATALINA_HOME%\bin\bootstrap.jar;%JAVA_HOME%\lib\tools.jar set CLASSPATH=%CP%;G:\Tomcat\jakarta-tomcat-4.0-b7\lib\db2java.zip echo Using CLASSPATH: %CLASSPATH% Jonathan Eric Miller wrote: > Tomcat 4 doesn't use the CLASSPATH variable. So, all the .jar files that > aren't in the jakarta-tomcat directory will be ignored AFAIK. I did notice > one thing that looks odd also. servlet.jar is normally found in common\lib, > not server\lib. Not sure if that would make a difference. > > Jon > > - Original Message - > From: "Raimee Stevens" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, September 06, 2001 1:01 PM > Subject: Re: java.lang.SecurityException: sealing violation - jBuilder4 > > > Catalina's Classpath: > > > > D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; > > > > D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; > > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; > > > > D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; > > > > D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; > > > > D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; > > D:\jBuilder\jdk1.3\jre\lib\i18n.jar; > > D:\jBuilder\jdk1.3\jre\lib\jaws.jar; > > > D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; > > D:\jBuilder\jdk1.3\lib\dt.jar; > > D:\jBuilder\jdk1.3\lib\tools.jar" > > > > > > = > > - > > Best Regards, > > Raimee Stevens > > > > __ > > Do You Yahoo!? > > Get email alerts & NEW webcam video instant messaging with Yahoo! > Messenger > > http://im.yahoo.com > >
Re: java.lang.SecurityException: sealing violation - jBuilder4
> I changed the main class to the org.apache.catalina.startup class and my problem went away as abruptly as it appeared. Sorry, that wasn't what I ment to say.. "org.apache.catalina.startup.BootStrap" class is the correct class. Raimee wrote: > That was - D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar - the api dist. not > > the one that ships with Tomcat. I took that one out believing that to be the > cause > of the name conflict. Apparently it wasn't. > > What was causing the problem was that I was loading Tomcat using the > org.apache.catalina.startup.Catalina. I changed the main > class to the org.apache.catalina.startup class and my problem went away as > abruptly as it appeared. > > I really should have consulted the catalina.bat for the correct info, but I > didn't. > I had to learn the hard way > > :doRun > if "%2" == "-security" goto doRunSecure > %_RUNJAVA% %CATALINA_OPTS% -Dcatalina.home="%CATALINA_HOME%" > org.apache.catalina.startup.Bootstrap %2 %3 %4 %5 %6 %7 %8 %9 start > goto cleanup > :doRunSecure > %_RUNJAVA% %CATALINA_OPTS% -Djava.security.manager > -Djava.security.policy=="%CATALINA_HOME%/conf/catalina.policy" > -Dcatalina.home="%CATALINA_HOME%" org.apache.catalina.startup.Bootstrap %3 %4 %5 > %6 %7 %8 %9 start > goto cleanup > > The "org.apache.catalina.startup.Bootstrap" Class name is glaring. > > Also, Catalina does indeed use a classpath. And also from catalina.bat : > > set _CLASSPATH=%CLASSPATH% > set _CP=%CP% > ... > > rem - Set Up The Runtime Classpath > > set CP=%CATALINA_HOME%\bin\bootstrap.jar;%JAVA_HOME%\lib\tools.jar > set CLASSPATH=%CP%;G:\Tomcat\jakarta-tomcat-4.0-b7\lib\db2java.zip > echo Using CLASSPATH: %CLASSPATH% > > Jonathan Eric Miller wrote: > > > Tomcat 4 doesn't use the CLASSPATH variable. So, all the .jar files that > > aren't in the jakarta-tomcat directory will be ignored AFAIK. I did notice > > one thing that looks odd also. servlet.jar is normally found in common\lib, > > not server\lib. Not sure if that would make a difference. > > > > Jon > > > > - Original Message - > > From: "Raimee Stevens" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Thursday, September 06, 2001 1:01 PM > > Subject: Re: java.lang.SecurityException: sealing violation - jBuilder4 > > > > > Catalina's Classpath: > > > > > > D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; > > > > > > D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; > > > D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; > > > > > > D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; > > > > > > D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; > > > > > > D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; > > > D:\jBuilder\jdk1.3\jre\lib\i18n.jar; > > > D:\jBuilder\jdk1.3\jre\lib\jaws.jar; > > > > > D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; > > > D:\jBuilder\jdk1.3\lib\dt.jar; > > > D:\jBuilder\jdk1.3\lib\tools.jar" > > > > > > > > > = > > > - > > > Best Regards, > > > Raimee Stevens > > > > > > __ > > > Do You Yahoo!? > > > Get email alerts & NEW webcam video instant messaging with Yahoo! > > Messenger > > > http://im.yahoo.com > > >
