Re: LoggerStore

Peter Donald wrote:
>  
> To be honest I have never seen this need except when parsing out the ELement. 
> When the element is already parsed I haven't needed the EntityResolver as 
> entitys are resolved at parse time. Could you give me an example where it is 
> needed when you already have the ELment object?
> 

The point is that the Element is incorrectly parsed without it.
Say someone parses it without the ER, eg using the ConfigurationUtil 
class or passing via a Configuration object - as I started doing.
It misses the ER and the configuration via the corresponding Element is
incorrect.  This scenario is not irrealistic - eg when you have the 
Element embedded in a larger XML configuration file.
I would like to find a way to enforce the fact that EntityResolver needs 
to be used.  Although it's not entirely fail-proof, since the ER is not
specified anyway in the Element API.

Or else it needs to be very well highlighted in the documentation.






-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge