What I imagine is a discovery model generally similar to JAXP. It's not a big change over what we currently have.
Parser parser = abdera.getParser(); - James Garrett Rooney wrote: > On 10/27/06, James M Snell <[EMAIL PROTECTED]> wrote: >> The current Abdera configuration model is designed around the notion of >> being able to configure alternative default implementations in a way >> that is transparent to consuming applications. However, since we only >> have one implementation of the interfaces as it's just as easy just to >> do Parser parser = new MyOtherParser(), I'm strongly leaning towards >> backing this stuff out and simplifying the configuration model. Using >> alternative Parser implementations would no longer require a >> configuration step. Implementations would just new up the alternative >> Parser. > > If we went this way would there still be the concept of a default > parser back end, or would we be having people hardcode > org.apache.abdera.parser.stax.* into their code since that's our only > current implementation? > > -garrett >
