[
http://www.stripesframework.org/jira/browse/STS-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12333#comment-12333
]
Timothy Stone commented on STS-834:
-----------------------------------
Can you clarify that last part... did you say you recompiled the Stripes JAR
against 1.6? or are you saying that you're executing your project against the
1.6 JDK (I thought that JRockit in 10.3.3.0 was 1.6.0_15-ish).
Also clarify your WLS versions, I suspect you mean 10.3.2.0 and 10.3.4.0, not
10.0.3.x as noted above.
I have an open ticket with Oracle, SR 3-3688679421. Oracle has not closed it
but wants me to reimplement an API to prove something, but I haven't had time
to do so, copied below:
{blockquote}
"I was looking to get more information from engineering on this, but off-hand
it was not clear what the issue might be, and from what we have found so far
they did not believe it necessarily point to a problem in Weblogic. So it is
doubtful they will accept a bug to investigate. Continue forward from a
Weblogic perspective, we may need to figure out how to debug further. This of
course, unfortunately, is not a simple task. What would be ideal is to
replicate the issue without Stripes. Does your team think it might be possible
to replicate with the basic Java functionality without Stripes( e.g.
RequestDispatcher#include)? Any further updates from your findings?"
{/blockquote}
The Oracle engineers are not likely to investigate further at this time, if
only because it seems to be a Stripes issue. I'm on the side of the fence that
this is *not* Stripes but some WLS default that is not obvious. Especially
since the problem is not exhibited in GlasshFish, Tomcat, or Resin.
I'm not sure that replicating the RequestDispatcher#include outside of Stripes
would be an easy task.
It's possible that the suggested fix found in the weblogic.xml for us works
because we compile our project against 1.6. That's an interesting finding. It
could possibly point to a clue to the source of the problem.
--
Please vote 'YES" on STS-833.
> CLONE - Stripes Layouts not working in Weblogic 10.3.3.0
> --------------------------------------------------------
>
> Key: STS-834
> URL: http://www.stripesframework.org/jira/browse/STS-834
> Project: Stripes
> Issue Type: Bug
> Components: Tag Library
> Affects Versions: Release 1.5.4, Release 1.5.5, Release 1.5.6
> Environment: Tested on Windows XP and RHEL.
> Oracle Weblogic 10.3.3.0.
> Tried from Stripes 1.5.3 to 1.5.6
> Reporter: Sander Theetaert
> Assignee: Timothy Stone
> Labels: layout, weblogic
> Fix For: Release 1.5.4, Release 1.5.5, Release 1.5.6, Release
> 1.5.7
>
>
> Stripes layout capabilities are unable to render correctly a layout in Oracle
> Weblogic.
> A simple test case has been tested in Weblogic under Windows and RHEL, both
> in WL 10.3.3.0 version, and in Glassfish.
> It works perfectly in Glassfish, but won't work in WL. Seems that the problem
> is the call to pageContext.include, which Stripes makes, and doesn't result
> in the target JSP being included in the result.
> I'm attaching the test jsp files. When accessing test.jsp it prints "Hello"
> on the screen, but doesn't print the "Default text", neither the "I'm here!"
> strings.
> Both jsp are stored in the root of the WAR file being uploaded to the
> container.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development
