app-schema FeatureTypeRegistry fails to handle substitution groups in unit tests
--------------------------------------------------------------------------------

                 Key: GEOT-3462
                 URL: http://jira.codehaus.org/browse/GEOT-3462
             Project: GeoTools
          Issue Type: Bug
          Components: data app-schema
            Reporter: Ben Caradoc-Davies
            Assignee: Niels Charlier


Niels,

FeatureTypeRegistry is flooding the logs with WARNING messages when app-schema 
unit tests run (see Jody's original bug report below). As a temporary cosmetic 
fix, I will reduce the logging level to FINE to reduce annoyance of other 
developers. I suspect that there is an underlying problem that should be 
investigated. To see the log messages, see FeatureTypeRegistry:312, where you 
build substitutionGroup before putting it into UserData. Change the log level 
back to WARNING to see that createAttributeDescriptor is throwing an exception; 
I don't know why.

Kind regards,
Ben.

{code}
-------- Original Message --------
Subject: app-schema log file use during testing
Date: Wed, 9 Mar 2011 08:50:11 +0800
From: Jody Garnett 
To: geotools dev
CC: Caradoc-Davies, Ben (CESRE, Kensington) 

Morning Ben:

I was performing a geotools build today ... and my log went mad with the 
following:
copedNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizedGenericNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizableScopedNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizableGenericNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizedScopedNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizedGenericNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizableScopedNameType
Mar 9, 2011 10:47:42 AM org.geotools.data.complex.config.FeatureTypeRegistry 
createAttributeDescriptor
WARNING: Could not create substitution descriptor: XSD type definition not 
found in schemas: {urn:cgi:xmlns:CGI:Utilities:1.0}LocalizableGenericNameType
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.064 sec

When testing the app schema resolver; do you think you can arrange to turn down 
the logging here? Or has something gone wrong with the test - and is this 
warning important to you?

--
Jody Garnett
{code}

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to