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 2008/06/17 21:11:00 UTC

[jira] Updated: (CAMEL-522) Problem with scanning Jar files for Converters if application is loaded with webstart

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

Claus Ibsen updated CAMEL-522:
------------------------------

    Fix Version/s: 1.5.0
                       (was: 1.4.0)

> Problem with scanning Jar files for Converters if application is loaded with webstart
> -------------------------------------------------------------------------------------
>
>                 Key: CAMEL-522
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-522
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.3.0, 1.4.0
>         Environment: Windows XP
>            Reporter: Andreas Kuhtz
>             Fix For: 1.5.0
>
>         Attachments: ResolverUtil.patch
>
>
> I've encountered a problem with the scanning of jar files with the @Converter annotation if the Jars are loaded with the webstart classloader. Because the URL starts with _http:_ the conversion to a file fails in ResolverUtil. 
> I've attached a patch that uses an UrlResource if the url starts with _http:_ and this works if the jar-resource has the version information added to the jar file in the JNLP-file (like <jar href="camel-core-1.4-SNAPSHOT.jar"/>). But if the version is added separately (like <jar href="activemq-core.jar" version="5.1.0"/>) it fails because the classloader returns the name of the jar-file without the version information (like http://....../activemq-core.jar) and this file does not exist. 
> I'm currently trying if it is possible to check whether the application is started via webstart (there is a class Tool that should only exist in the webstart classloader) and in this case I'll check if the filename of the jar-file is returned correctly. If yes maybe we can provide another patch to get rid of the problem described above.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.