I’ve gone back through this and read it again to try to familiarize myself with
the situation.
Is there a reason why GeoServer currently does it in the order it does it? For
instance, if I were to make the alternative — would it open up additional
issues that were prevented it from doing it how
Andrea,
you are right : I use the actuel featuretype name and *NOT* the string
"featuretypeName".
As stated I don't have this problem with 2.12.2 so I think it may be a
solved bug.
Let me know if you find anything with the problem Schema "SchemaName" does
not exist after the first recalulation v
Hi,
I don't have much experience with the rest api module, but I'm wondering...
you're not really using "featuretypeName", verbatim, in the request,
but you are setting the actual typename that you're trying to modify, right?
Silly question I know, but if you were to use it verbatim, it would expla
