This is the default unmodified jboss-tomcat installation. If I use the
jboss-jetty
installation, it all starts and runs as expected. I am using JDK1.3.1.
Tom Veldhouse
13:09:50,339 ERROR [URLDeploymentScanner] Failed to deploy:
org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@ecc8
d to jboss-user
To: <[EMAIL PROTECTED]>
cc:
Subject: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of the box.
This is the default unmodified jboss-tomcat installation. If I use the
jboss-jetty
installation, it all starts an
xxx
- Original Message -
From: "Thomas T. Veldhouse" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 08, 2002 12:50 PM
Subject: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of the box.
> This is the default unmodified jboss-tomcat installat
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 08, 2002 3:43 PM
Subject: Re: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of
the box.
> Using what OS, JDK, and is there an xml parser extension installed in the
JDK?
> This has to be an issue with ho
"Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 08, 2002 3:43 PM
Subject: Re: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of
the box.
> Using what OS, JDK, and is there an xml parser extension installed in the
JDK?
> T
;[EMAIL PROTECTED]>
Sent: Tuesday, October 08, 2002 2:29 PM
Subject: Re: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of the box.
> I think this is the reason:
>
> "The default value is that of the JBoss/Catalina bundle where the
> jakarta-tomcat-4.1.12-LE-j
Sent: Tuesday, October 08, 2002 4:40 PM
Subject: Re: [JBoss-user] JBoss 3.0.3 & tomcat 4.1.12 broken right out of
the box.
> Wrong, try reading the actual setting. As I stated I'm only using non-JDK
1.4 VMs.
>
>
> Scott Stark
&g
