[
https://issues.apache.org/jira/browse/FEDIZ-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17863358#comment-17863358
]
Jamie Mark Goodyear commented on FEDIZ-257:
-------------------------------------------
Updated branch:
Observing strange behavoir with spring security such that
springSecurityFilterChain alias is not registered?
Debug logging is set in security contexts for this to be logged in systests/idp
target/logs/idp.log.
Notes:
SSL seems to be fine.
When debug is turned off we'll observe 403 forbidden, when enabled we observe
404 error.
Happily accepting any directions from spring practioners on how to handle this
scenario.
```
2024-07-05 10:16:35,267 WARN o.s.w.c.s.XmlWebApplicationContext [main]
Exception encountered during context initialization - cancelling refresh
attempt: java.lang.IllegalStateException: No alias 'springSecurityFilterChain'
registered 2024-07-05 10:16:35,268 ERROR o.s.w.c.ContextLoader [main] Context
initialization failed java.lang.IllegalStateException: No alias
'springSecurityFilterChain' registered at
org.springframework.core.SimpleAliasRegistry.removeAlias(SimpleAliasRegistry.java:115)
~[spring-core-6.1.10.jar:6.1.10]
```
> Apache CXF Fediz Tomcat Plugin ver 1.6.1 does not work with Jakarta
> -------------------------------------------------------------------
>
> Key: FEDIZ-257
> URL: https://issues.apache.org/jira/browse/FEDIZ-257
> Project: CXF-Fediz
> Issue Type: Dependency upgrade
> Components: Plugin
> Affects Versions: 1.6.1
> Reporter: Mark
> Priority: Major
> Fix For: 1.6.1
>
>
> The following version of the fediz tomcat plugin was compiled with JDK 1.6
> and uses
> https://cxf.apache.org/fediz-downloads.html
> https://downloads.apache.org/cxf/fediz/1.6.1/
> If using version 1.6.1 with TomEE https://tomee.apache.org/download.html
> I see errors encountering, java.lang.NoClassDefFoundError:
> javax/xml/bind/JAXBException, that indicates the Java JAXB (Java Architecture
> for XML Binding) API is not available in the runtime environment. This issue
> is commonly encountered when running applications on Java versions 9 and
> later, as JAXB was removed from the Java SE platform starting with Java 11.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
