On Dec 10, 2004, at 12:26 PM, Mark Womack wrote:
I'll buy that.
Does this problem only happen with some xml config files, or ALL xml config
files? I don't use the xml include mechanism in my config files, so I guess
I never encountered this. But I have not been using the new
JoranConfigurator either. I need to get up to speed there.
The problem resolving DTD's will effect enough existing configuration files that it can't be ignored. I don't think the external entities example would be found in the wild, however it is something that you are "supposed" to be able to do safely in XML.
So, if xml configuration data were being pushed through a socket or a jms
message, it could not include any relative references, since there would be
no basis to resolve them. If they did, then there would be an error when
processing the data. I could live with that so long as I could resolve all
the references before pushing the data and send the fully resolved version
through the socket.
For our needs, all you would need to do would be to connect the output event stream of an XML parser to the input event stream of an XML serializer that writes to your payload.
I don't believe that there are any instances of relative URI's within the document content itself that would need to be explicitly resolved. I don't think our configuration file has anything like
<html> ... <image href="somepicture.jpg"/> </html>
where unless you absolutize "somepicture.jpg" before you move the HTML document, you are likely to get no picture or, worse yet, a different picture than the original document author intended.
The W3C's XML Base recommended provides mechanisms to deal with this issue, but as I said, I don't think it will affect us.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
