April 2014 - Topia-devel - mailman.cloud.codelutin.com

Pourquoi les getters ne renverraient pas une collection vide ?
by Brendan Le Ny 24 Nov '14

24 Nov '14

Actuellement, une propriété avec une multiplicité renvoie une collection null si on appelle le getter, pourquoi ne pas initialiser cette collection en lazy (on le fait bien dans le add) ? Voire même, pourquoi pas interdire d'appeler le setter avec null (sauf si Hibernate l'impose) ? Il me semblait y avoir une raison mais elle ne me revient plus. -- Brendan Le Ny, Code Lutin bleny(a)codelutin.com (+33) 02 40 50 29 28

4 4

Pool C3p0 non fermé
by Eric Chatellier 25 Aug '14

25 Aug '14

Bonjoir, Actuellement, lors d'un hot redeploy dans tomcat, le pool c3p0 semble garder les connexions ouvertes. Voici les traces au redémarrage: rave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|6c187ab5]-AdminTaskTimer] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|6c187ab5]-HelperThread-#0] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|6c187ab5]-HelperThread-#1] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|6c187ab5]-HelperThread-#2] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [H2 File Lock Watchdog /tmp/xxx/h2data-web.lock.db] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [H2 Log Writer H2DATA-WEB] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|7dfbfca7]-AdminTaskTimer] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|7dfbfca7]-HelperThread-#0] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|7dfbfca7]-HelperThread-#1] but has failed to stop it. This is very likely to create a memory leak. févr. 19, 2014 10:28:33 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads Grave: The web application [/xxx] appears to have started a thread named [C3P0PooledConnectionPoolManager[identityToken->z8kflt90l3muy4yyzl36|7dfbfca7]-HelperThread-#2] but has failed to stop it. This is very likely to create a memory leak. 22:28:36 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] WARN ActiveManagementCoordinator:68 - A C3P0Registry mbean is already registered. This probably means that an application using c3p0 was undeployed, but not all PooledDataSources were closed prior to undeployment. This may lead to resource leaks over time. Please take care to close all PooledDataSources. J'ai trouvé un gros gros hack qui fonctionne: http://stackoverflow.com/a/7472386 ce qui semble bien démontrer qu'il y a un problème quelque part avec Topia/Hibernate (c3p0?). To be continued... -- Éric Chatellier

3 3

Re: [Topia-devel] [Topia-commits] r3071 - branches/topia-2.9.x/topia-persistence/src/main/java/org/nuiton/topia/generator
by Tony Chemit 16 Apr '14

16 Apr '14

