Re: Work on Release 2.6: Maven Archetype and Tutorial Examples

Naveen Chawla <[email protected]> Sat, 19 Jan 2013 00:47:52 +0000
Newsgroups gmane.comp.java.prevayler
Message-ID <CAGs7EcXdqVQ5y-sD0Dw3WYKsedPXu0vT93fLe=wVbwL79aBiBQ@mail.gmail.com>
If included, e105 should come before e103 as it's more basic.

If "Entity" is changed to "Person", "Root" should be changed to "Club".

I've always disliked the "baptism/initiation problem" description. First of
all, it's not really a "problem", it's just the knowledge that nothing
outside the "prevalentSystem" variable can reference anything in the
Prevalent Object upon recovery execution, so I remember it by 3 simple
words:

"Stick to "prevalentSystem" ".

That's all the user has to do.

Both the "baptism/initiation problem" and e105 are derived from this very
simple principle, and so should probably say so.

I don't like it being described as a "common problem". It's not common or
even likely if the manual articulates "stick to "prevalentSystem" ".

------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122912

_______________________________________________
To unsubscribe go to the end of this page: http://lists.sourceforge.net/lists/listinfo/prevayler-discussion
_______________________________________________
"Databases in Memoriam" -- http://www.prevayler.org