I am +1 on the refactoring, both (1) and (2). If you think it makes sense, then I'm happy. I'd recommend waiting till Craeg Strong responds, as he was the last person actively editing this, and doing the resolver tie in.
----- Original Message ----- From: "Jose Alberto Fernandez" <[EMAIL PROTECTED]> To: "Ant Developers List" <[EMAIL PROTECTED]> Sent: Monday, November 25, 2002 9:14 AM Subject: RE: XMLCatalog needs urgent refactoring Well, if there is no big objection by tomorrow, I will try to do a refactoring based on (1) below. I think if gives the most flexibility to start with. We may want to do (2) also but mostly in order to improve XMLCatalog itself. Has anybody looked at the capabilities of other Catalogs like: - Geting from publicId prefix --> location - Geting from systemId prefix --> location - etc. Jose Alberto > > The fact that every method in XMLCatalog is private, > instead of protected mae things even more > > dificult. I would like to propose a refactoring of this > code so that befaviour can be redefined > > better. I see two ways of achieving this: > > > > 1) Make XMLCatalog have a Vector of referenced catalogs and > invoke recursively on them. > > This will require making resolveImpl() and > resolveEntityImpl() protected. > > > > 2) Making DTDLocation have associated behavior > DTDLocation.resolve(publicId, systemId) and allow to have > > diferent implementations of this objects. This would allow > for example having something like > > DTDPrefixLocation which uses prefix for the matching and > other such elements of full catalog implementations. > > > > Maybe we need a mixture of the two. > > > > Before I propose a patch, I would like to know what people > think and what constraints there are for > > such a refactoring so that the patch is not rejected or > becomes part of some religious war. > > > > Please let me know your opinion, > > > > Jose Alberto > > > > > > > > > > > > > > > -------------------------------------------------------------- > ---------- > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
