DDevelopment & Design

Servicemix: Could not parse settings maven_path/settings.xml under Windows XP

Today I encountered problem with servicemix

Could not parse settings [file:/C:/Documents and Settings/Bartek/.m2/settings.xml]

A quick look at karaf.log revealed the problem

Caused by: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 4-byte UTF-8 sequence.

So the problem is with BOM (byte order mark) in settings.xml file. Many Windows editors add it at start of an utf encoded files. You should save settings.xml as ordinary utf8 file without BOM.

Problem solved.

— Previous article

Oracle SQL Developer dla MSSQL

Next article —

Licealista zwycięzcą ITPW

You May Also Like
DDevelopment & Design

Spring Security by example: securing methods

This is a part of a simple Spring Security tutorial:

1. Set up and form authentication
2. User in the backend (getting logged user, authentication, testing)
3. Securing web resources
4. Securing methods
5. OpenID (login via gmail)
6. OAuth2 (login via Facebook)
7. Writing on Facebook wall with Spring Social

Securing web resources is all nice and cool, but in a well designed application it's more natural to secure methods (for example on backend facade or even domain objects). While we may get away with role-based authorization in many intranet business applications, nobody will ever handle assigning roles to users in a public, free to use Internet service. We need authorization based on rules described in our domain.

For example: there is a service AlterStory, that allows cooperative writing of stories, where one user is a director (like a movie director), deciding which chapter proposed by other authors should make it to the final story.

The method for accepting chapters, looks like this:

Read more »