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: > > > Hello World > <%=out.print("!") %> > > > > > 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: > > > Hello World > <%=out.print("!") %> > > > > > 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
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: Hello World <%=out.print("!") %> 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
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 > Subject: omegacms > > > Hello, > has any one tried installing omegacms on tomcat. > I have a fresh install of tomcat 3.2.2 that is working > fine on redhat linux 7.1. The app cannot find it's properties > file no matter where I put it. Unfortunately, it seems to be closed > source so I can't figure out where it is trying to look for the > conf.properties file. > The error message I get from Tomcat is : > > config.properties not found when trying to load properties: > config.properties in ./bin/../lib/test//usr/java/jdk1.3.1/ > > The docs say to have config.properties in the classpath, so I put it > in myApp/WEB-INF/classes, I even tried putting it in TOMCAT_HOME/lib > to no avail. Why Oh Why don't people use the jsp/servlet specs on > directory structure organization? > > Anyone experienced in making this thing work? > Thanks in Advance > > > > > > -- > Vincent Stoessel [EMAIL PROTECTED] > Internet Applications Engineer > IDEV http://www.idev.com > V: 301 495 7345 x129 >
omegacms
Hello, has any one tried installing omegacms on tomcat? I have a fresh install of tomcat 3.2.2 that is working fine on redhat linux 7.1. The app cannot find it's properties file no matter where I put it. Unfortunately, it seems to be closed source so I can't figure out where it is trying to look for the conf.properties file. The error message I get from Tomcat is : config.properties not found when trying to load properties: config.properties in ./bin/../lib/test//usr/java/jdk1.3.1/ The docs say to have config.properties in the classpath, so I put it in myApp/WEB-INF/classes, I even tried putting it in TOMCAT_HOME/lib to no avail. Why Oh Why don't people use the jsp/servlet specs on directory structure organization? Anyone experienced in making this thing work? Thanks in Advance Vincent
omegacms
Hello, has any one tried installing omegacms on tomcat. I have a fresh install of tomcat 3.2.2 that is working fine on redhat linux 7.1. The app cannot find it's properties file no matter where I put it. Unfortunately, it seems to be closed source so I can't figure out where it is trying to look for the conf.properties file. The error message I get from Tomcat is : config.properties not found when trying to load properties: config.properties in ./bin/../lib/test//usr/java/jdk1.3.1/ The docs say to have config.properties in the classpath, so I put it in myApp/WEB-INF/classes, I even tried putting it in TOMCAT_HOME/lib to no avail. Why Oh Why don't people use the jsp/servlet specs on directory structure organization? Anyone experienced in making this thing work? Thanks in Advance -- Vincent Stoessel [EMAIL PROTECTED] Internet Applications Engineer IDEV http://www.idev.com V: 301 495 7345 x129