May I suggest, until running DS as a static module in WF is tested and supported, removing the module.xml files from the distribution? It implies it's fully supported, and folks will just copy the directories into their JBoss/Wildfly installs and expect everything to work (and be disappointed).
I say that as someone who tried it, and was disappointed. ;) On Mon, May 25, 2015 at 3:27 AM, Ron Smeral <[email protected]> wrote: > Hi, > > running DS as a static module hasn't yet been tested by RH's DeltaSpike > QE. I've started some work on the DS testsuite so that it doesn't > automatically package DS in deployments and it could be run against a WF > with DS as a static module maybe just using a parameter or something. > This isn't finished yet though. > > I'd expect exactly that kind of issues as Harald writes -- classloading > issues. I think most things should work but I wouldn't suggest running > DS as static module in production just yet. > > Regards, > Ron > > On 22.5.2015 16:09, Karl Pietrzak wrote: > > Awesome! What's the advice for usage in Wildfly? Installed as a system > > module (e.g., module.xml and everything), or as packaged in the EAR/WAR? > > > > On Fri, May 22, 2015 at 3:18 AM, Gerhard Petracek <[email protected]> > > wrote: > > > >> The Apache DeltaSpike team is pleased to announce the 16th release of > >> DeltaSpike. > >> > >> Apache DeltaSpike is not a CDI-container, but a portable CDI extension. > >> > >> Documentation: > >> http://deltaspike.apache.org/documentation/ > >> > >> Download: > >> http://deltaspike.apache.org/download.html > >> > >> Release Notes: > >> http://s.apache.org/DeltaSpike_1.4.0 > >> > >> Enjoy! > >> > >> Gerhard Petracek > >> > > > > > > > > -- > Ron Smeral > JBoss Quality Engineer > Brno > -- Karl
