Changes between Version 4 and Version 5 of codesprint/201103
- Timestamp:
- 03/21/11 05:18:09 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
codesprint/201103
v4 v5 1 1 * Architecture discussion 2 3 == XML binding == 2 4 * [heikki] XML binding: 3 5 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. … … 28 30 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 ? 29 31 30 32 == DB == 31 33 32 34 * DB / Mckoi to H2 or HSQL or derby ? See #475 35 36 == Search and Lucene index == 37 33 38 * Lucene 34 39 * Merge LQB and lucene XSLTs … … 37 42 * Thread for indexing ? 38 43 * !IndexWriter alert !IndexReader about status 39 * Simplify40 * !SettingManager (lock, default value),41 * !DataManager,42 * XMLSerializer43 44 * Search 44 45 * Return JSON … … 49 50 * Comment: 50 51 * StandardAnalyzer keep accent, do not keep negative number, split dates after hour 51 * Perfomance improvements 52 * SOLR 53 54 55 == Code == 56 57 * Simplify 58 * !SettingManager (lock, default value), 59 * !DataManager, 60 * XMLSerializer 61 62 == Perfomance improvements == 52 63 * root/gui/localized - only current session language ? - faster XSL 53 64 * DB queries 65 66 == Misc. == 67 54 68 * Maven : version settings 55 69 * Harvester 56 * SOLR
