Hi,
I have a Jetty endpoint that when recieving a message will perform the
processing asynchronously and syncronously return a correlationId so the
client can come back later to another endpoint to see how processsing is
going.
I found an example on the mailing list of how to pass the HttpSession
ServletRequest req =
exchange.getIn().getBody(HttpServletRequest.class);
Regards
Wayne
On Wed, Jan 20, 2010 at 9:02 AM, Wayne Keenan wrote:
> Hi,
>
> I have a Jetty endpoint that when recieving a message will perform the
> processing asynchronously and syncronously return a correlationId
t on the HTTP protocol.
Is that something someone would be able to give me an example of please? Is
there a built-in way to auto populate Camel message properties with HTTP
properties
Alternatively, sticking with HTTP aware bean,I just get null using:
println exchange.getProperty(Exchange.HTTP_QUERY
4:16 PM, Wayne Keenan wrote:
> Hi,
>
> Thanks for replying.
>
> On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang wrote:
>
>> Hi,
>>
>> Can you try to set the ID into the message header instead of the message
>> body ? I
; as the
> content-type ?
> If so , you should get the parameters from the message header.
>
>
> Willem
>
> Wayne Keenan wrote:
>
>> Hi,
>>
>> I believe I have found the trouble I am having. I think this bug still
>> exists in the 2.1.0 release:
&g
Hi Willem,
Thanks very much, I can confirm that with 2.2-SNAPSHOT I can obtain the URI
QUERY parameters from the camel header(s) when POSTing content-type of
application/octet-stream.
I did notice that a HTTP PUT doesn't populate the headers with the URI Query
parameter
Regards
Wayne
On Fri, Ja
On Tue, Jan 26, 2010 at 5:25 AM, kitplummer wrote:
>
> Ok, just thinking at this point...and I don't yet understand Camel well
> enough. So, I need some insight.
>
> What I want to do is use Camel to facilitate some back-end business logic
> in
> my Grails app. Here's the general idea. From my
On Mon, Jan 25, 2010 at 4:25 AM, Willem Jiang wrote:
> Hi Wayne,
>
> I'm not sure we need to populate the headers for the HTTP PUT method.
> Can you point me out if there any specification for it ?
>
> Willem
>
>
> I looked at the RFC's for http 1.0 and 1.1, to me it doesn't appear to
preclude us
On Tue, Feb 9, 2010 at 2:03 AM, Pete Mueller wrote:
>
> Hello all,
>
> I am currently working with the camel-jetty integration for hosting some
> web
> services. During my implementation, I've found a few "oddities" that I
> thought I would post here before opening actual bug reports. (NOTE: I a
Hi,
I have run into an issue where the HTTP response message is being truncated
to the exactly length of the incoming CXF request, i.e.
response.contentLength seems to be being set to the request.contentLength,
I have the following setup:
1. I am advertising a WSDL file via a CXF endpoint.
Deleting the content length header as the last action is a workaround.
Should I raise thus as an issue?
Regards
Wayne
On 1 Mar 2010, at 19:22, Wayne Keenan wrote:
Hi,
I have run into an issue where the HTTP response message is being
truncated to the exactly length of the incoming CXF
On Tue, Mar 2, 2010 at 3:35 AM, Willem Jiang wrote:
> Hi
> Can you check out the latest released Camel 2.2.0 ?
>
working on camel 2.2.0, CXF 2.2.6 on Mac10.6
Thanks,
Wayne
Hi,
I have backend SCA components that is implemented in Java and the WSDL is
automatically generated by the Apache Tuscany SCA container.
I would like to be able to front access to my backend services using Camel.
For this to function I would like to know it its possible to configure a
(the CX
I'm afraid you still need to let camel-cxf know about the WSDL or
> generate the artifact with WSDL.
> Otherwise, you can leverage the camel-jetty and camel-http component to
> route the request to backend system.
>
> Willem
>
>
>
> Wayne Keenan wrote:
>
>>
Axis2 I already feel like I'm up against it...
Regards
Wayne
On Fri, Mar 12, 2010 at 2:16 PM, Wayne Keenan wrote:
> Hi,
>
> I tried the jetty/http combo but dont like the fact the WSDL service URL to
> the SCA component 'leaked' straight thru verbatim.
>
> The rea
Hi,
You might want to look at springs classpath*: mechanism.
I am using it to pull in in all the spring xml files that match a particular
pattern fo my app; some spring files may have their own camelContext, so
although you dont have a single camelContext you do get discrete config
files. This
16 matches
Mail list logo
