Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Orbit » CXF Apache in Orbit?
CXF Apache in Orbit? [message #12150] Tue, 06 May 2008 08:29 Go to next message
Eclipse User
Originally posted by: mickael.istria.openwide.fr

This is a multi-part message in MIME format.
--------------090501050903050805080600
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello,

We would like to write a CXF client in JWT project.
I understood that since it is an Apache project, there might not any
problem with the license? Am I right?

CXF depends on a lot of other "common" jars (see attached list for details).
According to what I see, it seems like STP project also uses CXF,
however, I don't know how they integrated it. Maybe that would interest
them too...
Do you think it is possible to add them into Orbit? or at least some of
them?


Thanks in advance
Mickael Istria

--------------090501050903050805080600
Content-Type: text/plain;
name="WHICH_JARS"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="WHICH_JARS"

This directory includes the CXF jar, the CXF manifest jar, the required
dependencies, and many optional dependencies. The "modules" directory
contains the cxf.jar split up into smaller pieces if you wish to use only
specific parts of CXF.

The following jars are required for all CXF usage:
- cxf.jar
- commons-logging.jar
- geronimo-activation.jar (Or the Sun equivalent)
- geronimo-annotation.jar (Or the Sun equivalent)
- geronimo-javamail.jar (Or the Sun equivalent)
- neethi.jar
- jaxb-api.jar
- jaxb-impl.jar
- stax-api.jar
- XmlSchema.jar
- wstx-asl.jar
- xml-resolver.jar

For Java2WSDL and WSDL2Java:
- The above jars
- jaxb-xjc.jar
- veliocity.jar
- velocity-dep.jar

For JAX-WS support:
- jaxws-api.jar
- saaj-api.jar
- saaj-impl.jar
- asm.jar (optional, but helps with performance of wrapper types)

For XML Configuration support:
- aopalliance.jar
- spring-beans.jar
- spring-context.jar
- spring-core.jar
- spring.web.jar

For standalone HTTP support:
- geronimo-servlet.jar
- jetty.jar
- jetty-sslengine.jar
- jetty-util.jar
- sl4j.jar & sl4j-jdk14.jar (optional - but improves logging)

For Aegis support:
- jaxen.jar
- jdom.jar
- stax-utils.jar

For WS-Security support:
- bcprov-jdk14.jar
- wss4j.jar
- xalan.jar
- xmlsec.jar

For HTTP Binding support:
- jra.jar
- jettison.jar (Needed for JSON services only)

--------------090501050903050805080600--
Re: CXF Apache in Orbit? [message #12903 is a reply to message #12150] Wed, 14 May 2008 03:21 Go to previous messageGo to next message
David Williams is currently offline David Williams
Messages: 696
Registered: July 2009
Senior Member
On Tue, 06 May 2008 08:29:45 -0400, Mickael Istria <mickael.istria@openwide.fr> wrote:



That's a lot of jars!

Yes, in general Apache license is compatible with EPL ... but, it does come down to individual projects at Apache, some are approved, some are not, depending on nit-picky little things found in the source code (or, more likely, not found, such as when a clear list of contributors is not maintained).

But, more to the point ... what Eclipse project are you working with? The "request" to put a 3rd party jar into Orbit should come from another Eclipse Project (it's not a service we offer to the general community).

So, sorry that I don't recognize your name, but the best way to go through the process is that your Eclipse Project submits the request to EMO to use third party code (called a CQ) in their project (and, technically, before that, you should discuss with the PMC of that project to be sure they agree ... that many jars would be expensive to have reviewed and analyzed, and while that's not stopped us before :) it does need to be considered. Then once that's approved, someone from your project would offer to become a committer in Orbit, if there wasn't one already. And, then, finally, a CQ submitted to put the third party code in Orbit.

Make sense?
Re: CXF Apache in Orbit? [message #12930 is a reply to message #12903] Wed, 14 May 2008 08:40 Go to previous messageGo to next message
Eclipse User
Originally posted by: mickael.istria.openwide.fr

Hello,

> That's a lot of jars!

Yes, indeed...


> Yes, in general Apache license is compatible with EPL ... but, it does come down to individual projects at Apache, some are approved, some are not, depending on nit-picky little things found in the source code (or, more likely, not found, such as when a clear list of contributors is not maintained).
> But, more to the point ... what Eclipse project are you working with? The "request" to put a 3rd party jar into Orbit should come from another Eclipse Project (it's not a service we offer to the general community).

I'm working for Java Workflow Toolbox (JWT) project.
And, since we want to be able to do some monitoring, we were interested
about integrating a WebService runtime to monitor retrieve informations
from a workflow engine into JWT.


> So, sorry that I don't recognize your name, but the best way to go through the process is that your Eclipse Project submits the request to EMO to use third party code (called a CQ) in their project (and, technically, before that, you should discuss with the PMC of that project to be sure they agree ... that many jars would be expensive to have reviewed and analyzed, and while that's not stopped us before :) it does need to be considered. Then once that's approved, someone from your project would offer to become a committer in Orbit, if there wasn't one already. And, then, finally, a CQ submitted to put the third party code in Orbit.

No problem for my name, I've only been involved in Eclipse for a few months.


> Make sense?

Yes.
Integrating such a library is not yet an emergency (and is maybe not
really necessary), we will see how JWT evolves.

Thank you for your answer!

Mickael
Re: CXF Apache in Orbit? [message #13411 is a reply to message #12930] Wed, 16 July 2008 02:54 Go to previous message
Christian Campo is currently offline Christian Campo
Messages: 590
Registered: July 2009
Senior Member
Hi,

maybe this is a good way to show interest for some kind of SOAP stack as third party library in Orbit. I am the project
lead from the Riena project and we are interested in using some SOAP stack for remote services. We have used XFire in
the past which is now discontinued and the sources went to CXF. So I was also interested to put CXF into Orbit but
stopped because "there are soo many jars". Axis2 isnt that much better. It seems to be impossible to write a simple SOAP
stack with a decent size these days.

Anyway if you make any decission on a SOAP stack and decide to put CXF in, I am interested to hear about it. Also there
is currently no rush for us to have a quick decision in any direction.

cheers
christian campo

Mickael Istria schrieb:
> Hello,
>
>> That's a lot of jars!
>
> Yes, indeed...
>
>
>> Yes, in general Apache license is compatible with EPL ... but, it does
>> come down to individual projects at Apache, some are approved, some
>> are not, depending on nit-picky little things found in the source code
>> (or, more likely, not found, such as when a clear list of contributors
>> is not maintained). But, more to the point ... what Eclipse project
>> are you working with? The "request" to put a 3rd party jar into Orbit
>> should come from another Eclipse Project (it's not a service we offer
>> to the general community).
>
> I'm working for Java Workflow Toolbox (JWT) project.
> And, since we want to be able to do some monitoring, we were interested
> about integrating a WebService runtime to monitor retrieve informations
> from a workflow engine into JWT.
>
>
>> So, sorry that I don't recognize your name, but the best way to go
>> through the process is that your Eclipse Project submits the request
>> to EMO to use third party code (called a CQ) in their project (and,
>> technically, before that, you should discuss with the PMC of that
>> project to be sure they agree ... that many jars would be expensive to
>> have reviewed and analyzed, and while that's not stopped us before :)
>> it does need to be considered. Then once that's approved, someone from
>> your project would offer to become a committer in Orbit, if there
>> wasn't one already. And, then, finally, a CQ submitted to put the
>> third party code in Orbit.
>
> No problem for my name, I've only been involved in Eclipse for a few
> months.
>
>
>> Make sense?
>
> Yes.
> Integrating such a library is not yet an emergency (and is maybe not
> really necessary), we will see how JWT evolves.
>
> Thank you for your answer!
>
> Mickael
Re: CXF Apache in Orbit? [message #563533 is a reply to message #12150] Wed, 14 May 2008 03:21 Go to previous message
David Williams is currently offline David Williams
Messages: 696
Registered: July 2009
Senior Member
On Tue, 06 May 2008 08:29:45 -0400, Mickael Istria <mickael.istria@openwide.fr> wrote:



That's a lot of jars!

Yes, in general Apache license is compatible with EPL ... but, it does come down to individual projects at Apache, some are approved, some are not, depending on nit-picky little things found in the source code (or, more likely, not found, such as when a clear list of contributors is not maintained).

But, more to the point ... what Eclipse project are you working with? The "request" to put a 3rd party jar into Orbit should come from another Eclipse Project (it's not a service we offer to the general community).

So, sorry that I don't recognize your name, but the best way to go through the process is that your Eclipse Project submits the request to EMO to use third party code (called a CQ) in their project (and, technically, before that, you should discuss with the PMC of that project to be sure they agree ... that many jars would be expensive to have reviewed and analyzed, and while that's not stopped us before :) it does need to be considered. Then once that's approved, someone from your project would offer to become a committer in Orbit, if there wasn't one already. And, then, finally, a CQ submitted to put the third party code in Orbit.

Make sense?
Re: CXF Apache in Orbit? [message #563557 is a reply to message #12903] Wed, 14 May 2008 08:40 Go to previous message
Mickael Istria is currently offline Mickael Istria
Messages: 744
Registered: July 2009
Location: Grenoble, France
Senior Member
Hello,

> That's a lot of jars!

Yes, indeed...


> Yes, in general Apache license is compatible with EPL ... but, it does come down to individual projects at Apache, some are approved, some are not, depending on nit-picky little things found in the source code (or, more likely, not found, such as when a clear list of contributors is not maintained).
> But, more to the point ... what Eclipse project are you working with? The "request" to put a 3rd party jar into Orbit should come from another Eclipse Project (it's not a service we offer to the general community).

I'm working for Java Workflow Toolbox (JWT) project.
And, since we want to be able to do some monitoring, we were interested
about integrating a WebService runtime to monitor retrieve informations
from a workflow engine into JWT.


> So, sorry that I don't recognize your name, but the best way to go through the process is that your Eclipse Project submits the request to EMO to use third party code (called a CQ) in their project (and, technically, before that, you should discuss with the PMC of that project to be sure they agree ... that many jars would be expensive to have reviewed and analyzed, and while that's not stopped us before :) it does need to be considered. Then once that's approved, someone from your project would offer to become a committer in Orbit, if there wasn't one already. And, then, finally, a CQ submitted to put the third party code in Orbit.

No problem for my name, I've only been involved in Eclipse for a few months.


> Make sense?

Yes.
Integrating such a library is not yet an emergency (and is maybe not
really necessary), we will see how JWT evolves.

Thank you for your answer!

Mickael
Re: CXF Apache in Orbit? [message #563998 is a reply to message #12930] Wed, 16 July 2008 02:54 Go to previous message
Christian Campo is currently offline Christian Campo
Messages: 590
Registered: July 2009
Senior Member
Hi,

maybe this is a good way to show interest for some kind of SOAP stack as third party library in Orbit. I am the project
lead from the Riena project and we are interested in using some SOAP stack for remote services. We have used XFire in
the past which is now discontinued and the sources went to CXF. So I was also interested to put CXF into Orbit but
stopped because "there are soo many jars". Axis2 isnt that much better. It seems to be impossible to write a simple SOAP
stack with a decent size these days.

Anyway if you make any decission on a SOAP stack and decide to put CXF in, I am interested to hear about it. Also there
is currently no rush for us to have a quick decision in any direction.

cheers
christian campo

Mickael Istria schrieb:
> Hello,
>
>> That's a lot of jars!
>
> Yes, indeed...
>
>
>> Yes, in general Apache license is compatible with EPL ... but, it does
>> come down to individual projects at Apache, some are approved, some
>> are not, depending on nit-picky little things found in the source code
>> (or, more likely, not found, such as when a clear list of contributors
>> is not maintained). But, more to the point ... what Eclipse project
>> are you working with? The "request" to put a 3rd party jar into Orbit
>> should come from another Eclipse Project (it's not a service we offer
>> to the general community).
>
> I'm working for Java Workflow Toolbox (JWT) project.
> And, since we want to be able to do some monitoring, we were interested
> about integrating a WebService runtime to monitor retrieve informations
> from a workflow engine into JWT.
>
>
>> So, sorry that I don't recognize your name, but the best way to go
>> through the process is that your Eclipse Project submits the request
>> to EMO to use third party code (called a CQ) in their project (and,
>> technically, before that, you should discuss with the PMC of that
>> project to be sure they agree ... that many jars would be expensive to
>> have reviewed and analyzed, and while that's not stopped us before :)
>> it does need to be considered. Then once that's approved, someone from
>> your project would offer to become a committer in Orbit, if there
>> wasn't one already. And, then, finally, a CQ submitted to put the
>> third party code in Orbit.
>
> No problem for my name, I've only been involved in Eclipse for a few
> months.
>
>
>> Make sense?
>
> Yes.
> Integrating such a library is not yet an emergency (and is maybe not
> really necessary), we will see how JWT evolves.
>
> Thank you for your answer!
>
> Mickael
Previous Topic:Orbit packages with versions]
Next Topic: JAX-WS 2.0
Goto Forum:
  


Current Time: Thu Aug 28 09:23:54 EDT 2014

Powered by FUDForum. Page generated in 0.05201 seconds