Matt, I've got the basics working, there are tweaks and adjustments needed before it's ready for prime time, IMHO, but I need to get some traction getting mule set up here so I'm going to move on to that but will continue to adjust and otherwise improve/optimize the CXF installation. I'd be happy to write this up for you, we might want to wait until some of the tweaks are in before going whole hog but if you let me know what thresholds are critical and how you want it done I'd be happy to help out, I know a number of us have been wanting to get CXF in there properly. Anyway, provide me with some direction and I'll provide you with some labor and hopefully we can u[grade appfuse to CXF for real.
One thing that I'm not comfortable with as it stands is the wsdl generation. The xfire implementation provided the full deal, with XSD stuff for the domain objects and it includes methods inherited from the mgr superclass. The CXF version exposes *only* those methods in the interface proper (no inherited methods are exposed) and it skips the XSD of the domain classes as well. There are probably some options that need tweaking in CXF to get the functionality we want, I've been playing with it yesterday a bit but I need to get on with my mission here so for now I'm going to move on to integrating mule and see how that goes. I'm interested in hearing what target functionality you consider threshold and will happily implement it as I figure out how. I'd personally like to see it support both code first and wsdl first dev. Hit me up and let me know what your thoughts are and I'll plug away toward it... --jack jackalista wrote: > > I just found Nils later post on the restful services stuff here: > > http://blog.srvme.de/2009/01/22/rest-soap-for-cxfapache-appfuse/ > > I followed the config adding the dependencies to the top level pom.xml and > was able to remove the endpoint registration from > web/applicationContext.xml and locate it in cxf-servlet.xml. I was also > able to remove the import's from core/applicationContext.xml in favor of > the ones in Nils' cxf-servlet.xml: > > <import resource="classpath:META-INF/cxf/cxf.xml" /> > <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" > /> > <import > resource="classpath:META-INF/cxf/cxf-extension-jaxrs-binding.xml" /> > <import resource="classpath:META-INF/cxf/cxf-servlet.xml" /> > > I'm far from sure but this seems better so I think I may keep it, at least > all the CXF stuff is in a CXF file. It's also closer to the way appfuse > supported XFire so I'll keep it like this for now. I also added the RS > (rest) stuff to the dependencies and imports as I may want to support REST > too (note also the JAX-RS binding import above). This still has a > circular import on cxf-servlet.xml but I guess that doesn't matter... > > -=j=- > > > jackalista wrote: >> >> OK, newsflash -- you don't need the cxf-servlet.xml at all, apparently. >> You can remove the entry from web.xml and remove the cxf-servlet.xml file >> from web/src/main/webapp/WEB-INF and all appears the same. I'm going to >> dig through the CXF docs a bit more... I want a better explanation of >> these config files and what / where /when they're needed... >> >> -=j=- >> >> >> >> jackalista wrote: >>> >>> OK, I got this working but it's not working exactly as I had expected. >>> I took a cue from the java_first_spring_support sample from CXF and took >>> the <jaxws:endpoint> decl and moved it from cxf-servlet.xml, where it >>> was causing the container to register it twice for some reason, to >>> applicationContext.xml. First I tried the core version of >>> applicationContext.xml (in modular struts2 appfuse archetype) but when >>> deployed, it blew up because it couldn't find >>> javax/servlet/ServletOutputStream. I then moved the <jaxws:endpoint> to >>> the applicationContext.xml in the web sub folder and it worked. >>> >>> The problem I'm seeing now is that the wsdl generated doesn't include >>> the inherited superclass service methods like get(), save(), remove(), >>> etc. Do you have to set a flag somewhere to get these methods included >>> from the superclass? >>> >>> So far, so good, however, I'm getting a service listing and it produces >>> a wsdl, so it seems to be working. >>> >>> To summarize quickly what you have to do (or rather what I *did* do): >>> >>> 1. add these dependencies to your top level pom.xml (for a modular >>> archetype): >>> >>> <dependency> >>> <groupId>org.apache.cxf</groupId> >>> <artifactId>cxf-api</artifactId> >>> <version>2.2.3</version> >>> </dependency> >>> <dependency> >>> <groupId>org.apache.cxf</groupId> >>> <artifactId>cxf-rt-frontend-jaxws</artifactId> >>> <version>2.2.3</version> >>> <exclusions> >>> <!-- >>> http://www.jroller.com/melix/entry/apache_cxf_maven_javamail_awful --> >>> <exclusion> >>> <groupId>org.apache.geronimo.specs</groupId> >>> <artifactId>geronimo-javamail_1.4_spec</artifactId> >>> </exclusion> >>> </exclusions> >>> </dependency> >>> <dependency> >>> <groupId>org.apache.cxf</groupId> >>> <artifactId>cxf-rt-core</artifactId> >>> <version>2.2.3</version> >>> </dependency> >>> <dependency> >>> <groupId>org.apache.cxf</groupId> >>> <artifactId>cxf-rt-transports-http</artifactId> >>> <version>2.2.3</version> >>> </dependency> >>> >>> 2. I also added these dependencies to the same top level pom.xml right >>> after the CXF ones above: >>> >>> <dependency> >>> <groupId>asm</groupId> >>> <artifactId>asm-all</artifactId> >>> <version>3.1</version> >>> </dependency> >>> <dependency> >>> <groupId>cglib</groupId> >>> <artifactId>cglib</artifactId> >>> <version>2.2</version> >>> </dependency> >>> <dependency> >>> <groupId>org.springframework</groupId> >>> <artifactId>spring-core</artifactId> >>> <version>${spring.version}</version> >>> </dependency> >>> <dependency> >>> <groupId>org.springframework</groupId> >>> <artifactId>spring-web</artifactId> >>> <version>${spring.version}</version> >>> </dependency> >>> >>> 3. I also added the following exclusions to the 2nd >>> appfuse-${dao-framework} dependency in the core/pom.xml (at least for a >>> modular archetype). Note: this is the same place you would put the >>> exclusion discussed in the tutorials WRT using / modifying the appfuse >>> core model classes, etc. Here's what it looks like: >>> >>> <dependency> >>> <groupId>org.appfuse</groupId> >>> <artifactId>appfuse-${dao.framework}</artifactId> >>> <version>${appfuse.version}</version> >>> <!-- -=j=-: moved down to the next block with >>> artifactId=appfuse-${dao.framework}, >>> didn't work putting it here in this <exclusions> block. >>> <exclusions> >>> </exclusions> >>> --> >>> </dependency> >>> <!-- this is the exclusion / dependency -=j=- added to use the >>> af model src --> >>> <dependency> >>> <groupId>org.appfuse</groupId> >>> <artifactId>appfuse-${dao.framework}</artifactId> >>> <version>${appfuse.version}</version> >>> <exclusions> >>> <exclusion> >>> <groupId>org.appfuse</groupId> >>> <artifactId>appfuse-data-common</artifactId> >>> </exclusion> >>> <!-- tried putting asm, asm-attrs and cglib exclusions here >>> but it didn't work --> >>> <exclusion> >>> <groupId>asm</groupId> >>> <artifactId>asm</artifactId> >>> </exclusion> >>> <exclusion> >>> <groupId>asm</groupId> >>> <artifactId>asm-attrs</artifactId> >>> </exclusion> >>> <exclusion> >>> <groupId>cglib</groupId> >>> <artifactId>cglib</artifactId> >>> </exclusion> >>> </exclusions> >>> </dependency> >>> >>> 4. Next, modify the web.xml. There are 3 pieces here (a-c). First, the >>> context-param, on disk the cxf-servlet.xml mentioned in the >>> context-param is in my web/src/main/webapp/WEB-INF dir: >>> >>> 4 a.) >>> >>> <context-param> >>> <param-name>contextConfigLocation</param-name> >>> <param-value> >>> classpath:/applicationContext-resources.xml >>> classpath:/applicationContext-dao.xml >>> classpath:/applicationContext-service.xml >>> classpath*:/applicationContext.xml >>> /WEB-INF/applicationContext*.xml >>> /WEB-INF/cxf-servlet.xml >>> /WEB-INF/security.xml >>> </param-value> >>> </context-param> >>> >>> The contents of this file are... empty, for the most part, this bit may >>> need some clean up as you can see that mine is all commented out. That >>> said, here's what's in mine: >>> >>> <beans xmlns="http://www.springframework.org/schema/beans"; >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >>> xmlns:jaxws="http://cxf.apache.org/jaxws"; >>> xsi:schemaLocation=" >>> http://www.springframework.org/schema/beans >>> http://www.springframework.org/schema/beans/spring-beans.xsd >>> http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/jaxws.xsd";> >>> >>> <!-- >>> <import resource="classpath:cxf/cxf.xml" /> >>> <import resource="classpath:cxf/cxf-extension-soap.xml" /> >>> <import resource="classpath:cxf/cxf-servlet.xml" /> >>> --> >>> >>> <!-- #errorManager points to my manager(with the @webservice >>> annotation) >>> defined in my applicationContext.xml--> >>> <!-- -=j=-: I changed this to match my services, FooService >>> was: id="errorService" | implementor="#errorManager" | >>> address="/ErrorService" --> >>> >>> <!-- >>> <jaxws:endpoint >>> id="folderService" >>> implementor="#folderManager" >>> address="/FolderService" /> >>> --> >>> </beans> >>> >>> 4 b.) The servlet declaration: >>> >>> <servlet> >>> <servlet-name>CXFServlet</servlet-name> >>> >>> <servlet-class>org.apache.cxf.transport.servlet.CXFServlet</servlet-class> >>> <load-on-startup>1</load-on-startup> >>> </servlet> >>> >>> 4 c.) The servlet mapping: >>> >>> <servlet-mapping> >>> <servlet-name>CXFServlet</servlet-name> >>> <url-pattern>/services/*</url-pattern> >>> </servlet-mapping> >>> >>> 5. I declared my endpoint in the web directory version of >>> applicationContext.xml (again, I'm using a modular appfuse archetype), >>> wihch was, until now, empty. Now it has this declaration in it, which I >>> moved here from cxf-servlet.xml since when it was declared there it >>> cuased the endpoint to get registered twice and so caused an exception. >>> Here's the endpoint declaration: >>> >>> <jaxws:endpoint >>> id="fooService" >>> implementor="#fooManager" >>> address="/FooService" /> >>> >>> >>> That should do it, at least to get your service exposed in some basic >>> fashion. I need to look further into why there's no get(), save(), >>> remove(), etc. which are all inherited methods from my service >>> superclass. The code first setup in appfuse with xfire exposes these >>> methods but this doesn't for some reason with CXF. >>> >>> I'm also interested in coming up with a good doc/wsdl first set up for >>> appfuse but am not sure what that might look like. I really like the >>> very "natural" usage of code first service dev in appfuse the way Matt >>> incorporated the code first support for xfire and would like to do the >>> analogous thing for wsdl first with CXF but I'm not sure how that would >>> best work. Any opinions? This is your chance to spout of an get >>> someone else to do the work... and if any of you are CXF "experts" (at >>> least more than I am), I'd love to hear from you. It would be nice if >>> appfuse could support both code first and wsdl first, and do so in a way >>> we could add to the tutorials so people can get up and running ASAP. >>> >>> Matt, how do you want this wrapped up? You did the orig. xfire services >>> to support java first dev, but doc first has become more popular since, >>> how do you want to set this up? Can we support both code first and wsdl >>> first in a natural way? >>> >>> As for your question to Nils about endpoint declaration, I have not made >>> this work without declaring an endpoint in some XML file, and it looks >>> like CXF is a little particular about which file it's declared in too. >>> It would be *really* helpful to get an expert on CXF to help us decide >>> how best to deploy it s I'm a bit of a newbie on CXF but I've got the >>> basics working now. The questions I have that remain are: >>> >>> 1. do you need to declare an endpoint in some config file or can it be >>> done like we did with xfire? >>> 2. how to get the inherited superclass service methods to be exposed as >>> in xfire? >>> 3. what is the purpose of cxf-servlet.xml, is it optional or required >>> and should endpoints be declared there? >>> 4. can we support both code first and wsdl first dev? >>> >>> Lastly, Matt, I'll write up a tutorial for this, it would be nice to >>> have this nailed down and documented in the tutorials, should I do it? >>> I haven't contributed to those before but will be happy to if you want. >>> That said, there are a few details remaining to be sorted out, like why >>> I need an empty cxf-servlet.xml file, for instance. >>> >>> -=j=- >>> >>> >>> jackalista wrote: >>>> >>>> The web app loads now with no errors but is also publishing no >>>> services... instead of trying to pub the service twice like last >>>> time... garr!! >>>> >>>> There's got to be a more complete discussion of these @#$%&*#$ config >>>> files somewhere... last time with the endpoint declared in the >>>> cxf-servlet.xml it complained because the service was already published >>>> via examination of interface FooService, but when I took that endpoint >>>> out of cxf-servlet.xml it doesn't even look at FooService... and it's >>>> not published at all...?!?!? WTF? Zoiks, yo... if anybody knows >>>> what's up with this, you know, feel free to jump on in, Jack could use >>>> a scooby snack... >>>> >>>> --j >>>> >>>> >>>> >>>> jackalista wrote: >>>>> >>>>> OK, I got rid of my pilfered cxf.xml, and moved the imports from >>>>> cxf-servlet.xml to applicationContext.xml otherwise leaving >>>>> cxf-servlet.xml as is. I also added a dependency to the top level pom >>>>> for cxf-core (for an appfuse modular archetype) and that appears to >>>>> have done away with the "download cxf and copy the cxf.xml" hack. >>>>> Here's the dependency: >>>>> >>>>> <dependency> >>>>> <groupId>org.apache.cxf</groupId> >>>>> <artifactId>cxf-rt-core</artifactId> >>>>> <version>2.2.3</version> >>>>> </dependency> >>>>> >>>>> I think I may be close, it looks like cxf is already working somewhat, >>>>> as I'm getting my FooService registered twice. I suspect what's >>>>> happening is that it's getting recognized from the annotations in the >>>>> src files and then is getting published a 2nd time (causing an error) >>>>> because it's listed in the cxf-servlet.xml file. Do I need this >>>>> cxf-servlet.xml file? Here's the semi triumphant output as the server >>>>> starts: >>>>> >>>>> 2009-09-28 11:49:25.272::INFO: jetty-6.1.9 >>>>> 2009-09-28 11:49:25.307::INFO: Extract >>>>> jar:file:/home/jack/java/af/2.02/asg.open.src/appfuse.mule/basetocxf/cxfmule/web/target/integration-webapp-1.0-SNAPSHOT.war!/ >>>>> to >>>>> /home/jack/java/af/2.02/asg.open.src/appfuse.mule/basetocxf/cxfmule/web/target/work/webapp >>>>> log4j:WARN Continuable parsing error 57 and column 64 >>>>> log4j:WARN Attribute value >>>>> "com.opensymphony.xwork2.util.OgnlValueStack" of type ID must be >>>>> unique within the document. >>>>> 2009-09-28 11:49:27.322::INFO: No Transaction manager found - if your >>>>> webapp requires one, please configure one. >>>>> 2009-09-28 11:49:28.396:/:INFO: Initializing Spring root >>>>> WebApplicationContext >>>>> Sep 28, 2009 11:49:34 AM >>>>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean >>>>> buildServiceFromClass >>>>> INFO: Creating Service >>>>> {http://impl.service.integration.jackalista.org/}FooService from class >>>>> org.jackalista.integration.service.FooManager >>>>> Sep 28, 2009 11:49:36 AM org.apache.cxf.endpoint.ServerImpl >>>>> initDestination >>>>> INFO: Setting the server's publish address to be /FooService >>>>> [integration] WARN [main] Settings.getLocale(143) | Settings: Could >>>>> not parse struts.locale setting, substituting default VM locale >>>>> Sep 28, 2009 11:49:40 AM org.apache.cxf.transport.servlet.CXFServlet >>>>> updateContext >>>>> INFO: Load the bus with application context >>>>> Sep 28, 2009 11:49:40 AM >>>>> org.apache.cxf.bus.spring.BusApplicationContext getConfigResources >>>>> INFO: No cxf.xml configuration file detected, relying on defaults. >>>>> Sep 28, 2009 11:49:40 AM >>>>> org.apache.cxf.transport.servlet.AbstractCXFServlet >>>>> replaceDestinationFactory >>>>> INFO: Servlet transport factory already registered >>>>> Sep 28, 2009 11:49:40 AM org.apache.cxf.transport.servlet.CXFServlet >>>>> loadAdditionalConfig >>>>> INFO: Build endpoints from config-location: /WEB-INF/cxf-servlet.xml >>>>> Sep 28, 2009 11:49:40 AM >>>>> org.apache.cxf.service.factory.ReflectionServiceFactoryBean >>>>> buildServiceFromClass >>>>> INFO: Creating Service >>>>> {http://impl.service.integration.jackalista.org/}FooService from class >>>>> org.jackalista.integration.service.FooManager >>>>> Sep 28, 2009 11:49:40 AM org.apache.cxf.endpoint.ServerImpl >>>>> initDestination >>>>> INFO: Setting the server's publish address to be /FooService >>>>> 2009-09-28 11:49:40.124::WARN: failed CXFServlet >>>>> javax.servlet.ServletException: >>>>> org.springframework.beans.factory.BeanCreationException: Error >>>>> creating bean with name 'fooService': Invocation of init method >>>>> failed; nested exception is javax.xml.ws.WebServiceException: >>>>> java.lang.RuntimeException: Soap 1.1 endpoint already registered on >>>>> address /FooService >>>>> >>>>> So I guess I'll take out the endpoint in the cxf-servlet.sml file? >>>>> Surgery with a pick ax here... :) >>>>> >>>>> -=j=- >>>>> >>>>> >>>>> jackalista wrote: >>>>>> >>>>>> OK, clue forming... my cxf-servlet.xml looks *just like* the >>>>>> beans.xml from this link: >>>>>> >>>>>> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html >>>>>> >>>>>> I looked through all the instances of cxf-servlet.xml in the samples >>>>>> from the cxf 2.2.3 dist and none of them have these in them: >>>>>> >>>>>> <import resource="classpath:cxf/cxf.xml" /> >>>>>> <import resource="classpath:cxf/cxf-extension-soap.xml" /> >>>>>> <import resource="classpath:cxf/cxf-servlet.xml" /> >>>>>> >>>>>> I'm beginning to suspect this is where my problem is, around this >>>>>> statement from the snackycracky tech blog "delete >>>>>> WEB-INF/xfire-servlet.xml and make a new file there called >>>>>> cxf-servlet.xml which has this content:", (from: >>>>>> http://blog.srvme.de/2009/01/06/migrate-appfuse-from-xfire-to-cxf/). >>>>>> >>>>>> If I have the content exactly as described in the snackycracky blog, >>>>>> I have a circular import as cxf-servlet.xml imports itself... From >>>>>> looking at the other cxf-servlet.xml instances in the CXF dist, it >>>>>> looks pretty common to declare jaxws:endpoint's in there but none of >>>>>> the instances have these import statements there... so I should move >>>>>> them to beans.xml? And in appfuse, beans.xml is >>>>>> applicationContext.xml, is it not? >>>>>> >>>>>> Also, I looked through the CXF samples I do see these imports in use >>>>>> in a few places but only in files like "beans.xml". It also has a >>>>>> slight path difference with what's in snackhy cracky's blog, all >>>>>> these examples have META-INF in them... So should I move these >>>>>> statements into applicationCOntext.xml? >>>>>> >>>>>> I'm kinda configuration challenged, but I'm thinking that the jars >>>>>> from the CXF dist should have these files in them, shouldn't it? I >>>>>> found cxf.xml and the soap-extentions XML in those jars... but do I >>>>>> want to have my own cxf-servlet.xml or should it be from the CXF dist >>>>>> too? I'm leaning towards putting these imports in >>>>>> applicationContext.xml and leaving my copy of cxf-servlet.xml in >>>>>> WEB-INF but without the imports in it since none of the >>>>>> cxf-servlet.xml files in the CXF dist have them. Do the CXF docs say >>>>>> where, when and why to use which config files? I haven't found >>>>>> that... If anyone has a clear handle on this I'd love some >>>>>> clarification... tia... >>>>>> >>>>>> --j >>>>>> >>>>>> >>>>>> jackalista wrote: >>>>>>> >>>>>>> One further detail is that I found cxf-rt-bindings-soap-2.2.3.jar, >>>>>>> the jar that contains cxf-extension-soap.xml (see 9th line of output >>>>>>> below) in the output piped to a file via mvn dependencies:tree, so >>>>>>> why doesn't it get found at runtime? That jar is also in the war it >>>>>>> looks like as well. Here's the tree: >>>>>>> >>>>>>> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.2.3:compile >>>>>>> [INFO] | +- xml-resolver:xml-resolver:jar:1.2:compile >>>>>>> [INFO] | +- >>>>>>> org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0:compile >>>>>>> [INFO] | +- >>>>>>> org.apache.geronimo.specs:geronimo-ws-metadata_2.0_spec:jar:1.1.2:compile >>>>>>> [INFO] | +- asm:asm:jar:2.2.3:compile >>>>>>> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.2.3:compile >>>>>>> [INFO] | | +- com.sun.xml.bind:jaxb-impl:jar:2.1.12:compile >>>>>>> [INFO] | | \- >>>>>>> com.sun.xml.fastinfoset:FastInfoset:jar:1.2.7:compile >>>>>>> [INFO] | +- org.apache.cxf:cxf-rt-bindings-soap:jar:2.2.3:compile >>>>>>> [INFO] | | +- org.apache.cxf:cxf-tools-common:jar:2.2.3:compile >>>>>>> [INFO] | | \- >>>>>>> org.apache.cxf:cxf-rt-databinding-jaxb:jar:2.2.3:compile >>>>>>> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.2.3:compile >>>>>>> [INFO] | +- org.apache.cxf:cxf-rt-frontend-simple:jar:2.2.3:compile >>>>>>> [INFO] | +- org.apache.cxf:cxf-rt-ws-addr:jar:2.2.3:compile >>>>>>> [INFO] | +- javax.xml.soap:saaj-api:jar:1.3:compile >>>>>>> [INFO] | \- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.2:compile >>>>>>> [INFO] +- org.apache.cxf:cxf-rt-transports-http:jar:2.2.3:compile >>>>>>> >>>>>>> >>>>>>> >>>>>>> jackalista wrote: >>>>>>>> >>>>>>>> here's the error: >>>>>>>> >>>>>>>> Offending resource: ServletContext resource >>>>>>>> [/WEB-INF/cxf-servlet.xml]; nested exception is >>>>>>>> org.springframework.beans.factory.BeanDefinitionStoreException: >>>>>>>> IOException parsing XML document from class path resource >>>>>>>> [cxf/cxf-extension-soap.xml]; nested exception is >>>>>>>> java.io.FileNotFoundException: class path resource >>>>>>>> [cxf/cxf-extension-soap.xml] cannot be opened because it does not >>>>>>>> exist >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> jackalista wrote: >>>>>>>>> >>>>>>>>> I mus be doing something dumb, it all looks just like the docs. >>>>>>>>> The import statements you reference are in cxf-servlet.xml (which >>>>>>>>> itself is in web/src/main/webapp/WEB-INF), like this: >>>>>>>>> >>>>>>>>> <import resource="classpath:cxf/cxf.xml" /> >>>>>>>>> <import resource="classpath:cxf/cxf-extension-soap.xml" /> >>>>>>>>> <import resource="classpath:cxf/cxf-servlet.xml" /> >>>>>>>>> >>>>>>>>> and my conxtConfigLocation from web.xml looks like: >>>>>>>>> >>>>>>>>> <context-param> >>>>>>>>> <param-name>contextConfigLocation</param-name> >>>>>>>>> <param-value> >>>>>>>>> classpath:/applicationContext-resources.xml >>>>>>>>> classpath:/cxf/cxf.xml >>>>>>>>> classpath:/applicationContext-dao.xml >>>>>>>>> classpath:/applicationContext-service.xml >>>>>>>>> classpath*:/applicationContext.xml >>>>>>>>> /WEB-INF/applicationContext*.xml >>>>>>>>> /WEB-INF/cxf-servlet.xml >>>>>>>>> /WEB-INF/security.xml >>>>>>>>> </param-value> >>>>>>>>> </context-param> >>>>>>>>> >>>>>>>>> I'm still getting this exception about file not found for the >>>>>>>>> cxf/cxf-extension-soap.xml when I start it in the web container >>>>>>>>> (embedded jetty). I'm suspicious I'm doing something or missing >>>>>>>>> something dumb. it looks mostly right but it's not finding that >>>>>>>>> xml, which is from this jar cxf-rt-bindings-soap-2.2.3.jar as far >>>>>>>>> as I can tell. i looked at that link ( >>>>>>>>> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html >>>>>>>>> ) and I think I've got it set up just like that but obvioiusly >>>>>>>>> something isn't quite right. Las thing I can think of right now >>>>>>>>> is that maybe my top level dependencies aren't complete? Those >>>>>>>>> are here, do you need more than this (or different from, etc.): >>>>>>>>> >>>>>>>>> <dependency> >>>>>>>>> <groupId>org.apache.cxf</groupId> >>>>>>>>> <artifactId>cxf-api</artifactId> >>>>>>>>> <version>2.2.3</version> >>>>>>>>> </dependency> >>>>>>>>> <dependency> >>>>>>>>> <groupId>org.apache.cxf</groupId> >>>>>>>>> <artifactId>cxf-rt-frontend-jaxws</artifactId> >>>>>>>>> <version>2.2.3</version> >>>>>>>>> <exclusions> >>>>>>>>> <!-- >>>>>>>>> http://www.jroller.com/melix/entry/apache_cxf_maven_javamail_awful >>>>>>>>> --> >>>>>>>>> <exclusion> >>>>>>>>> <groupId>org.apache.geronimo.specs</groupId> >>>>>>>>> >>>>>>>>> <artifactId>geronimo-javamail_1.4_spec</artifactId> >>>>>>>>> </exclusion> >>>>>>>>> </exclusions> >>>>>>>>> </dependency> >>>>>>>>> <dependency> >>>>>>>>> <groupId>org.apache.cxf</groupId> >>>>>>>>> <artifactId>cxf-rt-transports-http</artifactId> >>>>>>>>> <version>2.2.3</version> >>>>>>>>> </dependency> >>>>>>>>> >>>>>>>>> I know I'm doing something dumb here I can feel it... @#$%! >>>>>>>>> >>>>>>>>> --j >>>>>>>>> >>>>>>>>> >>>>>>>>> mraible wrote: >>>>>>>>>> >>>>>>>>>> You should be able to import CXF files from the classpath: >>>>>>>>>> >>>>>>>>>> <import resource="classpath:META-INF/cxf/cxf.xml" /> >>>>>>>>>> <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" >>>>>>>>>> /> >>>>>>>>>> <import resource="classpath:META-INF/cxf/cxf-servlet.xml" /> >>>>>>>>>> >>>>>>>>>> From >>>>>>>>>> http://cwiki.apache.org/CXF20DOC/writing-a-service-with-spring.html. >>>>>>>>>> >>>>>>>>>> Matt >>>>>>>>>> >>>>>>>>>> On Sun, Sep 27, 2009 at 1:21 PM, jackalista <j...@twaxx.com> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> Got this a little further, you apparently must have the cxf.xml >>>>>>>>>>> file. I >>>>>>>>>>> tried putting it in >>>>>>>>>>> top-level-project-home/web/src/main/webapp/WEB-INF/cxf >>>>>>>>>>> and in web.xml but it couldn't find it so moved it to >>>>>>>>>>> web/src/main/resources/cxf and used this web.xml config and it >>>>>>>>>>> seems to >>>>>>>>>>> work: >>>>>>>>>>> >>>>>>>>>>> <context-param> >>>>>>>>>>> <param-name>contextConfigLocation</param-name> >>>>>>>>>>> <param-value> >>>>>>>>>>> classpath:/applicationContext-resources.xml >>>>>>>>>>> classpath:/cxf/cxf.xml >>>>>>>>>>> classpath:/applicationContext-dao.xml >>>>>>>>>>> classpath:/applicationContext-service.xml >>>>>>>>>>> classpath*:/applicationContext.xml >>>>>>>>>>> /WEB-INF/applicationContext*.xml >>>>>>>>>>> /WEB-INF/cxf-servlet.xml >>>>>>>>>>> /WEB-INF/security.xml >>>>>>>>>>> </param-value> >>>>>>>>>>> </context-param> >>>>>>>>>>> >>>>>>>>>>> Now when I start up the web container it tells me: >>>>>>>>>>> >>>>>>>>>>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException: >>>>>>>>>>> Configuration problem: Failed to import bean definitions from >>>>>>>>>>> URL location >>>>>>>>>>> [classpath:cxf/cxf-extension-soap.xml] >>>>>>>>>>> Offending resource: ServletContext resource >>>>>>>>>>> [/WEB-INF/cxf-servlet.xml]; >>>>>>>>>>> nested exception is >>>>>>>>>>> org.springframework.beans.factory.BeanDefinitionStoreException: >>>>>>>>>>> IOException >>>>>>>>>>> parsing XML document from class path resource >>>>>>>>>>> [cxf/cxf-extension-soap.xml]; >>>>>>>>>>> nested exception is java.io.FileNotFoundException: class path >>>>>>>>>>> resource >>>>>>>>>>> [cxf/cxf-extension-soap.xml] cannot be opened because it does >>>>>>>>>>> not exist >>>>>>>>>>> >>>>>>>>>>> On to the next one... >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> jackalista wrote: >>>>>>>>>>>> >>>>>>>>>>>> I got this a bit farther. I looked the cxf.xml files available >>>>>>>>>>>> in the >>>>>>>>>>>> latest archive for CXF (2.2.3), and found a wsdl first xmlbeans >>>>>>>>>>>> example >>>>>>>>>>>> that seemed at least plausibly usable and set it up for one of >>>>>>>>>>>> the >>>>>>>>>>>> services I'm exposing. Where do I want to put this so it gets >>>>>>>>>>>> picked up >>>>>>>>>>>> properly? Does this need to go in that list of files in the >>>>>>>>>>>> web.xml?. >>>>>>>>>>>> >>>>>>>>>>>> -=j=- >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> jackalista wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> OK, I was able to build and successfully run all my dao and >>>>>>>>>>>>> mgr tests and >>>>>>>>>>>>> did an mvn install into web as well and that went smoothly but >>>>>>>>>>>>> when I >>>>>>>>>>>>> went into the web directory to do the run war target and pop >>>>>>>>>>>>> up jetty and >>>>>>>>>>>>> run the app it hit what looks like the other comments I saw >>>>>>>>>>>>> about the >>>>>>>>>>>>> cxf.xml missing. I guess I'll go back and look at that hack >>>>>>>>>>>>> about >>>>>>>>>>>>> manually copying a cxf.xml file from somewhere but that sounds >>>>>>>>>>>>> a bit >>>>>>>>>>>>> sketchy, where is this file and it's config supposed to be >>>>>>>>>>>>> coming from? >>>>>>>>>>>>> Is it produced by annotation processing? >>>>>>>>>>>>> >>>>>>>>>>>>> -=j=- >>>>>>>>>>>>> >>>>>>>>>>>>> Here's a bit of the error trace showing a file not found for >>>>>>>>>>>>> cxf.ml: >>>>>>>>>>>>> >>>>>>>>>>>>> 2009-09-26 16:10:18.700:/:INFO: Initializing Spring root >>>>>>>>>>>>> WebApplicationContext >>>>>>>>>>>>> [integration] ERROR [main] >>>>>>>>>>>>> ContextLoader.initWebApplicationContext(215) | >>>>>>>>>>>>> Context initialization failed >>>>>>>>>>>>> org.springframework.beans.factory.parsing.BeanDefinitionParsingException: >>>>>>>>>>>>> Configuration problem: Failed to import bean definitions from >>>>>>>>>>>>> URL >>>>>>>>>>>>> location [classpath:cxf/cxf.xml] >>>>>>>>>>>>> Offending resource: ServletContext resource >>>>>>>>>>>>> [/WEB-INF/cxf-servlet.xml]; >>>>>>>>>>>>> nested exception is >>>>>>>>>>>>> org.springframework.beans.factory.BeanDefinitionStoreException: >>>>>>>>>>>>> IOException parsing XML document from class path resource >>>>>>>>>>>>> [cxf/cxf.xml]; >>>>>>>>>>>>> nested exception is java.io.FileNotFoundException: class path >>>>>>>>>>>>> resource >>>>>>>>>>>>> [cxf/cxf.xml] cannot be opened because it does not exist >>>>>>>>>>>>> at >>>>>>>>>>>>> org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68) >>>>>>>>>>>>> at >>>>>>>>>>>>> org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85) >>>>>>>>>>>>> at >>>>>>>>>>>>> org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:76) >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> more to come... >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> jackalista wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> ok got the build problem with asm and cglib resloved with >>>>>>>>>>>>>> this mod done >>>>>>>>>>>>>> to the core/pom.xml (again, this is a struts2 modular >>>>>>>>>>>>>> project)., I added >>>>>>>>>>>>>> the exclusions to the appfuse-${dao.framework} dependency >>>>>>>>>>>>>> just after >>>>>>>>>>>>>> where you have to make the pom.xml mod from the tutorials for >>>>>>>>>>>>>> using >>>>>>>>>>>>>> appfuse core model classes and added a new dependency for >>>>>>>>>>>>>> cglib-nodep >>>>>>>>>>>>>> version 2.2 at the end of the list of dependencies and it >>>>>>>>>>>>>> built, I'll >>>>>>>>>>>>>> have to see what else works or doesn't work, here's the >>>>>>>>>>>>>> building >>>>>>>>>>>>>> configuration for the core/pom.xml: >>>>>>>>>>>>>> >>>>>>>>>>>>>> <dependency> >>>>>>>>>>>>>> <groupId>org.appfuse</groupId> >>>>>>>>>>>>>> <artifactId>appfuse-${dao.framework}</artifactId> >>>>>>>>>>>>>> <version>${appfuse.version}</version> >>>>>>>>>>>>>> <!-- moved down to the next block with >>>>>>>>>>>>>> artifactId=appfuse-${dao.framework}, >>>>>>>>>>>>>> didn't work putting it here in this >>>>>>>>>>>>>> <exclusions> block. >>>>>>>>>>>>>> <exclusions> >>>>>>>>>>>>>> </exclusions> >>>>>>>>>>>>>> --> >>>>>>>>>>>>>> </dependency> >>>>>>>>>>>>>> <!-- this is the exclusion / dependency -=j=- added >>>>>>>>>>>>>> to use the >>>>>>>>>>>>>> af model src --> >>>>>>>>>>>>>> <dependency> >>>>>>>>>>>>>> <groupId>org.appfuse</groupId> >>>>>>>>>>>>>> <artifactId>appfuse-${dao.framework}</artifactId> >>>>>>>>>>>>>> <version>${appfuse.version}</version> >>>>>>>>>>>>>> <exclusions> >>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>> <groupId>org.appfuse</groupId> >>>>>>>>>>>>>> <artifactId>appfuse-data-common</artifactId> >>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>> <!-- tried putting asm, asm-attrs and cglib >>>>>>>>>>>>>> exclusions here >>>>>>>>>>>>>> but it didn't work --> >>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>> <groupId>asm</groupId> >>>>>>>>>>>>>> <artifactId>asm</artifactId> >>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>> <groupId>asm</groupId> >>>>>>>>>>>>>> <artifactId>asm-attrs</artifactId> >>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>> <groupId>cglib</groupId> >>>>>>>>>>>>>> <artifactId>cglib</artifactId> >>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>> </exclusions> >>>>>>>>>>>>>> </dependency> >>>>>>>>>>>>>> <dependency> >>>>>>>>>>>>>> <groupId>cglib</groupId> >>>>>>>>>>>>>> <artifactId>cglib-nodep</artifactId> >>>>>>>>>>>>>> <version>2.2</version> >>>>>>>>>>>>>> </dependency> >>>>>>>>>>>>>> </dependencies> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> mraible wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Sat, Sep 26, 2009 at 3:27 PM, jackalista <j...@twaxx.com> >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I piped "mvn dependency:tree" to a file and found this >>>>>>>>>>>>>>>> refer under >>>>>>>>>>>>>>>> hibernate >>>>>>>>>>>>>>>> that appears to be 1.x: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [INFO] +- org.appfuse:appfuse-hibernate:jar:2.0.2:compile >>>>>>>>>>>>>>>> [INFO] | +- org.hibernate:hibernate:jar:3.2.6.ga:compile >>>>>>>>>>>>>>>> [INFO] | | +- javax.transaction:jta:jar:1.0.1B:compile >>>>>>>>>>>>>>>> [INFO] | | +- asm:asm-attrs:jar:1.5.3:compile >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Farther down I also found these which are 2.x & 3.x it >>>>>>>>>>>>>>>> looks like: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [INFO] +- >>>>>>>>>>>>>>>> org.apache.cxf:cxf-rt-frontend-jaxws:jar:2.1.3:compile >>>>>>>>>>>>>>>> [INFO] | +- >>>>>>>>>>>>>>>> org.apache.geronimo.specs:geronimo-jaxws_2.1_spec:jar:1.0:compile >>>>>>>>>>>>>>>> [INFO] | +- asm:asm:jar:2.2.3:compile >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [...] >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> [INFO] +- >>>>>>>>>>>>>>>> org.apache.cxf:cxf-rt-transports-http:jar:2.1.3:compile >>>>>>>>>>>>>>>> [INFO] +- asm:asm-all:jar:3.1:compile >>>>>>>>>>>>>>>> [INFO] +- cglib:cglib:jar:2.2:compile >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> So it looks like I have that problem, what do I have to do >>>>>>>>>>>>>>>> to effect >>>>>>>>>>>>>>>> this >>>>>>>>>>>>>>>> workaround here?: ""workaround" for Hibernate is to remove >>>>>>>>>>>>>>>> the asm 1.x >>>>>>>>>>>>>>>> jar >>>>>>>>>>>>>>>> they use and replace the cglib jar with the cglib-nodeps >>>>>>>>>>>>>>>> jar that >>>>>>>>>>>>>>>> includes a >>>>>>>>>>>>>>>> special internal version of asm that would not conflict >>>>>>>>>>>>>>>> with the 2.x/3.x version we need" >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I'm pulling in both the 2 and 3 versions of asm from the >>>>>>>>>>>>>>>> dependency:tree? >>>>>>>>>>>>>>>> Perhaps I'm not doing the right exclusion for hibernate? >>>>>>>>>>>>>>>> Sorry, I'm >>>>>>>>>>>>>>>> fairly >>>>>>>>>>>>>>>> green with maven... Also, how do I replace cglib.jar with >>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>> cglib-nodeps.jar? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Add an exclusion to appfuse-hibernate that excludes >>>>>>>>>>>>>>> asm-attrs and >>>>>>>>>>>>>>> cglib. Then add a dependency to the same pom for >>>>>>>>>>>>>>> cglib-nodeps. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> One more stupid question: why not get the latest CXF? It's >>>>>>>>>>>>>>>> a full >>>>>>>>>>>>>>>> major >>>>>>>>>>>>>>>> version past this 2.1.3, the current version is 2.2.3, >>>>>>>>>>>>>>>> should I use >>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>> latest as it may have various fixes or are there problems >>>>>>>>>>>>>>>> with that? >>>>>>>>>>>>>>>> Thanks >>>>>>>>>>>>>>>> Matt, you're doing pretty well for >>>>>>>>>>>>>>>> hacking-while-plane-hopping, much >>>>>>>>>>>>>>>> appreciated... >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Yes, I would recommend using the latest version of CXF. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Matt >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -=j=- >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> mraible wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> You should be able to simply upgrade ASM, not really >>>>>>>>>>>>>>>>> remove it. >>>>>>>>>>>>>>>>> Here's >>>>>>>>>>>>>>>>> what the CXF migration guide[1] says: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> The JAX-WS frontend now "requires" asm 2.x or 3.x to be >>>>>>>>>>>>>>>>> able to >>>>>>>>>>>>>>>>> process some of the JAXB annotations on the SEI interface. >>>>>>>>>>>>>>>>> If you >>>>>>>>>>>>>>>>> don't use those annotations on the SEI, or if you have >>>>>>>>>>>>>>>>> generated >>>>>>>>>>>>>>>>> wrapper classes (either via wsdl2java or java2ws with >>>>>>>>>>>>>>>>> -wrapperbean >>>>>>>>>>>>>>>>> flag), you can remove the asm jar. If you leave asm jar, >>>>>>>>>>>>>>>>> there can be >>>>>>>>>>>>>>>>> conflicts with other apps that use asm. The predominant >>>>>>>>>>>>>>>>> one is >>>>>>>>>>>>>>>>> Hibernate. The "workaround" for Hibernate is to remove the >>>>>>>>>>>>>>>>> asm 1.x >>>>>>>>>>>>>>>>> jar >>>>>>>>>>>>>>>>> they use and replace the cglib jar with the cglib-nodeps >>>>>>>>>>>>>>>>> jar that >>>>>>>>>>>>>>>>> includes a special internal version of asm that would not >>>>>>>>>>>>>>>>> conflict >>>>>>>>>>>>>>>>> with the 2.x/3.x version we need. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I would pipe "mvn dependency:tree" to a file and search it >>>>>>>>>>>>>>>>> too see if >>>>>>>>>>>>>>>>> you have the newer versions. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Matt >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> [1] http://cxf.apache.org/21-migration-guide.html >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sat, Sep 26, 2009 at 2:53 PM, -=j=- <j...@twaxx.com> >>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>> Ah, thanks, I'll put that back in. Also, I'm getting >>>>>>>>>>>>>>>>>> compile errors >>>>>>>>>>>>>>>>>> relating to asm and cglib, so I suspect that the >>>>>>>>>>>>>>>>>> exclusions or >>>>>>>>>>>>>>>>>> dependencies >>>>>>>>>>>>>>>>>> are in the wrong place. Are they in the right place? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -=j=- >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Sat, 2009-09-26 at 14:50 -0600, Matt Raible wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> You still need spring-web upgraded if you're using Struts >>>>>>>>>>>>>>>>>> 2. You >>>>>>>>>>>>>>>>>> should be able to use "mvn dependency:tree" to see if >>>>>>>>>>>>>>>>>> your >>>>>>>>>>>>>>>>>> dependencies look right. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Sat, Sep 26, 2009 at 2:46 PM, jackalista >>>>>>>>>>>>>>>>>> <j...@twaxx.com> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Hi Nils, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I'm tryingto follow along these directions and am having >>>>>>>>>>>>>>>>>>> trouble >>>>>>>>>>>>>>>>>>> understanding part of your guide. I'm using appfuse >>>>>>>>>>>>>>>>>>> 2.0.2 with the >>>>>>>>>>>>>>>>>>> modular >>>>>>>>>>>>>>>>>>> struts2 archetype, in case it matters. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I'm getting errors from both asm and cglib so I'm better >>>>>>>>>>>>>>>>>>> I didn't >>>>>>>>>>>>>>>>>>> put >>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>> <exclusion></exclusion> & <dependency></dependency> >>>>>>>>>>>>>>>>>>> stuff in the >>>>>>>>>>>>>>>>>>> right >>>>>>>>>>>>>>>>>>> place. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> For the "exclude also asm and the cglib from the >>>>>>>>>>>>>>>>>>> hibernate >>>>>>>>>>>>>>>>>>> dependency" >>>>>>>>>>>>>>>>>>> part, >>>>>>>>>>>>>>>>>>> I tried putting these exclusion blocks in the >>>>>>>>>>>>>>>>>>> core/pom.xml right >>>>>>>>>>>>>>>>>>> under >>>>>>>>>>>>>>>>>>> the >>>>>>>>>>>>>>>>>>> exclusion block with <groiupId>org.appfuse</groupId> >>>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>> <artifactId>appfuse-hibernate</artifactId>: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> [code] >>>>>>>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>>>>>>> <groupId>asm</groupId> >>>>>>>>>>>>>>>>>>> <artifactId>asm</artifactId> >>>>>>>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>>>>>>> <groupId>asm</groupId> >>>>>>>>>>>>>>>>>>> <artifactId>asm-attrs</artifactId> >>>>>>>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>>>>>>> <exclusion> >>>>>>>>>>>>>>>>>>> <groupId>cglib</groupId> >>>>>>>>>>>>>>>>>>> <artifactId>cglib</artifactId> >>>>>>>>>>>>>>>>>>> </exclusion> >>>>>>>>>>>>>>>>>>> [/code] >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I performed this step "add the asm-all and cglib >>>>>>>>>>>>>>>>>>> dependencies to >>>>>>>>>>>>>>>>>>> the top >>>>>>>>>>>>>>>>>>> level <dependencies>:" by putting the following >>>>>>>>>>>>>>>>>>> dependency blocks >>>>>>>>>>>>>>>>>>> in the >>>>>>>>>>>>>>>>>>> top >>>>>>>>>>>>>>>>>>> level pom.xml (it's a modular archetype) in the main >>>>>>>>>>>>>>>>>>> dependencies >>>>>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>>>>> at >>>>>>>>>>>>>>>>>>> the end of the list: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> <dependency> >>>>>>>>>>>>>>>>>>> <groupId>asm</groupId> >>>>>>>>>>>>>>>>>>> <artifactId>asm-all</artifactId> >>>>>>>>>>>>>>>>>>> <version>3.1</version> >>>>>>>>>>>>>>>>>>> </dependency> >>>>>>>>>>>>>>>>>>> <dependency> >>>>>>>>>>>>>>>>>>> <groupId>cglib</groupId> >>>>>>>>>>>>>>>>>>> <artifactId>cglib</artifactId> >>>>>>>>>>>>>>>>>>> <version>2.2</version> >>>>>>>>>>>>>>>>>>> </dependency> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I also put the CXF dependencies (cxf-api, >>>>>>>>>>>>>>>>>>> cxf-rt-frontend-jaxws & >>>>>>>>>>>>>>>>>>> cxf-rt-transports-http) in that same list in that same >>>>>>>>>>>>>>>>>>> top level >>>>>>>>>>>>>>>>>>> pom.xml >>>>>>>>>>>>>>>>>>> file, just before the asm and cglib stuff. Right after >>>>>>>>>>>>>>>>>>> the asm and >>>>>>>>>>>>>>>>>>> cglib >>>>>>>>>>>>>>>>>>> dependencies I put this spring-core dependency: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> <dependency> >>>>>>>>>>>>>>>>>>> <groupId>org.springframework</groupId> >>>>>>>>>>>>>>>>>>> <artifactId>spring-core</artifactId> >>>>>>>>>>>>>>>>>>> <version>${spring.version}</version> >>>>>>>>>>>>>>>>>>> </dependency> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I didn't put the spring-web dependency in as I'm using >>>>>>>>>>>>>>>>>>> struts2, but >>>>>>>>>>>>>>>>>>> I'm >>>>>>>>>>>>>>>>>>> not >>>>>>>>>>>>>>>>>>> sure if that's correct, since I'm hitting build errors >>>>>>>>>>>>>>>>>>> related to >>>>>>>>>>>>>>>>>>> asm >>>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>> cglib it's kind of hard to tell. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Sorry for the newbie questions but am I putting these >>>>>>>>>>>>>>>>>>> dependencies >>>>>>>>>>>>>>>>>>> and >>>>>>>>>>>>>>>>>>> exclusions in the right place? I suspect one or more >>>>>>>>>>>>>>>>>>> are not >>>>>>>>>>>>>>>>>>> correct, >>>>>>>>>>>>>>>>>>> any >>>>>>>>>>>>>>>>>>> help would be appreciated, thanks... >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> agathon wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> i made a litte guide for migrating appfuse from xfire >>>>>>>>>>>>>>>>>>>> to cxf : >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> http://snackycracky.wordpress.com/2009/01/06/migrate-appfuse-from-xfire-to-cxf/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>>>>>>>> http://www.nabble.com/CXF-and-AppFuse-2.0.1-tp14282383s2369p25628723.html >>>>>>>>>>>>>>>>>>> Sent from the AppFuse - User mailing list archive at >>>>>>>>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>>>>>>>> users-unsubscr...@appfuse.dev.java.net >>>>>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>>>>>>> users-h...@appfuse.dev.java.net >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>>>>>>> users-unsubscr...@appfuse.dev.java.net >>>>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>>>>>> users-h...@appfuse.dev.java.net >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>>>>>> users-unsubscr...@appfuse.dev.java.net >>>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>>>>> users-h...@appfuse.dev.java.net >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> View this message in context: >>>>>>>>>>>>>>>> http://www.nabble.com/CXF-and-AppFuse-2.0.1-tp14282383s2369p25629009.html >>>>>>>>>>>>>>>> Sent from the AppFuse - User mailing list archive at >>>>>>>>>>>>>>>> Nabble.com. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>>>>> users-unsubscr...@appfuse.dev.java.net >>>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>>>> users-h...@appfuse.dev.java.net >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>>>>>> To unsubscribe, e-mail: >>>>>>>>>>>>>>> users-unsubscr...@appfuse.dev.java.net >>>>>>>>>>>>>>> For additional commands, e-mail: >>>>>>>>>>>>>>> users-h...@appfuse.dev.java.net >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> View this message in context: >>>>>>>>>>> http://www.nabble.com/CXF-and-AppFuse-2.0.1-tp14282383s2369p25636680.html >>>>>>>>>>> Sent from the AppFuse - User mailing list archive at Nabble.com. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>>> To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net >>>>>>>>>>> For additional commands, e-mail: users-h...@appfuse.dev.java.net >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> --------------------------------------------------------------------- >>>>>>>>>> To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net >>>>>>>>>> For additional commands, e-mail: users-h...@appfuse.dev.java.net >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/CXF-and-AppFuse-2.0.1-tp14282383s2369p25667091.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net For additional commands, e-mail: users-h...@appfuse.dev.java.net
