Skip abstract classes in config auto-discovery
----------------------------------------------
Key: STS-513
URL: http://www.stripesframework.org/jira/browse/STS-513
Project: Stripes
Issue Type: Bug
Affects Versions: Release 1.5
Reporter: Sebastian Beigel
I created an abstract LocalizationBundleFactory and a concrete LBF extending
this abstract base. Both classes are in the same package (i.e.
foo.bar.stripes.ext). I get the following error message:
Found too many classes implementing/extending LocalizationBundleFactory: [class
foo.bar.stripes.ext.MyAbstractLocalizationBundleFactory, class
foo.bar.stripes.ext.MyImplLocalizationBundleFactory]
I think it would be a good idea to skip interfaces/abstract classes
implementing one of the auto-discovered interfaces.
In fact, my situation is a bit more complex since I have a base library (jar)
for my projects containing some Stripes extensions (including some abstract
base classes) an my concrete project with another stripes ext package
(containing implementations). So I have configured 2 stripes ext packages in
web.xml and I expected all concrete classes to be auto-discovered (not the
abstractz ones).
Of course a workaround would be to move the abstract base classes to another
package(s), but I see them as "stripes extensions", so I would like to keep
them in the same package :)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
