Cargo

Handle extra jars at the container implementation level so that they can be loaded in the correct classloaders

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.8
  • Fix Version/s: 1.2.1
  • Component/s: Core
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Right now extra jars are added to the container's classpath used to start the container. This is not correct in some cases as it can lead to classloading issues. Each container has some specific diredctories where to put extra jars. These should be used instead.

For example, for JBoss the extra jars should be put in the server configuration dir, in the lib/ dir.

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. CARGO-445 tomcat5x configuration does not copy common/endorsed directories

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is duplicated by

Bug - A problem which impairs or prevents the functions of the product. CARGO-438 Extra dependencies wrongly put on container execution classpath

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Hide
Permalink
Savas Ali Tokmen added a comment -

In CARGO 1.2.1, all containers have the extra JARs put in the correct locations for all local containers.

Show
Savas Ali Tokmen added a comment - In CARGO 1.2.1, all containers have the extra JARs put in the correct locations for all local containers.

People

  • Assignee:
    Unassigned
    Reporter:
    Vincent Massol
Vote (5)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: