On 10/3/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote: > > Thanx David, Gary. > > On 10/4/05, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > > The use-case application's purpose is to demo the requirements of a > specific > > feature of Shale. We have not built an example using all the Shale > > features. > > > > Shale is a framework built on top of JSF. It provides value added > features > > that are not in the vanilla API. If you are not fimillar with JSF, you > will > > really have a hard time seeing the value added features of Shale. > > I was hoping to find an example application like the mailreader (I > thought it has been rewritten for Shale, at least someone was > announcing it on the list). > Nevermind, I will start with myfaces, and move to shale afterwards :-)
For the record, that (shale-mailreader) is definitely on the agenda ... we had a volunteer, but so far that hasn't produced anything more than I've been able to do myself. > > > > One thing I noticed, every link (in the resulting html) is a form > > > submition. Is there a way to configure it? > > > .... > > > >Because, if not, it would > > > be an absolute NOGO, since it would make the site uncrawlable (at > > > least for modern search engines). > > > > > > > I would think that for most web applications, you wouldn't want a user > to > > attempt to jump into the middle of a dynamic web application without a > > context within the flow of the application? > > You mean, coming in with a non-functional link with some parameters? > That's not a problem, you can detect it pretty early in the base > action (filter whatever). The problem is, that if all your links are > posts, you will be considered as not-interesting content by the search > engine (only one url, different context). In a B2C business it's a > kind of death... As others have said, that particular issue is inherited from Shale's dependence on JSF. If you don't like POST-only webapps, you'll want to look elsewhere. On the other hand, being worried about whether a search engine will index pages of a dynamic web application (as oppposed to a primarily static web application that might have some dynamic aspects) seems like a contradictory set of motivations :-). In particular, you will most likely not like *any* Java based web application framework based on using RequestDispatcher.forward() -- including Struts, for example, because the URL that the client thinks it is indexing is *not* the URL of the action that actually produced the content of that page. > > > > Where is the best place to start with Shale? > > > > > > > There is some information here: > > http://struts.apache.org/shale/index.html > > was my first try too :-) I thought there was a Wiki page? Didn't found > any. There is a Wiki page: http://wiki.apache.org/struts/StrutsShale but it doesn't currently have any pointers to completed applications using the technoogy. > > > You might pick up one of the many books published on JSF. My favorite is > > coauthored by one of the Struts committers (David Geary - Core > JavaServer > > Faces, ISBN 0-13-146305-5). > > Hmm yes, but isn't David a RoR convert now? He definitely likes RoR, but he's also a Struts committer that has contributed significantly to Shale :-). In particular, he's been particularly active in the integration with Commons Validator and with Tiles. Anyway, thanx for your time :-) > > leon Craig
