Invalid jars in $MULE_HOME/lib cause exceptions when scanning the jars

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 2.0.1
  • Fix Version/s: 2.0.3
  • Component/s: Project
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

Description

Users tend to put additional jar files into $MULE_HOME/lib/user. The current code is not 100% prepared to handle all error situations that can occur while scanning the jar files:

  • jar files that don't have a pom.xml in them
  • jar files that have a pom but it does not have a name element
  • jar files that match the mule naming scheme but don't have a spring.handlers file in them

Make the code more robust and filter out all Jars in IMuleRuntime.getMuleModulesAndTransports() that don't match the requirements (probably log offending ones)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dirk Olmes added a comment -

Now that we have more tests, all major issues should be covered.

Show
Dirk Olmes added a comment - Now that we have more tests, all major issues should be covered.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: