Re: WebStart application with JavaHelp
markspace
> I understand that since JavaHelp isn't part of a standard Java
> Runtime environment, I should distribute jh.jar as part of my
> distribution.
Just put your jh.jar file in
<resource>
<jar href="jh.jar" />
</resource>
and it'll be downloaded automatically for you. The href is relative to
the "codebase" param so you may need to add some path info to that name.
More info:
<http://java.sun.com/developer/technicalArticles/Programming/jnlp/>
Here's the latest syntax guide. It's a little more dense than the link
above:
<http://java.sun.com/javase/6/docs/technotes/guides/javaws/developersguide/syntax.html>
Andrew Thompson
> Luc Van Bogaert wrote:
>..
> Just put your jh.jar file in
>
> <resource>
> <jar href="jh.jar" />
> </resource>
That is one way to do it. JH can also be delivered
as webtart extensions. That is how I did it for the
JavaHelp by Webstart e.g. <http://pscode.org/jh/>.
--
Andrew T.
pscode.org
markspace
Hmm, the OP has a Jar file, and that's what the <jar> element wants.
Whereas the <extension> tag takes a JNLP file.
Is there any advantage to using the <extension> that would warrant the
extra work of converting the existing jh.jar to use JNLP also? I'm not
really used to using JNLP files, so I don't know what kinds of
trade-offs exist.
Roedy Green
quoted or indirectly quoted someone who said :
>
>Could anyone outline how I should handle this? I assume that I could
>include jh.jar in my application jar.
If you are using Java Web Start, just specify it as yet another <jar,
part of the app. You probably want eager loading.
--
Roedy Green Canadian Mind Products
http://mindprod.com
An example (complete and annotated) is worth 1000 lines of BNF.
Andrew Thompson
> Andrew Thompson wrote:
> > On Nov 6, 3:13 am, markspace <nos...@nowhere.com> wrote:
> >> Luc Van Bogaert wrote:
> >> ..
> >> Just put your jh.jar file in
>
> >> <resource>
> >> <jar href="jh.jar" />
> >> </resource>
>
> > That is one way to do it. JH can also be delivered
>
> Hmm, the OP has a Jar file, and that's what the <jar> element wants.
> Whereas the <extension> tag takes a JNLP file.
>
> Is there any advantage to using the <extension> that would warrant the
> extra work of converting the existing jh.jar to use JNLP also? I'm not
> really used to using JNLP files, so I don't know what kinds of
> trade-offs exist.
Factoring out Jar(s) from commonly used extensions
can have some advantages, especially where there
is more then one Jar.
- It means the extension can be used in multiple
JNLP files with just a single line for each (main)
JNLP.
- Extensions can have their own icons and license
(etc.)
- Each JNLP can have different levels of trust.
- Code in different extensions can have different
code signers. This is important if the binary is
supplied already signed, and the license dictates
that the Jar must be distributed 'unaltered'.
--
Andrew T.
pscode.org