You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by "James M Snell (JIRA)" <ji...@apache.org> on 2006/10/28 19:11:16 UTC
[jira] Created: (ABDERA-19) Simplify Abdera Configuration
Simplify Abdera Configuration
-----------------------------
Key: ABDERA-19
URL: http://issues.apache.org/jira/browse/ABDERA-19
Project: Abdera
Issue Type: Improvement
Environment: all
Reporter: James M Snell
Assigned To: James M Snell
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ABDERA-19) Simplify Abdera Configuration
Posted by "James M Snell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ABDERA-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James M Snell updated ABDERA-19:
--------------------------------
Priority: Trivial (was: Major)
> Simplify Abdera Configuration
> -----------------------------
>
> Key: ABDERA-19
> URL: https://issues.apache.org/jira/browse/ABDERA-19
> Project: Abdera
> Issue Type: Improvement
> Environment: all
> Reporter: James M Snell
> Assigned To: James M Snell
> Priority: Trivial
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.