You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dennis Kieselhorst (JIRA)" <ji...@apache.org> on 2018/05/14 05:33:00 UTC

[jira] [Commented] (CXF-7718) CXF needs jcache on weblogic

    [ https://issues.apache.org/jira/browse/CXF-7718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16473780#comment-16473780 ] 

Dennis Kieselhorst commented on CXF-7718:
-----------------------------------------

There are a lot of changes between 3.1.x and 3.2.x. Could you please try the latest release 3.1.15 and 3.2.4 first to see if that makes any difference?

> CXF needs jcache on weblogic
> ----------------------------
>
>                 Key: CXF-7718
>                 URL: https://issues.apache.org/jira/browse/CXF-7718
>             Project: CXF
>          Issue Type: Bug
>    Affects Versions: 3.2.1
>         Environment: Weblogic Server 12cR2
>            Reporter: Christoph Giera
>            Priority: Critical
>
> Deploying a web application with cxf 3.2.1 on weblogic 12c doesn't work without adding jcache and an cache implementation.
> See [https://stackoverflow.com/questions/47650275/spring-boot-camel-cxf-on-weblogic-12c-java-lang-noclassdeffounderror-javax] 
> This post has similar libs/env but exact the same unwanted behaviour.
> CXF 3.1.9 on the same environment starts up without jcache exceptions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)