You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Randy Layman <ra...@aswethink.com> on 2001/06/19 16:48:07 UTC
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:vince@idev.com]
> 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 vince@idev.com
> Internet Applications Engineer
> IDEV http://www.idev.com
> V: 301 495 7345 x129
>
Re: omegacms, thanks and a new problem: compile errors
Posted by Vinny <vi...@xaymaca.com>.
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:
>
>
> <h2>Hello 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:vince@idev.com]
>>> Sent: Tuesday, June 19, 2001 11:17 AM
>>> To: Tomcat Users
>>
>>
>>>
>
>
Problem Installing Tomcat
Posted by Derek Pitts <de...@mail.chem.tamu.edu>.
Hi,
I am having trouble getting Tomcat 3.2.2 working correctly.
I have tried to install it on two Red Hat Linux 7.0
computers and neither one will function correctly. I have
tried both the rpm and the binary file and I cant seem to
get it to work right. When I run the
startup.sh or the tomcat.sh start scripts I get this error
message
Using classpath: var/tomcat/lib/*
[root@danna bin]# SIGSEGV 11* segmentation violation
stackbase=(nil), stackpointer=(nil)
Full thread dump:
NULL (TID:0x4059d0b0, sys_thread_t:0x8083dd8, state:R)
prio=5 *current thread*
java.lang.System.nullInputStream(System.java)
java.lang.System.<clinit>(System.java)
java.lang.String.getChars(String.java)
java.lang.StringBuffer.append(StringBuffer.java)
java.lang.StringBuffer.<init>(StringBuffer.java)
java.lang.Thread.<init>(Thread.java)
Monitor Cache Dump:
java.lang.Class@1079627864/1079893136: owner NULL
(0x8083dd8, 1 entry)
java.lang.StringBuffer@1079628136/1079893024: owner NULL
(0x8083dd8, 1 entry)
Registered Monitor Dump:
Thread queue lock: <unowned>
Name and type hash table lock: <unowned>
String intern lock: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class loading lock: <unowned>
Java stack lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Has finalization queue lock: <unowned>
Finalize me queue lock: <unowned>
Dynamic loading lock: owner NULL (0x8083dd8, 1 entry)
Monitor IO lock: <unowned>
Child death monitor: <unowned>
Event monitor: <unowned>
I/O monitor: <unowned>
Alarm monitor: <unowned>
Monitor registry: owner NULL (0x8083dd8, 1 entry)
Thread Alarm Q:
I am fairly certain that this should not happen when I start
tomcat. help would be greatly appreciated.
Thanks
Derek Pitts
Re: omegacms, thanks and a new problem: compile errors
Posted by Jeff Kilbride <je...@kilbride.com>.
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" <vi...@xaymaca.com>
To: <to...@jakarta.apache.org>
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:
>
>
> <h2>Hello 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:vince@idev.com]
> >>Sent: Tuesday, June 19, 2001 11:17 AM
> >>To: Tomcat Users
> >
> >>
>
>
>
Re: omegacms, thanks and a new problem: compile errors
Posted by Vinny <vi...@xaymaca.com>.
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:
<h2>Hello 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:vince@idev.com]
>>Sent: Tuesday, June 19, 2001 11:17 AM
>>To: Tomcat Users
>
>>