John O'Hanley
non lue,26 févr. 2011, 14:50:2526/02/2011Connectez-vous pour répondre à l'auteur
Connectez-vous pour transférer le message
Vous n'êtes pas autorisé à supprimer des messages dans ce groupe
Connectez-vous pour signaler le message
Afficher le message d'origine
Soit les adresses e-mail sont anonymes pour ce groupe, soit vous devez disposer de l'autorisation "Afficher les adresses e-mail des membres" pour afficher le message d'origine.
à web4j-users
Hi,
I'm considering splitting web4j into 2 jars.
The problem: the database/sql tools in web4j are pretty good. I, and
others, would like to be able to easily use those tools in non-web
contexts:
- command line applications
- Swing applications
However, that's not currently very easy. The reason is a design flaw
in web4j - the data layer tools have knowledge of ServletConfig, for
config information.
There are other aspects of config in general that I would like to
improve as well, to allow people to place config somewhere else than
the web.xml file.
The idea is to split off the code that deals with 2 things :
- model objects (SafeText, Decimal, and so on)
- transferring these model objects into and out of a relational
database (the data layer)
IF that is done, however, then it's natural to use new package names,
corresponding to the new jar. Thus,
hirondelle.web4j.model..
might become instead :
hirondelle.data4j.model
For existing apps, that's not the end of the world, but it is a
significant amount of pain, in order to change the imports to the
changed package names.
How would you feel about this sort of change, if this were done?
- John