[
https://issues.apache.org/jira/browse/CAMEL-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275134#comment-14275134
]
David J. M. Karlsen commented on CAMEL-8236:
--------------------------------------------
com.ibm. is still very wide (looking at
https://github.com/apache/camel/commit/91cc51ff0999e52ee284ab02ebfd768ac3f65c17)
I suggest to go at least one package deeper.
You can look at
https://github.com/spring-projects/spring-framework/blob/master/spring-context/src/main/java/org/springframework/context/annotation/MBeanExportConfiguration.java
to get some inspiration - but that is really about WAS management extensions.
I downloaded some javadocs from:
http://www-01.ibm.com/software/webservers/appserv/was/library/v85/nd-dp/
and maybe com.ibm.websphere.servlet.container. or com.ibm.websphere.servlet. is
more suitable?
> 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)