On Wed, 16 Apr 2014 12:41:21 +0200 (CEST) echatellier(a)users.nuiton.org wrote: > +++ branches/topia-2.9.x/topia-persistence/src/main/java/org/nuiton/topia/generator/TopiaTagValues.java 2014-04-16 10:41:21 UTC (rev 3071) > @@ -471,7 +471,7 @@ > /** > * Tag to specify if we want to generate fireOnPreRead and fireOnPostRead method into entity getters. > * > - * @see TopiaGeneratorUtil#isDoNotGenerateReadListeners(ObjectModelClassifier, ObjectModel) > + * @see TopiaGeneratorUtil#isDoNotGenerateReadListeners(ObjectModelAttribute, ObjectModel) > * @since 2.9 > */ > @TagValueDefinition(target = {ObjectModel.class, ObjectModelClassifier.class}, Il faut que le target soit en adéquation avec. AMHA, il faudrait ici avoir model, classifier, attribute. -- Tony Chemit -------------------- tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: chemit(a)codelutin.com twitter: https://twitter.com/tchemit

1 0

[ANN] - ToPIA 3.0-beta-2 released
by Arnaud Thimel 09 Apr '14

09 Apr '14

The ToPIA team is pleased to announce the topia-3.0-beta-2 release! Tools for Portable and Independent Architecture : Framework de persistance et de distribution d'application. Documentation of the project can be found here: https://doc.nuiton.org/topia Changes ------- Changes in this version include: Fixed Bugs: o HqlAndParameterBuilder.addWhereClause fails because of parameters collision Issue: 3143. Thanks to Tony Chemit. Resolved by tchemit. o Some queries fails because of unexpected HQL parameter names Issue: 3142. Thanks to Arnaud Thimel. Resolved by athimel. Downloads --------- No release file deployed. (all files are deployed in the maven repository) Maven artifacts --------------- Artifacts are deployed in Maven Central Repository http://repo1.maven.org/maven2/ Find us at * http://search.maven.org/#artifactdetails|org.nuiton|topia|3.0-beta-2|jar Have fun! -ToPIA team

1 0

[ANN] - ToPIA 3.0-beta-1 released
by Arnaud Thimel 07 Apr '14

07 Apr '14

The ToPIA team is pleased to announce the topia-3.0-beta-1 release! Tools for Portable and Independent Architecture : Framework de persistance et de distribution d'application. Documentation of the project can be found here: https://doc.nuiton.org/topia Changes ------- Changes in this version include: New features: o Add the TopiaDao#forAll() method Issue: 3141. Thanks to Arnaud Thimel. Resolved by athimel. o allow to add method generic method in a DAO with clean model Issue: 1165. Thanks to Brendan Le Ny. Resolved by bleny. o Remplacer l'utilisation de la requete SQL dans la génération pour le cas du delete N-N Issue: 319. Thanks to Florian DESBOIS. Resolved by athimel. o Add a way to delete several entities in one time Issue: 1926. Thanks to Yannick Martel. Resolved by bleny. o Expose HibernateSupport in DAO Issue: 3120. Thanks to Brendan Le Ny. Resolved by bleny. o Add methods for "like" sql operation Issue: 3118. Thanks to Brendan Le Ny. Resolved by bleny. Fixed Bugs: o Hibernate connection not closed since 4.3.1 update Issue: 3078. Thanks to Éric Chatellier. Resolved by athimel. o Check HibernateProvider#close method Issue: 3072. Thanks to Éric Chatellier. Resolved by athimel. o Non compiable code : getComposite use non visible association Issue: 2057. Thanks to Éric Chatellier. Resolved by bleny. o Unhandled 'null' value in collection when addIn is used in HqlAndParametersBuilder Issue: 3101. Thanks to Brendan Le Ny. Resolved by bleny. Changes: o Update to Hibernate 4.3.x Issue: 2969. Thanks to Arnaud Thimel. Resolved by athimel. o Re(use) tests that has been created in topia-3.0-jpa project Issue: 2774. Thanks to Arnaud Thimel. Resolved by athimel. Downloads --------- No release file deployed. (all files are deployed in the maven repository) Maven artifacts --------------- Artifacts are deployed in Maven Central Repository http://repo1.maven.org/maven2/ Find us at *http://search.maven.org/#artifactdetails|org.nuiton|topia|3.0-beta-1|jar Have fun! -ToPIA team

1 0

Services de migration (NG2 :D)
by Arnaud Thimel 07 Apr '14

07 Apr '14

Salut, On a relancé cet aprem un vieux débat sur le service de migration. Comme on était en nombre réduit, je tente de synthétiser les différentes idées qui en sont ressorties, dîtes-nous ce que vous en pensez. J'ajoute également que j'ai pris certaines libertés dans la rédaction de ce mail sans consulter Brendan et Éric avec qui j'en ai discuté cet aprem. Proposition 1 : distinguer la version de l'application de la version de la base de données ========================================================================================== Exemple : * Version de l'application = 0.10.3 * Versions de la base = 4, 5, 6 La version de la base serait un entier tout con qu'on incrémente à chaque modification de base. Pour les versions ultérieures, on aurait : * Version de l'application = 0.10.4 * Versions de la base = 7 Puis : * Version de l'application = 0.11 * Versions de la base = 8, 9 etc... Proposition 2 : une classe de migration par version applicative =============================================================== La classe Java de migration (une seule par version applicative) serait donc un regroupement logique des migrations de version de base liées à cette version (applicative). Si je reprends l'exemple, la classe MachinCallbackV0_10_3contiendrait 3 méthodes, une pour chaque version de base (migrateToVersion4, migrateToVersion5 et migrateToVersion6). Cette classe serait responsable du choix de commit, au choix parmi : - après chaque version de base ; - après l'ensemble des versions de base qui constituent la version applicative. Au passage il serait cool de pouvoir aller lire et exécuter un fichier "migrateToVersion5.sql" en lieu et place d'un appel à la méthode Java. Proposition 3 : conserver un historique dans la table TMSVersion ================================================================ Aujourd'hui, la table TMSVersion ne contient qu'une seule et unique ligne avec une seule colonne qui contient "0.10.2": topiaId | version ----------------- xxxxx | 0.10.2 La nouvelle table contiendrait plus d'informations (exemple) : topiaId | dbVersion | appVersion | date | success | comment ---------------------------------------------------------------------------------- xxxxx | 5 | 0.10.3 | 21/11/2013 | true | suppr de la table machin xxxxx | 6 | 0.10.3 | 21/11/2013 | true | renommage colonne truc xxxxx | 7 | 0.10.4 | 25/12/2013 | false | ajout table pouette xxxxx | 7 | 0.10.4 | 26/12/2013 | true |ajout table pouette (retry) xxxxx | 8 | 0.11 | 01/01/2014 | true | - xxxxx | 9 | 0.11 | 01/01/2014 | true | - Pour connaître la version actuelle de la base, cette simple requête suffit : select max(dbVersion) from tmsversion where success is true; Ce ne sont que des propositions que j'ai présenté ici, il y aura certainement des points bloquants (migration pour les applis existantes, ...) auxquels nous nous attaquerons si ces propositions conviennent au plus grand nombre. À vous. Cordialement, Arnaud

3 2

Utilisation de la snapshot 3.0
by Tony Chemit 04 Apr '14

04 Apr '14

Si vous voulez utiliser cette snapshot, pensez aussi alors à changer aussi la version d'hibernate. Il faut être en 4.3.5.Final -- Tony Chemit -------------------- tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: chemit(a)codelutin.com twitter: https://twitter.com/tchemit

1 0