Hello everyone, I've been struggling to get Glassbox running on an installation of Borland Enterprise Server (AppServer 6.6). Out the box this didn't really agree with being deployed. I have managed to get it a little bit further along by removing a number of jars (cglib, commons-logging, glassboxmonitor) from the war and deploying them directly into the app server, however, I don't know if there is any light at the end of that tunnel or whether I will just end up with an exploded version of a non-working Glassbox, instead of an archived version.
I don't know if these are to do with glassbox itself, or to do with how it's attempting to dig it's fingers into the code I want to examine (Search.war).
I've attached an example of the system log from the server as it attempts to start up.
I'd really appreciate any help, or any pointers as to which direction I should be digging!
Hello everyone, I've been struggling to get Glassbox running on an installation of Borland Enterprise Server (AppServer 6.6). Out the box this didn't really agree with being deployed. I have managed to get it a little bit further along by removing a number of jars (cglib, commons-logging, glassboxmonitor) from the war and deploying them directly into the app server, however, I don't know if there is any light at the end of that tunnel or whether I will just end up with an exploded version of a non-working Glassbox, instead of an archived version.
There are a number of
, then a few
s once it gets further.
I don't know if these are to do with glassbox itself, or to do with how it's attempting to dig it's fingers into the code I want to examine (Search.war).
I've attached an example of the system log from the server as it attempts to start up.
I'd really appreciate any help, or any pointers as to which direction I should be digging!
Thanks
Sandy Noble
Forgot to mention that Borland AppServer integrates Tomcat 5.5 as it's web container.