[
https://issues.apache.org/activemq/browse/CAMEL-2391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2391.
Resolution: Fixed
trunk: 902014.
> camel-ftp - Add option to disconnect after use
> --
[
https://issues.apache.org/activemq/browse/CAMEL-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57054#action_57054
]
Christian Schneider commented on CAMEL-2389:
I propose to already create the new
camel-ftp - Add option to disconnect after use
--
Key: CAMEL-2391
URL: https://issues.apache.org/activemq/browse/CAMEL-2391
Project: Apache Camel
Issue Type: New Feature
Components: camel
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
Using the Dispatch/Provider API to implement the camel-cxf PLAYLOAD datafromat
---
Key: CAMEL-2390
URL: https://issues.apache.org/activemq/browse/CAMEL-2390
Project: Apache C
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
Split camel transport for cxf out of camel-cxf module
-
Key: CAMEL-2389
URL: https://issues.apache.org/activemq/browse/CAMEL-2389
Project: Apache Camel
Issue Type: Task
Reporter
[
https://issues.apache.org/activemq/browse/CAMEL-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57049#action_57049
]
Willem Jiang commented on CAMEL-2388:
-
I tried to remove the camel-spring dependency and
[
https://issues.apache.org/activemq/browse/CAMEL-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57048#action_57048
]
Willem Jiang commented on CAMEL-2388:
-
we can remove the camel-spring, but the cxf-rt-tra
[
https://issues.apache.org/activemq/browse/CAMEL-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-2388:
---
Assignee: Willem Jiang
> Remove some dependencies
>
>
>
[
https://issues.apache.org/activemq/browse/CAMEL-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider updated CAMEL-2388:
---
Attachment: camel-cxf-2010-01-21.patch
> Remove some dependencies
> -
Remove some dependencies
Key: CAMEL-2388
URL: https://issues.apache.org/activemq/browse/CAMEL-2388
Project: Apache Camel
Issue Type: Improvement
Components: camel-cxf
Affects Versions: 2.1.0
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
> I think the only option is to split JAXRS and JAXWS into different maven
projects if number of jars/dependencies is a concern.
Or exclude some of the jars from cxf-frontend-jaxrs as I suggested to Willem
? Thus advanced users will just get a couple of extra jars.
William Tam wrote:
>
> If
[
https://issues.apache.org/activemq/browse/CAMEL-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57041#action_57041
]
Claus Ibsen commented on CAMEL-2347:
wiki documentation and a feature file is left to do
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
[
https://issues.apache.org/activemq/browse/CAMEL-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Haleby updated CAMEL-2358:
Component/s: camel-core
> packageScan should support Spring property placeholders
> ---
[
https://issues.apache.org/activemq/browse/CAMEL-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Haleby updated CAMEL-2358:
Affects Version/s: 2.1.0
> packageScan should support Spring property placeholders
> --
[
https://issues.apache.org/activemq/browse/CAMEL-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2387.
Resolution: Fixed
trunk: 901661.
> GenericFileConverter should honor charset from Exchange
> -
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
GenericFileConverter should honor charset from Exchange
---
Key: CAMEL-2387
URL: https://issues.apache.org/activemq/browse/CAMEL-2387
Project: Apache Camel
Issue Type: Bug
Compone
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
parser the request parameter for the POST method
Key: CAMEL-2386
URL: https://issues.apache.org/activemq/browse/CAMEL-2386
Project: Apache Camel
Issue Type: Improvement
Reporter: W
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
[
https://issues.apache.org/activemq/browse/CAMEL-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57035#action_57035
]
Claus Ibsen commented on CAMEL-2347:
trunk: 901596.
added nagios component
> create a N
31 matches
Mail list logo
