Thanks a lot Daniel! After your tests , there are 2 possibilities: 1) CXF its using the Spring 2.5.6 from liferay ( i dont really think this can cause that exception that i posted) 2) The imcompatibility is with another CXF version... My CXF version its not 2.2.x, its a older one, i´ve tested with a 2.1.x version .
I will try another cxf versions later. But now, we gived up CXF. We used java wsimport to generate de JAX-WS Artifacts, and it´s working. Anyway, i´ll keep you informed. If i have time to make other tests and investigation :) Again, thanks a lot for your quick response! Bruno Ledesma 2009/5/13 Daniel Kulp <[email protected]> > On Tue May 12 2009 5:14:13 pm Bruno Ledesma wrote: > > Sorry, JBoss is using Spring 2.07 (wrong info) > > I just ran the CXF trunk (2.2.x) tests with Spring 2.0.7 and everything > passed. Thus, you should be able to just use the Spring 2.0.7 stuff that > JBoss ships. > > Dan > > > > All CXF versions that i've been testing use at least Spring 2.08. I tryed > > to use a isolated classLoader in my war using jboss-web.xml Classloader > > isolation tags , but i get another problem, cause its a liferay portlet > and > > somehow im kind of limitating the portlet classpath. > > I also have spring jars loaded by Liferay (I think its a 2.5.6 spring) > > > > Im now on a JAR Hell that i dont see anyway to solve. > > > > thanks for your reply! > > Bruno Ledesma > > > > 2009/5/12 Daniel Kulp <[email protected]> > > > > > You MAY be able to use Spring 2.0.8 with CXF as well. The 2.1.x line > of > > > CXF > > > still uses Spring 2.0.8 and I don't think we "removed" anything on the > > > 2.2.x > > > line that would prevent it from working with 2.0.8. Thus, it might > > > work. Give it a try and see. :-) > > > > > > Dan > > > > > > On Mon May 11 2009 2:47:39 pm Bruno Ledesma wrote: > > > > Hello Everyone! > > > > > > > > Im currently developing WebService clients with CXF and the maven cxf > > > > codegen plugin. But im having some problems to deploy my war into > Jboss > > > > 4.2.2GA. > > > > > > > > The exception is: > > > > > > > > java.lang.IllegalArgumentException: Class > > > > [org.springframework.aop.config.AopNamespaceHandler] does not > > > > implement the NamespaceHandler interface > > > > at > > > > > > > org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.ini > > >tH > > > > > > >andlerMappings(DefaultNamespaceHandlerResolver.java:119) at > > > > > > > org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<in > > >it > > > > > > >>(DefaultNamespaceHandlerResolver.java:96) at > > > > > > > org.springframework.beans.factory.xml.DefaultNamespaceHandlerResolver.<in > > >it > > > > > > >>(DefaultNamespaceHandlerResolver.java:71) > > > > > > > > Looking for some explanations on google, i found that this kind of > > > > exception is a classpath issue. The JbossWebDeployer uses a older > > > > Spring than the CXF (jboss=> spring 2.0.8 - cxf 2.2 =>spring 2.5.5). > > > > Does anyone know a way to solve this problem? Does anyone uses Jboss > 4 > > > > as contatiner for a CXF WS Client? > > > > > > > > Thanks! > > > > > > > > Bruno Ledesma > > > > > > -- > > > Daniel Kulp > > > [email protected] > > > http://www.dankulp.com/blog > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog >
