[
https://issues.apache.org/jira/browse/TOMEE-4456?focusedWorklogId=957075&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-957075
]
ASF GitHub Bot logged work on TOMEE-4456:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 14/Feb/25 09:29
Start Date: 14/Feb/25 09:29
Worklog Time Spent: 10m
Work Description: struberg opened a new pull request, #1785:
URL: https://github.com/apache/tomee/pull/1785
plz review. Will commit after review.
Issue Time Tracking
-------------------
Worklog Id: (was: 957075)
Remaining Estimate: 0h
Time Spent: 10m
> beans.xml <trim/> doesn't work in openejb-core boot
> ---------------------------------------------------
>
> Key: TOMEE-4456
> URL: https://issues.apache.org/jira/browse/TOMEE-4456
> Project: TomEE
> Issue Type: Bug
> Components: TomEE Core Server
> Affects Versions: 8.0.16, 10.0.0
> Reporter: Mark Struberg
> Assignee: Mark Struberg
> Priority: Critical
> Fix For: 8.0.17
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It seems that a {{<trim/>}} in beans.xml does work when starting tomee in
> Tomcat but not when just using openejb-core for the bootstrap (via JNDI e.g.).
> In Tomcat we use the {{DeploymentLoader#mergeBeansXml}} which has the
> following code:
> {source}
> if ("ALL".equalsIgnoreCase(beanDiscoveryMode) && beans.isTrim()) {
> beanDiscoveryMode = "TRIM";
>
}
> {source}
> A similar path isn't here for the standard boot process in openejb-core e.g.
> in {{EJBJarInfoBuilder#239}}
> That means that we effectively pick up different CDI beans when running unit
> tests vs running in the real Tomcat later on.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
