ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sibla Wilfried <>
Subject AW: Simple Ace questions
Date Wed, 04 Sep 2013 09:55:43 GMT
Hi Ryan

Apache ACE currently supports only autoconf conpliant XML configuration files. CFGs in combination
with FileInstaller and configAdmin isn't possible.
If you are using or planning to do so, you must use the ACE OBR. You cannot upload autoconf
XML config files to a OBR (e.g. Nexus) as an artifact. But ACE itself is able to upload them
to its own ACE OBR.
I implemented a customized resource processor (including the ArtifactHelper and ArtifactRecognizer
required by ACE) which is able to unpack cfg config files from a zip to a certain folder monitored
by the FileInstaller.
So I'm able to configure my targets in a very simple way which is also compatible to the know
FileInstaller/ConfigAdmin way of configuring a application.

To the Karaf features: as I wrote in my last post, it wouldn't be a big deal to implement
this functionality.
I decided to use the maven pom because our development is fully maven centric (I assume that
maven is used more often in dev. as ANT/BND tools; in the meantime I like BNDTools a little
bit more during dev. time....).

In the attachment you find a description of a Nexus with the OBR feature. I assume, that it's
not 100 % correct, but it should help.


-----Urspr√ľngliche Nachricht-----
Von: Ryan Moquin [] 
Gesendet: Mittwoch, 4. September 2013 06:28
Betreff: Re: Simple Ace questions

Thanks for the response Wilfried.  I had read that at some point there should be a way to
switch out the OBR repo that is used by ACE, I didn't think that was possible as of this point,
but it sounds like it is.  You mean configuration files other than ones meant for the Configuration
 I heard of autoconf recently and have yet to get a chance to look into how it works yet.
I think ACE being able to use the POM for constructing features would be a good idea, I think
the Karaf features might be a ltttle better, but at this point, whatever is easier, is probably
better to start with.  I'm hoping to wrapping up some work for a presentation I have to do
so I can delve into one of these things and see where I can help out.  It would certainly
be great to be able to simplify the process of getting things into ACE and setup.

Let me know if there is anything I can at some point.  Thanks!


On Mon, Sep 2, 2013 at 3:41 AM, Sibla Wilfried

> Hi Ryan
> I configured ACE to use an external OBR (NexusPro). Thus you could 
> deploy you artifacts with maven directly from your build server/env to 
> the OBR and ACE can use those URLs directly.
> With such a config, within the dialog for adding artifacts to ACE all 
> artifacts from your repo are automatically listed without the 
> necessity for uploading them to the ACE OBR.
> But nevertheless they must be added explicitly (manually or 
> programmatically by using the REST or JAVA client API) to the ACE repo 
> (not OBR).
> But with this configuration it's currently not possible to use the 
> configuration XML files (autoconf etc.)
> I could possibly provide a utility to create ACE features by deriving 
> them directly from a maven pom project (it's already working in my test env.).
> With this, the process of developing, deploying to the dev. Repo, 
> uploading/adding it to the ACE OBR and to the ACE repo and creating 
> the corresponding ACE features could be simplified.
> Greetings
> Wilfried
> -----Urspr√ľngliche Nachricht-----
> Von: Ryan Moquin []
> Gesendet: Dienstag, 27. August 2013 15:17
> An:
> Betreff: Simple Ace questions
> 2 questions, Ace is supposed to be able to handle configurations for 
> deployment right?
> Can the maven-bundle-plugin deploy bundles to the ace obr?  I read it 
> can connect and add bundles to an obr repo.. trying to plan out how I 
> can use Ace in an automatic fashion since deploying new bundles 
> bundles into the obr repo manually would be a bit time consuming...
> Thanks for any input!
> Ryan

  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message