Hello,
It appears that going to CXF 2.2.6 may actually be quite painless.
Compilation succeeded immediately, all unit tests succeeded and the
server started with no problems. So far I've deployed a couple of things
and have run into no trouble at all.
All I changed was the top-level "cxfVersion" property in pom.xml (and
deleted a dependencies.xml which was re-generated). So I think the
maintainers should definitely consider moving the trunk to CXF 2.2.6
immediately and even consider it for the 2.2-branch. I'll open a JIRA
for this.
C:\g22>svn diff pom.xml plugins\cxf\cxf\src\main\history\dependencies.xml
Index: pom.xml
===================================================================
--- pom.xml (revision 912260)
+++ pom.xml (working copy)
@@ -67,7 +67,7 @@
<openejbVersion>3.1.2</openejbVersion>
<derbyVersion>10.5.3.0_1</derbyVersion>
- <cxfVersion>2.1.4</cxfVersion>
+ <cxfVersion>2.2.6</cxfVersion>
<axis2Version>1.5</axis2Version>
<axiomVersion>1.2.8</axiomVersion>
<springVersion>2.5.6</springVersion>
Index: plugins/cxf/cxf/src/main/history/dependencies.xml
===================================================================
--- plugins/cxf/cxf/src/main/history/dependencies.xml (revision 912260)
+++ plugins/cxf/cxf/src/main/history/dependencies.xml (working copy)
@@ -111,4 +111,9 @@
<artifactId>wss4j</artifactId>
<type>jar</type>
</dependency>
+ <dependency>
+ <groupId>org.bouncycastle</groupId>
+ <artifactId>bcprov-jdk15</artifactId>
+ <type>jar</type>
+ </dependency>
</plugin-artifact>On 20/2/2010 10:59 μμ, Kevan Miller wrote:
On Feb 20, 2010, at 3:33 PM, Alexandros Karypidis wrote:
I've put the CXF 2.2.6 jars in repository/org/apache/cxf/xxx/2.2.6, alongside
the 2.1.4 ones.
Could you please give an example / point me to documentation for "artifact-alias
entries"?
Have a look at var/config/artifact_aliases.properties
It will only contain alias entries for car artifacts, but you can also alias
jar artifacts. Something like the following, I think:
org.apache.cxf/xxx//jar=org.apache.cxf/xxx/2.2.6/jar
If I had to guess, I'd guess that aliasing won't work. But I've been wrong
before...
Meanwhile, I've checked out the trunk and am waiting for an "mvn install" to
complete. I may very well do the upgrade. CXF 2.1 will no longer be developed except for
significant issues (2.1.9 was the end of the line) and 2.2.6 is being adverized as the
most stable release ever (http://www.dankulp.com/blog/?p=182). So it'd be nice if
Geronimo 2.3 used it (or even 2.2.1).
That would be great.
However, branches/2.2
(https://svn.apache.org/repos/asf/geronimo/server/branches/2.2) is your best
bet for making this change. trunk is working on EE6 and OSGi. It's not going to
be very stable for your purposes.
You'll need to bump cxfVersion in pom.xml. FYI, you'll find most/all of the
integration code in plugins/cxf.
--kevan
