I agree this sounds like a bug; can you give me an idea what version you 
found this in? I am hoping 2.5.M2 :-) I am hoping to @deprecate many of 
the methods in DataUtilities because the new feature model is so much 
easier to use.

I would like to ask if you are available to test this fix? Or if you can 
create a test case for the problem?

There is some background info on why this really helps here:
- http://docs.codehaus.org/display/GEOTDOC/10+Communication+and+Support

As a general tip to getting these sorts of "easy" problems fix; the 
priority for me (and probably most developers goes something like):

100. Is someone paying - this may sound flippant but I have three weeks 
of paid bug fixes to do in front of me - and I won't even get to all of them
50. Is there a Jira with a patch and a test case
50. Is their a user to test if the fix works (assuming user can build 
from source or try out a fix deployed via maven) - can you do this? If I 
can try a fix and have confirmation from you it worked that would be great
30. Is there a Jira with a patch
30  Is there a test case to reproduce the problem - this would cut my 
time to solve the problem down a lot?
5. Is the problem description clear and reproducible
2. Is there a Jira describing the problem
1. Is there an email describing the problem - check

Right now we have more bug reports and even patches then we have 
developers to apply them; the good news is we are accepting volunteers 
:-) I also hope with OSGeo graduation wrapping up we will have more time 
to devote to the library itself.
Jody

Martin Schmitz wrote:
> Hello Jody,
>
> because you are the "author" of org.geotools.data.DataUtilities I 
> address this mail primary to you...
>
> The helper method defaultValue(AttributeType aType) throws an Exception 
> if AttributeType.createDefaultValue() returns NULL, but the given 
> attribute is not nillable.
> In my opinion the method should first try to generate a default value by 
> calling defaultValue(Class type) and only if this fails, react with the 
> IllegalAttributeException.
> If you have already the defaultValue(Class type) method, so why not 
> using it?
>
> Maybe you can fix this in the next release.
>
> Kind regards
>
> Martin
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Geotools-gt2-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
>   


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to