Hi Martin, Hi Justin,

Thanks for reply! I would prefer the way to extend the Element class with an 
pullOptionalString method analogous to the pullOptionalElement one. I created a 
patch for the two classes : Element and Parser itself. I guess for further 
discussion we should comment the issue (includes an additional test case - 
testAuthorithyCode):

http://jira.codehaus.org/browse/GEOT-2578

Who is going to apply the patch? I thought Martin is the module maintainer for 
the referencing stuff (taken from the pom)?

Frank

> Martin Desruisseaux a écrit :
> > From memory (but I would have to check for being sure) it seems to me 
> > that there is a pullOptionalString method, which would avoid the need 
> > for a try ... catch.
> 
> Checked the code and realized that there is no pullOptionalString(...) 
> method, 
> so my memory was wrong. An alternative is to define a new pullObject(...) 
> method 
> instead, which may returns a String or an Integer (among others), and use 
> Object.toString().
> 
>       Martin
> 



------------------------------------------------------------------------------
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to