[ 
https://issues.apache.org/jira/browse/ROL-2183?focusedWorklogId=1035286&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1035286
 ]

ASF GitHub Bot logged work on ROL-2183:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Aug/26 23:10
            Start Date: 11/Aug/26 23:10
    Worklog Time Spent: 10m 
      Work Description: mraible commented on PR #154:
URL: https://github.com/apache/roller/pull/154#issuecomment-5259915440

   The CI failures here predate the latest push: both runs failed the same way, 
with the it-selenium test meeting a 503 because the webapp never actually 
deployed. Debugging that locally turned up a chain of real migration bugs that 
the branch's only container test had been hiding, now fixed in the last four 
commits:
   
   - The Jetty 12 plugin renamed `jettyXml` to `jettyXmls` and silently ignored 
the old name, so the it-selenium harness never loaded jetty.xml, never bound 
the JNDI datasource, and never started the Derby network server (`Nothing to 
bind for name jdbc/rollerdb` in the earlier run's log).
   - webjars-servlet-2.x extends the javax `HttpServlet`, so on a Jakarta 
container it threw `NoClassDefFoundError` at startup and took the whole context 
down. WebJar assets are now served natively from `META-INF/resources` at the 
same `/webjars` paths.
   - Spring Security 7's XML config authorizes through `AuthorizationManager`, 
which denies requests that match no `intercept-url` rule; the old 
`FilterSecurityInterceptor` allowed them. Every unlisted URL, including the 
login page itself, redirected to the login page in a loop. An explicit `/**` 
permitAll rule restores the old behavior.
   - struts2-bootstrap-plugin had been removed as an unused taglib, but it also 
supplies the FreeMarker templates behind the `theme="bootstrap"` attribute that 
nearly every form JSP uses, so any page with a form failed with 
`TemplateNotFoundException`. The Jakarta-native 6.1.0 restores the theme; it 
emits Bootstrap 5 markup against the current Bootstrap 3 CSS, so some form 
styling is off until a follow-up converts the UI to Bootstrap 5.
   
   The full Selenium journey (register, log in, create a weblog, publish an 
entry) and the 157 unit tests pass locally on this branch after these changes.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1035286)
    Time Spent: 20m  (was: 10m)

> Migrate from javax to jakarta namespace (Jakarta EE 9+)
> -------------------------------------------------------
>
>                 Key: ROL-2183
>                 URL: https://issues.apache.org/jira/browse/ROL-2183
>             Project: Apache Roller
>          Issue Type: Improvement
>            Reporter: Matt Raible
>            Assignee: Matt Raible
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Roller currently uses Java EE 8 APIs with the {{javax.\*}} namespace (Servlet 
> API 4.0.1, JavaMail, JSP, JAXB, javax.activation). The JPA layer has been 
> partially migrated to {{jakarta.persistence}}, but the rest of the codebase 
> remains on {{javax.\*}}.
> This issue tracks the full migration to the {{jakarta.\*}} namespace to 
> support Jakarta EE 9+ and modern servlet containers like Tomcat 10+.
> *Scope of changes:*
> * \~305 {{javax.\*}} imports across the codebase (servlet, JSP, mail, 
> activation, XML bind)
> * \~31 {{jakarta.persistence}} imports already in place (JPA managers)
> * Servlet API dependency: {{javax.servlet:javax.servlet-api:4.0.1}} -> 
> {{jakarta.servlet:jakarta.servlet-api:5.0+}}
> * JavaMail: {{javax.mail}} -> {{jakarta.mail}}
> * JSP: {{javax.servlet.jsp}} -> {{jakarta.servlet.jsp}}
> * JAXB: {{javax.xml.bind}} -> {{jakarta.xml.bind}}
> * {{javax.activation}} -> {{jakarta.activation}}
> * Update {{web.xml}} and any deployment descriptors
> * Update third-party dependencies to Jakarta-compatible versions



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to