Ceki,
Thanks for responding so quickly.
I'm using the jar file that came with the latest download (log4j.jar).
Details:
JDK 1.2.2
Xerces 1.0.2
Windows NT OS
I've got the jar file imported properly (It allows the import of the
org.apache.log4j.* classes) it just doesn't seem to be able to see the dtd
from the jar file.
I think it may be a weblogic issue - although I have it usually happens in
.war files. When a .war file is deployed as a web application in weblogic
any non-.class files have to be physically removed and deposited to the
_tmp_war directory (ie. properties files) as they won't be picked up. This
is using Weblogic 5.1 sp5.
This may be the same issue but don't think so because I'm reading a .jar
file.
Cheers
-----Original Message-----
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 8 February 2001 8:19
To: LOG4J Users Mailing List
Subject: RE: Help using DOMConfigurator
Geoff,
When you say "jar file" what do you mean exactly? Is this log4j.jar or some
other jar file? Which OS, JDK version of Xerces is this? Ceki
At 07:56 08.02.2001 +0800, you wrote:
>I'm importing the jar file into the weblogic classpath and it's trying to
>get the dtd out of the jar file.
>The program has no problem getting the other files (.class files) out of
the
>jar file.
>
>I've deleted the dtd from the jar file and moved it to another directory
and
>pointed the xml to the dtd there.
>
>This is less than ideal - I would prefer to keep it in the jar file.
>
>Any ideas?
>
>Cheers
>
>Geoff
>
>-----Original Message-----
>From: Ceki Gülcü [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, 7 February 2001 17:21
>To: LOG4J Users Mailing List
>Subject: Re: Help using DOMConfigurator
>
>
>Geoff,
>
>There is no need to displace the log4j.dtd file. Leave it where it was.
>
>Why is java.util.zip involved? Have you placed the files in a jar archive?
>Ceki
>
>At 14:02 07.02.2001 +0800, you wrote:
>>Hello all,
>>
>>I'm trying to use the latest copy of log4j and trying to use the
>>DOMConfigurator.
>>
>>I've taken a copy of the sample1.xml, renamed it, copied the DTD to the
>same
>>directory and when I try and run:
>>
>>DOMConfigurator.configure(xmlFilePath);
>>
>>I get:
>>
>>log4j:ERROR Could not parse input stream
>[java.io.FileInputStream@86695348].
>>java.util.zip.ZipException: error in opening zip file
>> at java.util.zip.ZipFile.open(Native Method)
>> at java.util.zip.ZipFile.<init>(ZipFile.java:69)
>> at java.util.zip.ZipFile.<init>(ZipFile.java:84)
>> at
>>weblogic.utils.zip.ZipURLConnection.getInputStream(Handler.java:40)
>> at java.net.URL.openStream(URL.java:818)
>> at
>>org.apache.xerces.readers.DefaultReaderFactory.createReader(DefaultReaderF
a
>c
>>tory.java, Co
>>mpiled Code)
>> at
>>org.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEnt
i
>t
>>y(DefaultEnti
>>tyHandler.java:767)
>> at
>>org.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSub
s
>e
>>t(DefaultEnti
>>tyHandler.java:566)
>> at
>>org.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.ja
v
>a
>>:1131)
>> at
>>org.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocument
S
>c
>>anner.java:21
>>77)
>> at
>>org.apache.xerces.framework.XMLDocumentScanner.access$0(XMLDocumentScanner
.
>j
>>ava:2133)
>> at
>>org.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(X
M
>L
>>DocumentScann
>>er.java, Compiled Code)
>> at
>>org.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocumentScanne
r
>.
>>java, Compile
>>d Code)
>> at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:900)
>> at
>>org.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:
1
>2
>>3)
>> at
>>org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:566)
>> at
>>org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:513)
>>
>>
>>Any Ideas??
>>
>>Cheers,
>>
>>Geoff Oliphant
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
================================================================================================
IMPORTANT INFORMATION
This message and any files transmitted with it are confidential and should be read
only by those
persons to whom it is addressed.
If you have received this message in error, please notify us immediately by way of
reply. Please
also destroy and delete the message from your computer. Any unauthorised form of
reproduction
of this message is strictly prohibited.
It is the duty of the recipient to virus scan and otherwise test the information
provided before
loading onto any computer system.
SEALCORP does not warrant that the information is free of a virus or any other defect
or error.
SEALCORP is not liable for the proper and complete transmission of the information
contained in
this communication, nor for any delay in its receipt.
Any views expressed in this message are those of the individual sender, except where
the sender
specifically states them to be the views of SEALCORP.
================================================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
