[ http://nagoya.apache.org/jira/browse/XALANJ-1798?page=history ]
Henry Zongaro updated XALANJ-1798:
----------------------------------
Assign To: (was: Xalan Developers Mailing List)
type: New Feature (was: Bug)
Description:
I am using XALAN packages 2.4.1, 2.5.1 and 2.5.2 and all produce the same
errors, if I use the document() function to open an XHTML file with an external
DTD.
I have recognized, that the company I am developing the framework for
uses a Proxy server. XALAN does not use the settings entered in
the LAN settings of the Internet Explorer's LAN settings. So it cannot follow
the URI defined in the DTD header (connection time out):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
In this case, the entity must (should) not be opened by XALAN. It is only a XML
definition, but as far as I know, this information is not used for XML
transformation (that's what XALAN is used for). In my scenarios, the source XML
file has not to be validated against the Doctype definition. But I can't get
XALAN run, because my company uses a Proxy server for internet connection. If
opening such external entities could be optional in XALAN, I could use it
without deleting the DTD header in my sources.
was:
I am using XALAN packages 2.4.1, 2.5.1 and 2.5.2 and all produce the same
errors, if I use the document() function to open an XHTML file with an external
DTD.
I have recognized, that the company I am developing the framework for
uses a Proxy server. XALAN does not use the settings entered in
the LAN settings of the Internet Explorer's LAN settings. So it cannot follow
the URI defined in the DTD header (connection time out):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
In this case, the entity must (should) not be opened by XALAN. It is only a XML
definition, but as far as I know, this information is not used for XML
transformation (that's what XALAN is used for). In my scenarios, the source XML
file has not to be validated against the Doctype definition. But I can't get
XALAN run, because my company uses a Proxy server for internet connection. If
opening such external entities could be optional in XALAN, I could use it
without deleting the DTD header in my sources.
Environment:
Operating System: Windows NT/2K
Platform: PC
was:
Operating System: Windows NT/2K
Platform: PC
Priority: Major
Bugzilla Id: (was: 27068)
> XALAN fails using the document() function to open XML file with external DTD
> header offline
> -------------------------------------------------------------------------------------------
>
> Key: XALANJ-1798
> URL: http://nagoya.apache.org/jira/browse/XALANJ-1798
> Project: XalanJ2
> Type: New Feature
> Components: Xalan-interpretive, transformation
> Versions: 2.5
> Environment: Operating System: Windows NT/2K
> Platform: PC
> Reporter: Florian Saller
> Attachments: QMProcess.xhtml, QMProcess.xml, QMProcess.xslt
>
> I am using XALAN packages 2.4.1, 2.5.1 and 2.5.2 and all produce the same
> errors, if I use the document() function to open an XHTML file with an
> external
> DTD.
> I have recognized, that the company I am developing the framework for
> uses a Proxy server. XALAN does not use the settings entered in
> the LAN settings of the Internet Explorer's LAN settings. So it cannot follow
> the URI defined in the DTD header (connection time out):
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
> Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";>
> In this case, the entity must (should) not be opened by XALAN. It is only a
> XML
> definition, but as far as I know, this information is not used for XML
> transformation (that's what XALAN is used for). In my scenarios, the source
> XML
> file has not to be validated against the Doctype definition. But I can't get
> XALAN run, because my company uses a Proxy server for internet connection. If
> opening such external entities could be optional in XALAN, I could use it
> without deleting the DTD header in my sources.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
