Hi,I'm trying to set HTTP Authorization Policy as described in here
http://camel.apache.org/spring-security.html. But I need to set it using
JavaDSL:
from("jetty://http://localhost:9090/api?matchOnUriPrefix=true";)
.routeId("Activation Endpoint").routePolicyRef("admin_policy")But I
g
Hi,
I just started playing with Camel - I have an option to use it for upcoming
project.
I might miss something or there is an issue with getting custom "Accept"
http header across.
Here is my route builder:
from("servlet:///reporting")
.removeHeader(Exchange.HTTP_URI)
I think I found the issue. My understanding was that
Exchange.ACCEPT_CONTENT_TYPE maps to HTTP header Accept.
I was wrong. Exchange.ACCEPT_CONTENT_TYPE has nothing to do with it and I
have to set it (HTTP Accept header) manually.
--
View this message in context:
http://camel.465427.n5.nabble.c
Hi,
I'm prototyping a project. Works fine in jetty and tomcat.
Having trouble with deploying to JBoss 5.1.0:
org.apache.camel.RuntimeCamelException:
org.apache.camel.TypeConverterLoaderException: Failed to load type
converters because of: Cannot find any type converter classes from the
following
Thank you for the help I got before.
I'm still having trouble deploying the camel .war into JBoss.
This time it is JBoss Logging binding for slf4j.
When deployed with the default dependencies provided by the archetype it
fails with duplicate binding for SLF4J.
If the bindings are reconfigured to
At this moment I'm playing with WAR.
Would you be so kind to point to instruction how to define this for WAR?
--
View this message in context:
http://camel.465427.n5.nabble.com/JBoss-5-1-0-Camel-2-7-0-SLF4J-version-difference-tp4498593p4498620.html
Sent from the Camel - Users mailing list archiv
It seems not to work, as the camel has been compiled with a different class
version, thus when supplied with the older library it simply fails:
Caused by: java.lang.LinkageError: loader constraint violation: when
resolving method
"org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILog
Yes, Maven.
The issue is that camel is compiled expecting SLF4J api v 1.6.1.
The one provided with JBoss is 1.5.8.
So when Camel runs it detects a mismatch between expected class version and
provided and fails.
So excluding the dependency is not an option unless I recompile the Camel.
--
View
Hi,
Just wanted to double check if anyone is actually running Camel in JBoss
5.1.0 using Spring DSL and servlet endpoints.
I have an opportunity to introduce camel as an integration technology used
in our corporation but I'm having troubles with the simplest scenario
(albeit the real one).
JBoss
Thank you for your prompt answer.
I have seen the link and tried to implement this. I did not manage to fix
it.
Recompiling is out of question as it goes against some of the internal
requirements I need to satisfy.
--
View this message in context:
http://camel.465427.n5.nabble.com/JBoss-5-1-0
Jean-Baptiste,
Thank you for the suggestion. I have done that. Though I no longer get
complaints about the version mismatch it fails with
NoSuchFieldError: log
Despite the fact that that I have following jar in the lib dir:
log4j-1.2.16.jar
slf4j-api-1.6.1.jar
slf4j-log4j12-1.6.1.jar
The deta
Jean Baptiste,
thank you very much for that, much obliged.
Attaching the project.
http://camel.465427.n5.nabble.com/file/n4501000/camel-prototype-1.zip
camel-prototype-1.zip
Don.
--
View this message in context:
http://camel.465427.n5.nabble.com/JBoss-5-1-0-Camel-Spring-Servlet-endpoint-Anyone
Jean-Baptiste,
I have tried camel 2.6.0, but as Richard noted it depends on the Spring 3,
hence the issue with the Servlet loading order.
--
View this message in context:
http://camel.465427.n5.nabble.com/JBoss-5-1-0-Camel-Spring-Servlet-endpoint-Anyone-succeded-tp4500558p4501033.html
Sent from
Richard,
thank you.
I downgraded to camel 2.2.0/ spring 2.5.6 and prototype works now.
I'll continue with it to see if I can implement what's required and
introduce it internally.
Would be nice though to get the latest and greatest at some point.
--
View this message in context:
http://camel.
Claus,
I'm not sure JBoss 6 is an option for us. Our project goes live before 6.0
confirmed as the commercially supported platform and for me to introduce a
technology it got to have vendor support.
That brings me to the next question - what would be the best way to obtain a
quote on technical an
Claus,
I got it downloaded and deployed. It seems to present the same issue with
the servlets - i.e. Spring Context being instantiated by a listener before
the CamelServlet is available.
Searching the database for the JIRA number.
BTW, does Fuse 2.7 use slf4j ?
--
View this message in context:
I believe the issue is https://issues.apache.org/jira/browse/CAMEL-3549
CAMEL-3549
--
View this message in context:
http://camel.465427.n5.nabble.com/JBoss-5-1-0-Camel-Spring-Servlet-endpoint-Anyone-succeded-tp4500558p4501295.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I have seen this too. Though I have tried so many things in the last few days
I can not recall exactly what caused this.
I have a feeling it might be something to do with the camel web console...
Are you deploying one?
--
View this message in context:
http://camel.465427.n5.nabble.com/JBoss-5-
Thanks.
I guess in my situation using Fuse distribution is more preferrable
(enterprise affiliation is an important question for our management).
Do you think you could find time to look if anything can be done about
https://issues.apache.org/jira/browse/CAMEL-3549 CAMEL-3549 ?
--
View this mes
Hi,
has anyone been successfull with setting up a client endpoint that would
accept any given certificate/hostname?
The endpoint I'm trying to access has self signed certificate.
Camel 2.8.0
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/HTTP4-Client-SSL-Accept-All
Thank you.
That worked.
And do I understand correctly that it will conflict with other configurers -
for instance Basic Authentication defined as authUsername and authPassword ?
--
View this message in context:
http://camel.465427.n5.nabble.com/HTTP4-Client-SSL-Accept-All-Hostnames-Accept-A
After looking into the HTTP components I reckon the above-mentioned scenario
is not possible without heavy tweaking with custom HttpClientConfigurer
(since it overrides the configuration parameters specified in the URL).
Is my understanding correct?
--
View this message in context:
http://came
It seems that camel-http4 component (or the httpclient ) loses credentials
when a custom HttpClientConfigurer is used.
Here is my configuration:
from("servlet:///proxy?matchOnUriPrefix=true")
.removeHeader(Exchange.HTTP_URI)
.removeHeader(Exchange.HTTP_PATH)
Fully agree.
To the best of my understanding the latest version (2.8.0 it is) does
provide this functionality.
I'm not sure when it is due for the release tho.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-http4-loses-auth-credentials-when-a-custom-http-client-config
Claus,
would you be able to give me some guesstimate on when do you think Camel
2.8.0 could be ready?
I need to make a decision which version to pick and I would prefer 2.8.0,
subject to the release before we hit PROD.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/
Great news. Is the Release Candidate available through the -SNAPSHOT repo or
I need to check out and build myself?
--
View this message in context:
http://camel.465427.n5.nabble.com/Some-indication-on-when-2-8-0-could-be-released-tp4585340p4585547.html
Sent from the Camel - Users mailing list ar
Oh. My apologies - missed the repo.
I will switch to 2.8.0 tomorrow, test run it and vote.
Though I'm not sure I should be voting. The scope of the project is tiny.
--
View this message in context:
http://camel.465427.n5.nabble.com/Some-indication-on-when-2-8-0-could-be-released-tp4585340p4585
Babak,
I had a problem with camel deployment to JBoss. There was a need for a
special library to enable scanning of the custom packages as camel
components, and a configuation line in appContext.xml (assuming you are
using spring):
Have you fixed that?
If not I could send you the library
Hi Claus,
sorry I could not check the fix on the weekend. I have shut down my work PC
by mistake (instead of rebooting it) over the VPN.
I have run the scenario Camel -- HTTP --> proxy -- HTTPS --> destination.
Seem to work.
Will this fix be back ported to 2.8.0 at some stage or will it be avail
Hi,
does anybody have a example how to configure camel with JBoss Messaging?
Using AS 5.1.0.
Thanks.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-jms-JBoss-Messaging-tp4598676p4598676.html
Sent from the Camel - Users mailing list archive at Nabble.com.
30 matches
Mail list logo