[
https://issues.apache.org/jira/browse/TOMEE-4580?focusedWorklogId=1004770&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1004770
]
ASF GitHub Bot logged work on TOMEE-4580:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Feb/26 09:35
Start Date: 12/Feb/26 09:35
Worklog Time Spent: 10m
Work Description: jungm commented on PR #2470:
URL: https://github.com/apache/tomee/pull/2470#issuecomment-3889774686
@RedN4ks I'd have cherry picked this anyways once merged but you can of
course also open a second PR :slightly_smiling_face:
Issue Time Tracking
-------------------
Worklog Id: (was: 1004770)
Time Spent: 0.5h (was: 20m)
> Improve clarity of conf.0008 deployment mismatch error
> ------------------------------------------------------
>
> Key: TOMEE-4580
> URL: https://issues.apache.org/jira/browse/TOMEE-4580
> Project: TomEE
> Issue Type: Improvement
> Affects Versions: 10.1.4
> Reporter: Skander
> Assignee: Skander
> Priority: Minor
> Fix For: 10.1.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The conf.0008 message only reports the number of deployed beans
> versus the number declared in ejb-jar.xml, without indicating which beans
> were involved. The current message is the following:
> {code:java}
> Cannot Load jar {0}. The number of beans deployed ({2}) does not match the
> number of beans actually in the jar ({1}). Please redeploy this jar.{code}
> I propose to enhance the log message by explicitly listing:
> - The deployed bean names
> - The bean names declared in ejb-jar.xml
> This provides better diagnosability when investigating bean count mismatches
> and reduces troubleshooting time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
