WebLogic closed my SR, SR 3-3688679421.
However, I stand by my finding that the issue appears to be with WebLogic seeking a hint with the page encoding.
I can report that v1.5.6 works in WebLogic 10.3.3.0 after setting the page encoding in the jsp descriptor, as I noted earlier in
STS-823. We had the same problems every one is reporting. After some research, we added the jsp-descriptor and it solved the problem; no page directives, just the jsp-descriptor.
We are doing at least one thing that might be "helping" WebLogic a bit more:
Our POM explicitly declares the project encoding as UTF-8, <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
Maybe this helps our fairly standard, text book, use of Stripes Layouts.
We have dived into the generated source and found some clever optimizations, but nothing that seemed to scream a WebLogic or Stripes fault. Ben reports the Layout refactoring "abuses the JSP APIs," nothing more.
If there is a WebLogic fault it may be something in changes to the platform defaults that certain switches seem to control, but the WebLogic tech I worked with tried a number of things, including "honoring WEB-INF jars over WLS classpaths," etc.
I can see if Oracle will reopen the ticket, but it's doubtful. If any of you have Oracle support contracts, consider opening a ticket. Cite SR 3-3688679421,
STS-823 and this one. My tech raised it to the "engineering level" but it went no where after at least a cursory review by said engineers, citing no support for third party JARs, etc.
Maybe more customers seeing a problem will move the issue to engineering.