camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-8236) WebSphere class loader detection is too sensitive
Date Tue, 13 Jan 2015 11:48:35 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Willem Jiang resolved CAMEL-8236.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.15.0
                   2.14.2
                   2.13.4

Applied the patch into camel master, camel-2.14.x and camel-2.13.x branches.

> WebSphere class loader detection is too sensitive
> -------------------------------------------------
>
>                 Key: CAMEL-8236
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8236
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.14.1
>            Reporter: Rafael Winterhalter
>            Assignee: Willem Jiang
>            Priority: Minor
>             Fix For: 2.13.4, 2.14.2, 2.15.0
>
>
> The DefaultCamelContext attempts to detect an IBM WebSphere application server by a simple
test: loader.getClass().getName().startsWith("com.ibm")
> This test can introduce very subtle bugs when working with other IBM productes and I
suggest to replace it by a list of known class names of WebSphere class loaders. At least,
one should add an additional dot in order to avoid matching packages that only start with
"com.ibm" such as any "com.ibmfoobar".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message