= Application Architecture = 
Possible layers:
 * ui
 * services
 * dao
 * domain

= Artifacts = 
In SVN I have now created artifacts for the ebxml function. The following naming convention is used:
[software name] - [architecture level name] - [function name]
{{{
#!html
<table style="text-align: left; width: 100%;" border="1"
 cellpadding="2" cellspacing="2">
  <tbody>
    <tr>
      <td style="height: 26px; font-weight: bold; width: 190px;">aritifact
name</td>
      <td style="height: 26px; font-weight: bold; width: 777px;">responsibililty</td>
    </tr>
    <tr>
      <td style="height: 33px; width: 190px;">
geonetwork-domain-ebxml
      </td>
      <td style="height: 33px; width: 777px;">Represents
the domain model of the ebxml function.</td>
    </tr>
    <tr>
      <td style="height: 31px; width: 190px;">geonetwork-dao-ebxml</td>
      <td style="height: 31px; width: 777px;">Provides the
dao layer for the function. A Dao can be used to do CRUD operations on
domain objects towards the DB.&nbsp;</td>
    </tr>
    <tr>
      <td style="width: 190px;">geonetwork-services-ebxml <span
 style="font-weight: bold;">*)</span><br>
      <span style="font-weight: bold;"></span></td>
      <td style="width: 777px;">Provides the service layer
for the function. On this level everything is a offical transaction.
This layer can also be exposed to any other technical protocol like
Webservices, JMS, SMTP and so on. Fits well in a SOA architecture.
Every service call will probably use one or more Dao's and will use
heavily the domain.&nbsp;</td>
    </tr>
    <tr>
      <td style="height: 40px; width: 190px;">geonetwork-web-ebxml</td>
      <td style="height: 40px; width: 777px;">Provides the
application layer of the application. <br>
The application layer interacts with the users of the webapplication. A
user can be a browser or a machine. It parses the http request into a
service call. The service call goes to the service layer.&nbsp;</td>
    </tr>
  </tbody>
</table>
<span style="font-weight: bold;">*) not implemented
yet.&nbsp;</span><br>
<br>
}}}

Considerations
 * We could combine services and dao into one artifact named geonetwork-services-ebxml. 
 * We could call the dao artifact persistence.
 * In my other project people are complaining about having more artifacts instead of one for the application. Indeed you need a powerfull computer and IDE. Personally I think that the advantages of more artifacts are greater than the disadvantages. For instance Hudson works on artifact level.