Hi again, thanks a lot for your advice, Martin.
We spent a lot of time into skinny wars but stuck with ejb dependencies. The EAR contains several WAR modules and these WAR modules share several EJB modules. Unfortunately, the skinny war option seems to ignore transitive EJB dependencies so that we get errors with duplicate beans on startup. All workarounds we could imagine do not work properly. Recently we tried to omit the "<type>ejb</type>" on all EJB dependencies and put all libs into the EAR-root folder. This "hack" leads our wildfly into some unpredictable (and completely messed up state) deploying all beans into any random module... Some sites advice to exclude $(war_module)/lib completely what makes the WAR module undeployable in standalone mode. Could you please point us any direction to get skinny wars working with shared EJB modules? Thanks a lot, Clemens von Musil 2016-11-09 9:18 GMT+01:00 Martin Hoeller <mar...@xss.co.at>: > Hi! > > On 08 Nov 2016, Clemens von Musil wrote: > > > I am working on a multimodule maven project consisting of several EJB, > WAR > > and an EAR module. The EJB modules contain shared functionality. > > > > To increase development speed, I want the WAR modules build in a way that > > allows me to bundle them into the EAR as well as deploy them standalone > in > > my EE container. > > Wrong approach! Build the WAR as you would need it in standalone-mode and > configure the maven-ear-plugin to make the WAR a skinny war. > > Details can be found here: > https://maven.apache.org/plugins/maven-ear-plugin/ > examples/skinny-wars.html > > hth, > - martin > -- Clemens von Musil - mu...@sipgate.de Telefon: +49 (0)211-63 55 56-85 Telefax: +49 (0)211-63 55 55-22 sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.at - www.sipgate.co.uk
