Hey, what about creating a asciidoc/markdown repository on GitHub to centralise 
all related TomEE documentation? I would be happy to contribute sending pull 
requests every time I learn something or I put something to work. We could 
create a branch for each new TomEE release, so we couldn’t make the mistake of 
describing a feature not available yet in a older release.

In my understanding, documentation is as important as code for the success of a 
project.

On 22 Nov 2013, at 23:40, ymaraner <[email protected]> wrote:

> zeeman wrote
>> 2- Where can I find a reference to all options to be configured?
> 
> 
> Romain Manni-Bucau wrote
>> 2) http://tomee.apache.org/properties-listing.html + tomee/openejb jira i
>> guess
> 
> Seriously, is there a comprehensive reference for configuring TomEE?
> 
> Responses on the forums are very helpful, and I really appreciate the effort
> that it takes to respond to these questions. However, I frequently search
> all of JIRA, NABBLE, and the TomEE web site in the hopes of finding some
> configuration that might fix a particular problem before posting a new
> question. 
> 
> The properties-listing page that you reference doesn't even include the
> asynchronouspool settings that zeeman already uses. I can find no references
> to applications.properties anywhere except JIRA and release notes. There was
> a thread on the developer forum about changing the syntax of the
> configuration files, but I couldn't determine if that was ever implemented.
> 
> I realize that this is an open-source project and that people working on the
> project are not necessarily going to be paid based on the quality of the
> documentation, but someone with the knowledge of all of the available
> configurations settings, should be maintaining a comprehensive reference to
> configure TomEE.
> 
> 
> 
> -----
> - Tim
> --
> View this message in context: 
> http://openejb.979440.n4.nabble.com/Tomee-config-questions-tp4666085p4666335.html
> Sent from the OpenEJB User mailing list archive at Nabble.com.

Reply via email to