geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevan Miller <kevan.mil...@gmail.com>
Subject Re: [jira] Created: (GERONIMO-3348) java.lang.NoSuchMethodError in org.springframework.context.i18n.LocaleContextHolder
Date Fri, 03 Aug 2007 00:39:46 GMT

On Jul 31, 2007, at 2:53 PM, Jarek Gawor wrote:

> On 7/31/07, Kevan Miller <kevan.miller@gmail.com> wrote:
>>
>> OK. So, there are testsuite failures. I'm not seeing problems with
>> other testing, however... I see why you removed the hidden-classes
>> filter... Looks like we're in a bit of a Catch-22...
>>
>> I assume restructuring the spring-based configuration of cxf is
>> pretty disruptive/potentially error-prone? Looks like some apps which
>> include Spring and use jaxws could run into the same type of
>> catch-22. Their only option would be to include the same version of
>> spring that's used by our cxf module...
>
> Yes, I think so. But I could spend a day or two to see what it would
> take to configure CXF without Spring.

I wasn't able to get this working. As described previously, I can get  
Spring apps deploying properly by filtering Spring classes and  
resources:

     <hidden-classes>
       <filter>org.springframework.</filter>
       <filter>META-INF/spring</filter>
     </hidden-classes>

However, this breaks CXF-based JAXWS client code. So, some Spring  
apps running on Jetty/CXF will require a deployment plan to perform  
the filtering. For 2.0.1, we should switch our CXF configuration to  
not use Spring.

Also, we probably should create <hidden-resources> to our plans. So,  
above config would become:

     <hidden-classes>
       <filter>org.springframework.</filter>
     </hidden-classes>
     <hidden-resources>
       <filter>META-INF/spring</filter>
     </hidden-resources>

--kevan



Mime
View raw message