Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vmahrwald@googlemail.com
 designates 209.85.160.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=from:content-type:content-transfer-encoding:subject:date:message-id
         :to:mime-version:x-mailer;
        b=SPUkfktDeUpgzRKm3NEcSlbk58Z7OFVJ0jjAqQgOmbfuZQJfgyS1MkmU3NxHG1gq3p
         9YKVYeLaFALGv8PyOHWSyTjIVqV05zo4vqZt/GPXb08BhbsI213mU1CZH6TP39jNXc95
         5o/XbwVoD1nbH1elE1ICTu6c69bFh2+NdMj1U=
From: Valentin Mahrwald <vmahrwald@googlemail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Package structure in application api
Date: Sun, 12 Sep 2010 13:03:39 -0400
Message-Id: <BA5AD8E8-386D-404E-BB7C-22DBEBA597E2@gmail.com>
To: aries-dev@incubator.apache.org
Mime-Version: 1.0 (Apple Message framework v1081)

Hi,

currently the application api project has one package =
org.apache.aries.application.management which seems like a very =
disparate collection of  client interfaces and various layers of =
interfaces to glue the runtime together. I would like to split that so =
that the packages are more coherent and can be versioned with greater =
independence.

At the very least there ought to be a split between user's api and =
implementer's spi:

  API (everything available from AriesApplicationManager):=20
  AriesApplication, AriesApplicationContext, AriesApplicationEvent, =
AriesApplicationListener, AriesApplicationManager, BundleInfo, =
ManagementException, ResolveConstraint, ResolverException, =
UpdateException

  SPI (everything else)
  AriesApplicationContextManager, AriesApplicationResolver, =
BundleConversion, BundleConverter, BundleFramework, =
BundleFrameworkFactory, BundleFrameworkManager, BundleRepository, =
BundleRepositoryManager, ContextException, ConversionException, =
DeploymentManifestManager, LocalPlatform, PlatformRepository, =
RepositoryGenerator, UpdateStrategy

  InvalidAttributeException seems to belong in the =
org.apache.aries.application package since it is only referenced in =
DeploymentMetadata, which lives there.


But even with this the runtime bundles that currently exist would be =
client and implementer for interfaces in the SPI package at the same =
time. So a further (OTT) split by responsibility might make sense:
  spi.conversion: BundleConversion, BundleConverter, ConversionException
  spi.framework: BundleFramework, BundleFrameworkFactory, =
BundleFrameworkManager
  spi.repository: BundleRepository, BundleRepositoryManager, =
PlatformRepository, RepositoryGenerator
  spi.resolve: AriesApplicationResolver, DeploymentManifestManager
  spi.runtime: AriesApplicationContextManager
  spi.update: UpdateStrategy
  spi.util: LocalPlatform
 =20
With the oddball ContextException to be still sorted out


What do people think? Is either of these splits sensible or is there =
something else that would be better?


Valentin=