Mailing lists are great for discussing matters but I've always found them terrible at documenting things. If the questions on here were put on a web site and answered there I'm sure more people would get the knowledge.
It is also important to distinguish between documenting JEE and documenting TomEE. JEE has a really big learning curve and an equally large architecture. For TomEE should be documented where it exceeds or fails to meet the standards. There is no current documentation for instance covering why the plus edition is not certified so we have no idea whether we are missing something or doing something that will eventually need correcting when using a future (compliant) server release. Frankly I'd be pretty annoyed at having worked so long on a big release and a month or so on the home page is _still_ advertising an old release as latest! Where is the 1.6 release announcement? On 16 January 2014 21:36, Leonardo K. Shikida <shik...@gmail.com> wrote: > I am using tomee+ for almost an year. > > Started from 1.5.2 and now I am a happy user of 1.6.0 (so much faster) > > My opinion is that > > - you guys should give Romain lots of beers, because he's 90% of this > community. he saves the day. He's for tomee what balusC is for JSF. Most > communities are like this, but it would be nice if at least 2 people were > answering the questions. > - more books please. the only one I have is 60% copy and paste of the site > and provides little help. I'd love an o'reilly tomee well-written book > covering tomee+ (not only vanilla tomee) > - more documentation. more step-by-step tutorials for stupid dummies like > me, in the old eclipse tutorials style. Don't assume the reader knows what > you know. Dummies like me need documentation, not JEE gurus. > - wire this community somehow to stackoverflow > - make the forum easy to search and easy to read threads. Take best answers > and push into some wiki or add to the documentation > - my dream would be a big tomee+ tutorial embracing all aspects of a > full-featured solution, showing how to make jms and quartz persistent, how > to cluster, how to make it work with https, etc etc etc, like "the JEE > tutorial using tomee instead of geronimo" (yes, I know Tomee is web > profile, not full profile) > - very very detailed documentation about tomee+ configuration. There are > almost 10 configuration files involved. I know tomee+ relies n several > other projects, BUT, I think the idea here is to pack them all into a > single bundle and say "here's the integrated thing" > > that's what I think, I hope it helps. > > and congratulations for the good job. > > best regards > > Leo > > > [] > > Leo > > > On Thu, Jan 16, 2014 at 4:25 PM, Long, Doug > <doug.lon...@cardinalhealth.com>wrote: > > > We'd like to hear about anything you'd like to tell us. If you're short > > on ideas, here are some: > > > > - Ways we can speed up or improve your ability to evaluate TomEE > > > > o Make the stable release the version that is linked at > > http://openejb.apache.org/index.html as the download link, or at minimum > > link to a page that has the versions labeled as stable and development. > > > > o Create a "Getting started" document (per branch if the instructions > > are different) > > > > § Prerequisites > > > > · Versions of Tomcat, Java, and TomEE war > > > > · File permissions > > > > · Tomcat-users.xml roles > > > > § Installation and configuration: TomEE build > > > > § Installation and configuration: Tomcat stable + drop-in war > > > > o Create "TomEE GUI" documentation (per branch if the instructions are > > different) > > > > § Screenshots > > > > > > > > - Anything you found difficult or inconvenient about using TomEE > > > > o Did not realize the default download is the development branch > > > > o Required roles between snapshots utilize different standards... > > admin-gui/script vs manager-gui/script > > > > o TomEE war + Tomcat configuration instructions confusing : > > http://tomee.apache.org/installation-drop-in-war.html > > > > § Why does the example state "Please note that the instructions below do > > not currently work with the 1.5.0 binaries due to a bug," but then > > continues to use the 1.5.0 file names (tomee-webapp-1.5.0.war) in the > > example? > > > > § Then on http://tomee.apache.org/manual-installation.html , which is > > supposed to be referencing the 1.5.0 installation, it references the > > openejb.war instead of tomee-webapp-1.5.0.war (which doesn't appear to > > actually exist if you use the download link at > > http://tomee.apache.org/download/tomee-1.5.0.html . So if it should be > > referencing openejb-standalone-4.5.0.tar.gz, then it should be made clear > > on both pages to use this as the Tomcat + TomEE war installation method > for > > STABLE release, and not even have a reference to 1.5.0. Or is > > openejb-standalone-4.6.0.tar.gz considered the stable release for Tomcat > + > > TomEE? > > > > o http://tomee.apache.org/manual-installation.html has an "automatic > > installation" hyperlink that points back to homepage. If automatic > > installation simply refers to downloading the TomEE build, extracting and > > starting, then it should state so > > > > I still have no idea what instructions to use for a STABLE instance > > utilizing a drop in war. What is the correct stable war file? Which > > instructions should I use for this war file? > > > > > > > > Any help is greatly appreciated > > > > > > > > > > > > Keep in mind that out of every 100 people that try something out, maybe > > one will actually post about it. Feel incredibly encouraged to let us > know > > about your experiences with TomEE even if you think we've heard it a > > hundred times. Odds are we have not heard it and, if we have, the most > > requested things are done first. So definitely let us know! > > > > Apache TomEE is free, but you can pay us with feedback :) > > > > Best regards, > > The Apache TomEE community > > > > _________________________________________________ > > > > This message is for the designated recipient only and may contain > > privileged, proprietary > > or otherwise private information. If you have received it in error, > please > > notify the sender > > immediately and delete the original. Any other use of the email by you is > > prohibited. > > > > Dansk - Deutsch - Espanol - Francais - Italiano - Japanese - Nederlands - > > Norsk - Portuguese - Chinese > > Svenska: www.cardinalhealth.com/legal/email > > >
