The configuration file for webical to start the first time is packed into
the war. Settings vary per user so the war will not work on all systems out
of the box. Altering xml files after a deploy is tricky and the risk of
losing data after a re-deploy is present.
This can be solved by altering webical to look for a configuration file
outside the war. Because this is not the most elegant solution, a better
proposal would be the usage of an internal database with meta-information
(databases/authentication sources). This does however mean that container
based authentication is no longer an option. Or will be at least be very
complicated.
Further investigation in this area will be needed.
Original issue reported on code.google.com by mattijsh...@gmail.com on 14 Jan 2008 at 2:15
Original issue reported on code.google.com by
mattijsh...@gmail.comon 14 Jan 2008 at 2:15