Upgrading to JUEL 2.1.1 - Beware of API changes in JUEL
---
Key: CAMEL-1567
URL: https://issues.apache.org/activemq/browse/CAMEL-1567
Project: Apache Camel
Issue Type: Task
Compon
A while ago (last year) I've been chatting with Hiram, and we've agreed that
we could extend the Camel to support TX for InOut Exchanges, where we would
employ an AsynchProcessor for the IN message exchange flow and then deliver
the OUT message flow via a separate thread.
This effectively would ac
On Thu, Apr 23, 2009 at 11:21 PM, Claus Ibsen wrote:
> Hi Camel riders
>
> As you know we are working on Camel 2.0 and we decided to do a 2nd
> milestone release.
> This gives us more time to start on some of the ideas and internal
> refactorings I wanted
> to do for Camel 2.1.
>
> After having di
[
https://issues.apache.org/activemq/browse/CAMEL-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
christian ohr updated CAMEL-1566:
-
Patch Info: [Patch Available]
Description:
Long HL7 messages are split up into several e
HL7/MLLP receivers fails for long HL7 messages
--
Key: CAMEL-1566
URL: https://issues.apache.org/activemq/browse/CAMEL-1566
Project: Apache Camel
Issue Type: Bug
Components: camel-mina
[
https://issues.apache.org/activemq/browse/CAMEL-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51393#action_51393
]
Claus Ibsen commented on CAMEL-1565:
Raul see this link for the patch
http://svn.apache.o
[
https://issues.apache.org/activemq/browse/CAMEL-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea reassigned CAMEL-1566:
--
Assignee: Hadrian Zbarcea
> HL7/MLLP receivers fails for long HL7 messages
> --
Yep, we need camel-core feature includes the stax-api bundle.
But I did not find a way to add this bundle into the camel features.
Willem
James Strachan wrote:
> 2009/4/24 Willem Jiang :
>> Hi Gert,
>>
>> I'm try to load the Camel 2.0 SNAPSHOT features from the PAX-Exam.
>> I got below error when
[
https://issues.apache.org/activemq/browse/CAMEL-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1565.
Resolution: Fixed
Fix Version/s: 2.0.0
1.6.1
Assignee: Claus
[
https://issues.apache.org/activemq/browse/CAMEL-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51390#action_51390
]
Claus Ibsen commented on CAMEL-1565:
Raul, we will not backport a fix into Camel 1.4.x.
[
https://issues.apache.org/activemq/browse/CAMEL-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
christian ohr updated CAMEL-1566:
-
Attachment: HL7MLLPCodec.zip
the package names of the classes need to be adapted
> HL7/MLLP
[
https://issues.apache.org/activemq/browse/CAMEL-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1534.
Resolution: Fixed
Fix Version/s: (was: 2.1.0)
2.0.0
Thanks Joe fo
[
https://issues.apache.org/activemq/browse/CAMEL-1528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1528.
Resolution: Fixed
And added option to JMX Agent to only register processors if they have a cust
2009/4/24 Willem Jiang :
> Hi Gert,
>
> I'm try to load the Camel 2.0 SNAPSHOT features from the PAX-Exam.
> I got below error when the PAX-Runner load the below bundle
> mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jaxb-api-2.1/1.3.0
>
> BTW, If I remove the jaxb-api bundle, the cam
Hi Gert,
I'm try to load the Camel 2.0 SNAPSHOT features from the PAX-Exam.
I got below error when the PAX-Runner load the below bundle
mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jaxb-api-2.1/1.3.0
BTW, If I remove the jaxb-api bundle, the camel-context can be start
without any e
Agree, we should not remove anything until we have a solution.
Personally I'd like to see the async part fixed in 2.0.
One of the reasons for M2 is also to give us a bit more time to get it
right.
+1 for Channel, if it matters :)
Hadrian
On Apr 24, 2009, at 8:38 AM, James Strachan wrote:
[
https://issues.apache.org/activemq/browse/CAMEL-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1541.
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Claus Ibsen
trunk: 768292
> P
The Channel concept really makes a lot of sense. This will certainly make
Camel concepts fit more closely with the EIP book (channels are used in
between everything), and hopefully make Camel easier to understand as a
result.
I agree, the async backbone of Camel is in need for an overhaul. Though,
On Fri, Apr 24, 2009 at 2:36 PM, James Strachan
wrote:
> 2009/4/24 Claus Ibsen :
>> On Fri, Apr 24, 2009 at 11:23 AM, Guillaume Nodet wrote:
>>> The goal of the AsyncProcessor is to not block the calling thread when
>>> using an InOut exchange mostly.
>>> For example, if you invoke a web service
I'm not yet convinced we should remove something, without another
thing to put in its place. e.g. why don't we figure out a cleaner
model and just switch to it (say at 2.1).
For sure not that many things use async dispatch and it does cause
confusion debugging; but there's definitely been folks wi
2009/4/24 Claus Ibsen :
> On Fri, Apr 24, 2009 at 11:23 AM, Guillaume Nodet wrote:
>> The goal of the AsyncProcessor is to not block the calling thread when
>> using an InOut exchange mostly.
>> For example, if you invoke a web service which takes a long time to
>> answer, you don't really want th
A big +1 for Channel. The async processor is more complex; I'll try
reply to other comments in the thread directly...
2009/4/24 Claus Ibsen :
> Hi Camel riders
>
> As you know we are working on Camel 2.0 and we decided to do a 2nd
> milestone release.
> This gives us more time to start on some of
Make camel-validation thread-safe
-
Key: CAMEL-1565
URL: https://issues.apache.org/activemq/browse/CAMEL-1565
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 1.4.0
Hi
Another aspect of the impacts of the AsyncProcessor is that debugging
Camel routing is much more complex as well.
This will pull of end users with Camel as they can not easily just
single step in the route chain.
With the AsyncProcessor gone life will be much easier for both the
people that ma
On Fri, Apr 24, 2009 at 11:23 AM, Guillaume Nodet wrote:
> The goal of the AsyncProcessor is to not block the calling thread when
> using an InOut exchange mostly.
> For example, if you invoke a web service which takes a long time to
> answer, you don't really want the thread to be blocked for a f
On Fri, Apr 24, 2009 at 10:17 AM, Willem Jiang wrote:
>
> +1 for introducing Channel into Camel world.
>
> For the AsyncProcessor part, it's is really difficult to understand.
> I think it is more than Call back, it will not block the calling thread
> which will be used in the camel-jhc component[
Add an option to specify Ethernet network Interface to listen on for UDP
(Unicast & Multicast) and TCP.
-
Key: CAMEL-1564
URL: https://issues.apache.org/acti
The goal of the AsyncProcessor is to not block the calling thread when
using an InOut exchange mostly.
For example, if you invoke a web service which takes a long time to
answer, you don't really want the thread to be blocked for a few
seconds simply waiting for the answer: it just does not scale w
+1 for introducing Channel into Camel world.
For the AsyncProcessor part, it's is really difficult to understand.
I think it is more than Call back, it will not block the calling thread
which will be used in the camel-jhc component[1].
And I also did an enhancement[2] on the ErrorHandler of
DeadL
[
https://issues.apache.org/activemq/browse/CAMEL-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1560.
Resolution: Fixed
trunk: 768215
The bullet #1 is the most correct to use as it mimics how the
Definitively 1 for the Channel implementation.
This channel could be like in J2EE world with servlet filter used to by
example authenticated, authorized stuff coming into the bus.
Nevertheless, before to go directly into the coding, I propose that we
continue to discuss the concept of the cha
31 matches
Mail list logo
