jsClient installation

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

jsClient installation

and.vianello
Hi all,
I installed the 52n-sos-webapp##4.3.7.war and I changed the name of the war file to "sos.war".
The client is working well but not the jsClient and also some links in the nav-bar:
- the submunu inside client: jsClient
- the submenu in Documentation: Sensor Web Client REST-API

May be a problem like explained here:
The JavaScript SOS Client preconfigured to connect to the SWC REST-API provided by this bundle at localhost:8080/52n-sos-webapp. This works with the default WAR file name "52n-sos-webapp##.war", because https://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Naming.

If you change the name of the war file you have to update the REST-API URL of the JavaScript SOS Client in the settings file: [TOMCAT_HOME]\webapps\[SOS_NAME]\static\client\jsClient\settings.json of the deployed SOS.

I set the setting.json file without results.
If it is easier which is the best way to call the war file?
Thank you for helping me,
Andrea.

Reply | Threaded
Open this post in threaded view
|

Re: jsClient installation

Carsten Hollmann
Hi Andrea,

the renaming is not the problem but the browser behave differently than
in the past. The defined links do not have a "/" at the end and it the
past it works.

In future release we have fixed the links.

You can fix this in the header.jsp file which is located here in the
deployed SOS:

[TOMCAT_HOME]\webapps\sos\WEB-INF\views\common

Update the "value" of the following lines by adding "/index.html":

l85: value="/static/client/jsClient/index.html"
l100: value="/static/doc/api-doc/index.html"

The the links to the jsClient and documentation should work.

Best,
Carsten

Am 11.11.2016 um 09:07 schrieb and.vianello:

> Hi all,
> I installed the 52n-sos-webapp##4.3.7.war and I changed the name of the war
> file to "sos.war".
> The client is working well but not the jsClient and also some links in the
> nav-bar:
> - the submunu inside client: jsClient
> - the submenu in Documentation: Sensor Web Client REST-API
>
> May be a problem like explained here:
>
>
> I set the setting.json file without results.
> If it is easier which is the best way to call the war file?
> Thank you for helping me,
> Andrea.
>
>
>
>
>
> --
> View this message in context: http://sensorweb.forum.52north.org/jsClient-installation-tp4028727.html
> Sent from the 52° North - Sensor Web Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> SWE mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/swe
> http://sensorweb.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines
>

--
Carsten Hollmann

52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
48155 Münster, Germany

E-Mail: [hidden email]
Fon: +49 (0)-251-396371-35
Fax: +49 (0)-251-396371-11
http://52north.org/
Twitter: @FiveTwoN

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849
_______________________________________________
SWE mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/swe
http://sensorweb.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: jsClient installation

jr_rodriguez_l
Hi, I'm using 52n-sensorweb-sos-bundle-4.3.6 and your solution works like a charm!!  Thank you so much!!