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

Red Hat Fuse - Announcing Fuse 7 Tech preview 3 release.

Red Hat Fuse 7.0 technical preview three is out today! On the pathway to become one of the best cloud-native integration platform, Fuse gives developer freedom to choose how they want to develop the integration solution, where they want to deploy it and capabilities to address new integration personas that do not have development experience.
By supporting the three major runtime, developer is free to work on the runtime of their choice.By supporting standalone and cloud deployment, it simplifies the complexity to distinguish between these environments, allowing application to deploy freely among the environment of your choice. All levels of developers are welcome, you can either dive deep into creating customize complex integration logic, or using the new low code platform to quickly build a simple integration. In this Tech Preview release you get it all.
Fuse StandaloneSpring-boot for microserviceKaraf 4 for OSGi loverJBoss EAP for JavaEE developersFuse on OpenShiftPlugins for easy co…

JBoss EAP 6 - 效能調校 (一) DataSource 的 Connection Pool

效能沒有什麼Best Practice, 反正能調整的就那些。 通常,一個程式的效能大概有70-80% 都跟程式怎麼寫的其實比較有關係。

最近我最疼愛的小貓Puji 因為膀胱結石開刀的時候過世了,心情很差請原諒我的口氣沒有很好,也沒有心情寫部落格。

Puji R.I.P.

=======================正文=======================

這個題目很多人叫我寫,可是這題目好大,這分明就是整死我咩~
所以我會分幾段慢慢寫。

JBoss 的 SubsystemDatasource WebWeb Service EJB Hibernate JMSJCAJVM 調校OS (作業系統)

先來看一下 DataSource Subsystem, DataSource 的部分主要是針對Connection Pool 做調校。

通常,程式都會需要跟資料庫界接,電腦在本機,尤其是在記憶體的運算很快,但是一旦要外部的資源連接,就是會非常的耗資源。所以現在的應用程式伺服器都會有個Pool 放一些先連接好的 資料庫connection,當程式有需要的時候就可以馬上提供,而不用花那些多餘的資源去連接資料庫。

這就是為什麼要針對Connection Pool 去做調校。

以下會討論到的參數,都是跟效能比較有關係,Datasource 還有很多參數,像是檢核connection 是否正確的,我都不會提到。如果你追求的是非常快速的效能,那我建議你一個檢核都不要加。當然,這樣就會為伺服器上面執行的程式帶來風險。這就是你要在效能與正確,安全性上面的取捨了。 (套句我朋友說的話,不可能又要馬兒好,又要馬兒不吃草的..)

最重要的調校參數就是 Connection 的 Pool 數量。(也就是那個Pool 裡面要放幾條的connection.) 這個參數是每一個應用程式都不一樣的。

min-pool-size 

Connection Pool 最少會存留的connection 數量

max-pool-size 

Connection Pool 最多可以開啓的 connection 數量

prefill

事先將connection pool 裡面建立好min-pool-size 的connection.

我的建議是觀察一下平常程式要用到的量設定為 min-pool-size 。
加上…

JBoss Fuse - Fuse workshop 101 - Part One

On my way to Hong Kong for a day of workshop on JBoss Fuse, and as I go through my Slide deck, I cannot find any decent easy workshop for beginners. Therefore I decide make a workshop that is easy for Camel first timer to get their hands dirty.

The first of part of the workshop is an introduction to Camel, it first goes through what is exactly inside JBoss Fuse.

For part one of the workshop, it takes your through the very basic of Camel, one of the very important component inside JBoss Fuse.
Every Camel need to have a runtime container to run in, inside camel we call it a CAMEL CONTEXT.  Inside every Camel context, you can define lots of camel route and registry, don't worry about what those are, we will explain later.


So inside out blueprint xml, you will see a tag called camelContext.



Next up is camel route, they are a chain of command or process defined by you, as a developer.
Inside the camel route, there are consumer endpoints that listens to the incoming messages, producers …