[xep-support] [Solved] Re: SVG, identifiers, xml catalogs, resolver, net access

Steve Whitlatch swhitlat at getnet.net
Mon Jul 24 17:22:40 PDT 2006


To conclude on this thread and leave a record in the archives for others, 
 . . . it works. After setting everything up as described previously by others 
in this and similar threads, I needed to adjust the placement of the 
command-line parameters. 

Instead of:
% java -cp " . . ." \
com.renderx.xep.XSLDriver -DCONFIG=C:\\RenderX\\XEP\\xep.xml \
-Dcom.renderx.sax.entityresolver=org.apache.xml.resolver.tools.CatalogResolver 
-Dcom.renderx.jaxp.uriresolver=org.apache.xml.resolver.tools.CatalogResolver \
-fo file.fo -pdf file.pdf

The command string needed to have the "-D . . ." parameters associated with 
the java executable, not com.renderx.xep.XSLDriver. 

So, this works:
% java -cp " . . ." \
-Dcom.renderx.sax.entityresolver=org.apache.xml.resolver.tools.CatalogResolver 
-Dcom.renderx.jaxp.uriresolver=org.apache.xml.resolver.tools.CatalogResolver \
com.renderx.xep.XSLDriver -DCONFIG=C:\\RenderX\\XEP\\xep.xml \
-fo file.fo -pdf file.pdf

RenderX tech support solved it. Thanks!!

Steve Whitlatch 

-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo at renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html



More information about the Xep-support mailing list