Just quick note, I found the README.txt in the Camel 1.6.1 kit is still
using the old activemq URL.
Since http://activemq.apache.org/camel will be redirected to
http://camel.apache.org, I give my +1 for this vote.
Willem
Hadrian Zbarcea wrote:
> A new apache-camel-1.6.1 is finally out with 92 ne
[
https://issues.apache.org/activemq/browse/CAMEL-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1611.
Resolution: Fixed
Fix Version/s: 1.6.1
Assignee: Willem Jiang
Willem Jiang alre
[
https://issues.apache.org/activemq/browse/CAMEL-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47273#action_47273
]
Hadrian Zbarcea edited comment on CAMEL-1078 at 5/14/09 12:33 PM:
-
2009/5/14 Hadrian Zbarcea :
> I personally don't see a reason for a specialized Exchange. We already *do*
> have specialized Messages and I think we should keep that (others have a
> different opinion).
>
> CAMEL-1078, is implemented for the most part, I'll try to finish the
> remaining stuff, for
[
https://issues.apache.org/activemq/browse/CAMEL-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51696#action_51696
]
Willem Jiang commented on CAMEL-1594:
-
camel-cxf , camel-restlet *DONE*
http://svn.apache
[
https://issues.apache.org/activemq/browse/CAMEL-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-1594.
-
Resolution: Fixed
> Unify the "Content-Type" header around the camel components
> ---
[
https://issues.apache.org/activemq/browse/CAMEL-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51697#action_51697
]
Hadrian Zbarcea commented on CAMEL-1078:
@Roman,
I will work on finishing this issue
I personally don't see a reason for a specialized Exchange. We
already *do* have specialized Messages and I think we should keep that
(others have a different opinion).
CAMEL-1078, is implemented for the most part, I'll try to finish the
remaining stuff, for the upcoming 2.0-M2. In the me
On Thu, May 14, 2009 at 7:49 AM, Hadrian Zbarcea wrote:
> A new apache-camel-1.6.1 is finally out with 92 new features, improvements
> and bug fixes.
>
> Please find the staging repo here:
> http://repository.apache.org/content/repositories/camel-staging-021/
>
> The tarballs are here
> http://rep
Many thanks. I will test this tomorrow morning and provide you feedback
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
On Thu, May 14, 2009 at 4:20 PM, Hadrian Zbarcea wrote:
> You may want to change the
You may want to change the permissions on your home dir as well.
Another thing you might want to do is to setup your authorized_keys in
~/.ssh so you use a strong auth mechanism.
[hadr...@minotaur ~]$ ls -ld ~cmoulliard
drwx-- 2 cmoulliard cmoulliard 512 Apr 26 23:51 /home/cmoulliard
Hadrian,
Thanks for all the hard work getting this out! Here's my +1
On Thu, May 14, 2009 at 11:19 AM, Hadrian Zbarcea wrote:
> A new apache-camel-1.6.1 is finally out with 92 new features, improvements
> and bug fixes.
>
> Please find the staging repo here:
> http://repository.apache.org/conten
[
https://issues.apache.org/activemq/browse/CAMEL-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51695#action_51695
]
Hadrian Zbarcea commented on CAMEL-735:
---
The 1.6.1 release is already built. If the com
On Thu, 2009-05-14 at 09:49 -0400, Hadrian Zbarcea wrote:
> A new apache-camel-1.6.1 is finally out with 92 new features,
> improvements and bug fixes.
>
> Please find the staging repo here:
> http://repository.apache.org/content/repositories/camel-staging-021/
>
> The tarballs are here
> http:
[
https://issues.apache.org/activemq/browse/CAMEL-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51694#action_51694
]
Claus Ibsen commented on CAMEL-735:
---
You can disable JMX when using 1.x.
JMX has been slate
On Thu, May 14, 2009 at 3:49 PM, Hadrian Zbarcea wrote:
> A new apache-camel-1.6.1 is finally out with 92 new features, improvements
> and bug fixes.
>
> Please find the staging repo here:
> http://repository.apache.org/content/repositories/camel-staging-021/
>
> The tarballs are here
> http://rep
[
https://issues.apache.org/activemq/browse/CAMEL-735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Bentley reopened CAMEL-735:
We can not use Milestone builds on our project :-(
Can you please port this fix to the 1.6.1. branch
A new apache-camel-1.6.1 is finally out with 92 new features,
improvements and bug fixes.
Please find the staging repo here:
http://repository.apache.org/content/repositories/camel-staging-021/
The tarballs are here
http://repository.apache.org/content/repositories/camel-staging-021/org/apache
[
https://issues.apache.org/activemq/browse/CAMEL-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51691#action_51691
]
Willem Jiang commented on CAMEL-1594:
-
Move the HTTP_RESPONSE_CODE,HTTP_URI into Exchang
Add more @annotations for EIP, async routing and onCompletion and whatelse
--
Key: CAMEL-1616
URL: https://issues.apache.org/activemq/browse/CAMEL-1616
Project: Apache Camel
CamelExchangeException implements Serializable but may not be serializable
--
Key: CAMEL-1615
URL: https://issues.apache.org/activemq/browse/CAMEL-1615
Project: Apache Camel
You are right. I will test it tomorrow from my home.
For SVN, everything works fine here.
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
On Thu, May 14, 2009 at 11:39 AM, Claus Ibsen wrote:
>
[
https://issues.apache.org/activemq/browse/CAMEL-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51690#action_51690
]
Roman Kalukiewicz commented on CAMEL-1078:
--
So let me add my thoughts on it.
I beli
[
https://issues.apache.org/activemq/browse/CAMEL-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51689#action_51689
]
Claus Ibsen commented on CAMEL-1604:
Started on the global. Got it working with Java DSL.
On Thu, May 14, 2009 at 11:09 AM, Charles Moulliard
wrote:
> Hi,
>
> I'm blocked by my firewall to connect to the apache.org server using ssh
> protocol on port 22. I have tried to add our Windows Proxy server in the
> proxy section of putty but it didn't change anything
Wait until you get home an
Yes. My proxy allows HTTP and HTTPS.
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
On Thu, May 14, 2009 at 11:24 AM, Willem Jiang wrote:
> Hi Charles,
>
> Does your proxy server support the ssl connectio
Hi Charles,
Does your proxy server support the ssl connection ?
I don't know if a socket5 proxy can do this.
Willem
Charles Moulliard wrote:
> Hi,
>
> I'm blocked by my firewall to connect to the apache.org server using ssh
> protocol on port 22. I have tried to add our Windows Proxy server in
Hi,
I'm blocked by my firewall to connect to the apache.org server using ssh
protocol on port 22. I have tried to add our Windows Proxy server in the
proxy section of putty but it didn't change anything
Does anybody has a solution to connect to people.apache.org server through
maybe a HTTP/S tunn
[
https://issues.apache.org/activemq/browse/CAMEL-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1614.
Resolution: Fixed
trunk: 774678
1.x: 774687
Frank feel free to test the fix
> Warning "Disab
[
https://issues.apache.org/activemq/browse/CAMEL-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-1614:
---
Affects Version/s: (was: 2.0.0)
1.6.0
2.0-M1
[
https://issues.apache.org/activemq/browse/CAMEL-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51686#action_51686
]
Willem Jiang commented on CAMEL-1609:
-
Did some enhancement
trunk
http://svn.apache.org/v
Hi
Hadrian got the great idea (IMHO) to suggest that Exchange is final,
so we only have DefaultExchange as the implementation.
The ticket to track this is:
http://issues.apache.org/activemq/browse/CAMEL-1078
Even with James comment on the ticket I do feel that we should not
allow custom Exchange
[
https://issues.apache.org/activemq/browse/CAMEL-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51685#action_51685
]
Willem Jiang commented on CAMEL-1594:
-
camel-http , camel-jetty *DONE*
http://svn.apache.
[
https://issues.apache.org/activemq/browse/CAMEL-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-1614:
--
Assignee: Claus Ibsen
> Warning "Disabling JMSReplyTo as this Exchange is not OUT capable"
Hi Claus,
if (methodToUse.isEntityEnclosing()) {
((EntityEnclosingMethod)method).setRequestEntity(requestEntity);
if (requestEntity.getContentType() == null) {
LOG.warn("Missing the ContentType in the request entity!");
}
}
The Get method will be ex
Warning "Disabling JMSReplyTo as this Exchange is not OUT capable" on false
positives in JBossAS5
-
Key: CAMEL-1614
URL: https://issues.apache.org/activemq/browse/CAME
Willem
Beware to do WARN logging in case it will log all the time
+LOG.warn("Missing the ContentType in the request entity!");
Its quite often not to set a Content-Type using camel http to just do
a text/plain GET.
So be sure that the http client sets a Content-Type if the end use
37 matches
Mail list logo
