Hi,
The camel-http or camel-http4 does not yet support Oauth or Oauth2
authentication. So, for the moment, I would like to suggest that you code
yourself the client requesting the token with by example the Apache OLTU
client (
Can you show us how did you do the aggregation? Just some code snippet is OK.
BTW, you can always using write the stream into to file to avoid load the whole
message into memory.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
suspend is not like shutdown, it just suspend the route services and you can
resume the route services without spend lots of time.
If it takes a long time to suspend the camel context, maybe there are some
inflight messages which are not processed. Maybe you can go through the log for
more
If you cannot get the result form commons exec, we cannot do anything in camel
:(
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On October 13, 2014 at 6:50:33
Hi Gonzalo,
The xml-security dataformat of Camel uses behind the scene the Apache
Santuario project (= http://santuario.apache.org/) which support different
XMLCipher (
http://santuario.apache.org/Java/api/org/apache/xml/security/encryption/XMLCipher.html)
but unfortunately not XADES-BES.
We
I just found the code.
class JsonBodyAppender {
def append(existing: String, next: String) = existing + \n + next
}
There are too many String there, maybe you can just append the message into a
file.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog:
Thanks for the reply. I also came to that conclusion eventually. However,
could you explain to me more how I'd store each batch in a file?
It is my understanding so far that the Aggregator is called whenever the
input emits a new exchange. If I were to store the messages in a file,
how'd I know
Hi,
You should also set messageFactory accordingly.
--
View this message in context:
http://camel.465427.n5.nabble.com/Calling-Soap-1-1-Service-from-Camel-cxf-via-Java-DSL-tp5757538p5757539.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Your end point URL should be appended with messageFactory
eg:
.doTry()
.to(cxf:// + CxfUrl + ? + wsdlURL= + WsdlUrl+ + serviceName= +
ServiceName + + portName= + interpolPortName + +
headerFilterStrategy + =# + propagateAllHeaderMessages + +
dataFormat= + interpolDataFormat + +
Ok, that means that I'll have to code my own endpoint then, am I right?
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
Hi Gonzola,
What I suggest is that you develop a new dataFormat (= class with 2
methods) for the apache Camel project if you agree as described here (
http://camel.apache.org/custom-dataformat.html) with the API supporting the
XADES-BES. The dataformat could be integrated directly with the
Hi Charles,
Sounds good, I'm actually already using the base64 dataformat, so using a new
one wouldn't be complex. Although I'll first have to test the implementation
using de xades4j API.
Thanks.
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de
Excellent news. Could you please raise a ticket here to keep track of your
development https://issues.apache.org/jira/browse/CAMEL ?
On Tue, Oct 14, 2014 at 2:33 PM, Gonzalo Vasquez gvasq...@altiuz.cl wrote:
Hi Charles,
Sounds good, I'm actually already using the base64 dataformat, so using a
We could perhaps integrate your work with the existing xml-security
data-format - http://camel.apache.org/xmlsecurity-dataformat.html instead
of developing a new one.
If we add a new value for this property (xmlCipherAlgorithm = XADES-BES) we
could use the other API instead of Apache Santuario. We
OK, I'll try both approaches and as soon as I have something to show I'll let
you know.
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
You can just store the file into the message body, just as you did with the
String objects.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On October 14, 2014 at
Which API do you use ? For your information, we couldn't use xades4j with
Apache Camel as the license model used which is GPLv3 is not compatible
with Apache License 2 -
http://www.apache.org/licenses/GPL-compatibility.html.
I have created a ticket for the Apache Santuario project :
Oops, what about the MITyCLibXADES API ?
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
http://www.altiuzreports.com
El
The code developed by the Spanish government is EUPL v 1.1 and should be
supported by Apache (
https://joinup.ec.europa.eu/software/page/eupl/eupl-compatible-open-source-licences
).
On Tue, Oct 14, 2014 at 3:05 PM, Gonzalo Vasquez gvasq...@altiuz.cl wrote:
Oops, what about the MITyCLibXADES API
The route endpoint was
xslt:classpath:xslt/orch-encryptionkey-flowRemoveNamespace.xsl. You may have
been asking for the actual XSLT which I included but it looks like it got
pruned by the listserver. I will include it here xml encoded:
lt;xsl:stylesheet version=quot;1.0quot;
I am using Camel CronScheduledRoutePolicy to keep my route active between
certain hours.
CronScheduledRoutePolicy policy = new CronScheduledRoutePolicy();
policy.setRouteStartTime(0 0 9 * * ?);
policy.setRouteStopTime(0 0 18 * * ?);
from(jms:inboundqueue).routePolicy(policy).noAutoStartup()
---
Thanks, I did that eventually... although it did not solve the issue. Turns
out that camel-aws forcibly converts the Exchange body to an InputStream.
Camel's File-InputStream converter buffers the InputStream so things still
fail.
I've attached a patch that fixes this by having the AWS SDK handle
On 14/10/14 15:26, camelcoder07 wrote:
Thanks for the reply. Is it possible to do what I am doing above using cxf
and oauth since the web service I am posting to is a REST web service?
CXF ships OAuthClientUtils which might help; it is all quite
boilerplate, most of the client-side OAuth2
Would please answer the following questions. I also have
http://camel.apache.org/camel-23-threadpool-configuration.html doc but i am
clear how the thread pool works.
1) What is default thread pool and component level thread pool?
2) When i created a component such as http4, does it uses the
thx for the reply. incase if suspend() is not able to suspend a given route,
will it kill that route after a specific period of time and continue with
suspending the rest of the routes. I don't see any timeout parameter in the
suspend method to configure the timeout period as well. Please
Hi Andrew!
Did you checked http://camel.apache.org/smpp.html?
You can use it e.g. like:
smpp://smppclient@localhost:2775?password=passwordsessionStateListener=myS
essionStateListener
Where mySessionStateListener is the bean name in the registry.
Best,
Christian
On Wed, Oct 8, 2014 at 7:21
Hello Sam!
I don't have so much experience with XSLT, but maybe my suggestions are
nevertheless helpful:
- if possible, use the Saxon transformer factory as described here [1]. The
JDK build in is slow, buggy, ...
- if possible, use the Saxon XPath factory as described here [2]. It's much
faster
Hi Andreas,
Don’t worry,Please fill a JIRA and submit your patch.
I will take a look at it today.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On October 14,
28 matches
Mail list logo
