* Update persistence unit by adding eclipselink properties to enable multitenant

* Adding Bean to manage MultitenantVirtualJNDIBindingMBean

* Add eclipselink properties to enable multitenant

- add a prefix
- use a virtual JNDI binding management

JAX-WS 2.2 and JAXB 2.2 API needs to be for the JavaEE6 profile while for JavaEE5 we needs to use JAXB 2.1 and JAX-WS 2.1 API
Also for JAXB 2.1 API we don't need anymore to patch ContextFinder as the version (1.9.0) of the bundle already contains the fix

Provides in a directory the endorsed libraries of Java EE 6

JOnAS could start in more than 60s so increase max waiting time to check if cargorpc has been deployed

Also Java EE api should be available before deployment plan (for example JAXB api should be available before people using it, etc)

Also report fix from our patched ContextFinder
TypeConstraintException shouldn't be patched anymore as fix is in the upstream
Also upgrade also stax API so that both Jaxb and stax are using the same servicemix spec locator API

This is because as the WAR and the EJB should share the same ENC object (java:comp/env) we need to analyze first both web.xml and ejb-jar before starting components
By only delegating an EJB3 deployable to the deploymanager we can not manage the lifecycle (like resolving/enhancing) before performing other steps

Set timeout to 0 so that we don't wait JOnAS when starting (as failure with failfast mode will stop JOnAS before the ping)
And then, we need to add our own internal ping which is done by checking if cargoRPC is dropped in work/ folder