Re: Tomcat Windows Service Installer vs Core zip install xml

2008-01-24 Thread hoffmandirt

This issue was resolved by correctly utilizing the constructor of the
StreamSource object. It was expecting a String in URL/URI format and we were
passing in the file name only. The Zip download option of Tomcat did not
mind, but the Windows Service Installer option threw the Unknown protocol
c error. Does anyone know why this would be? Both installs were pointing to
the same JDK.
-- 
View this message in context: 
http://www.nabble.com/Tomcat-Windows-Service-Installer-vs-Core-zip-install-xml-tp15048926p15069803.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat Windows Service Installer vs Core zip install xml

2008-01-24 Thread Caldarale, Charles R
 From: hoffmandirt [mailto:[EMAIL PROTECTED] 
 Subject: Re: Tomcat Windows Service Installer vs Core zip install xml
 
 The Zip download option of Tomcat did not mind, but the 
 Windows Service Installer option threw the Unknown protocol
 c error.

Possibly due to the lack of a current directory setting when running as
a service.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Tomcat Windows Service Installer vs Core zip install xml

2008-01-24 Thread hoffmandirt

That makes sense to me. Thanks Chuck.



Caldarale, Charles R wrote:
 
 From: hoffmandirt [mailto:[EMAIL PROTECTED] 
 Subject: Re: Tomcat Windows Service Installer vs Core zip install xml
 
 The Zip download option of Tomcat did not mind, but the 
 Windows Service Installer option threw the Unknown protocol
 c error.
 
 Possibly due to the lack of a current directory setting when running as
 a service.
 
  - Chuck
 
 
 THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
 MATERIAL and is thus for use only by the intended recipient. If you
 received this in error, please contact the sender and delete the e-mail
 and its attachments from all computers.
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tomcat-Windows-Service-Installer-vs-Core-zip-install-xml-tp15048926p15070186.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Tomcat Windows Service Installer vs Core zip install xml

2008-01-23 Thread hoffmandirt

I am having issues with XSLT files depending on which download option of
Tomcat 6.0.14 that I choose.  If I download the ZIP file under Core, my XSLT
files transform with no problems.  However if I download and use the Windows
Service Installer instead, I am getting the following errors in my Tomcat
log:

 ERROR:  'unknown protocol: c'
FATAL ERROR:  'Could not compile stylesheet'

javax.xml.transform.TransformerConfigurationException: Could not compile
stylesheet [http-8080-1]
 
Has anyone else had this problem?
-- 
View this message in context: 
http://www.nabble.com/Tomcat-Windows-Service-Installer-vs-Core-zip-install-xml-tp15048926p15048926.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat Windows Service Installer vs Core zip install xml

2008-01-23 Thread Mark Thomas

hoffmandirt wrote:

I am having issues with XSLT files depending on which download option of
Tomcat 6.0.14 that I choose.  If I download the ZIP file under Core, my XSLT
files transform with no problems.  However if I download and use the Windows
Service Installer instead, I am getting the following errors in my Tomcat
log:

 ERROR:  'unknown protocol: c'
FATAL ERROR:  'Could not compile stylesheet'

javax.xml.transform.TransformerConfigurationException: Could not compile
stylesheet [http-8080-1]
 
Has anyone else had this problem?


Did you try Google? I found just over 0.75 million hits so it looks like 
the answer to your question is yes.


The issue is usually caused when you use C:\\MyFile.txt for a URL rather 
than file:///C:/MyFile.txt somewhere in your code.


Are both installs using exactly the same JVM? There may be slight 
differences in how tolerant different JVMs are of this issue.


Mark

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat Windows Service Installer vs Core zip install xml

2008-01-23 Thread hoffmandirt

Interesting, however I am pointing to the same JDK 1.5 for both. I wanted to
switch to the service instead of the bat startup and shutdown scripts. I
will give that a try and check it out.  I was searching google for could
not compile stylesheet.


markt-2 wrote:
 
 hoffmandirt wrote:
 I am having issues with XSLT files depending on which download option of
 Tomcat 6.0.14 that I choose.  If I download the ZIP file under Core, my
 XSLT
 files transform with no problems.  However if I download and use the
 Windows
 Service Installer instead, I am getting the following errors in my Tomcat
 log:
 
  ERROR:  'unknown protocol: c'
 FATAL ERROR:  'Could not compile stylesheet'
 
 javax.xml.transform.TransformerConfigurationException: Could not compile
 stylesheet [http-8080-1]
  
 Has anyone else had this problem?
 
 Did you try Google? I found just over 0.75 million hits so it looks like 
 the answer to your question is yes.
 
 The issue is usually caused when you use C:\\MyFile.txt for a URL rather 
 than file:///C:/MyFile.txt somewhere in your code.
 
 Are both installs using exactly the same JVM? There may be slight 
 differences in how tolerant different JVMs are of this issue.
 
 Mark
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Tomcat-Windows-Service-Installer-vs-Core-zip-install-xml-tp15048926p15054962.html
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]