Affichages des données avec JPA

Bonjour,

Je développe une application web en JAVA EE avec jsf primefaces, JPA…
J’essaye de faire un essai très simple car je suis débutant.
J’ai une base de données (MS SQL SERVER) avec 2 tables :
- Formation : IdFormation, NomFormation
- Person : IdPerson, NomPerson, IdFormation

J’ai écrit le code pour les entités comme ceci :
Entité Formation :

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
 
@NamedQueries({
	@NamedQuery(name="sqlAllFormation", query="SELECT f FROM Formation f ORDER BY f.idFormation DESC")})
 
@Entity
@Table(name= "Formation")
public class Formation {
 
 
	@Id
	@GeneratedValue( strategy = GenerationType.IDENTITY )
	@Column(name= "IdFormation")
	private long idFormation;
 
	@Column(name="NomFormation")
	@NotNull
	private String nomFormation;
 
	@OneToMany(mappedBy="formation", fetch=FetchType.EAGER)
	private Set<Person> person;
 
	// GETTER SETTER
 
}

Entité Person :

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
 
@Entity
@Table(name="Person")
public class Person implements Serializable {
 
 
	private static final long serialVersionUID = 1L;
 
 
	@Id
	@GeneratedValue( strategy = GenerationType.IDENTITY )
	@Column(name= "IdPerson")
	private long idPerson;
 
	@ManyToOne(fetch = FetchType.EAGER)
	@JoinColumn(name="IdFormation")
	private Formation formation;
 
	@Column(name="NomPerson")
	private String nomPerson;
 
	//GETTER SETTER

FormationDao :

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
 
@Stateless
public class FormationDao {
 
	@PersistenceContext( unitName = "bdd" )
	private EntityManager em;
 
	public List<Formation> liste_formation () throws DAOException {
 
		try {
			TypedQuery<Formation> sql = em.createNamedQuery("sqlAllFormation", Formation.class);
			return sql.getResultList();
		} catch ( DAOException e ) {
			throw new DAOException( e );
		}
	}
 
}

Backing Bean ListeFormation :

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
 
 
@ManagedBean
@ViewScoped
public class ListeFormation implements Serializable {
 
	private static final long serialVersionUID = 1L;
 
	/*Liste */
	private List<Formation> listeFormation = new ArrayList<Formation>();
 
	// Injection des EJB (Session Bean Stateless)
	@EJB
	private FormationDao formationDao;
 
	public List<Formation> getListeFormation() {
		listeFormation = formationDao.liste_formation();
		return listeFormation;
	}
 
}

La page liste_formation.xhtml

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
 
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml"
	xmlns:f="http://java.sun.com/jsf/core"
	xmlns:h="http://java.sun.com/jsf/html"
	xmlns:c="http://java.sun.com/jsp/jstl/core"
	xmlns:b="http://bootsfaces.net/ui"
	xmlns:ui="http://java.sun.com/jsf/facelets"
	xmlns:p="http://primefaces.org/ui">
 
<h:head>
	  <meta charset="utf-8"></meta>
		<h:outputStylesheet library="default" name="style.css" />
</h:head>
 
<h:body>
<ui:include src="/resources/entete/entete.xhtml"/>
 
<b:container>
<div>
	<h1 class="black">Liste des formations</h1></div>
		<br />
		<br />
<h:form>
 
	<p:dataTable id="dataTable" var="ls_f" value="#{listeFormation.listeFormation}" paginator="true" rows="10" paginatorPosition="bottom" emptyMessage="Aucun résultat trouvé." scrollable="true" scrollWidth="auto">
        <f:facet name="header">
			Liste des Formation
		</f:facet>
 
		<p:column id="idF" headerText="N°Formation"
			filterBy="#{ls_f.idFormation}" filterMatchMode="contains">
            	<h:outputText id="idCell" value="#{ls_f.idFormation}"/>
            </p:column>
            <p:column id="nomFormation" headerText="Formation"
            	filterBy="#{ls_f.nomFormation}" filterMatchMode="contains">
            	<h:outputText id="idCell1" value="#{ls_f.nomFormation}"/>
            </p:column>
			<p:column id="persons" headerText="Persons">
            	<h:dataTable value="#{ls_f.person}" var="p" styleClass="innerTab">
 
						<h:column>#{p.idPerson} - #{p.nomPerson}</h:column>
    			</h:dataTable>
            </p:column>
 
          	</p:dataTable>
 
</h:form>	
 
