Manik Surtani wrote:
On 19 Nov 2008, at 15:53, David M. Lloyd wrote:
> Is there really a need to print the message more than one time?
Just in case you didn't see it the first time. :-)
I'm guessing this is for > 1 config file being parsed.
No, it's not, it's from the multiple configs being parsed in
deploy/jboss-cache-manager.sar/META-INF/jboss-cache-configs.xml
>
>
> - DML
>
> On 11/19/2008 09:40 AM, Brian Stansberry wrote:
>> It's at DEBUG in the JBC 3.0.0.GA release that we'll be releasing.
>> That particular code has no way to know what file it's parsing, but
>> point taken; it's better if such logging came from something that has
>> some context.
>> Adrian Brock wrote:
>>> It would be helpful if it actually told you the file name as well. ;-)
>>>
>>> 15:53:01,200 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,286 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,366 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,371 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,373 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,416 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,422 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,428 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,434 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,449 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,455 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,461 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>> 15:53:01,469 INFO [CacheConfigsXmlParser] Detected legacy
>>> configuration
>>> file format when parsing configuration file. Migrating to the new
>>> (3.x)
>>> file format is recommended. See FAQs for details.
>>>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com