Dave,

Here's how I tested your idea: I changed the extensions of xalan-2.0.1.jar
and xerces_1_3_1.jar in both <tomcat_home>\lib and
<tomcat_home>\webapps\jetspeed\WEB_INF\lib. If there were any parser.jar
files in the path, or any other jar files that contained the parser, then
running tomcat and jetspeed should still work if you're right. But they
don't. When I run jetspeed now, I get a NoClassDefFoundError for
SAXNotRecognizedException, and multiple failures to instantiate other
classes.

So -- unless there's something I'm missing here -- the only parser and XSL
libs available to jetspeed are xalan-2.0.1  and xerces_1_3_1, but I still
get the Namespace not supported error.

I guess I'll keep poking around and see what I can find. Thanks for the
reply.

Steve


----- Original Message -----
From: "Dave Carlson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 17, 2001 11:07 AM
Subject: Re: TransformerException: Namespace not supported


> Hi Steven,
>
> The answer depends on which Java app server you are using.  There is
probably
> another old XML parser in you classpath before xalan.  For tomcat, you
likely
> have "parser.jar" in your lib directory.  Remove it and try again.
>
> Good luck!
>   Dave
>
> ----- Original Message -----
> From: "Steven Gollery" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, September 17, 2001 11:15 AM
> Subject: TransformerException: Namespace not supported
>
>
> I have installed the 9/14 build of v. 1.3a2, but when I start up tomcat, I
get
> this error in jetspeed.log:
>
> javax.xml.transform.TransformerException: Namespace not supported by
SAXParser
>
> (this is just after "Late init for Registry called")
>
> Later, when I point my browser at localhost:8080\jetspeed, I get the same
> error multiple times, starting with trying to load jetspeed-content.xml.
The
> result is that most of the sample portlets are marked "unavailable" in the
> customize screen.
>
> In the mail archive, I found Bruno Lowagie's message about this same error
(21
> Jun 2001), and  Christophe Mestrallet's reply: switch to xalan-2.0.1.jar
and
> xerces_1_3_1.jar. I tried this, but I still get the same error.
>
> Any ideas what else might be going on here?
>
> Thanks in advance.
>
> Steven Gollery
> [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to