Sunita
-Original Message-
From: Aki Yoshida [mailto:elak...@gmail.com]
Sent: Thursday, June 06, 2013 9:58 AM
To: users@camel.apache.org
Subject: Re: Camel 2.9.2, CXF 2.6.2 - How should the response look for CXF
producer using Payload dataformat
Actually, the payload check
your usage of requestBodyAndHeader doesn't look right.
inputProducerTemplate.requestBodyAndHeader(cxf:bean:CustomersServiceConsumerEndpoint,
body, mapHeaders);
the first argument is supposed to be the body value, see
/**
* Sends the body to the default endpoint and returns the result
Hi Bengt,
the quoted code itself is needed for the normal case to ensure the stepwise
operation moves the path upwards from the current directory to where it
started without touching its upper directory which you potentially have no
authorization to access.
but the code does not handle the case
Hi,
I created CAMEL-6393 to describe the change proposed.
regards, aki
2013/5/17 Aki Yoshida elak...@gmail.com
Hi Claus,
so the http component assumes always a list of string as its header value?
camel-cxf seems to currently always assume a string entry (there is a
casting code like
I think there is currently no way in camel to set the parser features for
the validator. And also for other xml parsers factories.
If that is the case, we should add a mechanism to set these properties.
Maybe some system properties or/and component properties to overwrite the
default values.
any
=HEAD
We could consider having such a method in camel-core in a
MessageHelper util class or something.
On Wed, May 8, 2013 at 12:45 AM, Aki Yoshida elak...@gmail.com wrote:
We have a header entry that has multiple entries that are in the response
HTTP message. These multiple entries
If you want to have the soap header part processed by CXF and let the
payload (i.e,, the soap body content) generically to be propagated to the
camel route, you should configure the cxf endpoint using the jaxws generic
provider mode (i.e, use PAYLOAD mode with no wsdl nor serviceClass given).
I
We have a header entry that has multiple entries that are in the response
HTTP message. These multiple entries are available in CXF, as each header
value is represented as a list. However, when this message is propagated
back to camel, only the first entry of this list is read into the camel
This is a CXF topic and actually doesn't belong here.
That ID value of the CXF logging interceptor is incremented not per route
but for all the CXF configurations so that each logged message gets a
unique ID.
So this is what it should be.
I don't know your purpose of getting this message count
. If you want to read it twice, you
need to call the reset method. In camel we have an intercepter which will
call the reset method before routing the exchange to the other endpoint if
you enable the stream cache feature.
发自我的 iPhone
在 2013-2-2，上午5:49，Aki Yoshida elak...@gmail.com 写道：
Hi
Hi,
When using Camel's CachedOutputStream, I thought I could get the
StreamCache over its getStreamCache() or the InputStream over its
getInputStream() multiple times and read the cached data independently
from them. But by looking at the implementation, this seems to be not
the case.
Am I
There is a known bug ( reported in CAMEL-5989) introduced 2.10.2 for
sftp using the stepwise directory traversal that results in a similar
error. But yours is for ftp and it is happening independent of the
stepwise property setting, it seems to be different. Could you
describe which variations you
Hi Lars,
So the camel endpoint you have at the end of the route is a cxf
endpoint, as you talk about a SOAP fault from the end of the route?
In a request-response scenario, you will get the SOAP fault
transferred back to the other end of the route and this is typically
returned as an HTTP 500
Does your wsdl define a response message?
If it doesn't, it is normal that you get an empty response. In that
case, you see an empty HTTP 202 response with the current CXF but with
older CXF versions, you will see an HTTP 200.
2012/12/14 brxv a...@almacivor.net:
Hello.
I'm just startig out with
Isn't it your intention that you receive a soap message at the cxf
endpoint and forward the message payload to your greetProcessor bean
to process it?
If you want to just call the service itself, you could have used just
a CXF jaxws endpoint using this service impl class.
Maybe you can explain
The behavior differs depending on the configuration. I'll try to give
a short overview.
If you have a request-response type service, the exception is normally
transferred to the caller. In that case, the corresponding soap fault
is returned to the caller and the http code is 500 for such general
yes in that case, you need to deploy the url-classpath handler one.
Since you have already the url-mvn handler already deployed, you can just invoke
install mvn:org.ops4j.pax.url/pax-url-classpath/1.3.5
(I used version 1.3.5 as an example, but you can use the same version
as your other pax's
I suppose the call is failing because you are not setting some
required properties (e.g., the http method) to fake the soap call.
camel:setHeader headerName=CamelHttpMethod
camel:constantPOST/camel:constant
/camel:setHeader
camel:setHeader headerName=Content-Type
are you using blueprint?
in that case, you need the pax-url-classpath bundle.
org.ops4j.pax.url/pax-url-classpath
regards, aki
2012/12/3 ucrkarthik ucrkart...@hotmail.com:
Hi Williem,
I have the following code cxf-endpoint defined and I get the same error.
cxf:cxfEndpoint
I think there is an issue in JettyHttpProducer.
public boolean process(Exchange exchange, final AsyncCallback callback) {
JettyContentExchange httpExchange = null;
try {
httpExchange = createHttpExchange(exchange, callback);
doSendExchange(client,
/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
On Monday, September 17, 2012 at 5:55 PM, Aki Yoshida wrote:
I think there is an issue in JettyHttpProducer.
public boolean process(Exchange exchange, final
Hi,
I stumbled on this issue as I was trying to build camel without
network connection.
The test file (mapping.xml) included in camel-beanio is using
namespace http://www.beanio.org/2011/01 with its schema location at
http://www.beanio.org/2011/01/mapping.xsd
The version of beanio that is
Hi,
thanks for the quick answer.
logged in CAMEL-5562.
regards, aki
2012/9/4 Claus Ibsen claus.ib...@gmail.com:
Hi
Yeah the schema should be updated IMHO. Fell free to log a JIRA with a patch.
On Tue, Sep 4, 2012 at 12:38 PM, Aki Yoshida elak...@gmail.com wrote:
Hi,
I stumbled
you need to encode the questionmark by replacing it with %3F.
2012/8/30 Hilde hilde.sch...@yahoo.de:
Hello folks!
We are using the ftp component and build up the ftp endpoint uri
dynamically. Occasionally the password consists of a questionmark but that
causes the uri to be invalid:
isn't that the wrong password string? i thought your password is pR
F3Snb}? and not pR+F3Snb}?.
with that in mind, I could use this password and its corresponding
encoded text pR+F3Snb%7D%3F with camel trunk successfully.
regards, aki
2012/8/30 Hilde hilde.sch...@yahoo.de:
Hello and thanks
Hi Yogesh,
could it be that your web service call is a oneway operation? If that
is the case, you should set the synchronous property to true
(...synchronous=true) for the camel-cxf endpoint to get the
transmission error. See http://camel.apache.org/cxf.html for more
info. Can you try setting
Hi Andi,
There have been some changes in the wiring between the camel-cxf
endpoints and cxf buses recently. Therefore, there may be some
combination of the cxf and camel versions that could lead to some
issues depending on how they are wired.
That's why I was asking for the camel version and if
Hi Yogesh,
This property will affect the invocation behavior at the camel-cxf
boundary. In other words, in this case, the call occurs synchronously
across this boundary.
That could be considered inefficient in some scenarios (e.g., if you
are not interested in any errors and you want to just
Hi Andi,
I think you always saw at the endpoint only the interceptors that are
configured at the endpoint. But you saw both interceptors when the
interceptor chain is built. Are you not seeing both interceptors when
the interceptor chain is invoked?
If you have this problem, can you tell us which
Hi,
There are some tools that let you convert an rpc-styled WSDL to its
somewhat equivalent doc-style WSDL.
Once you have such a doc-styled WSDL, you can use it with CXF. Axis
typically doesn't complain when a doc styled looking message (i.e., no
xsi inline types, no soap encoding, etc) is sent to
Hi,
but I think the test should be written in a way not to depend on how
you are retrieving the file, no?
If you use cygnwin's svn, you will get dummy.txt with the unix
line-ending, LF, as in the original source.
In this case, the test wil fail on windows.
So, what this test is testing is if you
I would like to understand the CxfPayload instantiation for the CXF to
Camel direction and the purpose of
org.apache.camel.component.cxf.interceptors.RemoveClassTypeInterceptor
that gets inserted into the CXF interceptor chain by Camel under the
payload mode. I think there is potentially some case
in the endpoint URL.
If no one says otherwise, I can create a jira ticket and attach this
change and the suggested patch in CxfDefaultBinding to fix this issue.
Regards, Aki
2011/4/29 Aki Yoshida elak...@googlemail.com:
I would like to understand the CxfPayload instantiation for the CXF to
Camel
to give us some time for testing this
new feature.
Willem
On 3/11/11 10:23 PM, William Tam wrote:
Thanks Aki. I'll take a closer look at the problem and commit it as
appropriate over the weekend.
On 03/11/2011 04:09 AM, Aki Yoshida wrote:
Hi William,
Yes. I initialy tried out that approach
cxf:properties
entry key=dataFormat value=PAYLOAD/
/cxf:properties
/cxf:cxfEndpoint
Also, could you elaborate on the purpose of addInvokeOperation()?
Thanks,
William
On 03/10/2011 01:19 PM, Aki Yoshida wrote:
Hi,
I added the CXF dispatch mode to the Camel CXF endpoint so that I can
ran
Hi,
I added the CXF dispatch mode to the Camel CXF endpoint so that I can
ran SOAP intermediary/gateway scenarios over a single CXF endpoint
with some CXF features enabled.
I attached the patch file and unit test files to CAMEL-3778.
In short, you can configure your endpoint like
Hi Willem,
I just saw you already patched the current 2.7-SNAPSHOT to fix this problem.
I just tried it and now it's working fine. I hope Scott's scenario is
also working fine with this version.
Thanks.
regards, aki
Hi Scott,
Have you checked if your payload XML matches the XML structure defined
by your cxf bean endpoint? I noticed the same problem sometime ago and
thought that this was happening when I had a wrong XML payload
document. I was using SAAJ to extract the SOAP body child at one of my
interceptors
possible).
Regards,
Aki
On 02/16/2011 06:35 AM, Aki Yoshida wrote:
Hi William,
I want to use this CXF endpoint just as a normal typed CXF endpoint
and I expect to have arbitrary generic CXF interceptors to be placed
just as for the normal case. So, I don't think Camel DSL or processor
Hi,
If you are writing a CXF client, you can write a client using the
CXF's dispatch API to send an arbitrary payload to some target
service.
I would like to configure a camel cxf endpoint that does the same
thing. However, the code seems to require either the WSDL or the
service class.
When I do
to the
limitation you observed.
Regards,
William
On 02/15/2011 07:49 AM, Aki Yoshida wrote:
Hi,
If you are writing a CXF client, you can write a client using the
CXF's dispatch API to send an arbitrary payload to some target
service.
I would like to configure a camel cxf endpoint that does
Hi,
I am trying to pass the Camel headers to the CXF component, but
somehow I am having trouble. For example, when I use the following
configuration:
camel:from uri=file:.../
camel:setHeader headerName=myheader
camel:constantmyvalue/camel:constant
/camel:setHeader
described, and created a JIRA[1] for it.
[1] https://issues.apache.org/jira/browse/CAMEL-3426
On 12/13/10 11:16 PM, Aki Yoshida wrote:
Hi,
I have a simple scenario using the file endpoint that polls a file and
sends it to a oneway CXF endpoint that calls an external web service.
The scenario
Hi Willem,
I verified that it's working fine with 2.6-SNAPSHOT as well.
thanks,
aki
On Wed, Dec 15, 2010 at 7:25 PM, Aki Yoshida sapa...@googlemail.com wrote:
Hi Willem,
Thank you for the quick fix. My complete trunk sync/build is taking
time. So I just applied the same change to my local
Hi,
I have a simple scenario using the file endpoint that polls a file and
sends it to a oneway CXF endpoint that calls an external web service.
The scenario works fine with Camel 2.4.0 with CXF 2.2.11, but does not
work with Camel 2.5.0.
The processing itself works fine with 2.5.0, but after the
101 - 145 of 145 matches
Mail list logo
