In a Windows development environment, open the file: C:\Documents and Settings\MyUserId\Application Data\Subversion\servers in your favourite text editor. Near the bottom of that file is a [global] section with http-proxy-host and http-proxy-port settings. Uncommented those two lines, modify them for your proxy server. Go back to the SVN Repository view in Eclipse, refresh the external SVN repository and it *should* work.

The tools I was using was Eclipse (Indigo), SlikSVN (1.7.2 64-bit), and SubClipse (1.8 via the Eclipse Update Site).

public class MostSpecific extends MediumSpecific<MySpecificModel> { }

public class MediumSpecific<T extends MyModel> extends LeastSpecific<T> { }

public class LeastSpecific<T extends MyModel> implements ILeastSpecificInterface {
	protected T model;
	public T getModel() {
		return model;
	}
}

This enables on the MostSpecific class for getModel() and model to be of type MySpecificModel within the MostSpecific class, yet it is of type MyModel in the classes MediumSpecific and LeastSpecific.

String regexPattern = ".*[" + Pattern.quote( "!\"£$_%^&*()-=[];'#,./\`¬¦|<>?:@~{}+" ) + "].*";

Your pattern will become .*[Q!"£$_%^&*()-=[];’#,./`¬¦|<>?:@~{}+E].*, which is escaped.

java.util.regex.Pattern.html#quote(java.lang.String)

Detail
The problem is that the user in the database is an “orphan”. This means that there is no login id or password associated with the user. This is true even if there is a login id that matches the user, since there is a GUID (called a SID in Microsoft-speak) that has to match as well.

This used to be a pain to fix, but currently (SQL Server 2000, SP3) there is a stored procedure that does the heavy lifting.

All of these instructions should be done as a database admin, with the restored database selected.

First, make sure that this is the problem. This will lists the orphaned users:

EXEC sp_change_users_login 'Report'

If you already have a login id and password for this user, fix it by doing:

EXEC sp_change_users_login 'Auto_Fix', 'user'

If you want to create a new login id and password for this user, fix it by doing:

EXEC sp_change_users_login 'Auto_Fix', 'user', 'login', 'password'

private String convertStreamToString( InputStream in ) throws Exception {
	StringBuilder out = new StringBuilder();
	byte[] b = new byte[4096];
	for ( int n; ( n = in.read( b ) ) != -1; ) {
		out.append( new String( b, 0, n ) );
	}
	return out.toString();
}

<c:set var="painless" value="${xyz.abc}" scope="request"/>
<s:property escapeJavaScript="true" value="%{ #request['painless'] }"/>

public interface MyInterface {
	Map<String, Object> getAttributes();
}

public class MyClass implements MyInterface {
	private Map<String, List<String>> attributes = new HashMap<String, List<String>>();

	public Map<String, Object> getAttributes() {
		return attributes; // Compile error here!
	}
}

Now if you are like me, you would have thought that List<String> is an object, but it doesn’t work like that. Instead you must use a cast with a bit more flexibility. The following cast will remove the compile error and should run like a charm.

@Override
public Map<String, Object> getAttributes() {
	return cast(attributes); // Compile error gone!
}

@SuppressWarnings( "unchecked" )
private <T> T cast( Object o ) {
	return (T) o;
}

Update: Perhaps a more correct way of doing this is already built into Java – an example is below adapted from stackoverflow.com.

public Map<String, Object> getAttributes() {
	return attributes.getClass().cast( attributes );
}