* Architecture discussion

== XML binding ==
 * [heikki] XML binding:
  In the ebRIM branch, and in the Nordic Security code (not public yet), JiBX is used for Java <--> XML binding. It is highly useful to have such a binding, as it can be invoked automatically on Web Service communications and leads to a much cleaner dealing with objects in Java than when DOM/JDOM is used. One disadvantage of JiBX is that this binding needs to be written manually, which is a bit of a pain in the neck. Another disadvantage is that it is not a Java standard. JAXB on the other hand *is* the standard and comes with a binding-generator that takes a schema and produces the bound Java classes. 

However, I've tried running it on the ISO19139 schema and it does not work :

 {{{

~/jaxb-ri-20110115/bin$ xjc -p testpackagename ~/source/ogc/ogc-schemas/trunk/iso/19139/20070417/schema/src/main/resources/iso/19139/20070417/gmd/gmd.xsd

The result is :

parsing a schema...
[ERROR] Property "Rows" is already defined. Use <jaxb:property> to resolve this conflict.
 line 648 of file:
~/source/ogc/ogc-schemas/trunk/iso/19139/20070417/schema/src/main/resources/gml/3.2.1/geometryPrimitives.xsd

[ERROR] The following location is relevant to the above error
 line 680 of file:
~/source/ogc/ogc-schemas/trunk/iso/19139/20070417/schema/src/main/resources/gml/3.2.1/geometryPrimitives.xsd

Failed to parse a schema.

 }}}

This is because of peculiarities in the schemas that we cannot control. I have asked !users@ogc.java.net if it is possible to do this at all, but I'd be surprised.

Question remains: if we cannot use JAXB to generate a binding for ISO19139, is it still desired to use JAXB for situations where we *can* use it, instead of using JiBX ?

== DB ==

 * DB / Mckoi to H2 or HSQL or derby ? See #475

== Search and Lucene index ==

 * Lucene
  * Merge LQB and lucene XSLTs
   * Add any search criteria
   * Search param is one value or an array value
  * Thread for indexing ?
  * !IndexWriter alert !IndexReader about status
 * Search
  * Return JSON
  * Using only stored field from the index
  * !StandardAnalyzer & !GeoNetworkAnalyzer
   * Remove character like (';,)} at the end/start of token
   * Add parameter to split URL
   * Comment:
    * StandardAnalyzer keep accent, do not keep negative number, split dates after hour
 * SOLR


== Code ==

 * Simplify
  * !SettingManager (lock, default value), 
  * !DataManager, 
  * XMLSerializer

== Perfomance improvements ==
  * root/gui/localized - only current session language ? - faster XSL
  * DB queries

== Misc. ==

 * Maven : version settings
 * Harvester