Thank's again for the answers so far.
To clarify some things:
> As I understand it, the Tapestry site is a dynamic application - IMO
> combining dynamic webapps with CMSs for static content is a quite
> typical approach.
Tapestry consists basically out of three things:
- Page Class
- HTML Template
- Page Specification
In the HTML Template you would find something like that:
<p>Now is <span jwcid="now">8:27, the 1st of April 2007</span>.</p>
jwcid means Java Web Component ID. If the code is running this part
will be replaced by the component with the name "now"
The pace specification looks like that:
<page-specification class="com.devshed.tapestry.first.Home">
<component id="now" type="Insert">
<binding name="value" value="currentDate"/>
</component>
</page-specification>
"com.devshed.tapestry.first.Home" is the Java Class associated with the
component.
The component is specified with:
<component id="now" type="Insert">
<binding name="value" value="currentDate"/>
</component>
The Java class itself then has a method:
public Date getCurrentDate() {
return new Date();
}
That's the basic idea.
Maybe this helps to clarify the things a bit.
-----Ursprüngliche Nachricht-----
Von: news [mailto:[EMAIL PROTECTED] Im Auftrag von Andreas Hartmann
Gesendet: Donnerstag, 3. Januar 2008 10:11
An: [email protected]
Betreff: Re: AW: Apache Lenya and Tapestry 4
Jörn Nettingsmeier schrieb:
> Andreas Hartmann wrote:
>> If you want WYSIWYG across multiple applications, I'd recommend the
>> following basic principles:
>>
>> - Keep the templates as simple as possible.
>> - Avoid duplicating template logic. If you have to duplicate them, try
>> to generate them automatically from a single source (meta templates).
>> - Do everything you can in CSS. CSS can be shared.
>>
>> In your specific case, I'd try to strip down the Tapestry templates to a
>> very basic XHTML structure, which can be duplicated in the Lenya
>> application with low maintainance costs.
>
> why would anyone want to do that? if you are prepared to touch and
> refactor existing templates, why not just migrate to lenya (or another
> CMS) entirely? or is there something special that only tapestry can do?
As I understand it, the Tapestry site is a dynamic application - IMO
combining dynamic webapps with CMSs for static content is a quite
typical approach. But of course I can't tell if it makes sense in this
special scenario here.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
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]
