Second that. CXF is the successor to XFire and its solid. Kalle
On Sun, Aug 29, 2010 at 3:56 PM, Daniel Honig <daniel.ho...@gmail.com> wrote: > I know of many projects using CXF without complaints. I'd say that CXF is > probably a good way to go. > > On Sun, Aug 29, 2010 at 1:35 PM, Jim O'Callaghan > <j...@peritussolutions.com>wrote: > >> I'm aware this is off topic, but since there are so many people on the list >> with a broad skill set am hoping I can learn from their experiences / >> heartbreak. I am evaluating various WS stacks for interfacing with a >> system >> - currently I am using XFire as it requires very little configuration and >> performs quite efficiently. XFire appears to qualify every xml element >> with >> a namespace, bloating the payload considerably, or, if using the patch from >> http://jira.codehaus.org/browse/XFIRE-687 appears to have unreliable / >> inconsistent namespace qualifiers. Can anyone recommend a good WS stack >> they have positive experience of? My constraints are quite liberal - java >> 1.5 up, currently jetty as an AS, spring 3.0.2.RELEASE. Is CXF any good? >> I >> want to find something with good performance obviously, minimal config, and >> hopefully something that consistently defines package level namespaces at >> an >> envelope level and reuses them. >> >> >> >> Many thanks, >> >> Jim. >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
