[MGNLADMLEG-33] Remove filter definition for EE modules not migrated for 5.2 Created: 24/Oct/13  Updated: 19/Nov/13  Resolved: 18/Nov/13

Status: Closed
Project: Admininterface Legacy 4.x (closed)
Component/s: None
Affects Version/s: 5.1
Fix Version/s: 5.2

Type: Task Priority: Major
Reporter: Eric Hechinger Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLPCK-55 Remove the version handling tasks con... Closed
is related to MGNLSLOCK-26 Remove the version handling tasks con... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:
Epic Link: Enable 4.5 to 5.x upgrade
Sprint: 5.2-rc2

 Description   

Modules

  • SoftLocking
  • Packager
    are out of the 5.2 release (as they need to be migrated) and are not part of the EE bundle.

This generate warn log during startup phase of the server.

As long as these modules are not migrated remove these configuration fron the admin interface module version handler.

2013-11-06 16:03:12,100 WARN  magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl: can't resolve class for node /server/filters/cms/softLocking
java.lang.ClassNotFoundException: info.magnolia.module.softlocking.filters.SoftLockingFilter
	at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
	at java.security.AccessController.doPrivileged(Native Method)
...
2013-11-06 16:03:12,115 WARN  magnolia.jcr.node2bean.impl.Node2BeanProcessorImpl: can't resolve class for node /server/filters/packager
java.lang.ClassNotFoundException: org.mgnl.magnolia.cms.pack.PackagerFilter
	at java.net.URLClassLoader$1.run(URLClassLoader.java:202)


 Comments   
Comment by Eric Hechinger [ 06/Nov/13 ]

Enabling the filter do not prevent this warn log.

Comment by Mikaël Geljić [ 06/Nov/13 ]

1. Ok, well it appears that this shouldn't belong to module adminInterface-legacy, but would rather make sense in migration module (move ticket to MGNLMIGRATION accordingly)
2. Then, it's ok to remove such servlet filters, since they are not particularly configurable and because of the potential side-effect of these ClassNotFoundException on the filter chain.
3. Finally, it seems bundle-parent still depends on 4-5-migration module 1.x !!! We need to point to 2.1-SNAPSHOT there.

Comment by Eric Hechinger [ 18/Nov/13 ]

1. Migration module is only to use for a 4.4.6 to 4.5.x migration.
So the only relevant place for me is to set this task in the adminInterface-legacy module.
3. This is know: see MAGNOLIA-5460.

Comment by Eric Hechinger [ 18/Nov/13 ]

Commit done within MGNLADMLEG-28 (2407183e1bc80488de1192de36a5c4720d7de94b)

Generated at Sun Feb 11 23:08:55 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.