Skip to main content

JBoss Fuse - Tips, Deploying Profile without Fabric8 maven plugin


If you want to take advantage of the Fuse Fabric deploy plugin, with new JBoss Fuse 6.2 requires you need to have Apache Maven 3.1.1 - 3.2.4. Otherwise, you may bump into error. The reason is because there has been a major API change in maven after 3.2.4. 

Here is the exception you might see if you don't have the correct maven version. 


No implementation for org.eclipse.aether.connector.wagon.WagonProvider was bound.
while locating org.eclipse.aether.connector.wagon.WagonRepositoryConnectorFactory

1 error
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1018)
at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1044)
at org.eclipse.sisu.space.AbstractDeferredClass.get(AbstractDeferredClass.java:48)
at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:54)
at com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:115)
at org.eclipse.sisu.bean.BeanScheduler$Activator.onProvision(BeanScheduler.java:176)
at com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:126)
at com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:68)
at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:46)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1066)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:36)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1009)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1059)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1005)
at org.eclipse.sisu.inject.LazyBeanEntry.getValue(LazyBeanEntry.java:81)
at org.eclipse.sisu.wire.EntrySetAdapter$ValueIterator.next(EntrySetAdapter.java:102)
at org.eclipse.aether.internal.impl.DefaultRepositoryConnectorProvider.newRepositoryConnector(DefaultRepositoryConnectorProvider.java:103)
at org.eclipse.aether.internal.impl.DefaultMetadataResolver$ResolveTask.run(DefaultMetadataResolver.java:603)
at org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

So there are two things you can do, 

1. Change you maven to 3.1.1 ~ 3.2.4 and you are good to go.

2. If for some reason, you need specific version in maven, probably the best way is not to use the fabric maven deploy plugin. So we have to do everything manually. What it basically does, 

  • A. Compile and package the application into maven repository.
  • B. Create a profile to deploy into Fuse Fabric.
  • C. Assign repositories, features and bundles into profile. 

For example, in my Travel agency demo, with the maven plugin, these are the configurations I need to provide. 

        <fabric8.profile>demo-travelagency-bookingservice</fabric8.profile>
<fabric8.parentProfiles>feature-camel mq-client</fabric8.parentProfiles>                                                       
<fabric8.bundles>mvn:com.h2database/h2/1.4.181</fabric8.bundles>
<fabric8.features>camel-jpa activemq-camel hibernate jdbc</fabric8.features>  

With the plugin, it will create a profile named "demo-travelagency-bookingservice" and have feature-camel and mq-client as the parent profile. Add camel-jpa , activemq-camel, hibernate, jdbc as features into profile. and lastly add two bundles, h2 and the application itself, bookingservice

Before I turn this into manual step, there are some settings I want to create beforehand, so it's easier to manage. Create a feature project, I added a new feature repository with a feature name "booking-service" that contains all the depended features and bundles in it.

<features name="TravelAgencyRepo" xmlns="http://karaf.apache.org/xmlns/features/v1.0.0">

  <repository>mvn:org.apache.camel.karaf/apache-camel/2.15.1.redhat-620133/xml/features</repository>
  <repository>mvn:org.apache.activemq/activemq-karaf/5.11.0.redhat-620133/xml/features</repository>
  <repository>mvn:org.apache.activemq/activemq-karaf/5.11.0.redhat-620133/xml/features-core</repository>
  <repository>mvn:org.apache.cxf.karaf/apache-cxf/3.0.4.redhat-620133/xml/features</repository>
  <repository>mvn:io.fabric8/fabric8-karaf/1.2.0.redhat-133/xml/features</repository>
  <repository>mvn:org.apache.karaf.assemblies.features/enterprise/2.4.0.redhat-620133/xml/features</repository>

  <feature name="booking-service" resolver="(obr)">
    <bundle start-level="20">mvn:com.h2database/h2/1.4.181</bundle>
    <feature version="2.15.1.redhat-620133">camel-jpa</feature>
    <feature version="5.11.0.redhat-620133">activemq-camel</feature>
    <feature version="4.2.19.Final-redhat-1">hibernate</feature>
    <feature version="2.4.0.redhat-620133">jdbc</feature>
  </feature>

</features>

Now we can start creating the profile, (make sure you have Fuse installed with Fabric created too). We first create the profile with two parent profiles

fabric:profile-create --parents feature-camel --parents mq-client demo-travelagency-webendpoint

And then add the repository we create previously to the profile.

fabric:profile-edit --repository mvn:org.blogdemo.travelagency/features/1.0/xml/features demo-travelagency-webendpoint

Add "booking-service" feature from the repository we just added to the profile.

fabric:profile-edit --feature webendpoint-service/0.0.0 demo-travelagency-webendpoint

Lastly add our application to the profile and we are done.

fabric:profile-edit --bundle mvn:org.blogdemo.travelagency/webendpoint/1.0 demo-travelagency-webendpoint


That's all you have to do :)

Comments

Paolo Antinori said…
Nice post!

I'd like to point to a couple of additional resources.

https://github.com/paoloantinori/fuse_ci

shows a full Maven based project that uses Maven templating capabilities to generate a features file:

https://github.com/paoloantinori/fuse_ci/blob/master/ci/features/src/main/resources/features.xml


And, as an alternative, an handy Maven companion script, that allows you to use the version of Maven you want, taking care of downloading, extracting and executing it on your behalf:

http://mvnvm.org/

The official documentation suggests to shade your original `mvn` executable with it, but I find it's more flexible to install and use it in this way:

```
# install
mkdir -p ~/bin && curl -s https://bitbucket.org/mjensen/mvnvm/raw/master/mvn > ~/bin/mvn_specific_version && chmod 0755 ~/bin/mvn_specific_version

# run
DEFAULT_MVN_VERSION=3.2.3 mvn_specific_version clean install
```


paolo

Popular posts from this blog

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …

RHTE - Supercharge your integration services

Red Hat Tech Exchange has taken place in Vietnam, Ho Chi Minh city two weeks ago, it is a great event held by Red Hat in Asia Pacific Region. It is open to all Red Hat partners who are interested in learning what Red Hat is doing recently, see what the trend of the open source world, basically it is a great event to share your knowledge and experience, to meet other enthusiastic people.

I am very fortunate to talk in this great event, to talk about the things I have been working on and even discuss it with many. Also got lots of great ideas too. So here are the slide.

My first talk was with Thomas Qvarnström about how to handle large size data in JBoss Fuse and how JBoss Data Grid can help in the situation.

Here is the agenda of the talk, we will be talk about this in the up coming webinar on 24th Sept.

Integration often involves storing, retrieving, and transforming data. Using a traditional database in your integration is likely to becomes a bottleneck that is expensive and hard to …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …