MPDL AB Meeting 2009-03-12

MPDL  Restricted Access to MPDL

Deployables and Jboss

 * Behavior of the postgresql driver ( no unlink to the database after redeploy )
 * Copy the postgres jar to JBoss' lib directory instead of delivering it with the pubman ear
 * Write something that manually unloads the driver when hot deploying
 * Disallow hot deployment
 * Migrate the CoNE database to Hypersonic. JBoss knows Hypersonic by default, so no extra driver would be required. Con: I have not much experience with HSQL and cannot judge performance and stability.
 * Delete the JNDI datasource and build up the JDBC connection from inside the code. This is a little less conforming to JavaEE standards but I can see no real disadvantage.
 * Isolation of ears running on one jboss (possibility to run several solutions on one jboss)
 * Dependencies between deployed ears (pubman -> coreservice in deploy phase)
 * Expected outcome: Find a deployment structure (classpath isolation; bootup order) on jboss which covers actual and future needs

Going Productive

 * Discussion on necessary steps for R5 (see http://colab.mpdl.mpg.de/mediawiki/ESciDoc_Solutions_Going_Productive)
 * Planning a meeting with all involved groups

Solution development

 * discussion on pubman deployment and how to approach it
 * discussion on solution properties and how to approach it
 * discussion on service locator issue and how to approach it
 * discussion on development of own policy templates and checking the possibilities to define policies on our own
 * background: more roles coming up with further solution developments
 * see also Talk:ESciDoc_Solutions_summary

Definition of TODOs for AB

 * scope: until March 2009
 * Proposal: have JIRA project for AB tasks only not to loose track of

EA Documentation

 * issues with the documentation
 * presentation of EA Documentation

Authoriziation issues

 * check http://zim01.gwdg.de:8080/browse/AS-381

Presentation test suite / test cases

 * What to test?
 * page flow
 * CRUD of items
 * FT upload
 * genre specific test cases
 * page behaviour (field/group presentation)
 * logic behaviour (save, cleanup)
 * simple or sophisticated item creation (using list elements -> i.e. create more than one creator, or not?)
 * search tests possible?
 * Javascript Tests?


 * Maintenance and creation of tests
 * who will create tests
 * who will maintain them?
 * is a graphical test creation (i.e. browser based) necessary?