Customizing WDK Login component.

Is there a recommended approach for customizing the WDK Login component?

I am trying to extend the WDK login component so I can override the authenticate method contained within. My class looks like this:

public class CWLogin extends Login

{

protected void authenticate(...) throws PasswordExpiredException, DfException

{

}

However, when I compile, I get the following strange error:

error: compiler message file broken: key=compiler.err.file javax\servlet\http\Ht
tpSession.class not found arguments=null, null, null, null, null, null, null
1 error

I cannot find any help with google. My assumption is I am doing something wrong, but what is it I'm doing wrong?

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

mszurap

Hi,

Have you added servlet-api.jar to your classpath (if you are using Tomcat for development)? Class not found points in this direction.

All comments

mszurap

Hi,

Have you added servlet-api.jar to your classpath (if you are using Tomcat for development)? Class not found points in this direction.

Francois Dauberlieu

You can find 2 examples of automatic login at http://developer.emc.com/developer/componentexchange.htm#0900c35580940c38

that will show you what to do in terms of development and in terms of configuration

Derrick

I posted my customization to another server by doing the following:

Copy CWLogin.class to $CATALINA/webapps/dam/WEB-INF/classes/com/allianceatlantis/dam/videodam.
Copy LoginNlsProp.properties to $CATALINA/webapps/dam/custom/strings/com/allianceatlantis/dam/videodam.
Copy login_component.xml to $CATALINA/webapps/dam/custom/config.
Copy cwlogin.jsp and cwappintglogin.jsp to $CATALINA/webapps/dam/custom/jsp.

I restarted Tomcat and it's still displaying the DAM Login page. Any ideas why it's skipping my login customization?

mszurap

It should work... Silly questions but:

Have you properly extended the login component? Do you use the same id ("login") in your custom/config/login_component.xml? Does your custom/app.xml extend the dam/app.xml?

Derrick

I actually resolved this a while back. It was the scope tag in the login_component.xml...I took out the version filter and now everything works as expected.

Derrick

I discovered during upgrading to Documentum 6 that customizing the login component doesn't really work for my specific user scenario.

Therefore, I just created a new authentication service and added it to the app.xml in the $CATALINA/webapps/dam/custom directory, within the <application> node:

<service_class>com.allianceatlantis.dam.videodam.CWAuthenticationService</service_class>

</authentication>

I then created a custom class that extended com.documentum.web.formext.session.AuthenticationService and overrode the login() method with my custom code. At the end of the method, I made sure to call super.login() in order to generate the login ticket. My method had to throw the DfAuthenticationException in order to work with WDK.