The <include> element is a way to build an XML file from parts found in other XML files. There are no limitations regarding the number of appenders you can place in the included XML file. I am afraid I did not understand the rest of your question. What do you mean when you write "In a few words, this is the problem..." ? José Juan Montiel wrote:

Hi,

this is my first time... :)

There is some limit in the numbers of appender that i define in a file included?

I have a logback.xml with 2 include...

<include resource="logback-X1.xml"/> <include resource="logback-X2.xml"/>

and de same number of appender in each file APP1_X1, APP2_X1... and APP1_X2, APP2_X2...

And when application start server output...

APP1_X1 APP1_X_n-(x) .. APP2_X2_n-(x+1) APP2_X2_n

In a standalond example (1 jar, 1 jvm), works ok....

In a few words, this is the problem...

And another question, diferences between documentation about wars/tomcat and ears/jboss?

Thanks in advice, and greate job.

PD: Git seems great for branches and branches... and offline, but as the first response, i thin there is good: "eclipse team sincronize" :)

-- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

Sorry... when i try to explain me quickly... :( But very quickly answers...

and de same number of appender in each file APP1_X1, APP2_X1... and APP1_X2, APP2_X2...

And when application start server output...

APP1_X1 APP1_X_n-(x) .. APP2_X2_n-(x+1) APP2_X2_n

In a standalond example (1 jar, 1 jvm), works ok....

In a few words, this is the problem...

And another question, diferences between documentation about wars/tomcat and ears/jboss?

Thanks in advice, and greate job.

The logs that appear in the stdout of jboss, show how logback read the configuration... and only show the first part of first include file, and the second part of the second included file. And, there is diferences between how deploy 2 wars in tomcat and 2 ears in jboss, related with "globaly" logback.xml configuration...

PD: Git seems great for branches and branches... and offline, but as the first response, i thin there is good: "eclipse team sincronize"

Git is great for "branch" a code and later merge, and works ofline, this is good for peoplo who'll try new improvements... but still thres is not a good "eclipse team synchronize plugin" i think (subclipse is great) Thanks and sorry. -- Jose Juan Montiel Martinez Eurobits Technologies Calle Musgo 3, 1ª Planta 28023 Madrid T +34-917080300 F +34-913077480 josejuan.montiel@eurobits.es http://www.eurobits.com