-
1. Re: How to deploy MS3.2 on EAP6.1.beta ?
hchiorean May 14, 2013 7:28 AM (in response to sebastien.michea)Not sure what you mean by "it seems that EAP6.1.beta doesnt have a standalone directory like jboss 7.1 did": assuming you downloaded EAP 6 beta from http://www.jboss.org/jbossas/downloads.html & extracted the zip file, the folder structure is 98% identical to AS7.1.1 (the only real difference is in the modules folder). In other words, it definitivelly has a jboss-eap-6.1/standalone/configuration folder with various standalone-<config>.xml files.
As far as the ModeShape kit goes, once you've unpacked that in jboss-eap-6.1, all you need to do is to startup EAP using jboss-eap-6.1/bin/standalone.sh(bat) -c standalone-modeshape.xml
-
2. Re: How to deploy MS3.2 on EAP6.1.beta ?
sebastien.michea May 14, 2013 3:38 PM (in response to hchiorean)Hi Horia,
Thank you for your answer, i downloaded from there but my mistake was when copying modeshape directories i replaced the EAP ones. Not yet accustomized to this Finder...
-
3. Re: How to deploy MS3.2 on EAP6.1.beta ?
sebastien.michea May 14, 2013 4:00 PM (in response to hchiorean)By the way is it normal that the modeshape kit contains javax and org dirs under modules/ ?
like you mentionned those modules are in EAP6.1 under modules/system/layers/base not under modules/ anymore -
4. Re: How to deploy MS3.2 on EAP6.1.beta ?
rhauch May 14, 2013 5:41 PM (in response to sebastien.michea)1 of 1 people found this helpfulBy the way is it normal that the modeshape kit contains javax and org dirs under modules/ ?
Yes, that is normal. The ModeShape kit contains modules for the JCR API (the "javax..." module) and quite a few "org..." modules for the ModeShape JARs and some 3rd party libraries that don't provide AS7/EAP modules.
like you mentionned those modules are in EAP6.1 under modules/system/layers/base not under modules/ anymore
Yes, EAP 6.1 contains the start of a change toward using "system/layers" (and other folder structures) underneath "modules". The design has not yet been finalized, so EAP actually looks for modules in multiple locations, including "modules" and "modules/system/layers" (among others). I expect this EAP feature to stabilize pretty quickly.
EAP contains a number of libraries that ModeShape strongly depends upon, so it's critical that ModeShape and dependency versions line up. That's why the kit from a given ModeShape release is intended for a specific version of EAP. This means that as EAP matures its "modules" directory structure over one or more future releases, ModeShape can easily adapt with its corresponding new release(s).
-
5. Re: How to deploy MS3.2 on EAP6.1.beta ?
sebastien.michea May 14, 2013 5:49 PM (in response to rhauch)Thats clear, thx !