Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1823

upgrade XFire to CXF

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • SOAP
    • crowd integration client in a maven environment.

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      We noticed that crowd is still using XFire as framework instead of CXF, which is more or less XFire2.0.

      This gives some problem in newer project which are already using CXF as their framework. One problem we had to overcome is the XmlSchema version needed for both CXF as XFire. Or that you need them both in your project which is a lot of unnecessary overhead. Can crowd been upgraded to CXF so that?

      <dependency>
	<groupId>com.atlassian.crowd</groupId>
	<artifactId>crowd-integration-client</artifactId>
	<version>2.0.3</version>
	<exclusions>
		<exclusion>
			<groupId>org.apache.ws.commons</groupId>
			<artifactId>XmlSchema</artifactId>
		</exclusion>
	</exclusions>
</dependency>

<dependency>
	<groupId>org.apache.ws.commons.schema</groupId>
	<artifactId>XmlSchema</artifactId>
	<version>1.4.2</version>
</dependency>

            [CWD-1823] upgrade XFire to CXF

            David O'Flynn [Atlassian] added a comment -

            Hi Stefan,

            Upgrading Crowd from XFire to CXF would be a major undertaking - having built a CXF client for Crowd, it's very different in how it's set up and configured. There's a fair amount of risk in doing this, particularly in breaking binary compatibility with clients written in other languages.

            Given the cost/benefit, we're not going to go to CXF. We're more likely to create a cleaner REST API than we are to update our SOAP one.

            Does this make sense?

            Cheers,
            Dave.
            Crowd Product Manager

            David O'Flynn [Atlassian] added a comment - Hi Stefan, Upgrading Crowd from XFire to CXF would be a major undertaking - having built a CXF client for Crowd, it's very different in how it's set up and configured. There's a fair amount of risk in doing this, particularly in breaking binary compatibility with clients written in other languages. Given the cost/benefit, we're not going to go to CXF. We're more likely to create a cleaner REST API than we are to update our SOAP one. Does this make sense? Cheers, Dave. Crowd Product Manager

              Unassigned Unassigned
              b85a0a10-6675-4247-bfff-069f65a51a5a Deleted Account (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: