Re: [higgins-dev] JavaScript Policy Context Provider (AKA, Mapping CP)

["Tom Doman" <TDoman@xxxxxxxxxx>]

Yes I will.  In fact, once I have a perfect replication of the mappings
we've hard coded for the STS, you'should have to change very little,
if anything, in the STS (perhaps a small change to configuration.xml???
perhaps nothing at all).  Nevertheless, I'll have samples in the test
project.

Tom

>>> Michael McIntosh <mikemci@xxxxxxxxxx> 3/9/2007 6:41 PM >>>
Tom,

Are you going to be able to provide sample code for how one would use this 
along with another CP (e.g. JNDI) to achieve what we do now with JNDI CP 
only?

Thanks,
Mike

higgins-dev-bounces@xxxxxxxxxxx wrote on 03/09/2007 07:05:34 PM:

> All,
> 
> The JavaScript Policy Context Provider and an associated test 
> project have been checked into eclipse and are now available for 
checkout.
> 
> I still need to fixup the test project a bit to properly reference 
> the JNDI CP and I need to check in the Virtual Context Provider to 
> eclipse so that the tests run against at least a couple of CPs.  I 
> also need to update the Higgins Components page as soon as I get my 
> next chance so that the CVS instructions and configuration 
> documentation are available there.
> 
> Next, I will be removing the hard coded mappings from the JNDI CP 
> and checking that in.  But I will not do that until I have a perfect
> replication of the mappings we've provided for the STS and reference
> application.  However, be warned, the change is coming and the 
> JavaScript Policy CP will be required to achieve configurable, 
> flexible mappings via simple JavaScript.
> 
> Tom
> 
> _______________________________________________
> higgins-dev mailing list
> higgins-dev@xxxxxxxxxxx 
> https://dev.eclipse.org/mailman/listinfo/higgins-dev 

_______________________________________________
higgins-dev mailing list
higgins-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/higgins-dev