Virtual hosting with IIS

2001-07-03 Thread Markus Strickler

Hi!
I have several IIS webserver instances running on different ports on the
same IP.
Now I need to map the *.xml extension to Cocoon for all instances.
Anybody an idea how to set this up?

I'm using IIS5, Tomcat-3.2.2, JDK1.3

Any help would be appreciated,

-markus





Re: Virtual hosting with IIS

2001-07-03 Thread Markus Strickler

Andi-

actually which parameters to set, is the problem.
For example I have two server instances with their doc roots at
C:\server1 and c:\server2

a) If I access a file from server1 like this:
http://server:9000/index.xml
I need the Cocoon servlet being invoked and the path C:\server1\index.xml
passed to it.
b) If I access a file from server2 like this:
http://server:9001/index.xml
I need the servlet being invoked and the path C:\server2\index.xml passed to
it.

The best solution would be if in case a) and b) different servlet contexts
could be invoked.

Any idea how to accomplish this?

Note that I have several dozens of web servers, so using a separate JVM for
each is ruled out.

Thanks for any help

 -markus
- Original Message -
From: "Everitt, Andrew" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 03, 2001 12:44 PM
Subject: RE: Virtual hosting with IIS


> Markus,
>
> Go in to IIS admin console and right click the computer icon, select
> properties. In 'Master Properties' select 'WWW Service' and click the
'Edit
> ...' button this will bring up the default properties page for all virtual
> server's on the computer - set the things you want set globally and you're
> done.
>
> Cheers,
> Andi.
>
> > -Original Message-
> > From: Markus Strickler [mailto:[EMAIL PROTECTED]]
> > Sent: 03 July 2001 10:53
> > To: [EMAIL PROTECTED]
> > Subject: Virtual hosting with IIS
> >
> >
> > Hi!
> > I have several IIS webserver instances running on different
> > ports on the
> > same IP.
> > Now I need to map the *.xml extension to Cocoon for all instances.
> > Anybody an idea how to set this up?
> >
> > I'm using IIS5, Tomcat-3.2.2, JDK1.3
> >
> > Any help would be appreciated,
> >
> > -markus
> >
>
>




Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?

2001-07-04 Thread Markus Strickler



Betty-
 
The problem is with the order the jars are 
loaded. There is a version confilict with some classes.
A common workaround is to rename parser.jar into 
zparser.jar, so it is loaded after xalan.jar and xerces.jar.
 
This worked for me.
 
-markus

  - Original Message - 
  From: 
  Betty Chang 
  
  To: [EMAIL PROTECTED] 
  
  Sent: Wednesday, July 04, 2001 5:34 
  AM
  Subject: conflict between jaxp.jar, 
  parser.jar (tomcat lib) and xalan.jar, xerces.jar?
  
  Hi --
   
  I'm running a servlet application that uses the 
  apache-XML   xalan.jar and xerces.jar files for handling XML/XSL 
  stuff.
   
  With tomcat 3.2.1,  when I run my servlet,  I 
  get  NoSuchMethodError on
   
   getNamespaceURI(),  called by 
  org.apache.xpath.DOM2Helper.getNamespaceOfNode().
   
  I solved this problem by removing the jaxp.jar and 
  parser.jar files that come with the tomcat installation and sit under 
  
  the lib directory.
   
  The servlet still runs without those jar files, so the 
  xalan.jar and xerces.jar must do the trick.
   
  Is there some kind of version conflict that causes the 
  NoSuchMethodError?
   
  Thanks
   
  Betty
   


Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?

2001-07-04 Thread Markus Strickler



Pete-
AFAK the Startscripts for tomcat construct their 
own classpath from the lib directory during startup. This is done in 
alphabetical order, on most platforms. So renaming parser.jar is a quick and 
dirty way to move it to the end of the Tomcat classpath.
See http://xml.apache.org/cocoon/install.html#tomcat for 
details.
 
-markus

  - Original Message - 
  From: 
  Edwards, Peter 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Wednesday, July 04, 2001 10:14 
  AM
  Subject: RE: conflict between jaxp.jar, 
  parser.jar (tomcat lib) and xalan.jar, xerces.jar?
  
  Markus
   
  Are 
  you suggesting that the jars are loaded in alphabetical order? I would have 
  said you should either move parser.jar to the end of the class path or remove 
  it entirely since xerces.jar contains the necessary jaxp interfaces. Tomcat 
  3.2 does not access the parser directly but through jaxp so you can safely 
  remove parser.jar and jaxp.jar and use only xerces.jar.
   
  Pete
  
-Original Message-From: Markus Strickler 
[mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 
08:57To: [EMAIL PROTECTED]Subject: Re: 
conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, 
xerces.jar?
Betty-
 
The problem is with the order the jars are 
loaded. There is a version confilict with some classes.
A common workaround is to rename parser.jar 
into zparser.jar, so it is loaded after xalan.jar and 
xerces.jar.
 
This worked for me.
 
-markus

  - Original Message - 
  From: 
  Betty Chang 
  
  To: [EMAIL PROTECTED] 
  
  Sent: Wednesday, July 04, 2001 5:34 
  AM
  Subject: conflict between jaxp.jar, 
  parser.jar (tomcat lib) and xalan.jar, xerces.jar?
  
  Hi --
   
  I'm running a servlet application that uses the 
  apache-XML   xalan.jar and xerces.jar files for handling XML/XSL 
  stuff.
   
  With tomcat 3.2.1,  when I run my servlet,  I 
  get  NoSuchMethodError on
   
   getNamespaceURI(),  called 
  by org.apache.xpath.DOM2Helper.getNamespaceOfNode().
   
  I solved this problem by removing the jaxp.jar and 
  parser.jar files that come with the tomcat installation and sit under 
  
  the lib directory.
   
  The servlet still runs without those jar files, so the 
  xalan.jar and xerces.jar must do the trick.
   
  Is there some kind of version conflict that causes the 
  NoSuchMethodError?
   
  Thanks
   
  Betty
   


Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?

2001-07-04 Thread Markus Strickler



Pete-
I'm not aware of any issues with your solution, 
but I never tried it either, as the workaround with renaming the jars gave me 
the results I wanted.
 
-markus

  - Original Message - 
  From: 
  Edwards, Peter 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Wednesday, July 04, 2001 11:16 
  AM
  Subject: RE: conflict between jaxp.jar, 
  parser.jar (tomcat lib) and xalan.jar, xerces.jar?
  
  Markus
   
  You 
  are right, I had forgotten that the scripts (even on NT) now create the class 
  path dynamically. I was thinking of situations where I'm debugging in JBuilder 
  and the classpath is static. I still suggest that it's as easy to make Tomcat 
  use xerces instead of jaxp and parser - are you aware of any issues with 
  this?
   
  Pete
  
-Original Message-----From: Markus Strickler 
[mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 
09:43To: [EMAIL PROTECTED]Subject: Re: 
conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, 
xerces.jar?
Pete-
AFAK the Startscripts for tomcat construct 
their own classpath from the lib directory during startup. This is done in 
alphabetical order, on most platforms. So renaming parser.jar is a quick and 
dirty way to move it to the end of the Tomcat classpath.
See http://xml.apache.org/cocoon/install.html#tomcat for 
details.
 
-markus

  - Original Message - 
  From: 
  Edwards, Peter 
  To: '[EMAIL PROTECTED]' 
  
  Sent: Wednesday, July 04, 2001 10:14 
  AM
  Subject: RE: conflict between 
  jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
  
  Markus
   
  Are you suggesting that the jars are loaded in 
  alphabetical order? I would have said you should either move parser.jar to 
  the end of the class path or remove it entirely since xerces.jar contains 
  the necessary jaxp interfaces. Tomcat 3.2 does not access the parser 
  directly but through jaxp so you can safely remove parser.jar and jaxp.jar 
  and use only xerces.jar.
   
  Pete
  
    -----Original Message-From: Markus Strickler 
[mailto:[EMAIL PROTECTED]]Sent: 04 July 2001 
08:57To: [EMAIL PROTECTED]Subject: 
Re: conflict between jaxp.jar, parser.jar (tomcat lib) and xalan.jar, 
xerces.jar?
Betty-
 
The problem is with the order the jars 
are loaded. There is a version confilict with some classes.
A common workaround is to rename 
parser.jar into zparser.jar, so it is loaded after xalan.jar and 
xerces.jar.
 
This worked for me.
 
-markus

  - Original Message - 
  From: 
  Betty 
  Chang 
  To: [EMAIL PROTECTED] 
  
  Sent: Wednesday, July 04, 2001 
  5:34 AM
  Subject: conflict between 
  jaxp.jar, parser.jar (tomcat lib) and xalan.jar, xerces.jar?
  
  Hi --
   
  I'm running a servlet application that uses the 
  apache-XML   xalan.jar and xerces.jar files for handling 
  XML/XSL stuff.
   
  With tomcat 3.2.1,  when I run my 
  servlet,  I get  NoSuchMethodError on
   
   getNamespaceURI(),  
  called by 
  org.apache.xpath.DOM2Helper.getNamespaceOfNode().
   
  I solved this problem by removing the jaxp.jar and 
  parser.jar files that come with the tomcat installation and sit under 
  
  the lib directory.
   
  The servlet still runs without those jar files, so 
  the xalan.jar and xerces.jar must do the trick.
   
  Is there some kind of version conflict that causes 
  the NoSuchMethodError?
   
  Thanks
   
  Betty