Matthew Peters wrote:
Suppose I wanted to create a new implementation that shared much of the
behaviour of <implementation.java> and then added a bit. Suppose I wanted
to make <implementation.servlet> for example, to be an implementation that
did what <implement.java> does WRT understanding @Reference and @Property
and getters and setters, but did some extra - for example looked in the
web.xml file for the servlet and added some extra properties. How could I
architect this to take advantage of all the code that already exists
within the support for <implementation.java>?
Matthew Peters
We may need to refactor some of that function to make it available to
others as a proper SPI. Could you describe the bits you'd want to reuse
in more details?
- some of the implementation model?
- introspection of a Java class and creation of the corresponding
componentType model?
- injection of properties and references?
- invocation? I guess it's different here as a servlet has a fixed
interface pattern?
- anything else?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
