Re: How to programmatically reset an application property?
It seems you are doing it wrong.
What is the intention of your doing?
How do you use placeholders in Camel routes? If you place them into
endpoints' URLs you could not change their values to take effect
immediately. You have to reset the whole Camel context. It leads to stop
all routes, reinit them and start again. It will take a time. Is it a thing
you really need?
Any way you can put all needed properties in class fields to make them change.
___
Best wishes,Vyacheslav.
Ron Cecchini 24 августа 2021 г. 07:53:29 написал:
I'm using Camel + Spring Boot.
In my application.properties, I set a property 'foo.bar.size'
In my routes, I use: {{foo.bar.size}}
In some Java processor code, I use:
camelContext.resolvePropertyPlaceholders("{{foo.bar.size}}")
I now need to reset that property in some Java code and have it take effect
immediately.
I read the "Properties" doc and tried a couple of things... but I'm missing
the magic sauce.
How do I reset an application property?
Thank you very much.
How to programmatically reset an application property?
I'm using Camel + Spring Boot.
In my application.properties, I set a property 'foo.bar.size'
In my routes, I use: {{foo.bar.size}}
In some Java processor code, I use:
camelContext.resolvePropertyPlaceholders("{{foo.bar.size}}")
I now need to reset that property in some Java code and have it take effect
immediately.
I read the "Properties" doc and tried a couple of things... but I'm missing the
magic sauce.
How do I reset an application property?
Thank you very much.
R: How to get camel-google-pubsub working on GKE, pubsub with workload identity (instead of service account keys?
Hello, You're welcome to open a Jira and work on a PR. We need to review more google cloud components for sure in relation to this. Thanks for reaching out to the community Inviato da Yahoo Mail su Android Il lun, 23 ago, 2021 alle 21:45, Tamás Utasi ha scritto: I'm trying to get a simple piece of code working using: - GKE (https://cloud.google.com/kubernetes-engine), - google pubsub, - workload identity ( https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity), - camel-google-pubsub and camel-google-pubsub-starter v 3.11.0 My app comes up OK, but when it tries to connect to my subscription it fails with: "io.grpc.StatusRuntimeException: PERMISSION_DENIED: The request is missing a valid API key." This is reasonable as I'm not providing the "serviceAccountKey" query parameter as I want to use workload identity (which I configured all the way through) cause, as of today, that is the recommended way to access Google Cloud services from GKE instead of a mounted service account keys. However. inspecting the code https://github.com/apache/camel/blob/camel-3.11.1/components/camel-google/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/GooglePubsubComponent.java tells me that this is impossible at the moment. I'm happy to create a JIRA and attempt to open a PR to add support for workload identity if someone can confirm that this is desired. Best Regards, Tamas
How to get camel-google-pubsub working on GKE, pubsub with workload identity (instead of service account keys?
I'm trying to get a simple piece of code working using: - GKE (https://cloud.google.com/kubernetes-engine), - google pubsub, - workload identity ( https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity), - camel-google-pubsub and camel-google-pubsub-starter v 3.11.0 My app comes up OK, but when it tries to connect to my subscription it fails with: "io.grpc.StatusRuntimeException: PERMISSION_DENIED: The request is missing a valid API key." This is reasonable as I'm not providing the "serviceAccountKey" query parameter as I want to use workload identity (which I configured all the way through) cause, as of today, that is the recommended way to access Google Cloud services from GKE instead of a mounted service account keys. However. inspecting the code https://github.com/apache/camel/blob/camel-3.11.1/components/camel-google/camel-google-pubsub/src/main/java/org/apache/camel/component/google/pubsub/GooglePubsubComponent.java tells me that this is impossible at the moment. I'm happy to create a JIRA and attempt to open a PR to add support for workload identity if someone can confirm that this is desired. Best Regards, Tamas
Re: Camel-ldap xtream issue
I will take a look. Regards JB > Le 23 août 2021 à 21:40, Daniel Langevin a écrit : > > > Hi ! > Anybody have a clue ? > > Regards. > > Daniel > >> On 2021/08/17 19:31:33, Daniel Langevin >> wrote: >> Hi, >> >> I try to modify an application who retrieve LDAP search, >> Convert result in XML and generate HTML with camel-saxon. >> >> CAMEL 3.11.1 Karaf 4.2.10 >> >> >> But facing a problem. >> >> I Add a variable in my Search, (networkAddress) this new variable contains >> String encoded in a special format and also contains null value >> >> When I use xsteam to format the body who contains >> ArrayList >> I received an error. >> >> ... >> > uri="ldap:ldapSHQinterne?base=ou=xx,o=yy&returnedAttributes=ou,sn,givenName,fullName,telephoneNumber,physicalDeliveryOfficeName,mail,pwmLastPwdUpdate,pwmResponseSet,Photo,passwordExpirationTime,loginGraceRemaining,loginDisabled,loginTime,lockedByIntruder,networkAddress" >> /> >> ERROR RECEIVE HERE >> >> ... >> >> Debugging information >> message : Failed calling method >> cause-exception : com.thoughtworks.xstream.io.StreamException >> cause-message : >> method : com.sun.jndi.ldap.LdapAttribute.writeObject() >> --- >>at >> com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:158) >> ~[!/:?] >>at >> com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:257) >> ~[!/:?] >>at >> com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:87) >> ~[!/:?] >>at >> com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:139) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:87) >> ~[!/:?] >>at >> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) >> ~[?:1.8.0_121] >>at >> javax.naming.directory.BasicAttributes.writeObject(BasicAttributes.java:293) >> ~[?:1.8.0_121] >>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> ~[?:1.8.0_121] >>at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> ~[?:1.8.0_121] >>at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> ~[?:1.8.0_121] >>at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121] >>at >> com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:154) >> ~[!/:?] >>... 73 more >> Caused by: com.thoughtworks.xstream.io.StreamException: >>at >> com.thoughtworks.xstream.io.xml.StaxWriter.setValue(StaxWriter.java:160) >> ~[!/:?] >>at >> com.thoughtworks.xstream.io.WriterWrapper.setValue(WriterWrapper.java:45) >> ~[!/:?] >>at >> com.thoughtworks.xstream.converters.SingleValueConverterWrapper.marshal(SingleValueConverterWrapper.java:45) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:50) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:87) >> ~[!/:?] >>at >> com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:139) >> ~[!/:?] >>at >> com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:87) >> ~[!/:?] >>at >> java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) >> ~[?:1.8.0_121] >>at >> javax.naming.directory.BasicAttribute.writeObject(BasicAttribute.java:507) >> ~[?:1.8.0_121] >>at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source) >> ~[?:?] >>at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> ~[?:1.8.0_121] >>at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121] >>at >> com.thoughtwor
Re: Camel-ldap xtream issue
Hi ! Anybody have a clue ? Regards. Daniel On 2021/08/17 19:31:33, Daniel Langevin wrote: > Hi, > > I try to modify an application who retrieve LDAP search, > Convert result in XML and generate HTML with camel-saxon. > > CAMEL 3.11.1 Karaf 4.2.10 > > > But facing a problem. > > I Add a variable in my Search, (networkAddress) this new variable contains > String encoded in a special format and also contains null value > > When I use xsteam to format the body who contains > ArrayList > I received an error. > > ... > uri="ldap:ldapSHQinterne?base=ou=xx,o=yy&returnedAttributes=ou,sn,givenName,fullName,telephoneNumber,physicalDeliveryOfficeName,mail,pwmLastPwdUpdate,pwmResponseSet,Photo,passwordExpirationTime,loginGraceRemaining,loginDisabled,loginTime,lockedByIntruder,networkAddress" > /> > ERROR RECEIVE HERE > > ... > > Debugging information > message : Failed calling method > cause-exception : com.thoughtworks.xstream.io.StreamException > cause-message : > method : com.sun.jndi.ldap.LdapAttribute.writeObject() > --- > at > com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:158) > ~[!/:?] > at > com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:257) > ~[!/:?] > at > com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90) > ~[!/:?] > at > com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68) > ~[!/:?] > at > com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) > ~[!/:?] > at > com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) > ~[!/:?] > at > com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:87) > ~[!/:?] > at > com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:139) > ~[!/:?] > at > com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:87) > ~[!/:?] > at > java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) > ~[?:1.8.0_121] > at > javax.naming.directory.BasicAttributes.writeObject(BasicAttributes.java:293) > ~[?:1.8.0_121] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ~[?:1.8.0_121] > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[?:1.8.0_121] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[?:1.8.0_121] > at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121] > at > com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:154) > ~[!/:?] > ... 73 more > Caused by: com.thoughtworks.xstream.io.StreamException: > at > com.thoughtworks.xstream.io.xml.StaxWriter.setValue(StaxWriter.java:160) > ~[!/:?] > at > com.thoughtworks.xstream.io.WriterWrapper.setValue(WriterWrapper.java:45) > ~[!/:?] > at > com.thoughtworks.xstream.converters.SingleValueConverterWrapper.marshal(SingleValueConverterWrapper.java:45) > ~[!/:?] > at > com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:50) > ~[!/:?] > at > com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) > ~[!/:?] > at > com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) > ~[!/:?] > at > com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:87) > ~[!/:?] > at > com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:139) > ~[!/:?] > at > com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:87) > ~[!/:?] > at > java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344) > ~[?:1.8.0_121] > at > javax.naming.directory.BasicAttribute.writeObject(BasicAttribute.java:507) > ~[?:1.8.0_121] > at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source) > ~[?:?] > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[?:1.8.0_121] > at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121] > at > com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:154) > ~[!/:?] > at > com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(Seriali
RE: Camel-ldap xtream issue
Hello,
does anyone have a clue?
A way to solve the problem?
An explanation ?
I'm still stuck
Regards!
Daniel Langevin
-Message d'origine-
De : Daniel Langevin
Envoyé : 17 août 2021 15:32
À : users@camel.apache.org
Objet : Camel-ldap xtream issue
Hi,
I try to modify an application who retrieve LDAP search, Convert result in XML
and generate HTML with camel-saxon.
CAMEL 3.11.1 Karaf 4.2.10
But facing a problem.
I Add a variable in my Search, (networkAddress) this new variable contains
String encoded in a special format and also contains null value
When I use xsteam to format the body who contains
ArrayList
I received an error.
...
ERROR RECEIVE HERE
...
Debugging information
message : Failed calling method
cause-exception : com.thoughtworks.xstream.io.StreamException
cause-message :
method : com.sun.jndi.ldap.LdapAttribute.writeObject()
---
at
com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:158)
~[!/:?]
at
com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:257)
~[!/:?]
at
com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90)
~[!/:?]
at
com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68)
~[!/:?]
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
~[!/:?]
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)
~[!/:?]
at
com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:87)
~[!/:?]
at
com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:139)
~[!/:?]
at
com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:87)
~[!/:?]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
~[?:1.8.0_121]
at
javax.naming.directory.BasicAttributes.writeObject(BasicAttributes.java:293)
~[?:1.8.0_121]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
~[?:1.8.0_121]
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
~[?:1.8.0_121]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_121]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121]
at
com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:154)
~[!/:?]
... 73 more
Caused by: com.thoughtworks.xstream.io.StreamException:
at
com.thoughtworks.xstream.io.xml.StaxWriter.setValue(StaxWriter.java:160) ~[!/:?]
at
com.thoughtworks.xstream.io.WriterWrapper.setValue(WriterWrapper.java:45)
~[!/:?]
at
com.thoughtworks.xstream.converters.SingleValueConverterWrapper.marshal(SingleValueConverterWrapper.java:45)
~[!/:?]
at
com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:50)
~[!/:?]
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58)
~[!/:?]
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43)
~[!/:?]
at
com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:87)
~[!/:?]
at
com.thoughtworks.xstream.converters.reflection.SerializableConverter$1.writeToStream(SerializableConverter.java:139)
~[!/:?]
at
com.thoughtworks.xstream.core.util.CustomObjectOutputStream.writeObjectOverride(CustomObjectOutputStream.java:87)
~[!/:?]
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:344)
~[?:1.8.0_121]
at
javax.naming.directory.BasicAttribute.writeObject(BasicAttribute.java:507)
~[?:1.8.0_121]
at sun.reflect.GeneratedMethodAccessor124.invoke(Unknown Source) ~[?:?]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[?:1.8.0_121]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_121]
at
com.thoughtworks.xstream.core.util.SerializationMembers.callWriteObject(SerializationMembers.java:154)
~[!/:?]
at
com.thoughtworks.xstream.converters.reflection.SerializableConverter.doMarshal(SerializableConverter.java:257)
~[!/:?]
at
com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:90)
~[!/:?]
at
com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68)
~[!/:?]
at
com.thoughtworks.xstream.core.TreeMarshaller.convertAnother
Re: [discuss] find a better name for KameletBinding
"Binding" sounds good to me, too. On Fri, Aug 20, 2021 at 7:07 PM Claus Ibsen wrote: > Hi > > Yeah one of the hardest problem is naming, and after that renaming as > a lot of old stuff "expects" the old name. > > I am also leading to Binding, as we have other concepts in Camel K > that are neutral named (no Camel or product in the name) like > Integration, IntegrationKit. > And they are all in the same namespace, so there are no clash on > kubernetes. > > +1 for Binding > > > > On Fri, Aug 20, 2021 at 10:59 AM John Poth wrote: > > > > +1 for Binding > > > > Dropping the Kamelet part makes it clearer that you can bind more > > than just Kamelets. > > > > Keeping it as "Binding" gives Kubernetes users a pretty good idea of what > > it's going to do without reading the documentation. > > > > On Mon, Aug 16, 2021 at 2:04 PM Antonin Stefanutti > > wrote: > > > > > Hi Luca, all, > > > > > > +1 for Binding. > > > > > > Users in the Kubernetes ecosystem may already be familiar with the > term, > > > as it seems it's the choice made by projects like Knative and Service > > > Binding, > > > to convey the general concept of "integrating" in their respective > domain. > > > > > > I find projecting that concept into the integration domain to be a good > > > fit, which > > > Would materialises in Kubernetes as bindings.camel.apache.org< > > > http://bindings.camel.apache.org> resources. > > > > > > On 16 Aug 2021, at 10:27, Luca Burgazzoli > > lburgazz...@gmail.com>> wrote: > > > > > > Hello, > > > > > > When the KameletBinding concept was introduced in camel-k, if was > meant to > > > bind two Kamelets and nothing more, but over time we have added more > > > capabilities, like: > > > > > > - support for processing steps to transform exchanges/messages > > > - support to address/source from different systems so the source/sink > does > > > not need be a kamelet anymore > > > > > > So I think the term KameletBinding is not more appropriate and to > reduce > > > confusion, we should try to find a better name. > > > > > > On top of my mind, I'd see the following names as a possible > replacement: > > > - Binding so leave Kamelet out of the game as Kamelets are one of the > > > option but not the exclusive on > > > - Connector as in essence, a KameletBinding describe how to connect A > to B > > > > > > Any opinion ? > > > > > > --- > > > Luca Burgazzoli > > > > > > > > > > -- > Claus Ibsen > - > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Tadayoshi Sato
