Re: [jboss-dev] JBoss Cache uninformative noise
On 19 Nov 2008, at 15:40, Brian Stansberry wrote:
It's at DEBUG in the JBC 3.0.0.GA release that we'll be
releasing.
Yes.
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.
It *can* know, since it delegates to the same internal private method
that parses a stream, but I could always pass in the file name as well
just for the sake of debugging. This is in trunk now anyway
(post-3.0.0.GA, since that is tagged now)
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.
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
_______________________________________________
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