- Mar 22, 2012
-
-
Florent Benoit authored
-
Mohammed Boukada authored
* Update persistence unit by adding eclipselink properties to enable multitenant
-
Mohammed Boukada authored
-
Mohammed Boukada authored
* Adding Bean to manage MultitenantVirtualJNDIBindingMBean
-
Mohammed Boukada authored
* Add eclipselink properties to enable multitenant
-
Mohammed Boukada authored
-
Mohammed Boukada authored
- add a prefix - use a virtual JNDI binding management
-
Mohammed Boukada authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
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
- Mar 21, 2012
-
-
Loris Bouzonnet authored
-
Loris Bouzonnet authored
-
Florent Benoit authored
Provides in a directory the endorsed libraries of Java EE 6
-
Florent Benoit authored
JOnAS could start in more than 60s so increase max waiting time to check if cargorpc has been deployed
-
Florent Benoit authored
-
Florent Benoit authored
Also Java EE api should be available before deployment plan (for example JAXB api should be available before people using it, etc)
-
Florent Benoit authored
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
-
Hélène Joanin authored
-
Jérémy Cazaux authored
-
Jérémy Cazaux authored
-
Jérémy Cazaux authored
-
- Mar 19, 2012
-
-
Florent Benoit authored
-
Florent Benoit authored
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
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Florent Benoit authored
-
Loris Bouzonnet authored
-
- Mar 16, 2012
-
-
Loris Bouzonnet authored
-
Florent Benoit authored
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
-
- Mar 14, 2012
-
-
Loris Bouzonnet authored
-