Eclipse Community Forums: Rich Client Platform (RCP)

Help

Home

Home » Eclipse Projects » Rich Client Platform (RCP) » RCP WebStart problems

Show: Today's Messages :: Show Polls :: Message Navigator

RCP WebStart problems [message #435774]

Tue, 23 August 2005 13:25

Dennis Vaughn

Messages: 13
Registered: July 2009

Junior Member

When my application is executed via the jnlp file all of the jars are
downloaded. Then the JWS console appears for a second or two before it
dissapears and nothing else happens. There is nothing in the logs. Is
there anyway to debug the jws app? Has anybody else had this problem?
Also my app uses the platform and jdt features in addition to rcp and my
feature.

tia,
Dennis

Report message to a moderator

Re: RCP WebStart problems [message #435776 is a reply to message #435774]

Tue, 23 August 2005 16:37

Ricky

Messages: 204
Registered: July 2009

Senior Member

> When my application is executed via the jnlp file all of the jars are
> downloaded. Then the JWS console appears for a second or two before it
> dissapears and nothing else happens.

I had this error for a long time and there are several suspects. Normally
I would say that a lot of my suggestions are unrelated to this problem but
using eclipse and RCP I learned that the only way to handle a big blob of
spagetti java code like the eclipse internals is to try random actions and
pray a lot. Especially if you get only cryptic error messages.

1. Missing plugins. Some plugins are simply not downloaded because they
were not properly exported in the first place.

2. Missing exports. If a plugin is used by another plugin the exporting
plugin must have a manifest file which lists all exported packages. Having
only a plugin.xml does not work as the tag runtime/libray/export isnt
evaluated.

3. ClassDefNotFoundError. My favorite and corelated to 2. Maybe you do not
have the lib in the classpath (runtime-tab of manifest.mf) or you forgot
to include it into your jar (build-tab). Or you accidently reduced
visiblity of the package (runtime-tab upper right).

4. osgi.bundles. I havent confirmed this one jet but having a property
"osgi.bundles=id.of.my.plguin:start,other.plugin:start" in your jnlp cant
be wrong. UPDATE. It is not needed so maybe it would break something if it
there.

5. Everything is working only the configuration files are outdated. Before
downloading the jnlp delete the configuration folder on the client.
Removing your app from the webstart cache is also a good idea to have a
clean start.

6. webstart complains that a file is not signed. Cancel and simply start
the download again, at least javaws 1.5 has some problems with verifing.

7. Do not load a application exported for one OS on another OS. Nothing
will happen. "Code once, run everywhere" was a reality successfully
destroyed by SWT.

> There is nothing in the logs.

Excuse me for this questing but did you look in the logs on the client in
the folder where your osgi.instance.area property is pointing to?

HTH,

Ricky

Report message to a moderator

Re: RCP WebStart problems [message #435783 is a reply to message #435776]

Wed, 24 August 2005 00:48

Pascal Rapicault

Messages: 440
Registered: July 2009

Senior Member

Man, your stealing my job :-)
Although usually I don't recommend the praying part :-)

PaScaL

Ricky wrote:
>> When my application is executed via the jnlp file all of the jars are
>> downloaded. Then the JWS console appears for a second or two before
>> it dissapears and nothing else happens.
>
>
> I had this error for a long time and there are several suspects.
> Normally I would say that a lot of my suggestions are unrelated to this
> problem but using eclipse and RCP I learned that the only way to handle
> a big blob of spagetti java code like the eclipse internals is to try
> random actions and pray a lot. Especially if you get only cryptic error
> messages.
>
> 1. Missing plugins. Some plugins are simply not downloaded because they
> were not properly exported in the first place.
>
> 2. Missing exports. If a plugin is used by another plugin the exporting
> plugin must have a manifest file which lists all exported packages.
> Having only a plugin.xml does not work as the tag runtime/libray/export
> isnt evaluated.
>
> 3. ClassDefNotFoundError. My favorite and corelated to 2. Maybe you do
> not have the lib in the classpath (runtime-tab of manifest.mf) or you
> forgot to include it into your jar (build-tab). Or you accidently
> reduced visiblity of the package (runtime-tab upper right).
>
> 4. osgi.bundles. I havent confirmed this one jet but having a property
> "osgi.bundles=id.of.my.plguin:start,other.plugin:start" in your jnlp
> cant be wrong. UPDATE. It is not needed so maybe it would break
> something if it there.
>
> 5. Everything is working only the configuration files are outdated.
> Before downloading the jnlp delete the configuration folder on the
> client. Removing your app from the webstart cache is also a good idea
> to have a clean start.
>
> 6. webstart complains that a file is not signed. Cancel and simply
> start the download again, at least javaws 1.5 has some problems with
> verifing.
>
> 7. Do not load a application exported for one OS on another OS. Nothing
> will happen. "Code once, run everywhere" was a reality successfully
> destroyed by SWT.
>
>
>> There is nothing in the logs.
>
>
> Excuse me for this questing but did you look in the logs on the client
> in the folder where your osgi.instance.area property is pointing to?
>
> HTH,
>
> Ricky

Report message to a moderator

Previous Topic:	How to get the text under the mouse in the org.eclipse.swt.widgets.Text
Next Topic:	documentation for Bundle-NativeCodeos

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sun Dec 08 07:04:07 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter