Appreciated Sergey.
You confirmed what I thought, the throwExceptionOnFailure option is not
being processed by the cxfrs component. I'll raise a jira for this, and
also that the default should be false.
Could someone chime in, and let me know if using cxfrs is the wrong
strategic direction
Hi Vivek:
You can't use the Jackrabbit application URL in the from() DSL method.
You must register your repository with the Camel registry (using a
registry implementation such as JndiContext or Spring's
ApplicationContextRegistry, see
http://camel.apache.org/registry.html).
I would suggest takin
Hi
Can you please open a JIRA to get throwExceptionOnFailure=false
affecting the client ?
I can do it too, we can get it supported in CXFRS
Typically, a JAX-RS client dealing with JAX-RS Response should not get
the exceptions propagated but I guess it is defaulted to right now in
the CXFRS c
Thanks Sergey - was looking to use jaxrs/cxf. Therefore thought cxfrs.
Any ideas about the throwExceptionOnFailure option for cxfrs, has anyone
being able to get it to work?
On 02/06/14 20:55, Sergey Beryozkin wrote:
Hi
camel jetty, http and restlet and possibly other components can be
used
Hi
camel jetty, http and restlet and possibly other components can be used too
Sergey
On 02/06/14 20:00, techbird wrote:
Hi, two questions if I may.
(1) If I want to invoke REST services, is the cxfrs the preferred
component to use?
(2) Using cxfrs I cannot get throwExceptionOnFailure option t
Hi, two questions if I may.
(1) If I want to invoke REST services, is the cxfrs the preferred
component to use?
(2) Using cxfrs I cannot get throwExceptionOnFailure option to work. I
would like to be able to process errors (>400) in the route, rather than
complicating the code with exceptio
Hi,
I'm trying to retrieve the files. I need to write a batch which just
retrieves the files at regular intervals.
I'm trying something like this.
from
("jcr://admin:admin@localhost:8080/jackrabbit-webapp-2.6.0/repository/default/b?recursive=true&noop=true").to("file:\\tmp\\out");
I'm getting
Any inputs please?
-Thanks
On Monday, June 2, 2014, Happy User wrote:
> I wonder if anyone could help me with this.
>
> 1. Setting Xpath value in a property in route 1
> 2. Setting a body and placing in Topic in route 1
> 3. Reading the value from Topic in route 2
> 4. Am trying to print the pr
No, it cannot be related to missing permissions on FTP server side. As I
mentioned in my previous post the very same route with the very same FTP
destination (and fileExist=Append command) worked perfectly fine with Apache
Servicemix 3.3.2. I am only getting the exception with Apache Servicemix
5.0
Hi guys,
I'm using camel 2.13 with the ElasticSearch component
(camel-elasticsearch-2.13).
I specify the endpoint as such:
*elasticsearch://clusterName?operation=INDEX&indexName=indexname&indexType=doctype&ip=127.0.0.1*
I would have assumed that by specifying the IP address of the ES instance
t
We are running Apache Camel inside a Redhat EAP/JBoss AS7 using CDI to setup
the context - from http://camel.apache.org/cdi.html.
This works fine, but since we use EJB's and MDB's as well, we need
transactional routes.
Looking at http://camel.apache.org/transactional-client.html, this seems to
I wonder if anyone could help me with this.
1. Setting Xpath value in a property in route 1
2. Setting a body and placing in Topic in route 1
3. Reading the value from Topic in route 2
4. Am trying to print the property set in Step 1 but am getting null
5. Calling another route 3 from route 2
6. P
Probably permissions on the ftp server don't allow you to write to the file
once it's first uploaded. I guess you wouldn't be allowed to delete it over
ftp either.
2. Juni 2014 14:11 skrev "simonglaubitz" følgende:
> Short addition to my original post:
>
> when changing the destination of my rout
Yes, that was it. Thanks a lot.
Max.
On Mon, Jun 2, 2014 at 6:58 AM, Claus Ibsen wrote:
> Hi
>
> Not sure if you need to set repeat=true ?
>
> On Mon, Jun 2, 2014 at 12:16 PM, Max Bridgewater
> wrote:
> > Hi,
> >
> > My route is as follows:
> >
> >
> >
> >
> >
Short addition to my original post:
when changing the destination of my route from FTP to FILE component
fileExist=Append works perfectly fine.
FTP:
ftp://testuser@testserver/test?password=testpassword&fileName=test.txt&fileExist=Append
FILE:
file:C:/test?fileName=test.txt&fileExist=Append
FtpReplyString=550 Permission denied
, CamelRedelivered=false, CamelRedeliveryCounter=0, JMS_IBM_Format=MQSTR ,
JMS_IBM_MQMD_CodedCharSetId=1208, JMS_IBM_MQMD_Encoding=546,
JMS_IBM_MsgType=8, JMS_IBM_PutApplType=28, JMS_IBM_PutDate=20140602,
JMS_IBM_PutTime=11034472, JMSCorrelationID=null, JMSDeliveryMode=1,
Hi
Not sure if you need to set repeat=true ?
On Mon, Jun 2, 2014 at 12:16 PM, Max Bridgewater
wrote:
> Hi,
>
> My route is as follows:
>
>
>
>
>
>
> I am using Zookeeper 3.4.6 with Camel 2.13. This route picks up only the
> first message after starting th
Hi,
My route is as follows:
I am using Zookeeper 3.4.6 with Camel 2.13. This route picks up only the
first message after starting the route. Is this the intended behavior?
After that message, it goes completely silent.
The zookeeper dependency is indeed
You should implement this interface as mentioned in the release note :
"The Mail component no longer uses Spring API, which means any custom
JavaMailSender should now implement
org.apache.camel.component.mail.JavaMailSender instead."
On Mon, Jun 2, 2014 at 11:45 AM, Claus Ibsen wrote:
> Hi
>
>
Hi
See the release notes for each of the Camel releases you upgrade
For example you can then find what you look for here
http://camel.apache.org/camel-290-release.html
On Mon, Jun 2, 2014 at 11:40 AM, OrackBahama wrote:
> Hello,
>
> configuring a custom javaMailSender in Camel java DSL seems to
Hello,
configuring a custom javaMailSender in Camel java DSL seems to not work
anymore (Camel 2.13.0).
...
.to(
"smtp://{{mail.host}}?username=xxx&password=yyy&javaMailSender=#javaMailSender"
)
...
with
throws ugly exceptions at me :-(, saying something about "Could not find a
suitable
On Mon, Jun 2, 2014 at 11:04 AM, Rajiv wrote:
> I have vendor provided product which is running over Weblogic, its an EJB.
> Vendor has also provided the Client API to communicate with the EJB and send
> various request to interact with EJB.
>
> Client API is packaged in jar.
>
> TO communicate we
I have vendor provided product which is running over Weblogic, its an EJB.
Vendor has also provided the Client API to communicate with the EJB and send
various request to interact with EJB.
Client API is packaged in jar.
TO communicate we need to first get the factory using the client API. th
23 matches
Mail list logo
