Hi,
My idea is actually that what we expect users to do is create their own profile
adapted to their particular apps, rather than relying on the particular
selection of subsystems or components we think might be useful. While the
mojos I've been working on at github let you assemble most of the profiles you
mention easily, my ultimate goal is to make it easier to assemble a custom
server than deploy stuff into an existing profile server.
thanks
david jencks
On Jan 24, 2011, at 10:13 AM, Jean-Baptiste Onofré wrote:
> Hi Charles,
>
> Agree for that.
> However I think in a short term enhancement. I think that we need to design
> something more generic and flexible.
> I already quickly discussed of that with Guillaume.
>
> I propose to think about Karaf profiles. A profile is based on instance but
> enhanced and improved.
>
> For instance, we can see the following profiles:
> 1/ micro kernel: corresponding to the minimal dist
> 2/ default: corresponding to the "normal" current dist
> 3/ mobile: for android
> 4/ enterprise: providing enterprise application server based on enterprise
> features/arirs
> 5/ esb: corresponding to ServiceMix/swordfish
>
> I have to think deeper around to design it. Maybe we can start a wiki page to
> brainstorm about it.
>
> Regards
> JB
>
> On 01/24/2011 05:27 PM, Charles Moulliard wrote:
>> Hi,
>>
>> I would like to start a discussion concerning the idea to generate
>> during assembly of Apache Karaf a version who can be run on Google
>> Android platform (Mobile Device).
>>
>> The existing process is quite tedious and could be simplified
>>
>> export PATH=<path-to-android>/tools:$PATH
>> cd bin
>> dx --dex --output=classes.dex felix.jar
>> aapt add felix.jar classes.dex
>> Prepare the bundle JARS:
>>
>> cd bundle
>> dx --dex --output=classes.dex org.apache.felix.shell-1.0.0.jar
>> aapt add org.apache.felix.shell-1.0.0.jar classes.dex
>> dx --dex --output=classes.dex org.apache.felix.shell.tui-1.0.0.jar
>> aapt add org.apache.felix.shell.tui-1.0.0.jar classes.dex
>> dx --dex --output=classes.dex EnglishDictionary.jar
>> aapt add EnglishDictionary.jar classes.dex
>> dx --dex --output=classes.dex FrenchDictionary.jar
>> aapt add FrenchDictionary.jar classes.dex
>> dx --dex --output=classes.dex SpellChecker.jar
>> aapt add SpellChecker.jar classes.dex
>> Transfer all of them to the emulator (note that you need some kind of
>> unix-like shell, such as the Mac OS X terminal or Linux):
>>
>> cd osgi-android
>> emulator&
>> find * -type f -exec adb push {} /data/felix/{} \;
>>
>> Some maven plugins exist and could be used to generate DEX files
>> required by Davik Virtual Machine -->
>>
>> http://maven-android-plugin-m2site.googlecode.com/svn/dex-mojo.html
>> http://www.sonatype.com/books/mvnref-book/reference/android-dev-sect-custom-details.html
>>
>> Running Apache Karaf on Android platform could be of great interest as
>> it could allow the deployment of ActiveMQ and usage in offline mode on
>> Mobile.
>>
>> What do you think about that ?
>>
>> Regards,
>>
>> Charles Moulliard
>>
>> Sr. Principal Solution Architect - FuseSource
>> Apache Committer
>>
>> Blog : http://cmoulliard.blogspot.com
>> Twitter : http://twitter.com/cmoulliard
>> Linkedin : http://www.linkedin.com/in/charlesmoulliard
>> Skype: cmoulliard
>
> --
> Jean-Baptiste Onofré
> ---------------------------------
> HomePage
> http://www.nanthrax.net
> ---------------------------------
> Contacts
> [email protected]
> [email protected]
> ---------------------------------
> OpenSource
> BuildProcess/AutoDeploy
> http://buildprocess.sourceforge.net
> Apache ServiceMix
> http://servicemix.apache.org
> -----------------------------------
> PGP : 17D4F086
