Just to add one thing. The problem is not related only to html responses.
The same issue is present with text, GML and GeoJSON responses. So my logic
tells me that this has nothing to do with freemarker templates. It has to
do with limiting attribute access through Geofence.
Best regards
Davor
On Jul 30, 2017 16:56, wrote:
> So when no ordering is present in freemarker template the normal behavior
> is that Geoserver orders attributes randomly for each Getfeatureinfo
> request? Is that what you are trying to tell me?
>
> So my logic tells me that if this is the case, this would be the case with
> the default Geoserver template. But that is not the case. There is an order
> if there is not an explicit order in the template, and that is the order in
> which attributes are listed in the table definition. If that isn't the case
> every Getfeatureinfo would have different attribute order. I haven't seen
> this behavior in any Geoserver setup.
>
> This behavior only exists when I apply attribute filter in Geofence -
> whether I have my own template or use the default one.
>
> Best regards
> Davor
>
> On Jul 28, 2017 21:04, "Ian Turton [via OSGeo.org]" <
> ml+s1560n5329680...@n6.nabble.com> wrote:
>
>> But in freemarker a feature's attributes are stored in a map so there is
>> no expected order to them. If you require an order then you should define
>> it.
>>
>> Ian
>>
>> On 28 Jul 2017 18:44, "dracic" <[hidden email]
>> <http:///user/SendEmail.jtp?type=node&node=5329680&i=0>> wrote:
>>
>>> Ok. I think I'm not clear enough. I do not want any specific order. I
>>> would like generic behavior - which is the one when Geofence rules don't
>>> apply and that is that the attributes are ordered in the way they are
>>> listed in database tables or in attribute list in geoserver layer
>>> properties. So that is the way that Geoserver displays attributes by
>>> default. The other issue is that when Geofence rule is applied, subsequent
>>> Getfeatureinfo requests have different attribute order. It changes
>>> constantly. This cannot be expected behavior in any case.
>>>
>>> http://gis.hrsume.hr/hrsume/wms
>>>
>>> For example layer - gj. If you click at least 10timeson features in qgis
>>> or any web mapping map that can display external wms and do Getfeatureinfo,
>>> you will see at least 4 or 5 different attribute orders.
>>>
>>> Best regards
>>> Davor
>>>
>>> On Jul 28, 2017 19:04, "Ian Turton [via OSGeo.org]" <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=5329670&i=0>> wrote:
>>>
>>> That is what I would expect, if you require a specific order then you
>>> should enforce it in the template (which by the way Nabble is deleting
>>> before they reach the list, please use a proper mail client).
>>>
>>> So something like in content.ftl:
>>>
>>>
>>> ${feature.STATE_NAME.value} has these characteristics:
>>> <ul>
>>> <li>${feature.PERSONS.value}</li>
>>> <li>$feature.MALE.value}</li>
>>> <li>$feature.EMPLOYED</li>
>>> <ul>
>>>
>>>
>>> or what ever ordering you need.
>>>
>>> Ian
>>>
>>>
>>> On 28 July 2017 at 13:47, dracic <[hidden email]
>>> <http:///user/SendEmail.jtp?type=node&node=5329667&i=0>> wrote:
>>>
>>>> So with the previous template with no Geofence rule limiting attribute
>>>> access, GetFeatureinfo request orders columns as they are listed in
>>>> tabel or
>>>> layer property. With Geofence rule, they have no particular order, and
>>>> subsequent request can have even different order from previous requests.
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context: http://osgeo-org.1560.x6.nabbl
>>>> e.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-pr
>>>> oblem-tp5329591p5329633.html
>>>> Sent from the GeoServer - User mailing list archive at Nabble.com.
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>> _______________________________________________
>>>> Geoserver-users mailing list
>>>>
>>>> Please make sure you read the following two resources before posting to
>>>> this list:
>>>> - Earning your support instead of buying it, but Ian Turton:
>>>> http://www.ianturton.com/talks/foss4g.html#/
>>>> - The GeoServer user list posting guidelines:
>>>> http://geoserver.org/comm/userlist-guidelines.html
>>>>
>>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5329667&i=1>
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>>
>>>
>>>
>>>
>>> --
>>> Ian Turton
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Geoserver-users mailing list
>>>
>>> Please make sure you read the following two resources before posting to
>>> this list:
>>> - Earning your support instead of buying it, but Ian Turton:
>>> http://www.ianturton.com/talks/foss4g.html#/
>>> - The GeoServer user list posting guidelines:
>>> http://geoserver.org/comm/userlist-guidelines.html
>>>
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5329667&i=2>
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>>
>>> ------------------------------
>>> If you reply to this email, your message will be added to the discussion
>>> below:
>>> http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-
>>> Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329667.html
>>> To unsubscribe from Geoserver 2.10 & external Geofence 3.2 -
>>> GetFeatureInfo problem, click here.
>>> NAML
>>> <http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>>
>>>
>>>
>>> ------------------------------
>>> View this message in context: Re: Geoserver 2.10 & external Geofence
>>> 3.2 - GetFeatureInfo problem
>>> <http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329670.html>
>>> Sent from the GeoServer - User mailing list archive
>>> <http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html> at
>>> Nabble.com.
>>>
>>> ------------------------------------------------------------
>>> ------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Geoserver-users mailing list
>>>
>>> Please make sure you read the following two resources before posting to
>>> this list:
>>> - Earning your support instead of buying it, but Ian Turton:
>>> http://www.ianturton.com/talks/foss4g.html#/
>>> - The GeoServer user list posting guidelines:
>>> http://geoserver.org/comm/userlist-guidelines.html
>>>
>>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5329680&i=1>
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>>
>> ------------------------------------------------------------------------------
>>
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> [hidden email] <http:///user/SendEmail.jtp?type=node&node=5329680&i=2>
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-
>> Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329680.html
>> To unsubscribe from Geoserver 2.10 & external Geofence 3.2 -
>> GetFeatureInfo problem, click here
>> <http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5329591&code=ZGF2b3IucmFjaWNAZ21haWwuY29tfDUzMjk1OTF8NjgxMTE0NzM1>
>> .
>> NAML
>> <http://osgeo-org.1560.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>
>
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/Geoserver-2-10-external-Geofence-3-2-GetFeatureInfo-problem-tp5329591p5329800.html
Sent from the GeoServer - User mailing list archive at Nabble.com.------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
