Is it possible to export incremental Resources Path in a REST Service? - Progress Community

Loading

Skip to Main Content

Is it possible to export incremental Resources Path in a REST Service?

Is it possible to export Resources Path in REST Services incrementally (.paar) from PDSOE and import it into an existing REST webapp (.war) running on a standalone Tomcat that is connecting to a Classic AppServer?

Dec 5, 2017
Knowledge

Title

Is it possible to export incremental Resources Path in a REST Service?

URL Name

Is-it-possible-to-export-incremental-Resources-Path-in-a-REST-Service

Article Number

000164384

Environment

Product: OpenEdge Version: 11.7.x OS: Windows Other: REST Services

Question/Problem Description

Is it possible to export Resources Path in REST Services incrementally (.paar) from PDSOE and import it into an existing REST webapp (.war) running on a standalone Tomcat that is connecting to a Classic AppServer?

Steps to Reproduce

Clarifying Information

- Currently the .war file is being generated in PDSOE on Windows and it is being copied to Linux, the .war file is then undeployed and redeployed through command line or Tomcat manager.
- The REST Adapter and Web App is running on a standalone Tomcat.
- REST Service includes some Resources Path when is deployed. For example:

/ResourcePath1
/ResourcePath2
....

- The goal is to add more Resources Path to a deployed REST Services when the exported .zip file includes only one resource Path. For example:
/ResourcePath3

The result in the deployed REST Service should be all the current Resources Path plus the new one:

/ResourcePath1
/ResourcePath2
/ResourcePath3

Error Message

Defect Number

Enhancement Number

Cause

Resolution

At the time of incremental export, all resources in the selected REST service are exported in the .zip. Exporting one or two resources in a single REST Service/.paar doesn’t happen because the resources are intertwined in the XML files inside the .paar. When an incremental .zip is republished, it overlays contents over existing services, resources etc.

Publishing incremental Resources in a Service is not supported. The incremental publishing works at Service level and the incremental export to a .zip file will include the REST Service and all resources Path in it. The Service could not be updated with new Resources Path without removing the ones already deployed.

When the Web Application is exported using the option “Export ABL services for Progress Application server” in PDSOE, it will create a .war file, which includes the complete structure of the Application. Using the incremental deployment option, it will export only the static and WEB-INF folders, but the WEB-INF folder will include only adapters, openedge and tlr folders. This is going to include all Services in a PDSOE project and other files that might be created in openedge folder. The Web Application is going to be incrementally deployed and the Services in the .zip file will be republished.

Progress Product is functioning as designed and supporting Export/Publish Resource Path incrementally qualifies as an enhancement request.

An enhancement to the product can be requested through the Progress Community via an Ideas submission. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.

For detailed information on how to submit an Idea, please refer to Knowledge Base article How to submit an idea for a Progress product enhancement

Workaround

Notes

Keyword Phrase

Last Modified Date

11/20/2020 7:12 AM

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Is it possible to export incremental Resources Path in a REST Service? - Progress Community