Yes, from Camel 2.4, you don't need camel-osgi bundle or
camel-spring-osgi bundle anymore.
BTW, Camel 2.4 is using Spring 3.x by default and I did some JMX test on
the Camel 2.5 snapshot with Spring 3.x, they look good.
Willem
Christian Schneider wrote:
Hi Edwin,
I think the camel-spring component now should work in osgi. So the
camel-osgi is not necessary anymore.
I have not tested this myself though.
In older versions of camel it was extremly important to use the
OsgiDefaultCamelContext if you configure camel outside of spring you
should try this.
Greetings
Christian
Am 17.08.2010 23:04, schrieb Park, Edwin:
Hi,
I have not been able to get certain Camel features working when in an
OSGi environment:
* I cannot get any TypeConverters to be recognized, even though I have a
META-INF/services/org/apache/camel/TypeConverter file with an entry for
the package containing my annotated type converter class.
* I cannot get the JMX lifecycle strategy to work. I constantly get the
below error, even though the spring-context bundle is present and loaded
in the OSGi container and even explicitly set as a bundle dependency in
my plugin manifest.
Aug 17, 2010 11:15:39 AM org.apache.camel.impl.DefaultCamelContext
createManagementStrategy
WARNING: Could not find needed classes for JMX lifecycle strategy.
Needed class is in spring-context.jar using Spring 2.5 or newer
(spring-jmx.jar using Spring 2.0.x). NoClassDefFoundError:
org/springframework/jmx/export/metadata/JmxAttributeSource
Aug 17, 2010 11:15:39 AM org.apache.camel.impl.DefaultCamelContext
createManagementStrategy
WARNING: Cannot use JMX. Fallback to using DefaultManagementStrategy
(non JMX).
I am using Camel 2.4.0 and Equinox.
I noticed a camel-core-osgi jar in the central maven repo, but
ironically this jar is not a bundle (does not have a proper OSGi
MANIFEST.MF) and is also not distributed with the downloadable Camel zip
on the Apache Camel site.
Are others able to load annotated TypeConverters or the JMX lifecycle
strategy in OSGi? If so can you please share how you were able to do it?
Thanks,
Edwin
________________________________________
This E-Mail (including any attachments) may contain privileged or
confidential information. It is intended only for the addressee(s)
indicated above.
The sender does not waive any of its rights, privileges or other
protections respecting this information.
Any distribution, copying or other use of this E-Mail or the
information it contains, by other than an intended recipient, is not
sanctioned and is prohibited.
If you received this E-Mail in error, please delete it and advise the
sender (by return E-Mail or otherwise) immediately.
This E-Mail (including any attachments) has been scanned for viruses.
It is believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened.
However, it is the responsibility of the recipient to ensure that it
is virus free.
The sender accepts no responsibility for any loss or damage arising in
any way from its use.
E-Mail received by or sent from RBC Capital Markets is subject to
review by Supervisory personnel.
Such communications are retained and may be produced to regulatory
authorities or others with legal rights to the information.
IRS CIRCULAR 230 NOTICE: TO COMPLY WITH U.S. TREASURY REGULATIONS, WE
ADVISE YOU THAT ANY U.S. FEDERAL TAX ADVICE INCLUDED IN THIS
COMMUNICATION IS NOT INTENDED OR WRITTEN TO BE USED, AND CANNOT BE
USED, TO AVOID ANY U.S. FEDERAL TAX PENALTIES OR TO PROMOTE, MARKET,
OR RECOMMEND TO ANOTHER PARTY ANY TRANSACTION OR MATTER.
