Since we now allow extended chars for any url, Aggregator filter may now check the esistence in the jcr repository of a path containing invalid chars.

Although this doesn't cause any problem to the user (an invalid path is translated to a 404, which is the expected result), this may generate some annoying logs.

Requesting a URL with:

• an invalid char like '*', ':' (e.g. http://mysite/test*a:b.html )
• a trailing slash (e.g. http://mysite/test /a.html )
• an single / (e.g. http://mysite// )

generates a MalformedPath/IllegalName exception wrapped into a RepositoryException and logged (with error level).

Since there is no specific exception thrown we can't add an appropriate silent catch, so we should avoid calling isExist() for invalid handles.

Unfortunately it seems there is nothing available for validating a path in Jcr... Jackrabbit has something similar but only in version 2.0 and using jackrabbit-specific APIs, so it's not an option. The only simple solution is to explicitly check for common chars/rules like the ones before in the Aggregator filter.