[TAP5-1577] Duplication in operation trace when invoking certain methods

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.3
• Fix Version/s: 5.3
• Component/s: tapestry-ioc
• Labels: exception-reporting
• Assignee: Unassigned
• Reporter: Howard Lewis Ship
• Created: 14/Jul/11 18:06
• Updated: 11/Aug/11 19:57
• Resolved: 11/Aug/11 19:28

Description

Noticed this in another bug (TAP5-1576):

SEVERE: Operations trace:
SEVERE: [ 1] Constructing instance of page class org.apache.tapestry5.corelib.pages.ExceptionReport
SEVERE: [ 2] Realizing service ValueEncoderSource
SEVERE: [ 3] Invoking org.apache.tapestry5.services.TapestryModule.buildValueEncoderSource(Map, InvalidationEventHub) (at TapestryModule.java:2337)
SEVERE: [ 4] Invoking org.apache.tapestry5.services.TapestryModule.buildValueEncoderSource(Map, InvalidationEventHub) (at TapestryModule.java:2337)
SEVERE: [ 5] Determining injection value for parameter #1 (java.util.Map)
SEVERE: [ 6] Collecting mapped configuration for service ValueEncoderSource
SEVERE: [ 7] Invoking method org.apache.tapestry5.jpa.JpaModule.provideValueEncoders(MappedConfiguration, boolean, EntityManagerSource, EntityManagerManager, TypeCoercer, PropertyAccess, LoggerSource) (at JpaModule.java:180).

Notice that [3] and [4] are the same thing; either [4] should be removed, or the "Invoking" on one of the frames should be changed to explain better what's going on.