struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From (Gary VanMatre)
Subject Re: [Shale]Newbie question
Date Tue, 04 Oct 2005 01:27:59 GMT
> after long time of scepticism I decided to try out Shale. I downloaded 
> the shale nightly and installed it on my tomcat 5.0.28. Somehow it was 
> not very satisfying. The struts-shale-usecases runs (or I suppose it 
> to run) with a lot of warnings, but dont give the example, an 
> application developer need. Are there other example applications? 

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.

> One thing I noticed, every link (in the resulting html) is a form 
> submition. Is there a way to configure it? 

The commandLink component is used on the usecases entry point menu page. A outputLink could
also be used which generates a HTML anchored tag.  

The one reason that the commandLink navigation was used in the usecase menu page was to demonstrate
the use of the ContextRelativePathFilter.  In this example, it restricts direct access to
*.jsp and *.jspf resources.  

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

> Where is the best place to start with Shale? 

There is some information here:

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).

> regards 
> Leon 


> P.S. Sorry for not WiKiing, but it has been a very long day, so asking 
> was easier :-( 
> --------------------------------------------------------------------- 
> To unsubscribe, e-mail: 
> For additional commands, e-mail: 
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message