https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #5 from Mark Thomas ---
(In reply to Phillip from comment #4)
> Mark, what do you mean by "delay the transformation until the the class is
> declared"? Does this mean moving the transformation code from
> WebAppClassLoader to a
https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #4 from Phillip ---
The solution that I had was to completely disable the scanning by adding an
empty tag into my web.xml. This obviously means that
there is no way to have both my Spring/persistent unit class transformation
al
https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #3 from Nick Williams ---
I will think about this some. Off the top of my head, I don't know what the
answer is, but it sure would be nice if there were a solution.
--
You are receiving this mail because:
You are the assignee
https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #2 from Mark Thomas ---
Happy to leave this closed but I wanted to add the following comments:
1. If the transformation attempts to make a change that would trigger something
in the annotation scanning then that change is going
https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
Phillip changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=57274
--- Comment #1 from Phillip ---
I think that this issue can be closed. The problems that I highlighted below
are a necessary outcome of Tomcat needing to scan for
ServletContainerInitializers in the web application. It does this by looping
