Hello Michael
Newcomb, Michael-P57487 a écrit :
> Can you please show me what the updated code for 2.5 looks like for the
> following?
>
> (...snip...)
>
> ParameterValueGroup parameters = mtFactory.getDefaultParameters("Oblique
> Stereographic");
>
> (...snip...)
>
>
> Conversion c =
> coordinateOperationFactory.createDefiniingConversion(properties, null,
> parameters);
> But that failed because operation method can't be null, but it was
> allowed to be null in 2.3 (my current version).
Instead of the null argument, you can use:
mtFactory.getLastMethodUsed();
This is a little bit the same idea than ResultSet.wasNull() in JDBC, which
gives
supplemental informations abot the last information returned. Despite the
apparence, this is thread-safe at least in GeoTools implementation because it
use java.lang.ThreadLocal for storing that information.
It probably sound like convolved. They were a wish to minimise the
compatibility
break, and also to keep the API more straightforward for the common case of
users not interrested in OperationMethod.
Martin
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
