Re: omegacms, thanks and a new problem: compile errors
Thank you very much, I had to explicitly put the omega jar and the directory containing the property file in my unix shell's classpath. Now the problem I'm running into is that some pages are getting compile error messages. 2001-06-19 12:07:40 - Ctx( /omega ): JasperException: R( /omega + /admin/hello.jsp + null) Unable to compile class for JSP/usr/local/jakarta-tomcat-3.2.2/work/localhost_8080%2Fomega/_0002fadmin_0002fhello_0002ejsphello_jsp_0.java:61: Incompatible type for method. Can't convert void to char[]. out.print( out.print(!) ); the hello.jsp file contains: h2Hello World %=out.print(!) % /h2 what's going on? Thanks again in advance. Randy Layman wrote: If you're on UNIX, add it to TOMCAT_HOME/classes, if you're on NT you'll need to modify the tomcat.bat file so that Tomcat adds this directory to its automatically built classpath. Another option it to add the conf.properties to the CLASSPATH environment variable. In either case, there are some ways that you can request resources that cause the wrong class loader to be used, which it seems is happening here. Since its closed source, there really is no way around this. Randy -Original Message- From: Vincent Stoessel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 19, 2001 11:17 AM To: Tomcat Users
Re: omegacms, thanks and a new problem: compile errors
Figured it out, this statement needed a semicolon to work. Thanks all. Vinny wrote: Thank you very much, I had to explicitly put the omega jar and the directory containing the property file in my unix shell's classpath. Now the problem I'm running into is that some pages are getting compile error messages. 2001-06-19 12:07:40 - Ctx( /omega ): JasperException: R( /omega + /admin/hello.jsp + null) Unable to compile class for JSP/usr/local/jakarta-tomcat-3.2.2/work/localhost_8080%2Fomega/_0002fadmin_0002fhello_0002ejsphello_jsp_0.java:61: Incompatible type for method. Can't convert void to char[]. out.print( out.print(!) ); the hello.jsp file contains: h2Hello World %=out.print(!) % /h2 what's going on? Thanks again in advance. Randy Layman wrote: If you're on UNIX, add it to TOMCAT_HOME/classes, if you're on NT you'll need to modify the tomcat.bat file so that Tomcat adds this directory to its automatically built classpath. Another option it to add the conf.properties to the CLASSPATH environment variable. In either case, there are some ways that you can request resources that cause the wrong class loader to be used, which it seems is happening here. Since its closed source, there really is no way around this. Randy -Original Message- From: Vincent Stoessel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 19, 2001 11:17 AM To: Tomcat Users
Re: omegacms, thanks and a new problem: compile errors
Hi Vinny, The %= opening jsp tag is for single expression evaluation, while the % is for scriptlets. So, you could do this two ways: % out.print(!); % or %= ! % As you've seen, the %= wraps whatever's inside it in an out.print() statement -- so you're own out.print() is redundant in this case. --jeff - Original Message - From: Vinny [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, June 19, 2001 9:27 AM Subject: Re: omegacms, thanks and a new problem: compile errors Thank you very much, I had to explicitly put the omega jar and the directory containing the property file in my unix shell's classpath. Now the problem I'm running into is that some pages are getting compile error messages. 2001-06-19 12:07:40 - Ctx( /omega ): JasperException: R( /omega + /admin/hello.jsp + null) Unable to compile class for JSP/usr/local/jakarta-tomcat-3.2.2/work/localhost_8080%2Fomega/_0002fadmin_0 002fhello_0002ejsphello_jsp_0.java:61: Incompatible type for method. Can't convert void to char[]. out.print( out.print(!) ); the hello.jsp file contains: h2Hello World %=out.print(!) % /h2 what's going on? Thanks again in advance. Randy Layman wrote: If you're on UNIX, add it to TOMCAT_HOME/classes, if you're on NT you'll need to modify the tomcat.bat file so that Tomcat adds this directory to its automatically built classpath. Another option it to add the conf.properties to the CLASSPATH environment variable. In either case, there are some ways that you can request resources that cause the wrong class loader to be used, which it seems is happening here. Since its closed source, there really is no way around this. Randy -Original Message- From: Vincent Stoessel [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 19, 2001 11:17 AM To: Tomcat Users
