HI all,
noticed this thread just now throwing in just a small consideration,
which may or may not be useful.
PropertyAccessor lookup goes directly to ServiceLoader, which has no
priority support. However, many other XYZFinder in GeoTools go through a
FactoryRegistry, which happens to have a pa
Hi Jody,
thank you for the feedback, lost track of this one during the holidays,
find my replies inline:
On Tue, Jul 23, 2024 at 12:41 AM Jody Garnett
wrote:
> Adding the priority is fine as a fallback plan (like it will work). But it
> is more a band-aid than a cure. It just puts off the proble
Adding the priority is fine as a fallback plan (like it will work). But it
is more a band-aid than a cure. It just puts off the problem (two accessors
can have the same number and we are right back to chance).
Some questions:
Q: Is there anyway to tighten up the reporting so that
FeaturePropertyA
Hi,
I've encountered an issue where a custom property accessor suddenly stopped
working. Upon investigation, I found that the problem originates from the
fact that the order in which property accessors are read and registered is
random and lacks an explicit priority mechanism. This is usually not
