On Jul 19, 2005, at 11:54 PM, Preston CRAWFORD wrote:

To answer your questions.

#1 - I have tried starting tomcat in that fashion and I still get the
same error. As I explained earlier, I followed the directions here
(http://blog.shadowbox.com/index.php?p=40 ) to try to get this going.
I couldn't get it to work for some reason.

#2 - As far as what I'm trying to accomplish? I'm trying to get
productive in Tapestry as quickly as possible. And in part that means
that in my development environment I can work in a more rapid fashion.
With JSP/Struts, etc. if I make changes to the JSP files I simply have
to create an Ant target that copies the JSP files into the proper
deployment directory and a refresh of the page does the rest. Here I
can't seem to get that working. I want to be able to change templates
and spec files and then be able to see my changes quickly, without
rebuilding the war, throwing it over the wall to the app server, and
restarting.
Can you run Tomcat on your dev machine? Eclipse and the Sysdeo plugin let you point to your workspace for the webapp, so I never copy anything anywhere except when I deploy it to the production server.

#3 - Regarding includes. We have the need to have items like a dynamic
side menu, a dynamic top menu. Items that will be reused over and over
again. And this could just be a lack of understanding of the Tapestry
mindset, but we just haven't been able to figure out how to accomplish
this. I hate to use the JSP paradigm, but in this case you start from
what you know. And what I know is an include. I'm trying to figure out
how to accomplish the same functionality in Tapestry. Basically an HTML
template that can be dropped into any other HTML template, but get
pre-processed the same way as the HTML template it's been included into.
A server side include, for lack of a better term.
You definitely want a @Border component. Here's what mine does:
sets the page title, displays a title in the page, includes a @Menu component, adds a footer, and then renders the body of the page. It's a single line of HTML:

<span jwcid="@Border" title="My Page">

<p>All of this goes in the page itself, but the top title bar, the menu, and the footer get inserted automagically by the @Border component</p>

</span>

Here's the only bad part: you need to do extra stuff to make it viewable as plain HTML without a webapp container running. But if you can deal with having to actually run the webapp to preview, then this works great.

If you'd like the relevant files for my @Menu, @Border (actually, I call it @Skeleton), etc., let me know.

Todd

Reply via email to