camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Whiteside (Updated) (JIRA)" <>
Subject [jira] [Updated] (CAMEL-4543) Camel Blueprint support is limited/hardcoded to Aries
Date Fri, 14 Oct 2011 18:50:11 GMT


Aaron Whiteside updated CAMEL-4543:

    Attachment: separate_aries_blueprint_support_from_generic_blueprint_support.patch

Patch that creates a new module called camel-aries-blueprint-support and moves all aries specific
stuff into that.

camel-blueprint no longer depends on any Aries classes.

Tested camel-blueprint on JBoss 7.0.2 and works wonderfully.

Haven't been able to test the new camel-aries-blueprint-support jar yet, as I haven't setup
ServiceMix or the like..
> Camel Blueprint support is limited/hardcoded to Aries
> -----------------------------------------------------
>                 Key: CAMEL-4543
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-blueprint, osgi
>    Affects Versions: 2.9.0
>         Environment: JBoss 7.0.2
>            Reporter: Aaron Whiteside
>            Priority: Blocker
>         Attachments: BlueprintContainerRegistry.patch, separate_aries_blueprint_support_from_generic_blueprint_support.patch
> Camel Blueprint support is limited/hardcoded to Aries. This makes it impossible to use
in JBoss 7 or with another blueprint implementation like Gemini.
> The following classes use various things from Aries.
> * BlueprintContainerRegistry
> * BlueprintPropertiesParser
> * CamelContextFactoryBean
> * CamelProxyFactoryBean
> * CamelNamespaceHandler
> Now obviously the last three are related to the custom namespace handler for Aries.
> It would be good if these were moved into their own module, something like camel-aries-namespace
or the like.
> That people can choose to include if they would like to use the custom blueprint namespace
handler in Aries. Otherwise the camel-blueprint module should be implementation agnostic and
work on all blueprint containers. Not just Aries.
> {code}
> 10:18:58,656 ERROR [org.jboss.osgi.framework.internal.FrameworkEventsPlugin] (MSC service
thread 1-3) Framework ERROR: org.osgi.framework.BundleException: Cannot resolve bundle resModule:
> 	at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.ensureResolved(
> 	at org.jboss.osgi.framework.internal.HostBundleState.startInternal(
> 	at org.jboss.osgi.framework.internal.AbstractBundleState.start(
> 	at$1.processService(
> 	at$1.transition(
> 	at org.jboss.msc.service.ServiceControllerImpl.invokeListener(
> 	at org.jboss.msc.service.ServiceControllerImpl.access$2600(
> 	at org.jboss.msc.service.ServiceControllerImpl$
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker( [:1.7.0]
> 	at java.util.concurrent.ThreadPoolExecutor$ [:1.7.0]
> 	at [:1.7.0] Caused by: org.jboss.osgi.resolver.XResolverException:
Unable to resolve Module[]: missing requirement [Module[]]
package; (package=org.apache.camel.blueprint) [caused by: Unable to resolve Module[org.apache.camel.camel-blueprint:2.9.0.SNAPSHOT]:
missing requirement [Module[org.apache.camel.camel-blueprint:2.9.0.SNAPSHOT]] package; (&(package=org.apache.aries.blueprint)(version>=0.3.0)(!(version>=1.0.0)))]
> 	at org.jboss.osgi.resolver.felix.FelixResolver.resolveInternal(
> 	at org.jboss.osgi.resolver.spi.AbstractResolver.resolve( [jbosgi-resolver-spi-1.0.9.jar:1.0.9]
> 	at org.jboss.osgi.framework.internal.ResolverPlugin.resolve(
> 	... 11 more
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message