Hi, I had an idea posted to twitter which triggered a short discussion with Romain. For the article I am writing I was looking at our OEJB examples to be able to explain different technical concepts. What I noticed is that some are using the calculator business scenario where others are using the movie fun scenario and so on. My hypothesis here is that our current example page isn't business scenario centric but technology and capability centric.
This is good in some circumstances and might have disadvantages in some other circumstances. Let's take the article I am writing for instance. There I'd like to introduce a single business scenario which can be used throughout the article to explain different technical capabilities (here: TomEE capabilities). Thus the business scenario would introduce the business domain model and so forth and would introduce new technical concepts while advancing throughout the article. The goal would be that after having finished the article the business scenario would have served as an accelerator to understand each newly introduced technical capability. I guess the idea is similar to what you sometimes find people discussing if starting writing a book where the discussion is whether to use one single, integrated example versus multiple isolated examples. I thought whether the following, maybe somehow carzy scenario would makes sense: 1) TomEE user goes to /examples-trunk/ 2) User chooses to either advance into the technical capability track or the business scenario track 2.1) for the technical capability track everything would remain the same 2.2) for the business scenario track the user would get a list of business scenarios to choose from 2.3) lets pretend the user choosen the movie fun business scenario 2.4) While the user advances to the next screen the business domain model, use cases and so on will be introduced (this screen is non-technical, either UML diagrams or BDD scenario could be used to describe the business scenario) 2.5) in the next step the user would now have the ability to define which behaviours should be supported by the business scenario 2.6) the user selects web profile only, persistency based on OpenJPA, REST web services plus arquillian based testing 2.7) while advancing to the next screen the user would now learn how to translate the business domain model into an object model, add persistency and so forth 2.8) the next screen would introduce how to add webservice support 2.9) the next screen would introduce how the finalized application could be deployed and tested using arquillian 2.10) have a final "what you have learned" screen I think the advantage here is that the example would be integrated because of using one single business scenario. The disadvantage might be the comprehensivenes which requires more time to implement such end-to-end examples based on business scenarios. Cheers Daniel
