[Geoserver-devel] Update web.xml from DTD to XML Schema

I am deploying GeoServer 2.7.2 onto WebLogic 12.1.3. I did not have a problem
configuring the DATA_DIR to work using an Environment Variable but what I
would prefer to do is deploy using a WebLogic plan xml. The plan file would
allow me to override the <context-param> without exploding or modifying the
war. This helps when deploying to multiple environments that I do not need
to modify the OS variables. Unfortunately, WebLogic does not support this
feature for xml files that use DTD.

Given that DTD is older and the web.xml is using web-app 2.3 is there a
specific reason it has not been updated to use the servlet 3.1
specification?

I updated the web.xml on my own with this and have not seen any issues.

<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://xmlns.jcp.org/xml/ns/javaee&quot;
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance&quot;
         xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee
                 http://xmlns.jcp.org/xml/ns/javaee/web-app_3_1.xsd&quot;
         version="3.1">

Thanks,
Brian

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Update-web-xml-from-DTD-to-XML-Schema-tp5233189.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.

We would be happy to review a pull request. You are the first person to request an upgrade to 3.1.

On Wed, Oct 28, 2015 at 1:10 PM brian.blain <brian.blain@anonymised.com> wrote:

I am deploying GeoServer 2.7.2 onto WebLogic 12.1.3. I did not have a problem
configuring the DATA_DIR to work using an Environment Variable but what I
would prefer to do is deploy using a WebLogic plan xml. The plan file would
allow me to override the without exploding or modifying the
war. This helps when deploying to multiple environments that I do not need
to modify the OS variables. Unfortunately, WebLogic does not support this
feature for xml files that use DTD.

Given that DTD is older and the web.xml is using web-app 2.3 is there a
specific reason it has not been updated to use the servlet 3.1
specification?

I updated the web.xml on my own with this and have not seen any issues.

<?xml version="1.0" encoding="UTF-8"?>

Thanks,
Brian


View this message in context: http://osgeo-org.1560.x6.nabble.com/Update-web-xml-from-DTD-to-XML-Schema-tp5233189.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.



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


Jody Garnett

Hi Brian,
I second Jody. Mind, it still has to work with the default version of Jetty we build the windows/osx/bin packages with,
and common Tomcat versions, it’s up to you to check that’s the case.

Also mind, only the developer series (master) uses a recent Jetty version (9.2, landed a few
days ago) whilst the stable and maintenance are still depending on Jetty 6, which is several
years old (so, it might not support servlet 3.1)

Cheers
Andrea

···

On Wed, Oct 28, 2015 at 9:00 PM, brian.blain <brian.blain@anonymised.com> wrote:

I am deploying GeoServer 2.7.2 onto WebLogic 12.1.3. I did not have a problem
configuring the DATA_DIR to work using an Environment Variable but what I
would prefer to do is deploy using a WebLogic plan xml. The plan file would
allow me to override the without exploding or modifying the
war. This helps when deploying to multiple environments that I do not need
to modify the OS variables. Unfortunately, WebLogic does not support this
feature for xml files that use DTD.

Given that DTD is older and the web.xml is using web-app 2.3 is there a
specific reason it has not been updated to use the servlet 3.1
specification?

I updated the web.xml on my own with this and have not seen any issues.

<?xml version="1.0" encoding="UTF-8"?>

Thanks,
Brian


View this message in context: http://osgeo-org.1560.x6.nabble.com/Update-web-xml-from-DTD-to-XML-Schema-tp5233189.html
Sent from the GeoServer - Dev mailing list archive at Nabble.com.



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

==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.