We're beginning the gradual process of converting our app over to
wicket. Since there isn't time to recreate our navigation menu in
wicket right now, I tried including the menu JSP in the wicket page
using the technique at
http://herebebeasties.com/2007-03-01/jsp-and-wicket-sitting-in-a-tree/.
It worked great in OC4J 10.1.2, but we've also starting moving over to
OC4J 10.1.3. When I load the same page in 10.1.3, the nav menu loads
but instead of the rest of the wicket page, An exception prints:
java.lang.IllegalStateException: OutputStream already
retrieved at com.evermind[Oracle Containers for J2EE 10g
(10.1.3.2.0)
].server.http.EvermindHttpServletResponse.getWriter(EvermindHttpServletResponse.java:917)
at
wicket.protocol.http.WebResponse.write(WebResponse.java:315) at
wicket.protocol.http.BufferedWebResponse.close(BufferedWebResponse.java:75)
at
wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:229) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at
javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:712)
at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:369)
at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:865)
at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:447)
at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:215)
at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.HttpRequestHandler.run(HttpRequestHandler.java:117) at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].server.http.HttpRequestHandler.run(HttpRequestHandler.java:110) at
oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at
oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at
oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at
oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at
com.evermind[Oracle Containers for J2EE 10g (10.1.3.2.0)
].util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at
java.lang.Thread.run(Thread.java:595)
It looks like OC4J changed something in the include() call of the
RequestDispatcher, which is either doing output or just calling an
OutputStream. I have no access to the source to confirm this however.
Regardless, it's doing something the break the rest of the page.
Obviously this is an issue with OC4J, but I was hoping someone here had
some answers or insight into the problem. Or, failing that, and
alternate solution for including JSP into wicket.
Currently we're using wicket 1.2.5. We love wicket so far. It really
makes sense to separate the programming logic from the presentation
layer (putting the code in Java where it belongs). Sifting through the
all the JSP code interspersed within the HTML was becoming a real chore.
Keep up the good work with this framework.
Joel
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
