-
Bug
-
Resolution: Done
-
Major
-
3.3.0.M4
-
None
In a web.xml file we have this bit of code:
<servlet>
<description></description>
<display-name>LoginServlet</display-name>
<servlet-name>LoginServlet</servlet-name>
<servlet-class>dk.jyskebank.core.jsf.login.FacesLoginServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>LoginServlet</servlet-name>
<url-pattern>/loginServlet</url-pattern>
</servlet-mapping>
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/loginServlet</form-login-page>
<form-error-page>/login/loginfail.jsp</form-error-page>
</form-login-config>
</login-config>
The 'Check form-login-page attribute' verification rule marks this as a failure, saying:
error: Attribute form-login-page references to /loginServlet that does not exist in web content
In a way, the verifier is right; the jar with the LoginServlet.class lives outside the web content folder, but it copied into WEB-INF/lib as part of Deployment Assembly.
And the jar is on build classpath, obviously.
I tried copying the jar into the web content folder directly, but it has no effect on the verifier.
