Hi
In Camel we have on completions
http://camel.apache.org/oncompletion.html
Which support 2 scope levels: context or route.
There is a rules of thumb currently:
- If you define a route scope it overrides all global scoped. So its
either or (not both).
The issue I would like to discuss is this
Route scoped onCompletion to only trigger if exchange completed at the given
route
--
Key: CAMEL-3548
URL: https://issues.apache.org/jira/browse/CAMEL-3548
Project:
[
https://issues.apache.org/jira/browse/CAMEL-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3548:
---
Attachment: CAMEL-3548.patch
A patch which implements most of this feature. Need more unit tests and
Hi Aaron,
I think this solution could avoid adding the dependency of script API
into camel-core in Camel 2.x. +1 for it.
When we move to Camel 3.x, we could let the camel-core looking up the
ScriptEngineFacotries.
BTW, we are closing to Camel 2.6 release, if the patch can't catch up
the
When I expose a CXF webservice using camel like
from(servlet://service).to(cxf:...)
and access the service using the browser I get an exception in CXF
ReadHeadersInterceptor
org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
at
Are you using cxfbean[1] component?
The DefaultCxfBeanBinding[2] does the mapping work that you want.
[1]http://camel.apache.org/cxf-bean-component.html
Hi Willem,
I used the Camel transport for CXF. Does it do the mapping differently?
Christian
-Ursprüngliche Nachricht-
Von: Willem Jiang [mailto:willem.ji...@gmail.com]
Gesendet: Montag, 17. Januar 2011 13:53
An: dev@camel.apache.org
Betreff: Re: Exception when accessing a CXF
[
https://issues.apache.org/jira/browse/CAMEL-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Schneider closed CAMEL-3262.
--
Resolution: Won't Fix
Checked the liberary ... I think it will not help us much in
On 1/17/11 9:05 PM, Christian Schneider wrote:
Hi Willem,
I used the Camel transport for CXF. Does it do the mapping differently?
I don't think current Camel transport has this kind of mapping
mechanism. It just redirect the stream between Camel and CXF.
Christian
-Ursprüngliche
It should be possible to configure the CamelHttpTransportServlet using the
spring ContextLoaderListener
---
Key: CAMEL-3549
URL:
Ok .. sounds like the short term solution could be to use the cxfbean. Do you
think it makes sense to add this mapping to the camel transport?
I could try to make the mapping logic of cxfbean component usable for both
cases.
Christian
-Ursprüngliche Nachricht-
Von: Willem Jiang
Camel 2.6 is almost ready for a release. The last hudson test [1] only had 4
failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the problem still exists in the current build [2]). It looks like
everything else is really stable and I'd suggest not committing
[
https://issues.apache.org/jira/browse/CAMEL-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12982656#action_12982656
]
Sebb commented on CAMEL-2583:
-
No, I cannot delete the files.
The index.html files are no
Hi Hadrian,
I'm gonna upgrade SMX projects to use CXF 2.3.2 and Camel 2.6-SNAPSHOT
to perform some tests and validate that unit tests are fine.
The plan is to release SMX 4.3.0 with:
- Karaf 2.1.3
- Camel 2.6.0
- CXF 2.3.2
- Spring 3.0.5.RELEASE
Regards
JB
On 01/17/2011 03:31 PM, Hadrian
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only had
4 failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the problem still exists in the current build [2]). It looks
like
[
https://issues.apache.org/jira/browse/CAMEL-2583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12982660#action_12982660
]
Hadrian Zbarcea commented on CAMEL-2583:
I removed the index files in the archives
Anyway, as reminder, in ServiceMix, the Camel features descriptor is
overrided. So if you use CXF 2.3.1 in Camel 2.6, the Camel feature
descriptor embedded in ServiceMix will use CXF 2.3.2.
So even if you wait for CXF 2.3.2 or not, finally in ServiceMix, CXF
2.3.2 will be used :)
Regards
JB
On Mon, Jan 17, 2011 at 3:55 PM, Daniel Kulp dk...@apache.org wrote:
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only had
4 failures in camel-scala (looks like the problem wasn't fully resolved by
Willem, and the
[
https://issues.apache.org/jira/browse/CAMEL-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12982663#action_12982663
]
Tracy Snell commented on CAMEL-913:
---
We could have quartz when it's a Producer send the
On Monday 17 January 2011 10:01:32 am Claus Ibsen wrote:
On Mon, Jan 17, 2011 at 3:55 PM, Daniel Kulp dk...@apache.org wrote:
On Monday 17 January 2011 9:31:33 am Hadrian Zbarcea wrote:
Camel 2.6 is almost ready for a release. The last hudson test [1] only
had 4 failures in camel-scala
As discussed on IRC, ServiceMix should provide more unit tests,
especially around Camel and CXF used in OSGi.
First, I'm gonna update to Camel 2.6-SNAPSHOT and CXF 2.3-SNAPSHOT in
preparation of the upgrade. It should be ready tonight (GMT+1 time).
After that, I'm gonna work on it. If you need
Typing mistake:
If you see some areas that should be spotted in the unit tests, please
keep us posted.
I'm tired before starting the unit tests coding :)
Regards
JB
On 01/17/2011 04:37 PM, Jean-Baptiste Onofré wrote:
As discussed on IRC, ServiceMix should provide more unit tests,
especially
[
https://issues.apache.org/jira/browse/CAMEL-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12982704#action_12982704
]
Claus Ibsen commented on CAMEL-3547:
We'll it would be much better if the community
[
https://issues.apache.org/jira/browse/CAMEL-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3547:
---
Component/s: (was: camel-core)
camel-spring
Affects Version/s:
The two scenarios are actually identical. The routes should be treated totally
independent. One could use all kinds of protocols between the two routes and
things should still not change.
scenario N
=
from bar:A
onCompletion - mock:a end
to XXX
to foo:b
-- optional --
to WWW
Fail starting Camel if AnnotationTypeConverterLoader could not load any type
converters
---
Key: CAMEL-3550
URL: https://issues.apache.org/jira/browse/CAMEL-3550
camel-pdf component
---
Key: CAMEL-3552
URL: https://issues.apache.org/jira/browse/CAMEL-3552
Project: Camel
Issue Type: New Feature
Reporter: Jean-Baptiste Onofré
Fix For: 2.7.0, 3.0.0
Apache
Upgrade to CXF 2.3.2
Key: CAMEL-3553
URL: https://issues.apache.org/jira/browse/CAMEL-3553
Project: Camel
Issue Type: Task
Components: camel-cxf
Reporter: Claus Ibsen
Assignee: Willem
[
https://issues.apache.org/jira/browse/CAMEL-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned CAMEL-3551:
---
Assignee: Jean-Baptiste Onofré
camel-fop component
---
[
https://issues.apache.org/jira/browse/CAMEL-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reassigned CAMEL-3552:
---
Assignee: Jean-Baptiste Onofré
camel-pdf component
---
[
https://issues.apache.org/jira/browse/CAMEL-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983050#action_12983050
]
Jean-Baptiste Onofré commented on CAMEL-3552:
-
Patch in progress.
camel-pdf
[
https://issues.apache.org/jira/browse/CAMEL-3551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12983051#action_12983051
]
Jean-Baptiste Onofré commented on CAMEL-3551:
-
Patch in progress.
camel-fop
32 matches
Mail list logo