	</b:container>
 
</h:body>
</html>

La question:
Quand je modifie ou j’ajoute une personne à une formation via Microsoft SQL Management Studio le changement n’apparait pas immédiatement sur ma page. Je suis obligé de redémarrer mon serveur GLASSFISH.
Dès fois la formation s’affiche toute suite sur mon tableau mais pas les personnes liées même si j’utilise fetch=FetchType.EAGER dans mes entités.

Est-ce que JPA Stock les données et n’émet pas de requête à chaque fois même si la console m’affiche la requête ?

Merci d’avance.

Je ne vois pas le code de mise à jour, tu procèdes comment ?

Peux-tu montrer le persistence.xml ?

Bonjour,

Merci d'avoir répondu.
Voici le fichier persistence.xml:

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
 
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0"
	xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
	<persistence-unit name="bdd" transaction-type="JTA">
		<jta-data-source>jdbc/bonecp_resource</jta-data-source>
		<class>gmaoMoulage.entities.Formation</class>
		<class>gmaoMoulage.entities.Person</class>
		<exclude-unlisted-classes>false</exclude-unlisted-classes>
		<properties>
			<property name="eclipselink.logging.level.sql" value="FINE" />
			<property name="eclipselink.logging.parameters" value="true" />
		</properties>
	</persistence-unit>
</persistence>

Merci d'avance pour votre aide.

Je ne sais toujours pas comment tu procèdes pour les mises à jour, la seule méthode de ta DAO est

Code:

public List<Formation> liste_formation ()

Enfaite j'utilise une connexion avec bonecp (pools de connexions JDBC) que j'ai ajouté sur mon serveur d'application Glassfish. Je fais rien d'autre pour récupérer les informations de ma base de données.

Code:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
 
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//GlassFish.org//DTD GlassFish Application Server 4.0 Resource Definitions//EN" "http://glassfish.org/dtds/glassfish-resources_1_5.dtd">
<!--
 Default options loaded by BoneCP. Modify as per your needs. This file has
     been automatically generated. 
-->
<resources>
<jdbc-connection-pool name="bonecpPool" datasource-classname="com.jolbox.bonecp.BoneCPDataSource" transaction-isolation-level="read-committed" is-isolation-level-guaranteed="true" steady-pool-size="1" max-pool-size="20" res-type="javax.sql.DataSource">
<!-- jdbc-connection-pool -->
<!--
Specifies the Transaction Isolation Level on the pooled       
             database connections. Optional. Has no default. If left       
             unspecified the pool operates with default isolation level    
             provided by the JDBC Driver. A desired isolation level can be 
             set using one of the standard transaction isolation levels,   
             which see.
-->
<!-- transaction-isolation-level="read-committed" -->
<!--
Applicable only when a particular isolation level is          
             specified for transaction-isolation-level. The default value  
             is true. This assures that every time a connection is         
             obtained from the pool, it is guaranteed to have the          
             isolation set to the desired value. This could have some      
             performance impact on some JDBC drivers. Can be set to false  
             by that administrator when they are certain that the          
             application does not change the isolation level before        
             returning the connection.
-->
<!-- is-isolation-level-guaranteed="true" -->
<!--
minimum and initial number of connections maintained in the pool.
-->
<!-- steady-pool-size="1" -->
<!-- maximum number of conections that can be created -->
<!-- max-pool-size="20" -->
<!--
To aid user in detecting potential connection leaks by the    
             application. When a connection is not returned back to the    
             pool by the application within the specified period, it is    
             assumed to be a potential leak and stack trace of the caller  
             will be logged. Default is 0, which implies there is no leak  
             detection, by default. A positive non-zero value turns on     
             leak detection. Note however that, this attribute only        
             detects if there is a connection leak. The connection can be  
             reclaimed only if connection-leak-reclaim is set to true.
-->
<!-- connection-leak-timeout-in-seconds="21600" -->
<!--
If enabled, connection will be reusable (put back into pool)  
             after connection-leak-timeout-in-seconds occurs. Default      
             value is false.          
-->
<!-- connection-leak-reclaim="true" -->
<!-- jdbc-connection-pool -->
<!--
 Sets the name of the pool for JMX and thread names. 
-->
<property name="poolName" value="BoneCPPool"/>
<!--
 Sets the minimum number of connections that will be contained in every partition.  
-->
<property name="driverClass" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
<property name="minConnectionsPerPartition" value="1"/>
<!--
 Sets the maximum number of connections that will be contained in every partition. 
          Setting this to 5 with 3 partitions means you will have 15 unique 
          connections to the database. Note that the connection pool will not create all 
          these connections in one go but rather start off with minConnectionsPerPartition and gradually 
          increase connections as required. 
-->
<property name="maxConnectionsPerPartition" value="20"/>
<!--
 Sets the acquireIncrement property.  When the available connections are about to run 
          out, BoneCP will dynamically create new ones in batches. This property controls how 
          many new connections to create in one go (up to a maximum of 
          maxConnectionsPerPartition). Note: This is a per partition setting. 
-->
<property name="acquireIncrement" value="2"/>
<!--
 Sets number of partitions to use.  In order to reduce lock contention 
          and thus improve performance, each incoming connection request picks off a connection from 
          a pool that has thread-affinity, i.e. pool[threadId % partition_count]. The higher this number, 
          the better your performance will be for the case when you have plenty 
          of short-lived threads. Beyond a certain threshold, maintenance of these pools will start 
          to have a negative effect on performance (and only for the case when 
          connections on a partition start running out).  Default: 1, minimum: 1, recommended: 
          2-4 (but very app specific) 
-->
<property name="partitionCount" value="1"/>
<!--  Sets the JDBC connection URL.  -->
<property name="jdbcUrl" value="jdbc:sqlserver://pc:1433;databaseName=bdd"/>
<!--  Sets username to use for connections.  -->
 
