abdera-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Calavera (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ABDERA-106) Spring provider definition parser should handle generic properties
Date Fri, 08 Feb 2008 20:36:07 GMT

     [ https://issues.apache.org/jira/browse/ABDERA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Calavera updated ABDERA-106:

    Attachment: springClassicSintax.patch

Upps, the routes were absolute, it's solved

> Spring provider definition parser should handle generic properties
> ------------------------------------------------------------------
>                 Key: ABDERA-106
>                 URL: https://issues.apache.org/jira/browse/ABDERA-106
>             Project: Abdera
>          Issue Type: New Feature
>            Reporter: Jim Ancona
>         Attachments: springClassicSintax.patch
> Currently the Spring provider definition parser allows the user to specify the Provider
class to use. But because it only allows specific provider properties (workspace, workspaceManager,
targetResolver, subjectResolver and filter) to be configured, it is often impossible to configure
the specified class using Spring. One solution would be for the <provider> element to
allow the standard Spring bean <property/> and <constructor-arg/> elements in
addition to the specialized elements.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message