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.
