Fix for wonder-89: Don't attempt to save the parent EC of a new EO as none exists.
check for different strings in exception message
Fix for false security exception

Security exceptions would be raised for file names with a "%20" in them. This is because it is also a url-encoding for the "space" character.

Signed-off-by: Aaron Rosenzweig <aaron@chatnbike.com>
Improve documentation explaining why decoding is being done when and where it is. Refactor individual logic blocks (fetching the ERAttachment, evaluating if a request is legitimate) into their own methods to make code more digestible and better encapsulated.
Making sure a SecurityException is always thrown when we aren't able to return an attachment.

Signed-off-by: Aaron Rosenzweig <aaron@chatnbike.com>
Issue #587 fixed
flip strings for correct regex matching
must start new transaction when using ERXJDBCAdaptor before creating _dbupdater
Unlock editing contexts disposed by the ERXRouteController

The ERXRouteController disposes the editing context at the end of the request handling. If the editing context is autoLocked during the request, at least one lock will remain open at disposal time (because of the coalesceAutoLocks property). This change unlocks the editing context before disposing it, avoiding inaccurate warnings when the tracing open locks option is enabled.
Merge pull request #593 from hprange/improveRestControllerCleanUp

Unlock editing contexts disposed by the ERXRouteController
Revert change caused "Should pop, but ec not found in Vector" errors in RestAPI.
- ERXApplication._endRequest() will call ERXEC.unlockAllContextsForCurrentThread() at proper time
- It's became to be possible to have unlocked ECs, not being disposed by this RouteController. It's causes unexpected side effects
Merge pull request #594 from hypeastrum/fixEcUnlockingIssue

Revert change caused "Should pop, but ec not found in Vector" errors in ...
Unlock the editing context disposed by the ERXRouteController

The ERXRouteController disposes the editing context at the end of the route request handling. If the editing context is autoLocked during the request, at least one lock will remain open at disposal time (because of the coalesceAutoLocks property). This change unlocks the editing context before disposing it, avoiding inaccurate warnings when the tracing open locks option is enabled.

`ERROR er.extensions.eof.ERXEC  - ERXEC@1877591773 Disposed with 1 locks (finalizing = false)`

Which was created by the ERXRouteController:

```
ERROR er.extensions.eof.ERXEC  - ERXEC@1877591773 Created:
java.lang.Exception: Creation
	at er.extensions.eof.ERXEC.<init>(ERXEC.java:471)
	at sun.reflect.GeneratedConstructorAccessor28.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
	at er.extensions.eof.ERXEC$DefaultFactory._createEditingContext(ERXEC.java:1807)
	at er.extensions.eof.ERXEC$DefaultFactory._newEditingContext(ERXEC.java:1741)
	at br.com.doit.eof.DOitEditingContextFactory._newEditingContext(DOitEditingContextFactory.java:28)
	at er.extensions.eof.ERXEC$DefaultFactory._newEditingContext(ERXEC.java:1720)
	at er.extensions.eof.ERXEC.newEditingContext(ERXEC.java:1874)
	at er.rest.routes.ERXRouteController.newEditingContext(ERXRouteController.java:264)
	at er.rest.routes.ERXRouteController.editingContext(ERXRouteController.java:252)
```

This solution is more specific than the solution provided in the pull request #593 and reverted by the pull request #594. It unlocks ONLY the editing context created by the ERXRouteController, rather than unlocking all editing contexts in the current thread.
Merge pull request #595 from hprange/improveRestControllerCleanUp2

Unlock the editing context disposed by the ERXRouteController
Fix loading of properties from jar bundles
Fix Ajax submits when deploying as servlet; Add ERXServletApplication class
Fix loading Resources/server.wsdd from a 'jar framework' (used to configure web services)
Remove duplicate dependency declaration
[maven-release-plugin] prepare release wonder-6.1.2
[maven-release-plugin] prepare for next development iteration