-
Notifications
You must be signed in to change notification settings - Fork 75
/
jboss-eap5and6to7-xml.windup.xml
468 lines (446 loc) · 30.2 KB
/
jboss-eap5and6to7-xml.windup.xml
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
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
<?xml version="1.0"?>
<ruleset id="jboss-eap5and6to7-xml"
xmlns="http://windup.jboss.org/schema/jboss-ruleset"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://windup.jboss.org/schema/jboss-ruleset http://windup.jboss.org/schema/jboss-ruleset/windup-jboss-ruleset.xsd">
<!--
Covers changes common to
* EAP 5 to EAP 6 upgrade and
* EAP 5 to EAP 7 upgrade.
-->
<metadata>
<description>
This ruleset provides analysis of configuration XML files in both JBoss EAP 5 and JBoss EAP 6
that may require individual attention when migrating to JBoss EAP 7+.
The purpose of this ruleset common to those two major JBoss EAP versions is to avoid duplication of rules
in rulesets dedicated to either version.
Mainly deals with datasources, JBoss Web and EJB configuration.
</description>
<dependencies>
<addon id="org.jboss.windup.rules,windup-rules-javaee,2.6.0.Final"/>
<addon id="org.jboss.windup.rules,windup-rules-java,2.6.0.Final"/>
</dependencies>
<sourceTechnology id="eap" versionRange="[5,7)"/>
<targetTechnology id="eap" versionRange="[7,)"/>
<tag>jboss-eap5</tag>
<tag>jboss-eap6</tag>
<tag>ejb</tag>
</metadata>
<rules>
<rule id="jboss-eap5and6to7-xml-37000">
<when>
<xmlfile matches="/*[local-name()='ejb-jar']/*[local-name()='assembly-descriptor']/*[local-name()='clustering']/*[local-name()='clustered']" in="jboss-ejb3.xml"/>
</when>
<perform>
<iteration>
<hint title="Stateful Session EJB Clustering configuration changes in EAP 7" effort="1" category-id="optional">
<message>
The `clustered` element is ignored in EAP 7 and is not useful. In case the application is started using HA profile, the replication will be done automatically.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_stateful_session_ejb_clustering_changes" title="Clustered annotation in EAP 7" />
<tag>cluster</tag>
<tag>ejb</tag>
<tag>configuration</tag>
</hint>
</iteration>
</perform>
</rule>
<!-- Seam -->
<rule id="jboss-eap5and6to7-xml-05000">
<when>
<xmlfile matches="/sc:components">
<namespace prefix="sc" uri="http://jboss.com/products/seam/components"/>
</xmlfile>
</when>
<perform>
<classification issue-display-mode="all" title="JBoss Seam Components (components.xml)" effort="5">
<description>You should migrate from Seam 2 Framework to Context Dependency Injection technology.</description>
<link title="Context and dependency injection - CDI" href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/development_guide/#contexts_and_dependency_injection_cdi"/>
<link title="Migration from Seam 2 to Java EE and alternatives" href="https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Web_Framework_Kit/2.7/html/Seam_Guide/ch36.html"/>
<tag>seam2</tag>
<tag>jboss-eap5</tag>
</classification>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-06000">
<when>
<xmlfile matches="/sp:pages">
<namespace prefix="sp" uri="http://jboss.com/products/seam/pages"/>
</xmlfile>
</when>
<perform>
<classification issue-display-mode="all" title="JBoss Seam Pages (pages.xml)" effort="5">
<description>You should migrate from Seam 2 Framework to Context Dependency Injection technology.
The most features from `pages.xml` file where it is specified a page flow and other configuration of the Seam Framework is achievable through JSF Flow.
</description>
<link href="https://docs.jboss.org/seam/latest/reference/html_single/" title="Seam 2 Framework Reference"/>
<link href="https://docs.oracle.com/javaee/7/tutorial/jsf-configure003.htm" title="Using Faces Flows"/>
<tag>seam</tag>
<tag>jboss-eap5</tag>
</classification>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-07000">
<when>
<xmlfile matches="/page" in="{*}.page.xml"/>
</when>
<perform>
<classification issue-display-mode="all" title="JBoss Seam Page" effort="3">
<tag>seam</tag>
<tag>jboss-eap5</tag>
</classification>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-09000">
<when>
<xmlfile matches="//*[local-name()='jboss-web']" in="jboss-web.xml"/>
</when>
<perform>
<classification issue-display-mode="detail-only" title="JBoss web application descriptor (jboss-web.xml)" effort="1">
<description>
The `jboss-web.xml` file configures a Java EE web application specifically for JBoss EAP.
It is an extension to standard `web.xml`.
</description>
<link title="jboss-web.xml Configuration Reference" href="https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/chap-Configuration_References.html#jboss-webxml_Configuration_Reference"/>
<tag>web</tag>
<tag>configuration</tag>
<tag>deployment</tag>
<tag>descriptor</tag>
<tag>jboss-eap5</tag>
</classification>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-12000">
<when>
<xmlfile matches="//*[local-name()='jbosscmp-jdbc']" in="jbosscmp-jdbc.xml"/>
</when>
<perform>
<classification issue-display-mode="all" title="JBoss EJB 2 CMP Deployment descriptor (jbosscmp-jdbc.xml)" effort="5" category-id="mandatory">
<description>
The `jbosscmp-jdbc.xml` is a deployment decriptor controlling the Container Managed Persistence (CMP).
Support for EJB Entity Beans is optional in Java EE 7 and they are not supported in JBoss EAP 7.
This means CMP entity beans must be rewritten to use Java Persistence API (JPA) entities.
</description>
<link title="JBoss EAP 4: The jbosscmp-jdbc Structure" href="https://docs.jboss.org/jbossas/docs/Server_Configuration_Guide/4/html/The_CMP_Engine-The_jbosscmp_jdbc_Structure.html"/>
<link title="Migrate Entity Beans to JPA" href="https://access.qa.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/migration_guide/#migrate_entity_beans_to_jpa"/>
<tag>jdbc</tag>
<tag>ejb2</tag>
<tag>jboss-eap5</tag>
<tag>jpa</tag>
</classification>
</perform>
</rule>
<!-- EAP 6 -->
<rule id="jboss-eap5and6to7-xml-17000">
<when>
<xmlfile matches="//*[local-name()='ejb-jar']" in="jboss-ejb3.xml"/>
</when>
<perform>
<classification issue-display-mode="all" title="JBoss EJB 3 deployment descriptor (jboss-ejb3.xml)" effort="5">
<description>
A JBoss specific EJB 3 configuration allows extensions of Java EE EJB 3.
</description>
<link title="jboss-ejb3.xml Deployment Descriptor Reference" href="https://access.redhat.com/documentation/en-US/JBoss_Enterprise_Application_Platform/6.4/html/Development_Guide/sect-Reference2.html#jboss-ejb3xml_Deployment_Descriptor_Reference"/>
<tag>jboss-eap5</tag>
</classification>
</perform>
</rule>
<!-- EAP 6 -->
<rule id="jboss-eap5and6to7-xml-18000">
<when>
<xmlfile matches="//*[local-name()='webservices']" in="jboss-webservices.xml"/>
</when>
<perform>
<classification issue-display-mode="all" title="JBoss web-services deployment descriptor (jboss-webservices.xml)" effort="5">
<description>
JBossWS 4.0 introduces a new deployment descriptor to configure web services.
The `jboss-webservices.xml` file provides additional information for the given deployment
and partially replaces the obsolete `jboss.xml` file.
For EJB webservice deployments, the expected location of the `jboss-webservices.xml` descriptor file
is in the `META-INF/` directory. For POJO and EJB webservice endpoints bundled in WAR file,
the expected location of the `jboss-webservices.xml` file is in the `WEB-INF/` directory.
</description>
<link title="JBoss web-services changes" href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/html-single/migration_guide/#migrate_web_service_application_changes"/>
<tag>jboss-ws</tag>
<tag>descriptor</tag>
<tag>webservice</tag>
<tag>jboss-eap5</tag>
</classification>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-31000">
<when>
<xmlfile matches="/ejb-jar/enterprise-beans/entity[persistence-type = 'Container'] | /jee:ejb-jar/jee:enterprise-beans/jee:entity[jee:persistence-type = 'Container'] | /j2e:ejb-jar/j2e:enterprise-beans/j2e:entity[j2e:persistence-type = 'Container'] | /jcp:ejb-jar/jcp:enterprise-beans/jcp:entity[jcp:persistence-type = 'Container']" in="ejb-jar.xml">
<namespace prefix="j2e" uri="http://java.sun.com/xml/ns/j2ee"/>
<namespace prefix="jee" uri="http://java.sun.com/xml/ns/javaee"/>
<namespace prefix="jcp" uri="http://xmlns.jcp.org/xml/ns/javaee"/>
</xmlfile>
</when>
<perform>
<iteration>
<hint title="CMP Entity EJB configuration" effort="3" category-id="mandatory">
<message>CMP entity beans are no longer supported in JBoss EAP 7. User is requested to use JPA entities that fully replaced the functionality provided by CMP beans.
CMP configuration provided in this ejb-jar.xml should be configured using JPA persistence.xml or using JPA annotations.</message>
<link title="CMP Bean migration" href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_entity_beans_to_jpa"/>
<tag>jpa</tag>
<tag>cmp</tag>
</hint>
</iteration>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-31500">
<when>
<xmlfile matches="/ejb-jar/enterprise-beans/entity[persistence-type = 'Bean'] | /jee:ejb-jar/jee:enterprise-beans/jee:entity[jee:persistence-type = 'Bean'] | /j2e:ejb-jar/j2e:enterprise-beans/j2e:entity[j2e:persistence-type = 'Bean'] | /jcp:ejb-jar/jcp:enterprise-beans/jcp:entity[jcp:persistence-type = 'Bean']" in="ejb-jar.xml">
<namespace prefix="j2e" uri="http://java.sun.com/xml/ns/j2ee"/>
<namespace prefix="jee" uri="http://java.sun.com/xml/ns/javaee"/>
<namespace prefix="jcp" uri="http://xmlns.jcp.org/xml/ns/javaee"/>
</xmlfile>
</when>
<perform>
<iteration>
<hint title="EJB 2.x BMP Entity Beans configuration" effort="3" category-id="mandatory">
<message>BMP entity beans are no longer supported in JBoss EAP 7. User is requested to use JPA entities that fully replaced the functionality provided by BMP beans.
BMP configuration provided in this ejb-jar.xml should be configured using JPA persistence.xml or using JPA annotations.</message>
<link title="CMP Bean migration" href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_entity_beans_to_jpa" />
<tag>jpa</tag>
<tag>bmp</tag>
</hint>
</iteration>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-32000">
<when>
<xmlfile matches="/jboss-web/valve | /jboss:jboss-web/jboss:valve" in="jboss-web.xml">
<namespace prefix="jboss" uri="http://www.jboss.com/xml/ns/javaee"/>
</xmlfile>
</when>
<perform>
<iteration>
<hint title="Valve is not supported in JBoss EAP 7" effort="1" category-id="mandatory">
<message>JBoss Web was replaced by Undertow, which does not contain support for the Valve functionality. It may be needed to migrate to Undertow handlers.</message>
<link title="Valve migration" href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_custom_application_valves"/>
<tag>web</tag>
</hint>
</iteration>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-33000">
<when>
<or>
<xmlfile matches="/webservices/webservice-description/jaxrpc-mapping-file | /jee:webservices/jee:webservice-description/jee:jaxrpc-mapping-file | /jcp:webservices/jcp:webservice-description/jcp:jaxrpc-mapping-file | /j2ee:webservices/j2ee:webservice-description/j2ee:jaxrpc-mapping-file">
<namespace prefix="j2ee" uri="http://java.sun.com/xml/ns/j2ee"/>
<namespace prefix="jcp" uri="http://xmlns.jcp.org/xml/ns/javaee"/>
<namespace prefix="jee" uri="http://java.sun.com/xml/ns/javaee"/>
</xmlfile>
<xmlfile matches="/ejb-jar/enterprise-beans/session/service-ref/jaxrpc-mapping-file | /jee:ejb-jar/jee:enterprise-beans/jee:session/jee:service-ref/jee:jaxrpc-mapping-file | /jcp:ejb-jar/jcp:enterprise-beans/jcp:session/jcp:service-ref/jcp:jaxrpc-mapping-file | /j2ee:ejb-jar/j2ee:enterprise-beans/j2ee:session/j2ee:service-ref/j2ee:jaxrpc-mapping-file">
<namespace prefix="j2ee" uri="http://java.sun.com/xml/ns/j2ee"/>
<namespace prefix="jcp" uri="http://xmlns.jcp.org/xml/ns/javaee"/>
<namespace prefix="jee" uri="http://java.sun.com/xml/ns/javaee"/>
</xmlfile>
<xmlfile matches="/java-wsdl-mapping | /jee:java-wsdl-mapping | /jcp:java-wsdl-mapping | /j2ee:java-wsdl-mapping">
<namespace prefix="j2ee" uri="http://java.sun.com/xml/ns/j2ee"/>
<namespace prefix="jcp" uri="http://xmlns.jcp.org/xml/ns/javaee"/>
<namespace prefix="jee" uri="http://java.sun.com/xml/ns/javaee"/>
</xmlfile>
</or>
</when>
<perform>
<iteration>
<hint title="JAX-RPC specific configuration" effort="3" category-id="mandatory">
<message>JAX-RPC support was removed in JBoss EAP 7. All the RPC calls will need to be migrated to JAX-WS.</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_jax_rpc_support_changes" title="JAX-RPC support changes" />
<tag>rpc</tag>
<tag>jax-ws</tag>
</hint>
</iteration>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-34000">
<when>
<file filename="deployment-plan.xml"/>
</when>
<perform>
<classification issue-display-mode="all" title="JSR-88 deployment plans are no more supported by JBoss EAP7" effort="3" category-id="mandatory">
<description>This file should be removed and instead rely on proprietary functionality to automate deployments. Please consult EAP 7 admin documentation to learn about such functionality.</description>
<link title="Migrate Deployment plan configurations" href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_deployment_plan_configurations"/>
<tag>configuration</tag>
</classification>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38000">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='replication-trigger']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config replication-trigger changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `replication-trigger` element in `jboss-web.xml` file descriptor.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38001">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='replication-mode']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config replication-mode changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates element `replication-mode` element without replacement in `jboss-web.xml` file descriptor.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38002">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='backups']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config backups changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `backups` element without replacement in `jboss-web.xml` file descriptor.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38003">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='use-jk']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config use-jk changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `use-jk` element without replacement in `jboss-web.xml` file descriptor.
Previously by specifying `use-jk` element, the instance-id of the node handling a given request was appended to the jsessionid (foruse by load balancers such as mod_jk, mod_proxy_balancer, mod_cluster, etc.) depending on the value specified for `use-jk`.
In the new implementation, the instance-id, if defined, is always appended to the jsessionid.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38004">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='max-unreplicated-interval']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config max-unreplicated-interval changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `max-unreplicated-interval` element in `jboss-web.xml` file descriptor.
Previously, this configuration option was an optimization that would prevent the replication of a session’s timestamp if no session attribute was changed. While this sounds nice, in practice it doesn't prevent any RPCs, since session access requires cache transaction RPCs regardless of whether any session attributes changed.
In the new implementation, the timestamp of a session is replicated on every request.
This prevents stale session metadata following failover.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38005">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='snapshot-mode']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config snapshot-mode changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `snapshot-mode` element in `jboss-web.xml` file descriptor.
Previously, one could configure `snapshot-mode` as INSTANT or INTERVAL. Infinispan’s replication queue renders this configuration option obsolete.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38006">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='snapshot-interval']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config snapshot-interval changes in EAP 7" effort="1" category-id="optional">
<message><![CDATA[
The EAP 7 Web Session Clustering configuration removed `snapshot-interval` element from `jboss-web.xml` file descriptor.
This option was only relevant for `<snapshot-mode>INTERVAL</snapshot-mode>`. Since `snapshot-mode` is no longer used, this option is no longer used as well.]]>
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-38007">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='replication-config']/*[local-name()='session-notification-policy']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config session-notification-policy changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `session-notification-policy` element in `jboss-web.xml` file descriptor.
Previously `session-notification-policy` element defined a policy for triggering session events.
In the new implementation, this behaviour is specification driven and not configurable.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-39000">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='passivation-config']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config passivation-config changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration deprecates `passivation-config` element and its sub-elements `use-session-passivation`, `passivation-min-idle-time` and `passivation-max-idle-time` completely in `jboss-web.xml` file descriptor.
* `use-session-passivation` enabled the passivation, but now passivation is enabled by specifying a non-negative value for `max-active-sessions` element.
* `passivation-min-idle-time` is not supported and the new implementation avoids waiting some time before the passivation.
* `passivation-max-idle-time` is not supported and the new implementation supports only lazy passivation. Sessions are only passivated when necessary to comply with `max-active-sessions`.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
<rule id="jboss-eap5and6to7-xml-40000">
<when>
<xmlfile matches="/*[local-name()='jboss-web']/*[local-name()='max-active-sessions']" in="jboss-web.xml"/>
</when>
<perform>
<hint title="Web Session Clustering config max-active-sessions changes in EAP 7" effort="1" category-id="optional">
<message>
The EAP 7 Web Session Clustering configuration changed `max-active-sessions` element meaning in `jboss-web.xml` file descriptor.
Previously, session creation would fail if an additional session would cause the number of active sessions to exceed the value specified by `<max-active-sessions/>`.
In the new implementation, `<max-active-sessions/>` is used to enable session passivation. If session creation would cause the number of active sessions to exceed `<max-active-sessions/>`,
then the oldest session known to the session manager will passivate to make room for the new session.
</message>
<link href="https://access.redhat.com/documentation/en-us/red_hat_jboss_enterprise_application_platform/7.0/single/migration_guide/#migrate_web_session_clustering_changes" title="Web Session Clustering config migration changes in EAP 7" />
<tag>cluster</tag>
<tag>web</tag>
<tag>configuration</tag>
</hint>
</perform>
</rule>
</rules>
</ruleset>