 <property name="Username" value="user"/> 
 <property name="Password" value="pwd"/> 
 <property name="characterEncoding" value="UTF-8"/>
 
<!--
 Sets username to use for connections. Just delegates to setUsername for clients hardcoded 
          with "setUser" instead. 
-->
<!--<property name="username" value="root"/>
  Sets password to use for connections.  
<property name="password" value="28!Epernon"/> -->
<!--
 Sets the idleConnectionTestPeriod.  This sets the time (in minutes), for a connection 
          to remain idle before sending a test query to the DB. This is 
          useful to prevent a DB from timing out connections on its end. Do 
          not use aggressive values here!   Default: 240 min, set to 0 
          to disable 
-->
<property name="idleConnectionTestPeriodInMinutes" value="240"/>
<!--
 Sets the idleConnectionTestPeriod.  This sets the time (in seconds), for a connection 
          to remain idle before sending a test query to the DB. This is 
          useful to prevent a DB from timing out connections on its end. Do 
          not use aggressive values here!   Default: 240 min, set to 0 
          to disable 
-->
<property name="idleConnectionTestPeriodInSeconds" value="14400"/>
<!--
 Sets Idle max age (in min).  The time (in minutes), for a 
          connection to remain unused before it is closed off. Do not use aggressive 
          values here!  Default: 60 minutes, set to 0 to disable. 
-->
<property name="idleMaxAgeInMinutes" value="60"/>
<!--
 Sets Idle max age (in seconds).  The time (in seconds), for a 
          connection to remain unused before it is closed off. Do not use aggressive 
          values here!  Default: 60 minutes, set to 0 to disable. 
-->
<property name="idleMaxAgeInSeconds" value="3600"/>
<!--
 Sets the connection test statement.  The query to send to the DB 
          to maintain keep-alives and test for dead connections. This is database specific and 
          should be set to a query that consumes the minimal amount of load 
          on the server. Examples: MySQL: "/* ping *\/ SELECT 1", PostgreSQL: "SELECT NOW()". 
		  Oracle : "SELECT SYS_CONTEXT('USERENV','SID') session_id, SYS_CONTEXT('USERENV','CURRENT_USER') oracle_user, SYS_CONTEXT('USERENV','DB_NAME') db_name, SYS_CONTEXT('USERENV','OS_USER') app_os_user, SYS_CONTEXT('USERENV','HOST') app_host, SYS_CONTEXT('USERENV','IP_ADDRESS') app_os_ip_address FROM DUAL"
          If you do not set this, then BoneCP will issue a metadata request 
          instead that should work on all databases but is probably slower.  (Note: 
          In MySQL, prefixing the statement by /* ping *\/ makes the driver issue 
          1 fast packet instead. See <a href="http://blogs.sun.com/SDNChannel/entry/mysql_tips_for_java_developers" target="_blank">http://blogs.sun.com/SDNChannel/entr...ava_developers</a> ) Default: Use metadata request 
-->
<property name="connectionTestStatement" value="/* ping */ SELECT 1"/>
<!--
 Sets statementsCacheSize setting.  The number of statements to cache. 
-->
<property name="statementsCacheSize" value="0"/>
<!--
 Sets number of helper threads to create that will handle releasing a connection. 
           When this value is set to zero, the application thread is blocked 
          until the pool is able to perform all the necessary cleanup to recycle 
          the connection and make it available for another thread.  When a non-zero 
          value is set, the pool will create threads that will take care of 
          recycling a connection when it is closed (the application dumps the connection into 
          a temporary queue to be processed asychronously to the application via the release 
          helper threads).  Useful when your application is doing lots of work on 
          each connection (i.e. perform an SQL query, do lots of non-DB stuff and 
          perform another query), otherwise will probably slow things down. 
-->
<property name="releaseHelperThreads" value="3"/>
<!--
 Sets the connection hook.  Fully qualified class name that implements the ConnectionHook 
          interface (or extends AbstractConnectionHook). BoneCP will callback the specified class according to the 
          connection state (onAcquire, onCheckIn, onCheckout, onDestroy). 
-->
<!--
 <property name="connectionHook" value="(null or no default value)"/> 
-->
<!--
 Specifies an initial SQL statement that is run only when a connection is 
          first created. 
-->
<!--
 <property name="initSQL" value="(null or no default value)"/> 
-->
<!--
 Instruct the pool to create a helper thread to watch over connection acquires 
          that are never released (or released twice). This is for debugging purposes only 
          and will create a new thread for each call to getConnection(). Enabling this 
          option will have a big negative impact on pool performance. 
-->
<property name="closeConnectionWatch" value="false"/>
<!--  If enabled, log SQL statements being executed.  -->
<property name="logStatementsEnabled" value="false"/>
<!--
 Sets the number of ms to wait before attempting to obtain a connection 
          again after a failure. 
-->
<property name="acquireRetryDelayInMs" value="7000"/>
<!--
 Set to true to force the connection pool to obtain the initial connections 
          lazily. 
-->
<property name="lazyInit" value="false"/>
<!--
 Set to true to enable recording of all transaction activity and replay the 
          transaction automatically in case of a connection failure. 
-->
<property name="transactionRecoveryEnabled" value="false"/>
<!--
 After attempting to acquire a connection and failing, try to connect these many 
          times before giving up. Default 5. 
-->
<property name="acquireRetryAttempts" value="5"/>
<!--
 Sets the connection hook class name. Consider using setConnectionHook() instead. 
-->
<!--
 <property name="connectionHookClassName" value="(null or no default value)"/> 
-->
<!--  Set to true to disable JMX.  -->
<property name="disableJMX" value="false"/>
<!--
 If set, use datasourceBean.getConnection() to obtain a new connection instead of Driver.getConnection(). 
-->
<!--
 <property name="datasourceBean" value="(null or no default value)"/> 
-->
<!--
 Queries taking longer than this limit to execute are logged. 
-->
<property name="queryExecuteTimeLimitInMs" value="0"/>
<!--
 Sets the Pool Watch thread threshold.  The pool watch thread attempts to 
          maintain a number of connections always available (between minConnections and maxConnections). This value 
          sets the percentage value to maintain. For example, setting it to 20 means 
          that if the following condition holds: Free Connections / MaxConnections < poolAvailabilityThreshold  
          new connections will be created. In other words, it tries to keep at 
          least 20% of the pool full of connections. Setting the value to zero 
          will make the pool create new connections when it needs them but it 
          also means your application may have to wait for new connections to be 
          obtained at times.  Default: 20. 
-->
<property name="poolAvailabilityThreshold" value="20"/>
<!--
 If set to true, the pool will not monitor connections for proper closure. 
          Enable this option if you only ever obtain your connections via a mechanism 
          that is guaranteed to release the connection back to the pool (eg Spring's 
          jdbcTemplate, some kind of transaction manager, etc). 
-->
<property name="disableConnectionTracking" value="false"/>
<!--
 Sets the maximum time (in milliseconds) to wait before a call to getConnection 
          is timed out.  Setting this to zero is similar to setting it 
          to Long.MAX_VALUE  Default: 0 ( = wait forever ) 
-->
<property name="connectionTimeoutInMs" value="0"/>
<!--
 Sets the no of ms to wait when close connection watch threads are 
          enabled. 0 = wait forever. 
-->
<property name="closeConnectionWatchTimeoutInMs" value="0"/>
<!--
 Sets number of statement helper threads to create that will handle releasing a 
          statement.  When this value is set to zero, the application thread is 
          blocked until the pool and JDBC driver are able to close off the 
          statement.  When a non-zero value is set, the pool will create threads 
          that will take care of closing off the statement asychronously to the application 
          via the release helper threads).  Useful when your application is opening up 
          lots of statements otherwise will probably slow things down. 
-->
<property name="statementReleaseHelperThreads" value="0"/>
<!--
 Sets the maxConnectionAge in seconds. Any connections older than this setting will be 
          closed off whether it is idle or not. Connections currently in use will 
          not be affected until they are returned to the pool. 
-->
<property name="maxConnectionAgeInSeconds" value="0"/>
<!--
 Sets the configFile. If configured, this will cause the pool to initialise using 
          the config file in the same way as if calling new BoneCPConfig(filename). 
-->
<!--
 <property name="configFile" value="(null or no default value)"/> 
-->
<!--
 Sets the queue serviceOrder. Values currently understood are FIFO and LIFO. 
-->
<!--
 <property name="serviceOrder" value="(null or no default value)"/> 
-->
<!--
 If set to true, keep track of some more statistics for exposure via 
          JMX. Will slow down the pool operation. 
-->
<property name="statisticsEnabled" value="false"/>
<!--
 Sets the defaultAutoCommit setting for newly created connections. If not set, use driver 
          default. 
-->
<!--
 <property name="defaultAutoCommit" value="(null or no default value)"/> 
-->
<!--
 Sets the defaultReadOnly setting for newly created connections. If not set, use driver 
          default. 
-->
<!--
 <property name="defaultReadOnly" value="(null or no default value)"/> 
-->
<!--
 Sets the defaultCatalog setting for newly created connections. If not set, use driver 
          default. 
-->
<!--
 <property name="defaultCatalog" value="(null or no default value)"/> 
-->
<!--
 Sets the defaultTransactionIsolation. Should be set to one of: NONE, READ_COMMITTED, READ_UNCOMMITTED, REPEATABLE_READ 
          or SERIALIZABLE. If not set, will use driver default. 
-->
<!--
 <property name="defaultTransactionIsolation" value="(null or no default value)"/> 
-->
<!--
 If set to true, no attempts at passing in a username/password will be 
          attempted when trying to obtain a raw (driver) connection. Useful for cases when 
          you already have another mechanism on authentication eg NTLM. 
-->
<property name="externalAuth" value="false"/>
<!--
 Sets the classloader to use to load JDBC driver and hooks (set to 
          null to use default). 
-->
<!--
 <property name="classLoader" value="(null or no default value)"/> 
-->
<!--
 If set to true, try to unregister the JDBC driver when pool is 
          shutdown. 
-->
<property name="deregisterDriverOnClose" value="false"/>
<!--
 Sets the nullOnConnectionTimeout.  If true, return null on connection timeout rather than 
          throw an exception. This performs better but must be handled differently in your 
          application. This only makes sense when using the connectionTimeout config option. 
-->
<!--
 <property name="nullOnConnectionTimeout" value="(null or no default value)"/> 
-->
 
</jdbc-connection-pool>
<jdbc-resource enabled="true" jndi-name="jdbc/bonecp_resource" object-type="user" pool-name="bonecpPool"/>
</resources>

Merci encore.

Salut,
cela ne repond toujours pas a la question : comment tu procèdes pour les mises à jour

Eric

Je pense que tu fais une "petite" confusion au niveau de JPA...

Si les entités (entity) restent attachées à une session, alors oui, les modifications seront persistées en base de données.
Par contre, dans une application web (à moins d'avoir fait quelque chose de spécial), on ouvre une connexion DB au début de la phase HttpRequest et on la ferme à la fin de la phase HttpResponse.
Ce qui veut dire que quand tu affiches ta pages, les entités sont détachées et plus rien ne se passe en DB.

Bref, il faudrait coder une méthode dans ta DAO pour mettre à jour (merge) et ajouter (persist) une entité dans la base...

Bonjour,

Je suis tout à fait d'accord avec vous pour dire que je confonds pas mal de chose.

D'après vous je devrai ré écrire mon code de formationDao?

Mais le problème c'est qu'il m'arrive d'attaquer ma base de données depuis sql server management studio et non via l'application.

Donc je ne peux pas faire merge ou persist si j'ajoute une ligne dans ma table depuis sql server management studio.

Merci
Cordialement

Ben là, oui, effectivement, tu t'emmêles bien les pinceaux :mouarf:

SQL Server Management Studio est une chose, l'application sur le serveur web en est une autre.
Seule ton application web va utiliser ce DAO, donc il faut que tu y codes ce qu'il faut pour ajouter ou modifier un "enregistrement" (à vrai dire ton entity)

Re,

En gros quelque soit la modifie, je suis obligé de passer par l'application?

Merci.

Oui, tu dois utiliser ton entityManager pour appliquer les modifications en base de données.
Typiquement, ce sera plus ou moins comme ça
Code:

1 2 3 4 5 6 7 8 9 10 public void save(MonEntity entity) { getEntityManager().persist(entity); } public void update(MonEntity entity) { getEntityManager().merge(entity); }