cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-5850) Can't find org.apache.cxf.APIMessages bundle
Date Tue, 08 Jul 2014 13:43:04 GMT

     [ https://issues.apache.org/jira/browse/CXF-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-5850.
------------------------------

       Resolution: Invalid
    Fix Version/s: Invalid
         Assignee: Daniel Kulp


This is not really something we'll look into for a few reasons:

1) We no longer support CXF 2.4.x.   Please update to a newer version of CXF and see if the
problem remains.  (it shouldn't, we not longer have that APIMessages.properties file)

2) This is using the JBoss CXF integration.  They use some custom classloaders and such (as
evident by the checkAndFixContextClassLoader call) which may be causing issues.  That is something
you would need to pursue with them.

> Can't find org.apache.cxf.APIMessages bundle
> --------------------------------------------
>
>                 Key: CXF-5850
>                 URL: https://issues.apache.org/jira/browse/CXF-5850
>             Project: CXF
>          Issue Type: Bug
>          Components: Bus
>    Affects Versions: 2.4
>         Environment: JDK 1.7_u55, JBOSS AS 7.1, CXF 2.4.6
>            Reporter: Gaurav
>            Assignee: Daniel Kulp
>            Priority: Critical
>             Fix For: Invalid
>
>
> We recently upgrade our application to JDK 1.7_u55 and now while initializing CXF it
is throwing exception saying : Can't find org.apache.cxf.APIMessages bundle. There is APIMessages.properties
file present inside cxf-api-2.4.6.jar. Has it got anything to do with JDK version.
> java.util.MissingResourceException: Can't find org.apache.cxf.APIMessages bundle
> 	at java.util.logging.Logger.setupResourceInfo(Logger.java:1534) [rt.jar:1.7.0_55]
> 	at java.util.logging.Logger.<init>(Logger.java:267) [rt.jar:1.7.0_55]
> 	at java.util.logging.Logger.<init>(Logger.java:261) [rt.jar:1.7.0_55]
> 	at org.apache.cxf.common.logging.AbstractDelegatingLogger.<init>(AbstractDelegatingLogger.java:43)
> 	at org.apache.cxf.common.logging.Log4jLogger.<init>(Log4jLogger.java:77)
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_55]
> 	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
[rt.jar:1.7.0_55]
> 	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
[rt.jar:1.7.0_55]
> 	at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_55]
> 	at org.apache.cxf.common.logging.LogUtils.createLogger(LogUtils.java:228)
> 	at org.apache.cxf.common.logging.LogUtils.getL7dLogger(LogUtils.java:190)
> 	at org.apache.cxf.BusFactory.<clinit>(BusFactory.java:71)
> 	at org.jboss.wsf.stack.cxf.client.ProviderImpl.checkAndFixContextClassLoader(ProviderImpl.java:193)
> 	at org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:139)
> 	at javax.xml.ws.Service.<init>(Service.java:57) [jboss-jaxws-api_2.2_spec-2.0.0.Final.jar:2.0.0.Final]



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message