OK, I was wondering which pom.xml needed to change. I just add in anything that's not already there and check the versions of anything that is there, correct? The equivalent of xfire-servlet.xml is called (I think) cxf.xml but I'll try to validate that further. Will that upgrade page detail Spring related changes?
Thanks Matt mraible wrote: > > I think it's a matter of using the XFire Upgrade Guide on the CXF site > and changing the dependencies in trunk/services/pom.xml. From there, > it's a matter of figuring out the equivalent of xfire-servlet.xml and > changing the web.xml's appropriately. > > Matt > > On 1/12/08, jackalista <[EMAIL PROTECTED]> wrote: >> >> OK, I posted to the thread that looked like the one you mentioned (of >> user >> jchartrand) and offered to help but in the mean time what are the main >> things that have to be done to integrate this? I'll take a look at CXF's >> site too which I've been doing anyway and start digging into it but if >> you >> can help kickstart me with some specifics especially as it relates to >> AppFuse that would be great. Later... >> >> -=j=- >> >> >> mraible wrote: >> > >> > I would suggest searching the archives (via nabble or markmail) for >> > "CXF" to see how was interested in doing this migration. In reality, >> > it should be pretty simple. I'd do it myself, but there's skiing to >> > do this weekend. ;-) >> > >> > http://appfuse.org/display/APF/Mailing+Lists >> > >> > Matt >> > >> > On Jan 11, 2008, at 3:10 PM, jackalista wrote: >> > >> >> >> >> Somehow extra elements got generated, I'm not sure how it happened >> >> but stuff >> >> like this "<bean class="org.jackalista.mx.service.PersonService"/>" >> >> was >> >> added to the context in addition to the tags that were already in >> >> there and >> >> which looked like your description. I don't think I put this in >> >> there but >> >> once it was removed everything worked. I now have managed to get >> >> the four >> >> interfaces I was interested in working, thanks for your help. On >> >> the CXF >> >> front, can you point out who was also interested in doing it? >> >> Maybe if >> >> they're already some distance along I can take some tasks and help >> >> them >> >> instead of doing it from scratch (I've been using AppFuse for a >> >> little while >> >> now but have yet to integrate a new package like CXF so I've got no >> >> idea as >> >> of yet what is involved but ...). >> >> >> >> Thanks again... >> >> >> >> >> >> mraible wrote: >> >>> >> >>> On 1/2/08, jackalista <[EMAIL PROTECTED]> wrote: >> >>>> >> >>>> I've been pushing this along in background but am having another >> >>>> problem >> >>>> with >> >>>> this tutorial. I got the problem below fixed but then hit a problem >> >>>> because of this tag in applicationContext.xml: >> >>>> >> >>>> <bean class="org.jackalista.mx.service.PersonService"/> >> >>>> >> >>>> Person service got a NoClassDefFoundError. As there is no such >> >>>> PersonService class I tried setting the tag to point at the service >> >>>> interface, PersonManager but jetty complained about it being an >> >>>> interface. >> >>>> I then tried setting it to the implementation class, >> >>>> PersonManagerImpl >> >>>> like >> >>>> this: >> >>>> >> >>>> <bean class="org.jackalista.mx.service.impl.PersonManagerImpl"/> >> >>> >> >>> Your bean definition should look like the following: >> >>> >> >>> <bean id="personDao" >> >>> class="org.appfuse.tutorial.dao.hibernate.PersonDaoHibernate"> >> >>> <property name="sessionFactory" ref="sessionFactory"/> >> >>> </bean> >> >>> <!-- Add new DAOs here --> >> >>> >> >>> <bean id="personManager" >> >>> class="org.appfuse.tutorial.service.impl.PersonManagerImpl"> >> >>> <constructor-arg ref="personDao"/> >> >>> </bean> >> >>> >> >>>> >> >>>> >> >>>> I now am getting an error saying that there's no default >> >>>> constructor in >> >>>> the >> >>>> PersonManagerImpl class (which is true). I don't think I want to >> >>>> add one >> >>>> though, as then the constructor injection that sets the PersonDao is >> >>>> subverted. Where have I gone wrong? >> >>>> >> >>>> Also, should I be trying to integrate CXF instead of monkeying >> >>>> around >> >>>> with >> >>>> xfire, given the status of the xfire vs. CXF projects? CXF looks >> >>>> mighty >> >>>> AppFuse-worthy to my eye, and I'll even do some of the work to >> >>>> make it >> >>>> happen but you'll have to provide some guidance as I'm new to the >> >>>> 2.0 >> >>>> AppFuse release. Should I refocus on getting CXF to work? >> >>> >> >>> Someone expressed an interest in upgrading from XFire to CXF a couple >> >>> of weeks ago. I don't know how they've progressed, but I'd hate to >> >>> see >> >>> duplicate efforts. You can see our thinking on CXF on the Web >> >>> Services >> >>> tutorial. >> >>> >> >>> http://appfuse.org/display/APF/Web+Services >> >>> >> >>> In other words, we'd love to upgrade to CXF and will likely accept >> >>> any >> >>> patches (whether they require JAXB over XMLBeans is not important). >> >>> >> >>>> Also, I've been >> >>>> using a 2.0 M5 release to do all this, should I just start over >> >>>> with the >> >>>> latest at this point? It seems that a fair bit has happened now >> >>>> since >> >>>> the >> >>>> M5 release... what do you think? >> >>> >> >>> 2.0 is much improved over M5. You might read the release notes since >> >>> M5 to see what's changed. >> >>> >> >>> http://appfuse.org/display/APF/Migration+Guide >> >>> >> >>> Matt >> >>> >> >>>> >> >>>> Thanks, >> >>>> >> >>>> Jack >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> On Dec 4, 2007, at 9:13 PM, jackalista wrote: >> >>>> >> >>>> >> >>>> Yes, anytime you change files in "core", you have to install it so >> >>>> "web" can use it. >> >>>> >> >>>> Matt >> >>>> >> >>>> >> >>>> -- >> >>>> View this message in context: >> >>>> http://www.nabble.com/Web-services-in-Appfuse-2.0- >> >>>> tp12777689s2369p14588090.html >> >>>> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >>>> >> >>>> -------------------------------------------------------------------- >> >>>> - >> >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >>>> For additional commands, e-mail: [EMAIL PROTECTED] >> >>>> >> >>>> >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >>> For additional commands, e-mail: [EMAIL PROTECTED] >> >>> >> >>> >> >>> >> >> >> >> -- >> >> View this message in context: http://www.nabble.com/Web-services-in- >> >> Appfuse-2.0-tp12777689s2369p14766326.html >> >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Web-services-in-Appfuse-2.0-tp12777689s2369p14778876.html >> Sent from the AppFuse - User mailing list archive at Nabble.com. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Web-services-in-Appfuse-2.0-tp12777689s2369p14780114.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
