That was it! It makes sense - but I thought there was likely some translation being done there and so never even considered that this time around ... great!

Thanks Robert.

-Luther



On Oct 5, 2008, at 12:43 AM, Robert Zeigler wrote:

Almost guaranteed that you're running into casing issues.
Windows is case insensitive with respect to filenames. Linux is not.
Check to make sure that your template files and your java files have the same casing for their names.
That is:
On windows:
Index.java and index.tml will work, but on linux, that will cause the exception that you see.
You need Index.java and Index.tml.
Internally, Tapestry is mostly case insensitive; this is one situation, however, where case does matter.

Robert

On Oct 5, 2008, at 10/512:37 AM , Luther Baker wrote:

This is very strange.
I just deployed to Jetty and I am getting the same error. If anyone has a
second, please feel free to take a look:

http://www.effectiveprogramming.com/effprog-web/

Development works just fine [eclipse + ganymede + m2 plugin].
I can run the application locally via (Tomcat / WTP) or (mvn jetty:run).

If I build the war (mvn clean install) I can drop the resulting war directly
into my local TOMCAT 6's webapps directory and it fires up.

I have root on the VPS (CentOS) - so I've installed and running jdk 1.6.07 and tomcat 6.0.18. I just installed maven 2.0.9 and ran (mvn clean install jetty:run) and the app fires up. I can see Tapestry kick in with its unique logging ... but then ... I get the page saying it can't find the templates.

I am running everything as tomcat on the machine at port 8080. Port 80 is being redirected to it. If I were to leave Tomcat up - my other servlet application continues to work. I can't for the life of me determine why Tapestry cannot find the files? I will leave the Jetty version up if anyone has time to take a look.Permissions on the files are generally 664 or 775
... and maven is building it right on the box (same JVM) and I'm just
baffled.

Thoughts?

-Luther




On Sat, Oct 4, 2008 at 9:13 PM, Luther Baker <[EMAIL PROTECTED]> wrote:

I've been developing with the m2 maven plugin.
I have both Tomcat via WTP and Jetty via mvn jetty:run working within
eclipse.

I just built the war from the command line via "mvn install" and deployed
it to a tomcat webserver and getting an error on the first page:

Page Index did not generate any markup when rendered. This could be because its template file could not be located, or because a render phase method in
the page prevented rendering.

If I open the war up, the *.tml files are there. The Java classes are in the WEB-INF/classes directory. The properties files are there. It all looks like a well-formed war. Any ideas as to where what this error might be
indicating?

Thanks in advance for any suggestions.

-Luther



Stack trace

 -
org .apache .tapestry5 .internal .services .PageMarkupRendererImpl .renderPageMarkup(PageMarkupRendererImpl.java:67)
 -
org .apache .tapestry5 .internal .services .PageResponseRendererImpl .renderPageResponse(PageResponseRendererImpl.java:57)
 -
org .apache .tapestry5 .internal .services .PageRenderRequestHandlerImpl .handle(PageRenderRequestHandlerImpl.java:59)
 -
org.apache.tapestry5.services.TapestryModule $29.handle(TapestryModule.java:1653)
 -
org .apache .tapestry5 .internal .services.PageRenderDispatcher.process(PageRenderDispatcher.java:97)
 -
org .apache .tapestry5 .internal .services.PageRenderDispatcher.dispatch(PageRenderDispatcher.java: 73)
 -
org.apache.tapestry5.services.TapestryModule $13.service(TapestryModule.java:953)
 -
com.effectiveprogramming.effprog.services.TapestryModule $1.service(TapestryModule.java:106)
 -
org .apache .tapestry5 .internal .services.LocalizationFilter.service(LocalizationFilter.java:42)
 -
org.apache.tapestry5.services.TapestryModule $2.service(TapestryModule.java:586)
 -
org .apache .tapestry5 .internal .services.RequestErrorFilter.service(RequestErrorFilter.java:26)
 -
org .apache .tapestry5 .internal .services.StaticFilesFilter.service(StaticFilesFilter.java:79)
 -
org.apache.tapestry5.internal.services.CheckForUpdatesFilter $2.invoke(CheckForUpdatesFilter.java:93)
 -
org.apache.tapestry5.internal.services.CheckForUpdatesFilter $2.invoke(CheckForUpdatesFilter.java:84)
 -
org .apache .tapestry5 .ioc .internal.util.ConcurrentBarrier.withRead(ConcurrentBarrier.java:83)
 -
org .apache .tapestry5 .internal .services.CheckForUpdatesFilter.service(CheckForUpdatesFilter.java: 106)
 -
org.apache.tapestry5.services.TapestryModule $12.service(TapestryModule.java:933)
 -
org .apache .tapestry5 .internal .services.IgnoredPathsFilter.service(IgnoredPathsFilter.java:62) - org.apache.tapestry5.TapestryFilter.doFilter(TapestryFilter.java: 177)
 -
org .apache .catalina .core .ApplicationFilterChain .internalDoFilter(ApplicationFilterChain.java:235)
 -
org .apache .catalina .core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java: 206)
 -
org .apache .catalina .core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
 -
org .apache .catalina .core.StandardContextValve.invoke(StandardContextValve.java:175)
 -
org .apache .catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
 -
org .apache .catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
 -
org .apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java: 568)
 -
org .apache .catalina.core.StandardEngineValve.invoke(StandardEngineValve.java: 109)
 -
org .apache .catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
 -
org .apache.coyote.http11.Http11Processor.process(Http11Processor.java: 844)
 -
org.apache.coyote.http11.Http11Protocol $Http11ConnectionHandler.process(Http11Protocol.java:583)
 -
org.apache.tomcat.util.net.JIoEndpoint $Worker.run(JIoEndpoint.java:447)
 - java.lang.Thread.run(Thread.java:619)





---------------------------------------------------------------------
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]

Reply via email to