[
https://issues.apache.org/activemq/browse/CAMEL-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44625#action_44625
]
akuhtz edited comment on CAMEL-522 at 7/30/08 1:04 AM:
--------------------------------------------------------------
Claus, a good description is under
http://mojo.codehaus.org/webstart/webstart-maven-plugin/ (and a copy under
http://coffeebreaks.org/tmp/maven-staging/webstart/site/).
This is almost the default jnlpTemplate.vm. The properties in the resources tag
are not required, they just show how to set properties that can be used in the
spring configuration....
{code:xml|title=jnlpTemplate.vm|borderStyle=solid}
$explicitTimestamp
<?xml version="1.0" encoding="utf-8"?>
<jnlp
spec="$jnlpspec"
codebase="$$codebase"
context="$$context"
href="$$name">
<information>
<title>$project.Name $project.Version</title>
<vendor>$project.Organization.Name</vendor>
<description>$project.Description</description>
<icon href="images/mylogo.gif" width="64" height="64"/>
<icon kind="splash" href="images/mysplash.gif"/>
#if($offlineAllowed)
<offline-allowed/>
#end
</information>
#if($allPermissions)
<security>
<all-permissions/>
</security>
#end
<resources>
<j2se version="$j2seVersion" max-heap-size="448m" />
<property name="remoteSite" value="https://$$hostname:32463"/>
<property name="amq.broker.url" value="failover:tcp://$$hostname:32935"/>
$dependencies
</resources>
<application-desc main-class="$mainClass"/>
</jnlp>
{code}
was (Author: akuhtz):
Claus, a good description is under
http://mojo.codehaus.org/webstart/webstart-maven-plugin/ (and a copy under
http://coffeebreaks.org/tmp/maven-staging/webstart/site/).
This is almost the default jnlpTemplate.vm.
{code:xml|title=jnlpTemplate.vm|borderStyle=solid}
$explicitTimestamp
<?xml version="1.0" encoding="utf-8"?>
<jnlp
spec="$jnlpspec"
codebase="$$codebase"
context="$$context"
href="$$name">
<information>
<title>$project.Name $project.Version</title>
<vendor>$project.Organization.Name</vendor>
<description>$project.Description</description>
<icon href="images/mylogo.gif" width="64" height="64"/>
<icon kind="splash" href="images/mysplash.gif"/>
#if($offlineAllowed)
<offline-allowed/>
#end
</information>
#if($allPermissions)
<security>
<all-permissions/>
</security>
#end
<resources>
<j2se version="$j2seVersion" max-heap-size="448m" />
<property name="remoteSite" value="https://$$hostname:32463"/>
<property name="amq.broker.url"
value="failover:tcp://$$hostname:32935"/>
$dependencies
</resources>
<application-desc main-class="$mainClass"/>
</jnlp>
{code}
> 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
> Assignee: Claus Ibsen
> 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.
