> Yeah I discovered this too. Anyway to accomplish this outside of > embeddng the war in an ear? >
I have always taken the EAR approach documented on the CXF site, but to save on the footprint of the ear files (i.e not duplicating CXF jars in every ear file) I create and deploy a WebLogic Shared Library that contains all of the required CXF jars and then reference it from the various WAR modules using the weblogic.xml descriptor like such: <?xml version = '1.0' encoding = 'ISO-8859-1'?> <weblogic-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-web-app http://www.bea.com/ns/weblogic/weblogic-web-app/1.0/weblogic-web-app.xsd"; xmlns="http://www.bea.com/ns/weblogic/weblogic-web-app";> <library-ref> <library-name>apache_cxf23_lib</library-name> </library-ref> </weblogic-web-app> At runtime Shared Library behaviour is exactly the same as bundling the CXF jars with the WAR, meaning the class loading behaviour is the same. Cheers Hannes
