<?xml version="1.0"?>

<!DOCTYPE jason SYSTEM "conf/jason.dtd">

<!--

*************************
JASon configuration file
*************************

This file describes all available services. All services are grouped in
a domain. User can update some global properties like the message manager or the verbosity.

A domain contains : 
- A set of configuration services file (from the services.dtd)
- A set of single configuration service file (from the service.dtd)
- A set of door for accessing to the a service repository. By default this is a path that contains a set of service
- A set of verbose definition

User can override a property from the single configuration service file adding inside a set of property. 
Please report to the service.dtd for more information about properties

-->

<jason version="0.6" domain="default">

 <!-- Domain definition -->

 <domain name="default" verbose="true">

   <!-- This is a location path for integrating services.
   For this case, the domain will integrate automatically
   every services located in the door directory -->

   <door location="door" name="defaultDoor"/>

   <!-- This is an example of a configuration services file -->

   <services location="services.xml"/>

   <!-- This is an example of independant service description -->

   <service location="services/admin.xml">

     <!-- We override the port property to a new value as example -->

     <property name="port" value="10004"/>

   </service>

   <!-- Here a message handler, look at the jason.core.MessageHandler interface for your own handler -->

   <messageHandler class="jason.core.ConsoleMessageHandler"/>


   <!-- Example from the /examples/hello directory please uncomment it for testing -->
   <!-- <service location="../../examples/hello/hello.xml"> </service> -->

   <!-- Example from the /examples/time directory please uncomment it for testing -->
   <!-- <service location="../../examples/time/time.xml"> </service> -->

 </domain>

</jason>