You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/08/17 06:28:35 UTC
[jira] Commented: (CAMEL-1917) DefaultPackageScanClassResolver not
able to scan package in jar url
[ https://issues.apache.org/activemq/browse/CAMEL-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53638#action_53638 ]
Claus Ibsen commented on CAMEL-1917:
------------------------------------
Willem please refrain from committing this to 2.0 so *late in the game*.
We would rather have this fixed in 2.1 or later as the resource loading can be tricky on many different platform such as Oracle App Server, IBM WebSphere, JBoss and whatelse.
It would be a pity if something breaks in one of these containers because of this patch.
-1 = 2.0
+1 = 2.1 or later
> 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.0.0
>
>
> The DefaultPackageScanClassResolver seems to have problem finding packages from URL jar:file:/path/to/my.jar!/"
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (CAMEL-1917) DefaultPackageScanClassResolver
not able to scan package in jar url
Posted by William Tam <em...@gmail.com>.
running Camel standalone.
On Mon, Aug 17, 2009 at 12:37 AM, Claus Ibsen<cl...@gmail.com> wrote:
> On Mon, Aug 17, 2009 at 6:35 AM, William Tam<em...@gmail.com> wrote:
>> Hi Claus,
>>
>> No problem. I'll back it out then.
>>
> Thanks for your understanding.
>
> Do you use a container/server when you discovered the issue? Or was it
> from running Camel standalone or what?
>
>
>
>> William
>>
>> On Mon, Aug 17, 2009 at 12:28 AM, Claus Ibsen (JIRA)<ji...@apache.org> wrote:
>>>
>>> [ https://issues.apache.org/activemq/browse/CAMEL-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53638#action_53638 ]
>>>
>>> Claus Ibsen commented on CAMEL-1917:
>>> ------------------------------------
>>>
>>> Willem please refrain from committing this to 2.0 so *late in the game*.
>>>
>>> We would rather have this fixed in 2.1 or later as the resource loading can be tricky on many different platform such as Oracle App Server, IBM WebSphere, JBoss and whatelse.
>>> It would be a pity if something breaks in one of these containers because of this patch.
>>>
>>> -1 = 2.0
>>> +1 = 2.1 or later
>>>
>>>> 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.0.0
>>>>
>>>>
>>>> The DefaultPackageScanClassResolver seems to have problem finding packages from URL jar:file:/path/to/my.jar!/"
>>>
>>> --
>>> This message is automatically generated by JIRA.
>>> -
>>> You can reply to this email to add a comment to the issue online.
>>>
>>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
Re: [jira] Commented: (CAMEL-1917) DefaultPackageScanClassResolver
not able to scan package in jar url
Posted by Claus Ibsen <cl...@gmail.com>.
On Mon, Aug 17, 2009 at 6:35 AM, William Tam<em...@gmail.com> wrote:
> Hi Claus,
>
> No problem. I'll back it out then.
>
Thanks for your understanding.
Do you use a container/server when you discovered the issue? Or was it
from running Camel standalone or what?
> William
>
> On Mon, Aug 17, 2009 at 12:28 AM, Claus Ibsen (JIRA)<ji...@apache.org> wrote:
>>
>> [ https://issues.apache.org/activemq/browse/CAMEL-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53638#action_53638 ]
>>
>> Claus Ibsen commented on CAMEL-1917:
>> ------------------------------------
>>
>> Willem please refrain from committing this to 2.0 so *late in the game*.
>>
>> We would rather have this fixed in 2.1 or later as the resource loading can be tricky on many different platform such as Oracle App Server, IBM WebSphere, JBoss and whatelse.
>> It would be a pity if something breaks in one of these containers because of this patch.
>>
>> -1 = 2.0
>> +1 = 2.1 or later
>>
>>> 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.0.0
>>>
>>>
>>> The DefaultPackageScanClassResolver seems to have problem finding packages from URL jar:file:/path/to/my.jar!/"
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Re: [jira] Commented: (CAMEL-1917) DefaultPackageScanClassResolver
not able to scan package in jar url
Posted by William Tam <em...@gmail.com>.
Hi Claus,
No problem. I'll back it out then.
William
On Mon, Aug 17, 2009 at 12:28 AM, Claus Ibsen (JIRA)<ji...@apache.org> wrote:
>
> [ https://issues.apache.org/activemq/browse/CAMEL-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53638#action_53638 ]
>
> Claus Ibsen commented on CAMEL-1917:
> ------------------------------------
>
> Willem please refrain from committing this to 2.0 so *late in the game*.
>
> We would rather have this fixed in 2.1 or later as the resource loading can be tricky on many different platform such as Oracle App Server, IBM WebSphere, JBoss and whatelse.
> It would be a pity if something breaks in one of these containers because of this patch.
>
> -1 = 2.0
> +1 = 2.1 or later
>
>> 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.0.0
>>
>>
>> The DefaultPackageScanClassResolver seems to have problem finding packages from URL jar:file:/path/to/my.jar!/"
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>