forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "IAS" <iasan...@apache-korea.org>
Subject RE: [problem] xdocs validator doesn't support Korean characters
Date Thu, 28 Nov 2002 08:35:21 GMT
Instead of copying a schema from forrest, you can mmodify
forrest.propertiees to point out forrest default schema like
"project.schema-dir=d:/apache/xml/forrest/context/resources/schema" in
order to avoid validation failure.

Thanks.
IAS

-----Original Message-----
From: IAS [mailto:iasandcb@apache-korea.org] 
Sent: Thursday, November 28, 2002 4:46 PM
To: forrest-dev@xml.apache.org
Subject: RE: [problem] xdocs validator doesn't support Korean characters

I checked out the changes from CVS HEAD of Ant, and downloaded the built
jars(ant.jar, nodeps.jar, resolver.jar) at
http://gump.covalent.net/jars/latest/jakarta-ant/ and
http://gump.covalent.net/jars/latest/xml-commons/ . (2002-11-27)

I'm very glad to tell you that now forrest (with the updated ant)
validates Korean document very smoothly. I guess it's also the same in
case of Japanese and all the other DBCS.

However, it seems that the validator wants schema directory based on a
project with "Apache resolver library found, xml-commons resolver will
be used" message. For example, if a project doesn't explicitly put a
schema directory under src/documentation/resources, you can meet an
error message like this:

BUILD FAILED
file://D:/apache/xml/forrest/forrest.build.xml:716:
D:\sites\appolo\src\documentation\resources\schema not found.
        at
org.apache.tools.ant.types.AbstractFileSet.getDirectoryScanner(AbstractF
ileSet.java:369)
        at
org.apache.tools.ant.types.XMLCatalog$ApacheResolver.processExternalCata
logs(XMLCatalog.java:1083)
        at
org.apache.tools.ant.types.XMLCatalog$ApacheResolver.resolveEntity(XMLCa
talog.java:921)
        at
org.apache.tools.ant.types.XMLCatalog.resolveEntity(XMLCatalog.java:398)
        at
org.apache.xerces.util.EntityResolverWrapper.resolveEntity(EntityResolve
rWrapper.java:148)
        at
org.apache.xerces.impl.XMLEntityManager.resolveEntity(XMLEntityManager.j
ava:608)
        at
org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XML
DocumentScannerImpl.java:839)
        at
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDo
cumentFragmentScannerImpl.java:329)
        at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:5
25)
        at
org.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:5
81)
        at org.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
        at
org.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java
:1175)
        at
org.apache.tools.ant.taskdefs.optional.XMLValidateTask.doValidate(XMLVal
idateTask.java:410)
        at
org.apache.tools.ant.taskdefs.optional.XMLValidateTask.execute(XMLValida
teTask.java:298)
        at org.apache.tools.ant.Task.perform(Task.java:348)
        at org.apache.tools.ant.Target.execute(Target.java:309)
        at org.apache.tools.ant.Target.performTasks(Target.java:336)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1331)
        at
org.apache.tools.ant.Project.executeTargets(Project.java:1275)
        at org.apache.tools.ant.Main.runBuild(Main.java:614)
        at org.apache.tools.ant.Main.start(Main.java:197)
        at org.apache.tools.ant.Main.main(Main.java:235)

This failure can be resolved by just copying schema directory from
forrest main resources to your project.

In addition, I enjoy editing forrest xdocs with jEdit. In particular, if
you can add forrest/resources/schema/catalog.xcat to catalog of XML
plugin options, validation works very fine before forrest does.

Thanks a lot.

-----Original Message-----
From: Stefan Bodewig [mailto:bodewig@apache.org] 
Sent: Thursday, November 28, 2002 1:41 AM
To: forrest-dev@xml.apache.org
Subject: Re: [problem] xdocs validator doesn't support Korean characters

On 26 Nov 2002, Stefan Bodewig <bodewig@apache.org> wrote:

> Looks easy to fix, I'll take a stab at it sometime this week.

This is supposed to be fixed in CVS HEAD of Ant now.

If you update forrest's version of Ant - so it can be tested here -
remember that you'll need a CVS version of resolver.jar as well.

Stefan



Mime
View raw message