stay
if there're camelcxf/simple frontend users out there but excluded if not
thanks, Sergey
- Original Message - From: "Hadrian Zbarcea"
To:
Sent: Monday, January 25, 2010 3:17 PM
Subject: Re: Why does camel-cxf need cxf-rt-frontend-jaxrs
Thanks Sergey! This is very h
To:
Sent: Monday, January 25, 2010 3:17 PM
Subject: Re: Why does camel-cxf need cxf-rt-frontend-jaxrs
Thanks Sergey! This is very helpful.
I am messing with the camel poms today anyway and I will try the suggested
change.
Cheers,
Hadrian
On Jan 25, 2010, at 4:52 AM, Sergey Beryozkin wrote
Thanks Sergey! This is very helpful.
I am messing with the camel poms today anyway and I will try the suggested
change.
Cheers,
Hadrian
On Jan 25, 2010, at 4:52 AM, Sergey Beryozkin wrote:
> Hi
>
> as suggested earlier on, the following dependencies can also be exclused from
> cxf-rt-fronten
Hi
as suggested earlier on, the following dependencies can also be exclused from
cxf-rt-frontend-jaxrs in a camel-cxf pom :
org.apache.abdera:abdera-core:jar:0.4.0-incubating:compile
org.apache.abdera:abdera-extensions-json:jar:0.4.0-incubating:compile
org.apache.abdera:abdera-extensions-main:
I just experimentally created a camel-cxf-camel-transport component that
only implements the camel transport for cxf.
The compile dependencies go down from 54 for camel-cxf to 27 for the new
component.
I added the dependencies below.
Greetings
Christian
mvn dependency:list -DincludeScop
Claus Ibsen wrote:
On Wed, Jan 20, 2010 at 11:51 PM, Christian Schneider
wrote:
Hi Sergey,
I am just concerned with the dependencies jaxrs brings into our projects.
The architects from the projects at my company that use camel and cxf
complain about the many dependencies needed to simply do we
As CXF supports lots of other API, just one simpel cxf-api and cxf-core
can't provides what we want to in camel-cxf :(
Christian, I checked the camel-cxf pom.xml, if you want to use the CXF
mini bundle , you just need to exclude below module, but you may need to
add some other third part depen
We can split the transport part out camel-cxf, but consider the backward
compatibility, we may do it in camel 2.3 or camel 3.0.
I already create a JIRA[1] for it.
[1]https://issues.apache.org/activemq/browse/CAMEL-2389
Willem
Christian Schneider wrote:
Am 21.01.2010 15:01, schrieb Hadrian Z
While I think it is great that a mini bundle is there for some special
cases I think it should possible to make the modular version more
independent of external libs. Especially the cxf api and core should
have no dependencies. Spring and camel have also achieved this. Having
said this I know i
Am 21.01.2010 15:01, schrieb Hadrian Zbarcea:
Christian, since you brought this up, what do you think a reasonable solution
for you would be?
Hi Hadrian,
Ideally I would like to have a camel-cxf component that only adapts
camel to cxf. So this component would need neither of
cxf-rt-fro
o is
>>>>>> added in
>>>>>> camel-cxf. I remember that recently Dan added the jaxb jars to maven
>>>>>> central
>>>>>> so I think this repo can now be removed. I checked with an empty
>>>>>> local
>>>>>> repo
>>>>>> and was able to build camel-cxf.
>>>>>>
>>>>>> Greetings
>>>>>>
>>>>>> Christian
>>>>>>
>>>>>> Am 20.01.2010 10:31, schrieb Sergey Beryozkin:
>>>>>>
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> I am using the camel-cxf component to attach a jaxws service to
>>>>>>>> camel.
>>>>>>>> Unfortunatelly the camel-cxf component also depends on
>>>>>>>> cxf-rt-frontend-jaxrs. Is this necessary? It would be nice if this
>>>>>>>> depdendency could be removed or made optional.
>>>>>>>>
>>>>>>> Does it cause any issues for you ? Or are you just concerned about
>>>>>>> extra
>>>>>>> module being unnecessarily loaded ?
>>>>>>>
>>>>>>> I'm not sure it makes sense to introduce another camel component
>>>>>>> specifically dedicated to handling cxf-rt-frontend-jaxrs.
>>>>>>> Some users may have JAXWS and JAXRS services attached through a
>>>>>>> single
>>>>>>> bean with the help of camel-cxf.
>>>>>>>
>>>>>>> cheers, Sergey
>>>>>>>
>>>>>> --
>>>>>>
>>>>>> Christian Schneider
>>>>>> ---
>>>>>> http://www.liquid-reality.de
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> --
>>>>> Claus Ibsen
>>>>> Apache Camel Committer
>>>>>
>>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>>> Open Source Integration: http://fusesource.com
>>>>> Blog: http://davsclaus.blogspot.com/
>>>>> Twitter: http://twitter.com/davsclaus
>>>>>
>>>>>
>>>>
>>>> --
>>>> Claus Ibsen
>>>> Apache Camel Committer
>>>>
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>> Open Source Integration: http://fusesource.com
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Twitter: http://twitter.com/davsclaus
>>>>
>>
>>
>>
>
>
--
View this message in context:
http://old.nabble.com/Why-does-camel-cxf-need-cxf-rt-frontend-jaxrs-tp27237712p27260617.html
Sent from the Camel Development mailing list archive at Nabble.com.
If you look at the runtime dependencies, there are not that many. I
think the only option is to split JAXRS and JAXWS into different maven
projects if number of jars/dependencies is a concern.
org.apache.camel
camel-core
org.apache.camel
camel-spring
Chill...
Christian made a valid point. There are a few *types* of dependencies in Camel:
1. compile dependencies - which cannot be avoided and should be kept to a
minimum
2. test runtime dependencies - needed for tests, which again cannot be avoided
but should be tagged as such in the pom, and i
On Thu, Jan 21, 2010 at 11:09 AM, Sergey Beryozkin
wrote:
>>>
>>> I totally agree that CXF / camel-cxf is a having way way to many
>>> dependencies out of the box.
>>>
S.B : lets limit the scope of the discussion. Christian has not
initiated
this thread to complain about the fact CX
Just a quick note for camel-cxf module:
There are more than 4 components in the camel-cxf
cxf, cxfrs, cxfbeans, camel transport for cxf , and an unused soap component.
If 'soap' is unused then looks like it can go.
I can see cxfrs has just 10 classes.
I think we just put them into camel-cxf m
Just a quick note for camel-cxf module:
There are more than 4 components in the camel-cxf
cxf, cxfrs, cxfbeans, camel transport for cxf , and an unused soap
component.
I think we just put them into camel-cxf module because they are CXF
related, if there are many people complain about it introd
I totally agree that CXF / camel-cxf is a having way way to many
dependencies out of the box.
S.B : lets limit the scope of the discussion. Christian has not initiated
this thread to complain about the fact CXF brings up to 81 jars in total but
rather to raise a valid issue to do with the fact
On Thu, Jan 21, 2010 at 10:40 AM, Sergey Beryozkin
wrote:
> See comments with S.B
>
>
> On Wed, Jan 20, 2010 at 11:51 PM, Christian Schneider
> wrote:
>>
>> Hi Sergey,
>>
>> I am just concerned with the dependencies jaxrs brings into our projects.
>> The architects from the projects at my company
See comments with S.B
On Wed, Jan 20, 2010 at 11:51 PM, Christian Schneider
wrote:
Hi Sergey,
I am just concerned with the dependencies jaxrs brings into our projects.
The architects from the projects at my company that use camel and cxf
complain about the many dependencies needed to simply d
Hi Christian
Hi Sergey,
I am just concerned with the dependencies jaxrs brings into our projects. The architects from the projects at my company that use
camel and cxf complain about the many dependencies needed to simply do web services. So I am constantly searching how to have
less depend
On Wed, Jan 20, 2010 at 11:51 PM, Christian Schneider
wrote:
> Hi Sergey,
>
> I am just concerned with the dependencies jaxrs brings into our projects.
> The architects from the projects at my company that use camel and cxf
> complain about the many dependencies needed to simply do web services.
Hi Christian,
You can try to use the cxf bundle jar which will reduce lots of the jar
head. You can find the jar dependency from camel-cxf section of the
features.xml[1]
[1]
https://svn.apache.org/repos/asf/camel/trunk/platforms/karaf/features/src/main/resources/features.xml
Willem
Christ
Hi Sergey,
I am just concerned with the dependencies jaxrs brings into our
projects. The architects from the projects at my company that use camel
and cxf complain about the many dependencies needed to simply do web
services. So I am constantly searching how to have less dependencies.
Curre
Hi all,
I am using the camel-cxf component to attach a jaxws service to camel.
Unfortunatelly the camel-cxf component also depends on
cxf-rt-frontend-jaxrs. Is this necessary? It would be nice if this
depdendency could be removed or made optional.
Does it cause any issues for you ?
Or ar
Hi all,
I am using the camel-cxf component to attach a jaxws service to camel.
Unfortunatelly the camel-cxf component also depends on
cxf-rt-frontend-jaxrs. Is this necessary? It would be nice if this
depdendency could be removed or made optional.
Greetings
Christian
--
Christian Schneide
25 matches
Mail list logo
