Command context-list extend class CamelControllerImpl.
This class find OSGi services
Used OsgiDefaultCamelContext class is not a service. Why do his service?
Where is it written that it is necessary to register it as a service?
Where can I see an example of how this is done?
I use Apache Karaf 4.0.7.
Camel karf commands do not work.
Or when I did not think to stop running components.
First OSGI bundle use dynamic OSGi components.
The class is an analogue of the standard Bundle activator.
Second OSGI bundle use Karaf Shell annotation.
First OSGI bundle defines
>From the karaf prompt I do a "list" and get the following:
237 | Active | 80 | 0.32 |
qpid-amqp-1-0-client-jms
238 | Active | 80 | 0.32 |
qpid-amqp-1-0-common
239 | Active | 80 | 0.32 |
Hi
Do you use CXFRS ? If yes you might to experiment with CXFRS
Jetty-backed endpoints, with the SAML2 filters:
http://cxf.apache.org/docs/jaxrs-oauth2-assertions.html#JAXRSOAuth2Assertions-SAML2Bearer
Though they have not been as well stressed as the filters for the JWT
assertions
Just to be clear did you install the qpid jar first? Something like the
below in the karaf prompt.
bundle:install wrap:mvn:org.apache.qpid/qpid-amqp-1-0-client/0.20
Run a bundle list to ensure the bundle is properly installed. Can verify in
the logs. Only then add the camel-amqp.
On Tue, Feb
Thanks for that link. That's where I first found a list of dependencies
that I need. I've also gone through the camel-amqp component source code
for both 2.16.x and 2.18.x to try and figure out the differences. Below
is the output when trying to install camel-amqp version 2.16.2
This should give you some indication of what dependencies are required..
https://mvnrepository.com/artifact/org.apache.camel/camel-amqp/2.18.2
On Tue, Feb 21, 2017 at 10:35 PM, Mark Webb [via Camel] <
ml-node+s465427n5794222...@n5.nabble.com> wrote:
> The problem I'm running in to is figuring
The problem I'm running in to is figuring out what the dependency and
version I'm missing is. The dependency that is being reported is in
ServiceMix. My guess its a dependency of a dependency and its not getting
reported all the way back. I turned up the logging and don't see anything
there
https://servicemix.apache.org/docs/7.x/users-guide/deployer.html
Somewhere in the middle sections there is documentation on the wrapper.
So I think you need to deploy the dependency as a wrapper and then the
camel-amqp as a feature.
On Tue, Feb 21, 2017 at 10:10 PM, Mark Webb [via Camel] <
Hi,
We are implement OAuth+SAML Bearer assertion and wanted to know if someone
played around with JETTY acting as OAuth token server based on SAML Assertion?
Basically - https://tools.ietf.org/html/draft-ietf-oauth-saml2-bearer-23 we
want to test within camel route with JETTY as OAuth Token
I believe you are correct. The problem with the wrapping of a jar into a
bundle is that you often lose the dependencies and the wrapped bundle
always shows as active even if there are missing dependencies.
On Tue, Feb 21, 2017 at 4:06 PM, souciance wrote:
>
I have not worked with ServiceMix but with Karaf if the thing you are
deploying is not a osgi bundle you need to use the "wrap" command to wrap
it which will instruct Karaf to add some OSGI stuff to it. Must be
something similar for ServiceMix.
Something like
Well it sounds a bit strange that the camel commands do not work. What
version of Camel and Karaf do you run? I have 2.17.0 and 4.0.2 and that
works and I have tried with two camel contexts in a bundle.
Anyway stopping one shouldn't stop the other unless you have some other
kind of dependency
Yeah I understand. We will either have to convince the other group (not
helpful one) to change the folder name or fork the code and extend.
Hopefully they will do the first option.
We have no permissions to run scripts on that ftp server...its not ours do
do anything with.
-Dave
On Tue, Feb
Not sure if this should be posted here or the servicemix users forum, but
I'm trying to install camel-amqp in ServiceMix 6.1.1, which uses Camel
2.16.2, and I'm seeing the following error in the ServiceMix/Karaf console:
karaf@root>feature:install camel-amqp
Error executing command: Can't install
Oh maybe you can run some script periodically on that ftp server where
they will rename those folders.
On Tue, Feb 21, 2017 at 7:25 PM, Claus Ibsen wrote:
> Sorry but thats not on the table - it would complicate / confuse too
> much the code - as there is a fair amount of
Sorry but thats not on the table - it would complicate / confuse too
much the code - as there is a fair amount of code that parses folder
names with / and \ slashes and whatnot.
You can fork the code and built your own extended ftp component or use
some other ftp library.
On Tue, Feb 21, 2017
I did try including separator=UNIX in the URI but that didn't help.
I totally agree it would be better to not use such 'bad' folder names but
these are specified by external parties and its difficult to control what
they do.
It would be ideal of the Camel component can handle any folder name
Hi,
I tried this also but the resolver gets not invoked when resolving the dtd,
with the xsd it works fine.
Mit TouchDown von meinem Android-Telefon gesendet (www.symantec.com)
-Original Message-
From: Claus Ibsen [claus.ib...@gmail.com]
Received: Dienstag, 21 Feb. 2017, 19:08
To:
You can maybe plugin a custom resource resolver and let it return null
/empty or something.
Check the docs
https://github.com/apache/camel/blob/master/camel-core/src/main/docs/validator-component.adoc
And you can find some unit tests that test this resolver
On Tue, Feb 21, 2017 at 6:55 PM,
Hi
That is a very unfortunate folder name to use.
You can try setting the separator option on the ftp endpoint.
Otherwise then .. you would be out of luck. Its maybe better to avoid
such "bad" folder names instead.
On Tue, Feb 21, 2017 at 6:34 PM, David Hoffer wrote:
> I'm
Hi,
I'm using the camel validator component to validate an XML. The XML has a DTD
declaration inside. This points to a relative path, where I don't want to have
the DTD.
Is there any way to disable the DTD validation or resolve the declared DTD to a
path where I want to have the DTD?
I
In the first OSGI bundle is multiple camel routes.
Camel karaf command do not work
camel:context-list
camel:component-list
camel:route-list
I stop and will start component (OSGI bundle stop and start).
Fires once. After 5-6 seconds, I repeat. Again, it does not work.
The first way should not
I'm trying to connect to a Linux SFTP server that has a literal sub-folder
name of \a\b\c. Where \ are literal backslash characters. Note, this
subfolder is a child of the user's login folder and does not represent a
root folder.
Is there any way to configure Camel to treat the backslashes as
Here is a repo with the example.
https://github.com/owain68/camel-spring-boot-examples
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-2-18-2-Spring-Boot-Unit-Tests-Does-mockOut-expectedMessageCount-work-tp5794070p5794204.html
Sent from the Camel - Users mailing list
Before running it a second time, you can run bundle:list to see if that
bundle containing the first consumer is active or not.
On Tue, Feb 21, 2017 at 3:45 PM, alexey-s [via Camel] <
ml-node+s465427n5794194...@n5.nabble.com> wrote:
> There are two OSGI bundle.
>
> First OSGI bundle
>
>
OK, my issue was caused by incorrect version of commons-pool2 in
dependencies.
Had 2.0, upgrading to 2.4.2 fixed the issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/NullPointer-org-apache-camel-component-jms-DefaultJmsMessageListenerContainer-tp5788071p5794195.html
There are two OSGI bundle.
First OSGI bundle
from("direct-vm:makeDoc")
.bean(loacalBean, "make");
Second OSGI bundle
void execute(String entityGuid) {
SimpleRegistry registry = new SimpleRegistry();
BundleContext bundleContext =
getMockEndpoint is when you extend CamelSpringTestSupport class which
you do NOT do.
For more information about notifier, testing and whatnot there is the
Camel docs, and then also the Camel books.
For example the Camel in Action 2nd edition is up to date with latest
Camel stuff
On Tue, Feb 21,
Well that bit was much easier.
@RunWith(CamelSpringBootRunner.class)
@MockEndpoints
@UseAdviceWith
@SpringBootTest(classes = SpringBootCamelVanilla.class)
public class RouteBTests {.}
--
View this message in context:
Well it looks as though everything has changed! Just for Spring Boot?
MockEndpoint mockOut = getMockEndpoint("mock:out");
is now
MockEndpoint mockOut = camelContext.getEndpoint("mock:out",
MockEndpoint.class);
The documentation is somewhat thin on the ground to say the least.
This is all I
Hi,
I have opened a new bug in CXF Jira
https://issues.apache.org/jira/browse/CXF-7260. You can watch the progress
there.
Martin
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-won-t-load-ReceiveTimeout-from-conduit-file-tp5794169p5794177.html
Sent from the Camel
Hi Martin
Looks like it is a CXF centric query, the configuration as set in the
container/etc/org.apache.cxf.http.conduits-common.cfg has no effect.
Can you please forward your query to the CXF users list first and then
we can take it from there
Cheers, Sergey
On 21/02/17 10:34,
Hi Claus,
I thought the issue concerns the Apache Camel CXF components as Blueprint
leverages http://camel.apache.org/schema/blueprint/cxf and
http://camel.apache.org/schema/blueprint.
Error I am getting is from DelayService (Blueprint Proxy implementing Camel
CXF).
Could you elaborate more
Hi
Ask the vendor of that product you use, eg Talend.
On Tue, Feb 21, 2017 at 11:11 AM, martin.pelikan
wrote:
> Hello,
>
> configuration ReceiveTimeout does not work via conduit file.
>
> Scenario:
> Published SOAP service DelayService with SSL on port 8443. This
Hello,
configuration ReceiveTimeout does not work via conduit file.
Scenario:
Published SOAP service DelayService with SSL on port 8443. This service
calls another service SOAP Web service, where thread.sleep(70s) is
implemented. DelayService is invoked via SOAPUI.
Expected result:
Successful
Yes, thank you, I solved that last night at the end of the day ! I used
version 2.13...
--
View this message in context:
http://camel.465427.n5.nabble.com/Route-with-the-jt400-component-and-Blueprint-tp5794147p5794160.html
Sent from the Camel - Users mailing list archive at Nabble.com.
37 matches
Mail list logo