We're updating the issue view to help you get more done. 

Add support for context path configuration for WebLogic

Description

Right now it isn't possible to set context path for WebLogic WAR deployment by Cargo.

WebLogic doesn't support dynamic context path configuration so there are several deployment options left:

  1. Current state - WAR files are deployed using WLST
    advantages: - WAR file stays in place where is defined, no inner modifications are done
    disadvantages: - cannot configure context path

  2. Copy WAR file to autodeploy directory and rename it (WebLogic use WAR file name as context path)
    advantages: - context path configured, no inner modifications are done
    disadvantages: - WAR file is copied and renamed, can cause problems for users who needs their deployable to stay intact

  3. Copy WAR file to autodeploy directory and create/update weblogic.xml file to add there context root
    advantages: - context path configured, file name stays
    disadvantages: - WAR file is copied and modified, can cause problems for users who needs their deployable to stay intact

Every option has advantages and disadvantages. It could be possible to control deployment option by Cargo configuration property. Question is - which approach should be used as default one?

Status

Assignee

S. Ali Tokmen

Reporter

Karel Suta

Components

Fix versions

Priority

Major