AW: [ANNOUNCE] New Shale PMC Chair
-Ursprüngliche Nachricht- Von: Gary VanMatre [mailto:[EMAIL PROTECTED] Gesendet: Montag, 24. März 2008 19:31 An: user@shale.apache.org Betreff: RE: [ANNOUNCE] New Shale PMC Chair From: [EMAIL PROTECTED] Congrats Gary! I hope Shale restart the development. Yeah, I have a few new Clay ideas but all are JSF 1.2ish. I also hope that Shale has some future (that were my last words at the JSF days presentation about Shale: It's not yet dead !). For the Clay vs. Facelets: I think one major problem is really the confusing naming (HTML, full HTML, full XML ...) and documentation of Clay, there should be put some effort in there. Bernhard
Shale Status
Hi all, I make a small presentation about Shale in the JSF Days in Vienna, for that I'd like to have some information about the current status of Shale. I just went through the maillist, but it's a bit difficult to find hard facts. So my questions are the following - Next Shale relaese Right now there is no plan for a Shale 1.0.5 release right? Corresponding thread: http://markmail.org/message/nagpn7igxeowjtx6?q=org%2Eapache%2Eshale%2Edev - What goes where? There was this thread: http://markmail.org/message/3ws5fzthj2yfdjjp?q=org%2Eapache%2Eshale%2Edev+list:org%2Eapache%2Eshale%2Edev But there was no final decision on what goes where, so is it still open, or is there a decision? - Shale itsself Will it disappear as an Apache Top Level project? Cheers Bernhard
AW: MyFaces
-Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Auftrag von Craig McClanahan Gesendet: Samstag, 20. Oktober 2007 12:18 An: user@shale.apache.org; [EMAIL PROTECTED] Betreff: Re: MyFaces ... that I'm not particularly interested in spending my personal time on Java related frameworks :-). The captain left, the ship seems to sink ...
RE: Clay templating
-Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] I'll try to give you some more background. There are three types of clay templates. !-- Clay HTML View Suffix (default .html) -- context-param param-name org.apache.shale.clay.XML_TEMPLATE_SUFFIX /param-name param-value.fhtml/param-value /context-param Html templates use and extend common elements. This type of template can be a fragment or the entire page. If the template is the entry point to the page, it must be a physical resource meaning that it can't be a pseudo tiles like resource that doesn't exist. * The next type of template are what we call full XML views. For this type of template, the page entry point is a clay XML configuration definition. The default suffix of a full XML view is .xml but can be changed using a web.xml context param. !-- Clay XML View Suffix (default .xml) -- context-param param-name org.apache.shale.clay.XML_TEMPLATE_SUFFIX /param-name param-value.html/param-value /context-param !-- Clay Configuration Full XML view Resources -- context-param param-name org.apache.shale.clay.FULLXML_CONFIG_FILES /param-name param-value/WEB-INF/clay-tiles-config.xml/param-value /context-param This option is similar to Tiles. The page entry point is not a physical resource but a metadata definition. Gary, thanks a lot for the answer. This is nearly a full blonw tutorial you gave me here. I was trying it out and it's working fine. So I use one configuration file /WEB-INF/clay-config.xml for both my common and my full XML view resources. !-- Clay Common Configuration Resources -- context-param param-name org.apache.shale.clay.COMMON_CONFIG_FILES /param-name param-value /WEB-INF/clay-config.xml /param-value /context-param !-- Clay Configuration Full XML view Resources -- context-param param-name org.apache.shale.clay.FULLXML_CONFIG_FILES /param-name param-value /WEB-INF/clay-config.xml /param-value /context-param The former start.html is replaced by an entry in the jsfid in my component defintion. component jsfid=/start.xml extends=basePage symbols set name=@title value=Application Home / set name=@bodycontent value=/startBody.html / /symbols /component One small thing, I guess it's a typing or copy and paste error. You metioned the same context parameter for the HTML views and for the full XML views, I guess the HTML view parameter is wrong. But in the turtorial I couldn't find the name of the context parameter of the HTML view suffix. What is it? !-- Clay HTML View Suffix (default .html) -- context-param param-name org.apache.shale.clay.XML_TEMPLATE_SUFFIX /param-name param-value.fhtml/param-value /context-param Bernhard
AW: Clay templating
Rich, thanks for the answer. I use an HTML page not a JSP page (Clay HTML View). This is useful because I don't need to define a separate component for every page. Ist this possible (to set the values of the symbols) for an HTML View too? Bernhard -Ursprüngliche Nachricht- Von: Richard Eggert [mailto:[EMAIL PROTECTED] Gesendet: Montag, 26. Februar 2007 12:30 An: user@shale.apache.org Betreff: RE: Clay templating Let me see if I'm understanding you properly. Do you also have a corresponding JSP page (start.jsp) to load the HTML template? If so, it can contain an element like this: clay:clay jsfid=basePage clay:symbol name=title value=Application Home / clay:symbol name=bodyContent value=/startBody.html / /clay This is instead of doing clay:clay jsfid=startPage / (i.e., startPage isn't strictly necessary). Does this help? Rich Eggert Member of Technical Staff Proteus Technologies, LLC http://www.proteus-technologies.com -Original Message- From: Bernhard Slominski [mailto:[EMAIL PROTECTED] Sent: Mon 2/26/2007 6:14 AM To: 'user@shale.apache.org' Subject: Clay templating Hi all, I use Clay to build my pages with templates. I have a base page, all my actual pages are derived from the base page. My clay-config.xml looks like this component jsfid=basePage extends=clay attributes set name=clayJsfid value=/templates/layout.html / /attributes symbols set name=@title value=Default Title / set name=@headercontent value=/templates/header.html / set name=@bodycontent value=space / set name=@footercontent value=/templates/footer.html / /symbols /component component jsfid=startPage extends=basePage symbols set name=@title value=Application Home / set name=@bodycontent value=/startBody.html / /symbols /component The problem is my actual page start.html it looks like this: span jsfid=startPage/ So the issue I'm having is that for every page I need two files start.html startBody.html The start.html page only calls the startPage clay component. So I'd like to have only one file which contains my body. Are there any possibilties to do this? Thanks Bernhard
AW: AW: Clay Using Taglibs (e.g validation)
-Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Hermond, thanks for the answer. This looks not so difficult. I'm glad you said that it didn't look difficult. It sounds like you are also a believer that inheritance should be part of object oriented programming even as it relates to presentation (visual metadata inheritance :-). When trying to get the E-Mail validation working it turned out to be a bit painful, because even in the Clay usecases it's not working correctly. The reason was just a missing jar file, I added it to the Issue Tracker (http://issues.apache.org/struts/browse/SHALE-407). Concerning inheritance in the presentation layer, I'm sure it makes sense and it's a useful concept. Gary, also thanks for the other links. Bernhard
AW: Clay Using Taglibs (e.g validation)
Hermond, thanks for the answer.
This looks not so difficult.
Bernhard
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 9. Februar 2007 14:03
An: user@shale.apache.org
Betreff: RE: Clay Using Taglibs (e.g validation)
Hi
You need to configure these as Clay components. Have a look
at some of the Clay sample apps, specifically the
clay-config.xml files. To integrate other libs, there must be
a mapped clay-config file for them, or you need to run the
Tld2ClayCfg tool on the tld files for these 3rd party libs.
There is a sample app in the sandbox which demonstrates this.
A sample Clay component definition with validation (using
commons validator) from the shale-clay-usecases:
component jsfid=email extends=inputText id=email
attributes
set name=value
value=[EMAIL PROTECTED] /
set name=size value=30 /
set name=maxlength value=50 /
set name=required value=false /
/attributes
validator jsfid=commonsValidator
attributes
set name=type value=email /
set name=client value=true /
set name=server value=true /
set name=arg
value=#{messages['rolodex.email']} /
/attributes
/validator
/component
Hermod
-Original Message-
From: Bernhard Slominski [mailto:[EMAIL PROTECTED]
Sent: Friday, February 09, 2007 8:58 AM
To: user@shale.apache.org
Subject: Clay Using Taglibs (e.g validation)
Hi,
I want to use the Clay HTML views together with the Shale validation.
How do I integrate the taglib directive
%@ taglib uri=http://shale.apache.org/core; prefix=val %
into my HTML view?
How can I integrate other 3rd Party taglibs?
Bernhard
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that the
DnB NOR Group
cannot accept any payment orders or other legally binding
correspondence with
customers as a part of an email.
This email message has been virus checked by the anti virus
programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * *
