aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Holly Cummins (JIRA)" <>
Subject [jira] Resolved: (ARIES-321) Demo application which can be coded up from scratch
Date Tue, 01 Jun 2010 13:29:37 GMT


Holly Cummins resolved ARIES-321.

    Resolution: Fixed

Mark Nuttall has committed the sample to samples-sandbox, so this issue can now be closed.

> Demo application which can be coded up from scratch
> ---------------------------------------------------
>                 Key: ARIES-321
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: Samples
>            Reporter: Holly Cummins
>            Priority: Minor
>         Attachments: aries-321.txt
> I've been presenting Apache Aries a bit lately, and think there's a gap in our current
demos. The samples are really useful as samples, but they're not quite right for a live demo.
What would be idea for Aries is something that can be coded up live from scratch. I think
this makes an engaging demo in general, and it's especially suitable for Aries because it's
partly a programming model - what will be different for developers is the development experience,
rather than the externals of the finished application. We could code up helloworld from scratch
but it's a bit too simple, and the blog sample has much too much code to be coded live. 
> The intention is to have an application which shows a lot of the main elements of an
enterprise architecture - a web front end, a persistence layer, a modular design - but almost
no code. I chose keyword association for two reasons. The first is that it's pretty trivial
to implement. The second is that I am hoping it will work well in front of a live audience
because the audience can be prompted to supply the associations, which should help wake them
up. :)
> The main collateral is the script for the demo. It is in the wordassociation root, and
is called demoscript.html. It probably needs further refinement as we use it in front of a
live audience and discover what works and what needs further explanation. I've also included
the completed bundles for reference.
> I have deviated from our usual org.apache.aries.sample naming convention and left the
package names quite short so that it's easy to type them during live coding. Having the names
in the subversion copies match names we might use live means that if something goes wrong
during the demo it should be possible to swap in a pre-built bundle from the repository.
> I have included a maven build so that the bundles can be built independently of eclipse
(although I don't think coding up the maven build scripts live in front of an audience would
be much fun for either the audience or the speaker.) The maven build doesn't strictly follow
best practices for the module names, again to keep the names short so that the mvn modules
are interchangeable with those coded live.
> The projects were built using the Rational free tools for OSGi applications, and their
internal layout reflects this. They build fine with maven but .don't build brilliantly when
imported into normal eclipse. They do work (obviously) when imported into the web tools platform
with the OSGi Applications free tools installed. Instructions for installing the free tools
are given in demoscript.html. The demo could also be done using normal eclipse or normal eclipse
and a maven build, although the instructions would be slightly different at some steps. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message