camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rafael Winterhalter (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-8236) WebSphere class loader detection is too sensitive
Date Tue, 13 Jan 2015 14:09:34 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275223#comment-14275223
] 

Rafael Winterhalter edited comment on CAMEL-8236 at 1/13/15 2:08 PM:
---------------------------------------------------------------------

I second that. As class loader magic becomes more and more common place, this might just break
for any future weblogic family application. The name of the WebSphere class loader should
however be pretty stable, wouldn't it be easiest to match the exact name? Also, one could
add some system property "-Dcamel.websphereClassLoader" for overriding this name if it would
indeed change before Camel would add this additional name.


was (Author: raphw):
I second that. As class loader magic becomes more and more common place, this might just break
for any future weblogic family application. The name of the WebSphere class loader should
however be pretty stable, wouldn't it be easiest to match the exact name. Also, one could
add some system property "-Dcamel.websphereClassLoader" for overriding this name if it would
indeed change before Camel would add this additional name.

> 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