Hi Jim,

don't make the following mistake: 
"I use Struts but I want to move on, so I have to use Shale!"

Shale is build ON TOP of JSF, so to understand the benefit of Shale you have
to know JSF.
So the first question to ask yourself: 
"Do I want to move to JSF or is Struts just fine for me?"
When you decided to move to JSF or to at least take a closer look at it then
after being familiar with JSF you can look at Shale and see if that's the
right technology for you.
I guess in your case you seem to be fine with Struts, so just stay with it!

Bernhard

> -----Ursprüngliche Nachricht-----
> Von: Jim Reynolds [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 29. Dezember 2005 15:10
> An: user@struts.apache.org
> Betreff: How does Shale affect my Struts development
> 
> 
> First off, a little background. I have started using the 'Struts'
> framework about 1 year ago. I have created three apps, and all is
> moving along pretty well with the Struts and model 2 approach. I am
> just starting to use more design patterns for my business logic, etc.
> 
> Anyway, as you may be aware I frequent this list, and try to keep up
> with what is going on with the Struts project.
> 
> I am noticing a lot of 'Shale' discussion, and I have just finished
> reading the link here <http://struts.apache.org/struts-shale/> and
> franky, I am not sure what Shale brings to the table that is not
> already included with Struts?
> 
> I guess, the reason for this post is, I was hoping possibly there are
> people out there who understand this Struts/Shale and could tell me
> how to get started, and what the gain is. Whether the best approach is
> to build a simple Struts app and convert it, or what steps I need to
> take in order to be prepared and keep my skill set where it needs to
> be.
> 
> Regards
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to