[
https://issues.apache.org/jira/browse/ABDERA-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567106#action_12567106
]
James M Snell commented on ABDERA-106:
--------------------------------------
The patch does not appear to line up with the current code in trunk and I don't
know enough about spring to fix it up myself. Can you please take another look
at the patch?
> 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.
