[Geoserver-devel] [JIRA] (GEOS-10007) Update REST response http status code when adding an already exist workspace

[JIRA]

异君 张 ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=605afea60a9b690071a282c8
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMWJkM2E3MWYzNDNhNDU2MTljN2NjYjQ4MjdmMzFhZDQiLCJwIjoiaiJ9
 ) / Improvement ( 
https://osgeo-org.atlassian.net/browse/GEOS-10007?atlOrigin=eyJpIjoiMWJkM2E3MWYzNDNhNDU2MTljN2NjYjQ4MjdmMzFhZDQiLCJwIjoiaiJ9
 ) GEOS-10007 ( 
https://osgeo-org.atlassian.net/browse/GEOS-10007?atlOrigin=eyJpIjoiMWJkM2E3MWYzNDNhNDU2MTljN2NjYjQ4MjdmMzFhZDQiLCJwIjoiaiJ9
 ) Update REST response http status code when adding an already exist workspace 
( 
https://osgeo-org.atlassian.net/browse/GEOS-10007?atlOrigin=eyJpIjoiMWJkM2E3MWYzNDNhNDU2MTljN2NjYjQ4MjdmMzFhZDQiLCJwIjoiaiJ9
 )

Issue Type: Improvement Assignee: Unassigned Components: REST Created: 
07/Apr/21 4:30 AM Priority: Low Reporter: 异君 张 ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=605afea60a9b690071a282c8
 )

It's confusing that trying add an exist workspace through REST ( 
https://github.com/geoserver/geoserver/blob/c78b567e872b4167408683ef3aeb1d599da9e86b/src/restconfig/src/main/java/org/geoserver/rest/catalog/WorkspaceController.java#L116
 ) will get 401(UNAUTHORIZED) Whether you take right BASIC AUTH HEADER or not.

Http status code 4xx(eg 409) or 5xx better?
Here is the work in process GitHub PR ( 
https://github.com/geoserver/geoserver/pull/4933 )

( 
https://osgeo-org.atlassian.net/browse/GEOS-10007#add-comment?atlOrigin=eyJpIjoiMWJkM2E3MWYzNDNhNDU2MTljN2NjYjQ4MjdmMzFhZDQiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-10007#add-comment?atlOrigin=eyJpIjoiMWJkM2E3MWYzNDNhNDU2MTljN2NjYjQ4MjdmMzFhZDQiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495=EmailNotificationLink=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100156- 
sha1:d8159f4 )
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Advice on UI approach

[peter.rushforth]

Hi Brad,

 

Thanks for your response.

 

> Seems like we normally start with freemarker templates, and that might be 
> appropriate in your case.

 

I did come across that in the docs, and I’ll look into it a bit more, it looks 
very much like what I should have started with!  It looks like it will be very 
useful to come up to speed on for my project.

 

> One thing that you might want to consider is how the translation into other 
> languages would work.

 

Thanks for that reminder. Does freemarker have a role to play in 
internationalizing layer content in GeoServer?  How do you provide for > 1 
language of content, in general? 

 

Cheers, and thanks,

Peter

 

 

From: br...@frogmouth.net  
Sent: April 6, 2021 7:25 PM
To: peter.rushfo...@gmail.com
Cc: 'Geoserver-devel' 
Subject: Re: [Geoserver-devel] Advice on UI approach

 

Seems like we normally start with freemarker templates, and that might be 
appropriate in your case. Otherwise its pretty open with what works in terms of 
Wicket - I don't think that the admin UI is a great source of UX design 
patterns,  so not a lot of constraints. 

 

One thing that you might want to consider is how the translation into other 
languages would work. There are a lot of variations out there...

 

Brad

 

On 7 Apr. 2021 02:07, peter.rushfo...@gmail.com 
  wrote:

Hi,

 

I’ve been working on developing a way to process strings templated with 
attribute name placeholders, when serializing a WFS GetFeature / WMS/WMTS 
GetFeatureInfo response.

 

 

The strings will look like something like this, for example: “This string can 
contain zero or more attribute ${name} placeholders. The placeholders can be 
for any ${attribute}, not only name.” .

 

I want to build a user interface to allow the user to enter the text part of 
those strings, but to select the attribute names from a list or palette.  

 

Do you have any opinions about what would be a good / appropriate GeoServer way 
of accomplishing this task?  

 

I was thinking about doing the simplest thing that could possibly work, which 
seems to me might be similar to how the Proxy Base URL text input works

–allow the user to type the placeholder and other text into the field, maybe 
with a supporting select of attribute names.

 

Thank you!

 

Peter

 

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Advice on UI approach

[bradh]

Seems like we normally start with freemarker templates, and that might be appropriate in your case. Otherwise its pretty open with what works in terms of Wicket - I don't think that the admin UI is a great source of UX design patterns,  so not a lot of constraints. One thing that you might want to consider is how the translation into other languages would work. There are a lot of variations out there...BradOn 7 Apr. 2021 02:07, peter.rushfo...@gmail.com wrote:Hi, I’ve been working on developing a way to process strings templated with attribute name placeholders, when serializing a WFS GetFeature / WMS/WMTS GetFeatureInfo response.  The strings will look like something like this, for example: “This string can contain zero or more attribute ${name} placeholders. The placeholders can be for any ${attribute}, not only name.” . I want to build a user interface to allow the user to enter the text part of those strings, but to select the attribute names from a list or palette.   Do you have any opinions about what would be a good / appropriate GeoServer way of accomplishing this task?   I was thinking about doing the simplest thing that could possibly work, which seems to me might be similar to how the Proxy Base URL text input works –allow the user to type the placeholder and other text into the field, maybe with a supporting select of attribute names. Thank you! Peter___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Advice on UI approach

[peter.rushforth]

Hi,

 

I've been working on developing a way to process strings templated with
attribute name placeholders, when serializing a WFS GetFeature / WMS/WMTS
GetFeatureInfo response.

 

 

The strings will look like something like this, for example: "This string
can contain zero or more attribute ${name} placeholders. The placeholders
can be for any ${attribute}, not only name." .

 

I want to build a user interface to allow the user to enter the text part of
those strings, but to select the attribute names from a list or palette.  

 

Do you have any opinions about what would be a good / appropriate GeoServer
way of accomplishing this task?  

 

I was thinking about doing the simplest thing that could possibly work,
which seems to me might be similar to how the Proxy Base URL text input
works

-allow the user to type the placeholder and other text into the field, maybe
with a supporting select of attribute names.

 

Thank you!

 

Peter

___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel