Cargo

tomcat5x configuration does not copy common/endorsed directories

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 0.8
  • Fix Version/s: 1.1.0, 1.2.0
  • Component/s: Tomcat
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

tomcat allows for customization of the loaded classes by adding classes to the common directory.
http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html

I've created a hosted custom tomcat distribution zip file (5.5.20 + jdk1.4 compatibility), and cargo does not create the configuration using the jars i have placed in common/endorsed.

Issue Links

depends upon

Improvement - An improvement or enhancement to an existing feature or task. CARGO-435 Handle extra jars at the container implementation level so that they can be loaded in the correct classloaders

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

Improvement - An improvement or enhancement to an existing feature or task. CARGO-928 Fixed and improved Maven2 shared/extra classpath configurations with Tomcat

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

Improvement - An improvement or enhancement to an existing feature or task. CARGO-1061 Avoid having the cargo-specific XML files in the Tomcat local containers

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

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Massol added a comment -

hmm.. Just quickly scanned the link you gave and yes it seems shared libs go in $CATALINA_BASE (which is the root of Cargo's config dir). I always thought they were looked up in $CATALINA_HOME but it does make sense that they are in $CATALINA_BASE.

I think this is very much related to the CARGO-435 issue and I believe the implementation will be the same.

Let me know if you agree and I'll close this issue, mark it as a duplicate of CARGO-435 and link it for reference.

Thanks!

Show
Vincent Massol added a comment - hmm.. Just quickly scanned the link you gave and yes it seems shared libs go in $CATALINA_BASE (which is the root of Cargo's config dir). I always thought they were looked up in $CATALINA_HOME but it does make sense that they are in $CATALINA_BASE. I think this is very much related to the CARGO-435 issue and I believe the implementation will be the same. Let me know if you agree and I'll close this issue, mark it as a duplicate of CARGO-435 and link it for reference. Thanks!
Hide
Permalink
Vincent Massol added a comment -

Actually we should probably keep this one open as we won't implement this for all containers at once so CARGO-435 will probably be split into several issues when it comes to implementation. This issue could be a subtask of CARGO-435.

Show
Vincent Massol added a comment - Actually we should probably keep this one open as we won't implement this for all containers at once so CARGO-435 will probably be split into several issues when it comes to implementation. This issue could be a subtask of CARGO-435 .
Hide
Permalink
Ryan Sonnek added a comment -

I think your right that they're closely related. Whatever you think is best to track this is fine by me.

Show
Ryan Sonnek added a comment - I think your right that they're closely related. Whatever you think is best to track this is fine by me.
Hide
Permalink
Savas Ali Tokmen added a comment -

Fixed by CARGO-928 and CARGO-1061

Show
Savas Ali Tokmen added a comment - Fixed by CARGO-928 and CARGO-1061

People

  • Assignee:
    Unassigned
    Reporter:
    Ryan Sonnek
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: