Hi,
I've been playing with the notion of embedding CXF inside an EAR
application, written by me, that is deployed to an app server. In JBoss
4.2.3, embedding is straightforward, however, several issues pop up in
Geronimo 2.1.3 with respect to the
MANIFEST/META-INF/MANIFEST.MF/Class-path attribute. These issues are
related to saaj.jar, activation.jar and jaxp-api.jar (because of the
incorrect Class-path value, eg. looking for saaj.jar when the version
includes saaj-1.3.jar or because they are not required to run either a
service or a client accessing a service, in the simple case).
Geronimo seems a lot less tolerant of an EAR deployment that cannot
resolve all of the referenced jar files that are embedded in the
class-path attribute of the MANIFEST.MF file, which I understand is more
in line with the Java EE 5 specification.
My question is, do I need to go through all of jar files and make sure
their MANIFEST.MF/Class-path's are in alignment with included
dependencies in order to resolve the deployment issue in Geronimo or is
there an easier way to embed CXF directly for this use case?
Note, I am aware that I can configure Geronimo to use an embedded CXF
container rather than the default Axis version installed, however, I
would like to be able to embed CXF directly in this app, at least for now.
Thanks for any suggestions,
John
