Do we have access to 100% of the features proposed by Apiman using the
It's certainly not impossible. If you try it, let me know! :)
love to have support for it if it's not difficult to do.
On 11/24/2015 10:09 AM, Charles Moulliard wrote:
> Thx for the response Eric. As the code is outdated, it should be more
> appropriate to use what exist within latest apiman core project and to
> start from the MicroService. If I add a BundleActivator class for the
> gateway & manager, we could easily deploy/start them on Karaf. As we
> have created a feature to deploy Elasticsearch top of JBoss Fuse, we
> don't have to take about the backend.
> Like you have done, we can replace the config file used to configure
> apiman (gateway/manager) on EAP using OSGI config admin
> On 24/11/15 13:44, Eric Wittmann wrote:
>> We originally thought that Karaf was going to be a requirement.
>> However, as priorities shifted so too did our support for OSGi and
>> Karaf/Fuse. It turns out to be quite difficult to support Karaf and
>> EAP and WildFly and Fabric8 and vert.x with the contributors we
>> currently have. :)
>> So bottom line is that Karaf support does not exist. I do not believe
>> anyone has tried to run it on Karaf since the commit you referenced.
>> Based on my experience with Karaf, I do not believe it would go very
>> well, but I'd be happy to be proven wrong!
>> On 11/24/2015 6:43 AM, Charles Moulliard wrote:
>>> Eric has created this project to "test/run" apiman into Apache
>>> Karaf/JBoss Fuse container (I think so) -
>>> Is this project still up to date or replaced by another ? Do we
>>> know if
>>> somebody has tried to install the war files of apiman
>>> gateway/manager ?
>>> Apiman-dev mailing list