Re: [Htmlparser-developer] ParserFeedback mechanism

[Derrick O. <Der...@ro...>]

You're right, there aren't many places in the code making calls to the 
feedback subsystem.

The reason to internalize the Apache logging classes is to avoid another 
jar.
It's not changing rapidly anyway.

Derrick

dha...@or... wrote:

>Its not that all our files use the Feedback and hence I really don't
>think all files should require change. I've explained below.
>  
>
>How about making ParserFeedback extend Log interface of Logging Wrapper.
>Then DefaultHTMLParserFeedback should declare feedback as follows :
>
>private static ParserFeedback feedback; 
>
>Obviously all mode related code would have to be deprecated/deleted. We
>could have a single argument constructor as follows
>
>public DefaultParserFeedback (Class clazz)
>{
>      feedback = LogFactory.getInstance(clazz)
>}
>
>and a no-arg constructor as
>
>public DefaultParserFeedback ()
>{
>      feedback = LogFactory.getInstance(this.class)
>}
>
>Classes using the same will create feedbacks as :
>
>new DefaultParserFeedback(this.class);
>
>Hope I've not taken things too simply and have given a comprehensive
>idea of how the Logging Wrapper should be incorporated with the Parser.
>
>Regards,
>Dhaval
>
>
>  
>