[
https://issues.jboss.org/browse/WFLY-12605?page=com.atlassian.jira.plugin...
]
Brian Stansberry resolved WFLY-12605.
-------------------------------------
Resolution: Won't Do
Won't do. There seems to be some point to this EJB stuff that should perhaps be
restored (but in such a way that the app is still useful in a non-EJB server; e.g.
EJBServlet can have the EJB lookup uncommented by a NNFE is ignored.)
Clean out cruft EJB content from the ear used for web SSO testing
-----------------------------------------------------------------
Key: WFLY-12605
URL:
https://issues.jboss.org/browse/WFLY-12605
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Minor
The application deployed for web SSO testing is an ear that includes an EJB jar. The EJBs
are not used in any tests; the servlets in the EAR do not reference them. (There's
some code commented out in 2012 that indicates there was a plan to, but it's not been
done in 7 years.)
The web.xml sets up some JNDI mappings for the EJBs, but nothing uses those. The ear can
actually deploy just fine in a server without any ejb subystem.
Task is to clean this ejb stuff out so it's more obvious tests using this deployment
are suitable for execution against a slimmed server that does not include ejb support.
Low priority because such tests can actually pass fine without this cleanup; it's
just a source of confusion when trying to understand what's going on if there's
any problem with the test.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)