Your binding mode is JSON.
bindingMode=“json"
You are supposed to return an object, but you are returning a JSON string. Add
bindingMode=“off” to this rest service.
Best regards,
Alex soto
> On Aug 20, 2020, at 12:20 PM, Gerald Kallas wrote:
>
> bindingMode="json"
Done: https://issues.apache.org/jira/browse/CAMEL-15435
<https://issues.apache.org/jira/browse/CAMEL-15435>
Best regards,
Alex soto
> On Aug 20, 2020, at 1:08 AM, Jean-Baptiste Onofre wrote:
>
> Hi Alex,
>
> Not yet, I will get back on this one asap.
> Did you
I am not sure you can do that but can try.
Also, I don’t understand why you would want to share a servlet across bundles.
Best regards,
Alex soto
> On Aug 19, 2020, at 12:02 PM, Gerald Kallas wrote:
>
> Thanks Alex.
>
> That seems to be a problem as I'll have every Blu
Thanks Alex,
Also looking for a way to configure this in a Blueprint XML file.
Best regards,
Alex soto
> On Aug 18, 2020, at 11:13 AM, Alex Dettinger wrote:
>
> Hi Alex,
>
> It seems the timeout is tuned after the context creation. One may achieve
> the desired
http://camel.apache.org/schema/blueprint”>
. . .
Again, all files need to be in the same bundle.
Best regards,
Alex soto
> On Aug 19, 2020, at 7:59 AM, Gerald Kallas wrote:
>
> Thanks Daniel.
>
> Not sure if I did explain right.
>
> I want to define
>
>
Any update on this, JB?
Best regards,
Alex soto
> On Aug 15, 2020, at 4:06 AM, Jean-Baptiste Onofre wrote:
>
> Hi,
>
> It seems to be related to a change on the camel-bean processor.
>
> Let me reproduce it and make a bisect to identify the change.
>
> Thanks !
I think you are missing:
http://www.osgi.org/xmlns/blueprint/v1.0.0";
>
> xmlns:ext="http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://
regards,
Alex soto
Thank you, JB, I hope it is an easy fix.
Best regards,
Alex soto
> On Aug 15, 2020, at 4:06 AM, Jean-Baptiste Onofre wrote:
>
> Hi,
>
> It seems to be related to a change on the camel-bean processor.
>
> Let me reproduce it and make a bisect to identify th
a:511)
~[?:?]
at
org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:391)
~[?:?]
... 22 more
Any ideas?
Best regards,
Alex soto
:
exchange.getContext().getRestConfiguration().getContextPath();
And the registry sometimes has data:
exchange.getContext().getRestRegistry()
But sometimes it doesn’t, all during in the same execution session.
Best regards,
Alex soto
> On Jul 22, 2020, at 2:13 AM, Jean-Bapti
PR here: https://github.com/apache/camel/pull/4027
<https://github.com/apache/camel/pull/4027>
Best regards,
Alex soto
> On Jul 21, 2020, at 9:57 AM, Alex Soto wrote:
>
> Thanks Claus, will create a PR
>
> Best regards,
> Alex soto
>
>
>
>
>>
ing?
Thanks and best regards,
Alex soto
Thanks Claus, will create a PR
Best regards,
Alex soto
> On Jul 19, 2020, at 3:53 AM, Claus Ibsen wrote:
>
> Hi
>
> Created a JIRA to not forget
> https://issues.apache.org/jira/browse/CAMEL-15311
>
> On Fri, Jul 17, 2020 at 10:40 AM Claus Ibsen wrote:
>>
I am sorry I posted this to the wrong mailing list.
Best regards,
Alex soto
> On Jul 13, 2020, at 12:22 PM, Jean-Baptiste Onofre wrote:
>
> Hi Alex,
>
> I don’t see this error on Jenkins, so I guess this error is in your itest.
>
> Can you share a simple project t
OsgiLocator package.
Best regards,
Alex soto
> On Jul 13, 2020, at 12:11 PM, Alex Soto wrote:
>
> With Karaf 4.2.9 and Pax-Exam 4.13.3, and openjdk version "11.0.7"
> 2020-04-14, running integration tests produces warning:
>
> WARNING: package org.apach
Worker.run(ThreadPoolExecutor.java:628)
[?:?]
at java.lang.Thread.run(Thread.java:834) [?:?]
Any idea?
Best regards,
Alex soto
is not calling it, instead logging directly with INFO level.
Best regards,
Alex soto
Also, take a look at org.apache.karaf.itests.KarafTestSupport.executeCommand
from
org.apache.karaf.itests
common
Best regards,
Alex soto
> On May 28, 2020, at 9:50 AM, Alex Soto wrote:
>
> Hi Gerald,
>
> There is no "/opt/apache-karaf/bin/user-add”
know which service deals with the JAAS subsystem,
but I suspect there is one, in which case, you can reference the service, as in:
Then call “myService” as a bean:
And avoid interacting with the shell. I hope this helps.
Best regards,
Alex soto
> On May 23, 2020, at
table, LDAP server, etc.
Best regards,
Alex soto
> On May 20, 2020, at 3:48 PM, Gerald Kallas wrote:
>
> Tx JB.
>
> So in this case, how can i call the jaas:* service from a Camel route? I did
> some research but wasn't able to find this ..
>
> Regards
&
Thank you, Grzegorz, this is excellent news!
I'm looking forward for this to be improved in version 8, as it is very useful,
and not only for Keycloak.
In particular, for securing Camel Rest services, and perhaps there are many
other use cases as well.
Best regards,
Alex soto
> O
.4.22.v20191022 | No authenticator
for: {RoleInfo,C[admin],None}
Which suggest something is misconfigured.
Best regards,
Alex soto
> On May 15, 2020, at 2:23 PM, Gerald Kallas wrote:
>
> 2020-05-15T18:20:50,256 | WARN | qtp1611313605-201 | SecurityHandler
&g
I’m not sure what is happening, but I noticed, you have ‘basic’ as lowercase,
maybe it is case sensitive. Try uppercase:
login.config.authMethod = BASIC
Also, what is in your 'etc/jetty.xml’ and ‘etc/org.ops4j.pax.web.cfg’ files ?
Best regards,
Alex soto
> On May 15, 2020, at
| 256 - org.ops4j.pax.web.pax-web-jetty -
> 7.2.11 | registering JasperInitializer
> 2020-05-14T21:15:19,003 | INFO | paxweb-context-4-thread-22 |
> CamelHttpTransportServlet| 288 - org.apache.camel.camel-servlet -
> 3.0.0 | Initialized CamelHttpTransportServle
I found a solution. See here:
http://karaf.922171.n3.nabble.com/Basic-authentication-of-WAB-using-Jaas-in-Karaf-tp4058251p4058280.html
<http://karaf.922171.n3.nabble.com/Basic-authentication-of-WAB-using-Jaas-in-Karaf-tp4058251p4058280.html>
Best regards,
Alex soto
> On May
Hello,
I am facing the same issue, using Camel Rest DSL on top of Servlet, Blueprint,
Karaf, Pax-Web, Jetty, how to add Basic authentication to the Rest endpoints?
Any pointers/examples will be appreciated.
Best regards,
Alex soto
> On Feb 4, 2020, at 3:15 AM, Gerald Kal
Bringing this up again, not getting headers in Camel traces with Blueprint.
Anybody experiencing the same?
Best regards,
Alex soto
> On Feb 6, 2020, at 9:29 AM, Alex Soto wrote:
>
> I’m sorry Guillaume, but I don’t see the similarity, although you may know
> something I don
parameters (good).
Best regards,
Alex soto
> On Feb 7, 2020, at 1:29 PM, Zoran Regvart wrote:
>
> query Hi Alex,
> perhaps I can shed some light on this, the header in header filter
> strategy refers to Camel message headers and external (say HTTP)
> headers. I think (haven&#x
both should behave the same way, preferable not being affected by
the header filter strategy.
Best regards,
Alex soto
> On Feb 6, 2020, at 4:44 PM, Alex Soto wrote:
>
> Look like it is caused by my:
>
>
>
> Which is very strange, since the ones that have defaul
I have this in my route:
${type:java.util.Collections.EMPTY_LIST}
parameters, since this is done by Camel and it is still useful. Is
there a way to control this?
Best regards,
Alex soto
> On Feb 6, 2020, at 3:34 PM, Alex Soto wrote:
>
> Hello:
>
> Running Camel 3.0.1. I have a Rest DSL, where Query Params are not being
> copi
documentation
https://camel.apache.org/manual/latest/rest-dsl.html
<https://camel.apache.org/manual/latest/rest-dsl.html> seems to imply that the
query parameters are copied to the Exchange headers, but this is not happening.
Any idea?
Best regards,
Alex soto
SEDA consumer is
not causing the desired effect.
Best regards,
Alex soto
> On Feb 6, 2020, at 12:09 PM, WEIQUAN YUAN wrote:
>
> as it is known that SEDA component is asyn component, but direct is sync
> one, can you use direct instead of seda?
>
> On Wed, Jan 29, 2020 at
I’m sorry Guillaume, but I don’t see the similarity, although you may know
something I don’t.
In any case do you know of a workaround?, basically I need to be able to enable
tracing of exchange headers (in Blueprint) for troubleshooting, but I have not
yet found how.
Best regards,
Alex soto
e exchange headers
are still not logged. Any idea?
Best regards,
Alex soto
array of classes as required by the data format
property in Rest DSL restConfiguration Blueprint XML?
Best regards,
Alex soto
> On Feb 4, 2020, at 10:58 AM, Alex Soto wrote:
>
> Tried this:
>
> bindingMode=“json”>
>
>
>
Tried this:
Produces error:
Error binding property (dataFormatTypes=org.my.class.here) with name:
dataFormatTypes on bean:
org.apache.camel.component.jsonapi.JsonApiDataFormat@409e7690 with value:
org.my.class.here
Best regards,
Alex soto
> On Feb 4, 2020,
Hello,
I am trying to use the JSonApi data format with Camel Rest DSL. There are not
examples, as far as I know.
So I am configuring it like this:
Thanks Claus,
I tested adding synchronous=true to the SEDA consumer, but it does not make any
difference.
The only thing that worked was to add asyncDelayed=“false” to the delay EIP.
Is this perhaps a bug?
Best regards,
Alex soto
> On Jan 29, 2020, at 1:48 PM, Claus Ibsen wrote:
>
Thanks Claus….
Oh, I see, after returning from the delay, it is a different thread that
processes the rest of the route.
Where should the synchronous=true be added, in the Producer or Consumer or
both URIs?
Best regards,
Alex soto
> On Jan 29, 2020, at 11:13 AM, Claus Ibsen wr
less like this:
1000
From logs, I can see messages being processed in parallel by this route. Any
idea?
(Camel version is 3.0.1)
Best regards,
Alex soto
Thank you JB,
I created a new ticket:
https://issues.apache.org/jira/browse/CAMEL-14457
<https://issues.apache.org/jira/browse/CAMEL-14457>
Best regards,
Alex soto
> On Jan 29, 2020, at 3:15 AM, Claus Ibsen wrote:
>
> On Wed, Jan 29, 2020 at 6:57 AM Jean-Baptiste On
Maybe ticket https://issues.apache.org/jira/browse/CAMEL-4171
<https://issues.apache.org/jira/browse/CAMEL-4171> should be reopened, or a
new one created, not sure. Will leave it to somebody that knows better.
Best regards,
Alex soto
> On Jan 28, 2020, at 1:51 PM, Alex So
Adding:
DynamicImport-Package: groovy.*, org.codehaus.groovy.*
To my bundle seems to work.
So I suppose this should be added somewhere in a Camel bundle?
Best regards,
Alex soto
> On Jan 28, 2020, at 1:29 PM, Alex Soto wrote:
>
> This appears to be a regression, as I
This appears to be a regression, as I remember seeing this problem in the past:
https://issues.apache.org/jira/browse/CAMEL-4171
<https://issues.apache.org/jira/browse/CAMEL-4171>
I will try your suggestion
Best regards,
Alex soto
> On Jan 28, 2020, at 1:24 PM, Jean-Baptiste Onof
(GroovyExpression.java:73)
…
I am running Camel in Karaf OSGi environment with camel-groovy feature
installed. In old Karaf 2.X, I had to install features camel-script, and
camel-script-groovy, but they are no longer available.
Best regards,
Alex soto
dleContext));
itCamelContext.setDataFormatResolver(new
OsgiDataFormatResolver(bundleContext));
Language simple = itCamelContext.resolveLanguage("simple");
assertNotNull(simple);
Best regards,
Alex soto
> On Jan 25, 2020, at 3:29 AM, Claus
running as part of an OSGi environment (Karaf)
Best regards,
Alex soto
nt status = httpclient.executeMethod(httppost);
The problem is that upload handler never receives any attachments. Any help
would be appreciated.
Best regards,
Alex soto
is properly registered.
Best regards,
Alex soto
> On Mar 12, 2019, at 10:44 AM, Alex Soto wrote:
>
> Hello,
>
> I am trying to use a custom Data Format with Camel Rest DSL in an OSGi
> container (Karaf) but the bundle fails to initialize with error:
>
>
>
I am instantiating the data format class as a Blueprint bean:
Then, in my Camel Context I register the custom data format:
Which I then reference in the Rest DSL configuration:
Any idea of what is going on here?
Best regards,
Alex soto
so the package contains ObjectFactory and all proper
annotations.
What else does Camel need to properly bind the XML to the Java class?
Why is it not parsing the XML correctly?
Best regards,
Alex soto
Created issue : https://issues.apache.org/jira/browse/CAMEL-12414
<https://issues.apache.org/jira/browse/CAMEL-12414>
Best regards,
Alex soto
> On Mar 28, 2018, at 12:46 PM, Alex Soto wrote:
>
> Anybody has any insight on what may be happening? Should I submit a Jira
>
Anybody has any insight on what may be happening? Should I submit a Jira
ticket?
Best regards,
Alex soto
> On Mar 27, 2018, at 3:18 AM, Owain McGuire
> wrote:
>
> Alex,
>
> Just had a quick look.
>
> The post in the Rest DSL route goes to direct:echo-route but
, cap: 38, components=1))
HTTP/1.1 200 OK
content-length: 38
content-type: application/octet-stream
connection: keep-alive
I have looked into the unit tests in Camel source, which are doing something
similar and it works there, so I can’t figure out why it wouldn’t work for me.
Can you take a took now
raf-netty-producer-test/tree/master>
Can anybody take a look and let me know what I am doing wrong?
Thanks and best regards,
Alex soto
> On Feb 22, 2018, at 5:42 PM, Alex Soto wrote:
>
> Hello,
>
> I am having some problems migrating to Camel 2.20.2 from 2.17.4.This has
it is imported by Bundle B, but it looks as if it
is bundle B the one doing the property lookup. This was working fine in Camel
2.17.4. Any idea?
Best regards,
Alex soto
Thank you Grzegorz, but I was using Camel 2.20.2, so I think it already
contains your fix.
Best regards,
Alex soto
> On Feb 23, 2018, at 2:07 PM, Grzegorz Grzybek wrote:
>
> Hello
>
> Please check https://issues.apache.org/jira/browse/CAMEL-12251
> There's a problem
I just created a ticket for this issue:
https://issues.apache.org/jira/browse/CAMEL-12291
<https://issues.apache.org/jira/browse/CAMEL-12291>
Feel free to amend if necessary.
Best regards,
Alex soto
> On Feb 23, 2018, at 2:07 PM, Grzegorz Grzybek wrote:
>
> Hello
>
&g
Thank you Guillaume,
You are correct, I tried your suggestion locally and it does work.
I don’t know what are the potential side effects of this change though.
Probably better that somebody more familiar with this code takes a look and
fixes it.
Best regards,
Alex soto
> On Feb 23, 2018,
;
> Is that really the XML? It’s not well formed - you start with a
> cm:property-placeholder element and end with a cm:default-properties element.
>
>> On Feb 22, 2018, at 12:48 PM, Alex Soto wrote:
>>
>> Hello,
>>
>>
http:https://localhost:8895/service?sslContextParameters=#sslParams&ssl=true";,
requestMessage.message,
byte[].class);
assertNotNull(response);
I appreciate any help with this problem.
Best regards,
Alex soto
:
Then it works fine, no errors. So this seems to be related to the property
placeholders. Has anybody seen this?
I appreciate any insight on how to solve this problem.
Best regards,
Alex soto
Yet another problem is that the exception is thrown even though I am passing
option throwExceptionOnFailure=false
I hope somebody can help me figure out what I am doing wrong.
Best regards,
Alex soto
> On Nov 30, 2017, at 9:22 AM, Alex Soto wrote:
>
> Hello,
>
> I am using
keChannelInactive(AbstractChannelHandlerContext.java:241)[32:io.netty.transport:4.0.43.Final]
Notice the error occurs in a different thread.
I don’t know why this error is occurring because there is a response, and why
is it not handling the exchange synchronous ?
Best regards,
Alex soto
I found this which looks very similar to my problem:
https://access.redhat.com/solutions/1428583
<https://access.redhat.com/solutions/1428583>
Anybody knows about this?
Best regards,
Alex soto
> On Jan 11, 2017, at 2:55 PM, Alex Soto wrote:
>
> I think it is
the property in the client bundle context, and
not in the context of the defining bundle.
Best regards,
Alex soto
> On Jan 11, 2017, at 1:58 PM, Quinn Stevenson
> wrote:
>
> Could it be because you’ve changed the placeholder prefix/suffix?
>
>
>> On Jan 11, 2017
fine with Camel 2.17.4, not so with 2.18.x
Any ideas?
Best regards,
Alex soto
> On Jan 10, 2017, at 6:05 PM, Alex Soto wrote:
>
> Hello,
>
> Starting with Camel 2.18.0, and including 2.18.1, I am getting this error
> during deployment of my Blueprint routes. The ex
omponent.parseUri(PropertiesComponent.java:160)
at
org.apache.camel.impl.DefaultCamelContext.resolvePropertyPlaceholders(DefaultCamelContext.java:2348)[51:org.apache.camel.camel-core:2.18.0]
at
org.apache.camel.util.jsse.JsseParameters.parsePropertyValue(JsseParameters.java:74)
Thanks for any help or pointers.
Best regards,
Alex soto
destroy
method. As they are, these classes seem to be of very little use, if at all.
Best regards,
Alex soto
> On Aug 24, 2016, at 11:43 AM, Claus Ibsen wrote:
>
> You can maybe build your own pojo that shutdown the pool and has a
> void method so you can use destroy-method in the b
2.17.0)
Best regards,
Alex soto
Dennis,
In your case, I think you are missing the idempotent option in the File URI.
Best regards,
Alex soto
> On Aug 18, 2016, at 10:59 AM, Dennis Bohnstedt Hansen wrote:
>
> Hi
>
> I’m seeing the same problem with pollEnrich, using a dynamic endpoint. I
> send a my r
problem where it does not work correctly when used under high concurrency.
Thank you Claus.
Best regards,
Alex soto
> On Aug 18, 2016, at 2:12 AM, Claus Ibsen wrote:
>
> Its easier to do a message transformation and set the body as a java.io.File
>
>
> {{env:HO
the file is still
present in the directory.
Am I setting the options correctly? How can this be accomplished?
Best regards,
Alex soto
That worked, thanks!
Best regards,
Alex soto
> On Jun 2, 2016, at 11:20 PM, Quinn Stevenson
> wrote:
>
>> org.apache.camel.builder.LoggingErrorHandler
ilder
package:
Import-Package: org.apache.camel.builder;version="[2.17,3)”
Any ideas?
Best regards,
Alex soto
It was my fault, I had a custom Trace Formatter that was printing null
mistakenly.
Best regards,
Alex soto
> On Apr 9, 2016, at 3:11 AM, Claus Ibsen wrote:
>
> That would be a bit odd as this is the code that maps the netty status to
> Camel
>
> headers.put(Exchange.
.
Best regards,
Alex soto
> On Apr 8, 2016, at 10:46 AM, Vanshul.Chawla wrote:
>
> We use this
>
>
> java.lang.Exception
>
> ${exception.message} contains
> '404&#
. . .
The problem is that the CamelHttpResponseCode is always null. I can see it the
trace logs:
Headers:{CamelHttpResponseCode=null, Connection=keep-alive,
CamelHttpResponseText=Not Modified, Content-Length=0}
How can I check the HTTP response code?
Best regards,
Alex soto
Thank you Claus,
Best regards,
Alex soto
> On Feb 28, 2016, at 1:30 AM, Claus Ibsen wrote:
>
> I logged a ticket
> https://issues.apache.org/jira/browse/CAMEL-9653
>
> On Sat, Feb 27, 2016 at 7:25 AM, Claus Ibsen wrote:
>> It was not designed primary to call utility
Hello,
Running Camel 2.16.1, I am trying to invoke a static method as follows:
However I get an exception with this message:
Bean instance is null. OGNL bean expressions requires bean instances.
Any idea why?
Thanks and best regards,
Alex soto
So, to summarize:
if I have ${} then use , if not, use
I am not sure I have seen this explained anywhere in the documentation, perhaps
it should be, to save others time.
Thanks for the help Claus.
Best regards,
Alex soto
> On Feb 24, 2016, at 12:04 PM, Claus Ibsen wr
y.
Curiously, changing back to works now without any issue.
Best regards,
Alex soto
> On Feb 24, 2016, at 10:58 AM, Claus Ibsen wrote:
>
> Hi
>
> Yeah there was a bug in the backwards compatible parser (checking the
> old simple style)
> https://issues.apache.org/jira/b
Startup resolution is fine, as the home directory is not expected to change.
So it is and not ? This is strange, I wouldn’t have guessed
it.
Thanks
Best regards,
Alex soto
> On Feb 24, 2016, at 10:21 AM, Claus Ibsen wrote:
>
> The simple function is
> ${sysenv:HOME}
>
&g
Sorry, I am using Camel 2.16.0
Do you mean, like this?
file:{{env:HOME}}/.ra/chains?autoCreate=false&noop=true&idempotent=false
My intention is to have {{env:HOME}} substituted with the home directory at
runtime
Best regards,
Alex soto
> On Feb 24, 2016, at 10:0
createExpression(SimpleLanguage.java:160)
at
org.apache.camel.builder.SimpleBuilder.createExpression(SimpleBuilder.java:107)
... 85 more
Best regards,
Alex soto
Great, in this case I am not doing any aggregation, so that won’t be a problem.
I just finished testing, and it worked, so thats for the help.
Best regards,
Alex soto
> On Nov 10, 2015, at 3:23 PM, Daniel Lamb wrote:
>
> If you do some parallel processing and have an aggregation
Thanks, I will give it a try.
Do you know if there is some concern using exchange properties that I should
worry about, perhaps with multi-threading?
Best regards,
Alex soto
> On Nov 10, 2015, at 2:57 PM, Daniel Lamb wrote:
>
> Store the headers as properties on the exchan
.
Best regards,
Alex soto
> On Nov 10, 2015, at 2:30 PM, Alex Soto wrote:
>
> Hello,
>
> I have a route with some custom headers that I need to preserve after sending
> an HTTP client request (HTTP producer), however, I do not want these headers
> to be sent as HTTP
Hello,
I have a route with some custom headers that I need to preserve after sending
an HTTP client request (HTTP producer), however, I do not want these headers
to be sent as HTTP headers to the remote server.
Is there a way to accomplish this?
Best regards,
Alex soto
Thank you Claus!
I found good example in the unit test of camel-netty4 component. In case it
helps anybody here is the fragment:
http://camel.apache.org/schema/spring";>
Best regards,
Alex soto
> On Oct 12, 2015, at 10:15 AM, Claus I
I am trying to follow documentation to:
Reusing Netty boss and worker thread pools
with Netty4 component, but if the page is referring to Netty3, how would this
work with Netty-4? Any pointers?
Best regards,
Alex soto
> On Oct 12, 2015, at 10:03 AM, Claus Ibsen wrote:
>
> Its
Best regards,
Alex soto
Hello,
I am using Camel 2.15.1. I have a Camel route that sets some custom headers,
then calls a Nettt4-http endpoint:
CompositeByteBuf, but isn’t
Camel supposed to convert this automatically?
Best regards,
Alex soto
test execution, so the question is:
How should I write the integration test code in order to verify the header is
not present?
Is there some flag or setting I can set to prevent the ProducerTemplate from
adding a bread crumb header?
Best regards,
Alex soto
> On Jun 15, 2015, at 10:02
P_RESPONSE_CODE, Integer.class);
assertEquals(500, code);
final Map headers = out.getHeaders();
assertNotNull(headers);
assertFalse(headers.containsKey(Exchange.BREADCRUMB_ID));
Last assertion is not passing!!!
Best regards,
Alex soto
> On Jun 1
500
1
Adding the removeHeaders does not seem to cause any effect; I am still getting
the breadcrumbId header in the HTTP response headers.
Best regards,
Alex soto
regards,
Alex soto
> On May 26, 2015, at 5:42 AM, Claus Ibsen wrote:
>
> Hi
>
> Ah maybe there is a glitch configuring those on the component level?
>
> You are welcome to log a JIRA so we wont forget. On the component
> level makes it configurable once for end u
1 - 100 of 102 matches
Mail list logo
