[jetty-dev] [jira] (JETTY-1549) jetty-maven-plugin fails to reload the LoginService properly

Jan Bartel
resolved JETTY-1549 as Fixed

jetty-maven-plugin fails to reload the LoginService properly

Fixed for jetty-9. For jetty-7 and jetty-8, I suggest a workaround, where the identityService is explicitly configured:

<pre>

<Configure class="org.eclipse.jetty.webapp.WebAppContext">

<Get name="securityHandler">

<Set name="identityService">

<New id="idService" class="org.eclipse.jetty.security.DefaultIdentityService"/>

</Set>

<Set name="loginService">

<New id="DefaultLoginService" class="org.eclipse.jetty.security.HashLoginService">

<Set name="name">MyRealm</Set>

<Set name="config">src/main/webapp/WEB-INF/realm.properties</Set>

<Set name="refreshInterval">5</Set>

<Set name="identityService"><Ref id="idService"/></Set>

</New>

</Set>

</Get>

</Configure>

</pre>

A couple of other tips:

1. The call to start on the SecurityHandler in jetty-web.xml shouldn't be necessary, as it should be started as the context is started.

2. You should probably use the jetty "start" mojo, rather than "run", as "start" was designed specifically for use in execution bindings in the pom, rather than from the command line (for which "run" was designed). Here's some doc on that: http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin#jetty:start__:__Starting_jetty_without_first_executing_the_build_up_to_.22test-compile.22_phase

regards,

Jan

Change By:

Jan Bartel
(04/Nov/12 10:18 PM)

Resolution:

Fixed

Fix Version/s:

9.0.0

Status:

Open
Resolved

This message is automatically generated by JIRA.

If you think it was sent incorrectly, please contact your JIRA administrators .

For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email