Well, when you get to it let me know, it's ~very~ easy to make a change and
quickly deploy the docs now.

On 6/9/06, James Carman <[EMAIL PROTECTED]> wrote:

Oh, so you want to directly link to my site?  I figured that since we will
already have a link to tapestry-javaforge that folks could get to
tapernate, tapestry-autowire, tapestry-acegi, etc. from there.  I would
imagine (and I control it) that the URL for the tapestry-acegi project's
documentation will be www.carmanconsulting.com/tapestry-acegi.


> I meant linked here:
>
> http://tapestry.apache.org/
>
> On 6/9/06, James Carman <[EMAIL PROTECTED]> wrote:
>>
>> The tapestry-acegi and tapernate modules are both subprojects of the
>> tapestry-javaforge project.  So, we're already linked in.  I need to
>> update the tapestry-javaforge site in SVN to point to my sites on my
>> server.
>>
>> It won't be difficult to get the documentation written for
>> tapestry-acegi.
>> It'll just take a bit of time.
>>
>> > If you put up a shell mvn site I'll make sure you get linked in.
>> >
>> > On 6/9/06, James Carman <[EMAIL PROTECTED]> wrote:
>> >>
>> >> All,
>> >>
>> >> The tapernate-example application has been refactored to reflect the
>> >> latest
>> >> changes in the Tapestry/Acegi integration module.  Now, the Acegi
>> >> support
>> >> is
>> >> more "drop-in-able."  Here's the only configuration required:
>> >>
>> >> <implementation service-id="hivemind.acegi.dao.UserDetailsService" >
>> >>   <invoke-factory>
>> >>     <construct
>> >> class="
>> >>
com.carmanconsulting.tapernate.example.domain.dao.impl.UserDetailsSer
>> >> viceImpl"/>
>> >>   </invoke-factory>
>> >> </implementation>
>> >>
>> >> This is required because the hivemind.acegi.dao module automatically
>> >> adds
>> >> the DaoAuthenticationProvider to the authentication providers list
>> and
>> >> the
>> >> DaoAuthenticationProvider requires a UserDetailsService.
>> >>
>> >> <contribution configuration-id="hivemind.acegi.AccessDecisionVoters
">
>> >>   <voter object="instance:org.acegisecurity.vote.RoleVoter" />
>> >> </contribution>
>> >>
>> >> This is required because Acegi needs at least one "decision voter."
>> >>
>> >> <contribution configuration-id="hivemind.ApplicationDefaults">
>> >>   <default symbol="hivemind.acegi.dao.systemWideSalt" value="DUKE"
/>
>> >> </contribution>
>> >>
>> >> This isn't exactly required, but suggested.  The hivemind.acegi.dao
>> >> module
>> >> uses a system-wide salt which defaults to "CAFEBABE" (the Java class
>> >> file
>> >> "magic number").  You should override this.
>> >>
>> >> Other than that, it just works (as long as you want BASIC
>> >> authentication).
>> >> You can also override the authentication realm name using symbol
>> >> overrides.
>> >>
>> >> James
>> >>
>> >>
>> >>
>> >>
---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>> > --
>> > Jesse Kuhnert
>> > Tacos/Tapestry, team member/developer
>> >
>> > Open source based consulting work centered around
>> > dojo/tapestry/tacos/hivemind.
>> >
>>
>>
>> James Carman, President
>> Carman Consulting, Inc.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Jesse Kuhnert
> Tacos/Tapestry, team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind.
>


James Carman, President
Carman Consulting, Inc.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Jesse Kuhnert
Tacos/Tapestry, team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind.

Reply via email to