camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From William Tam <email.w...@gmail.com>
Subject Re: [jira] Commented: (CAMEL-1917) DefaultPackageScanClassResolver not able to scan package in jar url
Date Wed, 10 Mar 2010 14:56:04 GMT
Sorry,  let me take a look at how it was broken.  The runtime was Sonic 
ESB container.

Claus Ibsen (JIRA) wrote:
>     [ https://issues.apache.org/activemq/browse/CAMEL-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58144#action_58144
] 
>
> Claus Ibsen commented on CAMEL-1917:
> ------------------------------------
>
> William this one broke BEA WebLogic support.
>
> In what use case did you encounter this problem?
> We eventually have to restore BEA WebLogic support, so I am curious what runtime you
used to load resources like that jar?
>
>   
>> DefaultPackageScanClassResolver not able to scan package in jar url
>> -------------------------------------------------------------------
>>
>>                 Key: CAMEL-1917
>>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1917
>>             Project: Apache Camel
>>          Issue Type: Bug
>>          Components: camel-core
>>    Affects Versions: 2.0-M3
>>            Reporter: William Tam
>>            Assignee: William Tam
>>             Fix For: 2.1.0
>>
>>
>> The DefaultPackageScanClassResolver seems to have problem finding packages from URL
jar:file:/path/to/my.jar!/"
>>     
>
>   

Mime
View raw message