I checked the code and the change log, camel-http component supports
https protocol after Camel 1.5.0.
So you'd better upgrade the camel version, or ask commercial support as
Claus suggested.
Willem
bwhite wrote:
I found only one reference to "https" in the camel-http 1.4.0 codebase.
getPort
I found only one reference to "https" in the camel-http 1.4.0 codebase.
getPort() returns 443 when the protocol is "https", otherwise returns 80.
I don't know where else there might be SSL related code in the entire camel
codebase, but this alone makes me think that https is not completely workin
Hi Christian,
This bundle will help camel-core to find the converters, components,
resolver language in OSGi platform. So please install it before you
start the camel context.
Cheers,
Willem
Schneider Christian wrote:
Not yet. Will this bundle register the converters?
Greetings
Christia
On Thu, Nov 12, 2009 at 5:45 PM, DRy wrote:
>
> Hi,
>
>
> Claus Ibsen-2 wrote:
>>
>> But try it out and see how goes :)
>> Otherwise check back tomorrow and see if the jar/zip is newer.
>>
>
> Checked! Works fine!
>
> I tested it with that build from 11. Nov 17:xx:xx! If I throw a
> UnmarshalExcep
Hi,
Claus Ibsen-2 wrote:
>
> But try it out and see how goes :)
> Otherwise check back tomorrow and see if the jar/zip is newer.
>
Checked! Works fine!
I tested it with that build from 11. Nov 17:xx:xx! If I throw a
UnmarshalException with a nested XMLException (from XMLBeans). The
onExcepti
Not yet. Will this bundle register the converters?
Greetings
Christian
Christian Schneider
Team Handel und Risikomanagement
Informationsverarbeitung Business Solutions Trading
EnBW Systeme Infrastruktur Support GmbH
Informationsverarbeitung
Business Solutions
Handel und Dispatching
Durlacher
Hi Christian,
Did you install the camel-osgi bundle?
Willem
Schneider Christian wrote:
Now my service call works but when receiving the response I get a new
exception (see below)
"InvalidPayloadException: No body available of type: java.io.InputStream but
has value: [...@2e86f5 of type: byte
Now my service call works but when receiving the response I get a new
exception (see below)
"InvalidPayloadException: No body available of type: java.io.InputStream but
has value: [...@2e86f5 of type: byte[]"
as I also get the warning "java.io.FileNotFoundException:
\org\apache\camel\converter" I
I think I have found the reason. I had to define my own cxf
CamelTransportFactory that references my camelcontext.
This log entry brought me to the right solution:
12.11.2009 15:44:48 org.apache.camel.component.cxf.transport.CamelConduit
getCamelContext
INFO: No CamelContext injected, create a def
I currently try to port a Swing GUI to Eclipse RCP. In the old GUI we
already use a CXF service over the camel jms transport.
In Swing the service call works without any problems.
In the new Eclipse RCP GUI we use the same applicationContext that worked in
the Swing case. We use the cxf and camel
Hi
I guess the problem is that you use bean parameter binding and that
you use a List type in your bean.
And that the quickfix message cannot be coverted to a java.util.List.
Otherwise create an small unit test in camel-quickfix that
demonstrates this and mark it with @Ignore.
Then I can take a l
Hi
I have created a ticket
https://issues.apache.org/activemq/browse/CAMEL-2163
To add a option on the endpoint so its easier to do in Spring XML also.
On Mon, Nov 9, 2009 at 7:48 PM, Claus Ibsen wrote:
> On Mon, Nov 9, 2009 at 10:26 AM, marcin80 wrote:
>>
>> Hi,
>>
>> Thanks for your help. I
On Wed, Nov 11, 2009 at 7:28 PM, bwhite wrote:
>
> Hi Claus,
>
> Yes, this is my first attempt at getting camel-http working with https. Can
> you verify if this should work in Camel 1.4.0? Thanks!
Sorry you can check the source code yourself.
https://svn.apache.org/repos/asf/camel/tags/camel-1.4
13 matches
Mail list logo
