Hi Jim,
I also am just another plain Camel user.
OSGi and multiple contexts: This is obviously a prime motivation. We
need to view and observe the details of multiple Camel Contexts
contributed by multiple bundles. The spring extender binds
ApplicationContext objects as OSGi services - we want to
Your activator should be getting called - this has nothing to do with
camel. Is the bundle state showing as STARTED ? Is the
Bundle-Activator header in the MANIFEST.MF correct ? (stupid questions
I know but sometimes these can hang you up)
Hi,
At a first glance (please correct me if I am wrong), the camel web
console implementation appears to be very heavy - depending on Scala,
scala template engines and several Jersey libraries which have a
non-Apache licenses. It also appears to be unsuited to running on an
OSGi environment where
Why not make your job easier by using the Spring extender and wrap
this camel-context.xml in a separate bundle of its own which can be
hot-deployed ?
Most providers reserve message properties starting with JMSX and JMS
for internal use and many drivers check such properties against the
standard set supported by the vendor. Technically the JMS spec only
says that 'JMSX' properties are reserved, but most providers reserve
all the 'JMS' properties
Actually this could have been simply solved if camel core and all
camel components delegated their threading needs to a
java.util.concurrent.ThreadFactory. Then one could have centralized
thread management. Unfortunately even if Camel is well behaved many of
its components are not and even associat
It seems that defining a OSGi managed service factory for producing
configurable bean instances could solve your problem ?
Hi,
It seems that all you want is buffering of messages and not true
logical aggregates right ? In which case you should simply configure
ActiveMQ appropriately to enable async sending (if you aren't using
transactions) and set an appropriate prefetch when consuming messages.
You can also see whet
> The error is in attempting to set that value but I am unclear why it should
> be.
Well..I can explain the reason if not how to solve this problem
specifically for the camel jms component. I probably will run into
your problem in the future since we have need to post and reply using
native messag
Hi,
Why would any commercial environment still use Java 5 for current
development considering it has passed its end of service life (with
all the associated legal ramifications) ?
-Tarun
Do you have a wsdlUrl resolvable without contacting the CXF server ?
> My cxf endpoint configuration is not wrong.
> when my order is : start cxf server --> start camel server , it is normal.
>
> but I want : start camel server --> start cxf server , it is throws
> FailedToCreateProducerExceptio
A little unclear on what you expect here. The CamelContext does not
start because of an invalid endpoint. The only way to make it start
AFAIK would be to remove this invalid endpoint. I assume you are using
Spring. If you have control over when the spring application context
is constructed, you ca
Hi,
Wouldn't setting and customizing an error handler on the route that delivers
to the CXF endpoint do this for you ?
Best Regards,
Tarun
On Tue, Mar 8, 2011 at 3:08 PM, Bill wrote:
> Hi,
> My camel contains some routes, and one route to a cxf endpoint.
> If the cxf endpoint is not start whe
21, 2011 at 2:44 PM, Tarun Ramakrishna wrote:
>> Hi all,
>>
>> I have multiple error handlers defined in XML (using )
>> who wish to reuse the same . It appears that
>> doesn't support the 'id' attribute so I can't 'ref'
>> it. Is th
Hi all,
I have multiple error handlers defined in XML (using )
who wish to reuse the same . It appears that
doesn't support the 'id' attribute so I can't 'ref'
it. Is there a way to achieve this?
Thanks & Regards,
Tarun
Just please ignore the mail below and save me the embarassment. This will
teach me not to send emails at 3:00am in the morning.
Thanks,
Tarun
On Thu, Dec 9, 2010 at 3:07 AM, Tarun Ramakrishna wrote:
> Hi all,
>
> I have a puzzler and I thought I would throw it to the list before
>
Hi all,
I have a puzzler and I thought I would throw it to the list before
going into camel debugging.
I have a custom mapping processor that given an Exchange, takes its
payload, split it to several payloads, creates an array list of byte[]
and sets them back into the IN message of the exchange.
Hi Claus, Willem,
Thanks for your answers! I had thought the Registry might be bound as
an oSGI service somewhere too..but missed the fact that one can use
any bound CamelContext and call getRegistry() on the same.
Thanks!
Tarun
Hi all,
How does one access the Camel registry in an oSGI environment ? (i.e.
instance of org.apache.camel.spi.Registry that holds all the component
registrations made by bundles, etc).
Also what is the purpose of the 'camel-osgi' jar ? It doesn't seem to
be necessary since there is an extender in
19 matches
Mail list logo
