tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Hoffer <dhoff...@gmail.com>
Subject Re: Problems with EAR deployments and CXF
Date Sat, 07 Jun 2014 20:47:45 GMT
Hum, I made those 3 changes but didn't help I get the same CXF marshaling
errors.  Is there I way I can view the actual classpath used by my war(s)?

Maybe the problem is unrelated to this class loading issue but seems
strange the wars work in TomEE but not in the Ear.

-Dave


On Sat, Jun 7, 2014 at 2:34 PM, David Hoffer <dhoffer6@gmail.com> wrote:

> Okay perfect, thanks.
>
> -Dave
>
>
> On Sat, Jun 7, 2014 at 2:16 PM, Romain Manni-Bucau <rmannibucau@gmail.com>
> wrote:
>
>> it will force cxf to be loaded from the app instead of the container
>>
>>
>>
>> Romain Manni-Bucau
>> Twitter: @rmannibucau
>> Blog: http://rmannibucau.wordpress.com/
>> LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> Github: https://github.com/rmannibucau
>>
>>
>> 2014-06-07 22:07 GMT+02:00 David Hoffer <dhoffer6@gmail.com>:
>>
>> > Thanks for the config tips.
>> >
>> > Regarding the optional
>> > openejb.classloader.forced-load=org.apache.cxf...what
>> > will that do?
>> >
>> > Yes I see now we should have just used webprofile.
>> >
>> > -Dave
>> >
>> >
>> > On Sat, Jun 7, 2014 at 11:20 AM, Romain Manni-Bucau <
>> rmannibucau@gmail.com
>> > >
>> > wrote:
>> >
>> > > Hi
>> > >
>> > > edit conf/conf.d/cxf.properties and conf/conf.d/cxf-rs.properties to
>> set
>> > > the property:
>> > >
>> > > disabled = true
>> > >
>> > >
>> > > you can also add in conf/system.properties:
>> > > openejb.classloader.forced-load=org.apache.cxf
>> > >
>> > >
>> > > Finally using tomee webprofile would allow you to not have cxf in the
>> > > container
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > Romain Manni-Bucau
>> > > Twitter: @rmannibucau
>> > > Blog: http://rmannibucau.wordpress.com/
>> > > LinkedIn: http://fr.linkedin.com/in/rmannibucau
>> > > Github: https://github.com/rmannibucau
>> > >
>> > >
>> > > 2014-06-07 15:13 GMT+02:00 David Hoffer <dhoffer6@gmail.com>:
>> > >
>> > > > I'm trying to get my EAR to work correctly when deployed in TomEE.
>>  My
>> > > EAR
>> > > > contains several WARs that are CXF based webservices.  These work
>> fine
>> > as
>> > > > standalone WARs in Tomcat and in TomEE but when I deploy as EAR in
>> > TomEE
>> > > > I'm getting CXF marshaling errors.
>> > > >
>> > > > I see that TomEE has several CXF jars in it's lib folder so I'm
>> > wondering
>> > > > if those are conflicting with the CXF jars in my EAR.
>> > > >
>> > > > How do I manage this?  I don't think I need/want any CXF support
>> from
>> > the
>> > > > container as I already have the jars I need.  Does TomEE support
>> this?
>> > >  Do
>> > > > I have to configure TomEE to use my jars/etc?
>> > > >
>> > > > -Dave
>> > > >
>> > >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message