DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27258>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27258

XML file included into validation.xml via entity reference not found

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement
            Summary|XML file included into      |XML file included into
                   |validation.xml via entity   |validation.xml via entity
                   |reference not found         |reference not found



------- Additional Comments From [EMAIL PROTECTED]  2004-06-07 18:56 -------
Unfortunately, I don't believe this is possible how validator is currently used
by Struts.  The validator, when initialized using ValidatorResources, uses
InputStreams for the source of the validator XML file(s).  InputStreams don't
have any location information for the default entity resolver to use when
resolving entity URIs.  When Struts loads its module config files, it does so by
passing digester URL's, giving the Digester something to resolve entities
against.  Therefore, Struts XML files can contain external entity references,
while Validator files cannot (at least when using ValidatorResources to load the
XML files).

The good news is with this patch, it will now be possible once Struts is
patched.  I added several constructors that take String uri's instead of the
usual InputStream.  This allows digester to properly resolve entity uris as
evidenced by the unit tests accompanying the patches.  I'm changing this to
enhancement since it is basically adding a feature other frameworks like Struts
can take advantage of, but will require patching.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to