Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@chemistry.apache.org
Date: Mon, 30 May 2011 16:23:48 +0000 (UTC)
From: "Peter Monks (JIRA)" <jira@apache.org>
To: dev@chemistry.apache.org
Message-ID: 
 <222158983.53713.1306772628250.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <806874597.52708.1306729008492.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CMIS-379) Allow custom AuthenticationProvider's
 to be registered via dependency injection
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CMIS-379?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D130411=
87#comment-13041187 ]=20

Peter Monks commented on CMIS-379:
----------------------------------

The singleton I was referring to was CmisBindingFactory - it uses the class=
ic "private constructor + static getInstance() method" singleton anti-patte=
rn.

> Allow custom AuthenticationProvider's to be registered via dependency inj=
ection
> -------------------------------------------------------------------------=
------
>
>                 Key: CMIS-379
>                 URL: https://issues.apache.org/jira/browse/CMIS-379
>             Project: Chemistry
>          Issue Type: Wish
>          Components: opencmis-client
>    Affects Versions: OpenCMIS 0.3.0
>         Environment: n/a
>            Reporter: Peter Monks
>            Assignee: Florian M=C3=BCller
>             Fix For: OpenCMIS 0.4.0
>
>
> As documented at http://incubator.apache.org/chemistry/opencmis-client-bi=
ndings.html, the only way to configure a custom AuthenticationProvider is t=
o specify the fully-qualified classname as a String entry in the Session pa=
rameters Map.  This is a crude approach that (amongst other things) makes i=
t very difficult to implement a custom AuthenticationProvider that itself h=
as one or more dependencies.
> The solution is to support (but not require, obviously) the dependency in=
jection of custom AuthenticationProviders, either directly (can be injected=
 directly into the CmisBindingFactory) or indirectly (can be injected into =
custom client code, and than passed either as a Session parameter or whatev=
er to CmisBindingFactory).
> From a brief perusal it appears there are at least two ways of achieving =
this:
> # allow an *instance* of an AuthenticationProvider to be provided in the =
Session parameters Map.  Note: this would require that the type of the Map =
is modified from Map<String, String> to Map<String, Object>, but this is pr=
obably a good idea anyway as it seems unlikely that all Session parameters,=
 now and in the future, will always be Strings.
> # add a setter to the CmisBindingFactory that allows the AuthenticationPr=
ovider to be configured directly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira