thanks, it worked (removing the portlet jar)
On 2-Aug-05, at 072507, Ron Piterman wrote:
This is a classpath problem.
If you don't need it, remove the tapestry protlet jar from your
class path.
If you do need it, add the dependencies (portlet api jar?).
Cheers,
Ron
ציטוט X. Y. Zhao:
The reason i did not post any log information is because these
exception pages seem to be absent on any general exception.
Exceptions such as "Unable to process client request: Unable to
read OGNL expression", or "Unable to process client request:
Template for component Home contains multiple references to
embedded component formX.", are no longer reported in the browser.
The report i get in the browser is the standard tomcat servlet
exception report. The stack trace:
javax.servlet.ServletException: Unable to construct service
tapestry.describe.DescribableStrategy: Unable to construct
configuration tapestry.describe.DescribableStrategies: Error at
jar:file:/Volumes/black/opt/share/jakarta-tomcat-4.1.31/webapps/
davinci/WEB-INF/lib/tapestry-portlet-4.0-beta-3.jar!/META-INF/
hivemodule.xml, line 297, column 105: Unable to process attribute
class (of element strategy): Unable to convert type
'javax.portlet.PortletSession' to a Java class, either as is, or
in package org.apache.tapestry.portlet.
at
org.apache.tapestry.services.impl.WebRequestServicerPipelineBridge.se
rvi ce(WebRequestServicerPipelineBridge.java:60)
at $ServletRequestServicer_105725e66a6.service
($ServletRequestServicer_105725e66a6.java)
at $ServletRequestServicer_105725e66a5.service
($ServletRequestServicer_105725e66a5.java)
at org.apache.tapestry.request.DecodedRequestInjector.service
(DecodedRequestInjector.java:55)
at $ServletRequestServicerFilter_105725e66a2.service
($ServletRequestServicerFilter_105725e66a2.java)
at $ServletRequestServicerFilter_105725e66a1.service
($ServletRequestServicerFilter_105725e66a1.java)
at $ServletRequestServicer_105725e66a7.service
($ServletRequestServicer_105725e66a7.java)
at
org.apache.tapestry.multipart.MultipartDecoderFilter.service
(MultipartDecoderFilter.java:52)
at $ServletRequestServicerFilter_105725e66a0.service
($ServletRequestServicerFilter_105725e66a0.java)
at $ServletRequestServicerFilter_105725e669f.service
($ServletRequestServicerFilter_105725e669f.java)
at $ServletRequestServicer_105725e66a7.service
($ServletRequestServicer_105725e66a7.java)
at
org.apache.tapestry.services.impl.SetupRequestEncoding.service
(SetupRequestEncoding.java:53)
at $ServletRequestServicerFilter_105725e66a4.service
($ServletRequestServicerFilter_105725e66a4.java)
at $ServletRequestServicerFilter_105725e66a3.service
($ServletRequestServicerFilter_105725e66a3.java)
at $ServletRequestServicer_105725e66a7.service
($ServletRequestServicer_105725e66a7.java)
at $ServletRequestServicer_105725e669a.service
($ServletRequestServicer_105725e669a.java)
at $ServletRequestServicer_105725e6699.service
($ServletRequestServicer_105725e6699.java)
at org.apache.tapestry.ApplicationServlet.doService
(ApplicationServlet.java:145)
at org.apache.tapestry.ApplicationServlet.doGet
(ApplicationServlet.java:101)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:696)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:809)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:200)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:146)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:209)
at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:948)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:144)
at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:948)
at org.apache.catalina.core.StandardContext.invoke
(StandardContext.java:2358)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:133)
at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke
(ErrorDispatcherValve.java:118)
at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:116)
at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:948)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:127)
at org.apache.catalina.core.StandardPipeline
$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596)
at org.apache.catalina.core.StandardPipeline.invoke
(StandardPipeline.java:433)
at org.apache.catalina.core.ContainerBase.invoke
(ContainerBase.java:948)
at org.apache.coyote.tomcat4.CoyoteAdapter.service
(CoyoteAdapter.java:152)
at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol
$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt
(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable.run (ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:613)
On 1-Aug-05, at 100508, Howard Lewis Ship wrote:
The exception pages are absolutely still in place. So, what you
need
to do is TAKE THAT INFORMATION IN THE LOGS and actually supply it to
this list. We are not mind readers.
On 8/1/05, X. Y. Zhao <[EMAIL PROTECTED]> wrote:
hello,
i've started using tapestry 4, and the most noticeable
difference is
the exception reporting pages from tap3 have dissappeared. it
seems
that i now have to read the log files in order to find out what
caused the exception and how to resolve things.
when do we expect to have these exception pages restored (as
they are
very useful for development purposes)?
thanks
-------------------------------------------------------------------
--
To unsubscribe, e-mail: tapestry-user-
[EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: tapestry-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
