...
Cleanup - Notably
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-5 Now looking at
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1927 Engaging with JISC and Canarie Support Team on requirements
Nature study under way
Scott
Started on getting a Xerces patch out the door, to pick up some memory leak patches and other fuzzing issues. No immediate plans for an SP release, just getting it done in case.
Finished? the refactor/rename in the support classes.
Have some remaining ideas for improvement but since everything has been rehomed, the breakage can’t get worse.
Redesigned the use of web.xml to deal with the prevelance of class names
Old filter references are stubs for the V5 release, will be removed in V6
3 new context initializers are exposed via idp-conf-impl
One installs the Spring listener and context-init parameters (enabled via a new context parameter)
One installs the filters via a new “chaining” filter that calls other filters, defined via Spring (filters.xml)
The new filters can influence relative order Apache style
Enabled by default, old filters are no-ops or harmless, can be disabled via a context parameter for testbed
One installs the servlets (individual context parameters to enable/disable each)
Subject to testing, should be backward compatible with V4 web.xml
...