Bug 221526 - Enterprise Application Client when deployed to Glassfish wrongly shows as Java Web Start disabled
Enterprise Application Client when deployed to Glassfish wrongly shows as Jav...
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: GlassFish
7.1.2
Macintosh Mac OS X
: P3 (vote)
: 7.4
Assigned To: Vince Kraemer
issues@serverplugins
NB_ONLY
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-11-06 05:45 UTC by ianb
Modified: 2013-07-19 23:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ianb 2012-11-06 05:45:31 UTC
Product Version = NetBeans IDE 7.1.2 (Build 201204101705)
Operating System = Mac OS X version 10.6.8 running on x86_64
Java; VM; Vendor = 1.6.0_33
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.8-b03-424

G'day

When an Enterprise Application Client is deployed by NetBeans to Glassfish the Glassfish admin server shows the client application as not Java Web Start enabled. 

Documentation elsewhere suggests that being an EAC the application is intended to be JWS enabled on deployment.

And indeed if you try to JWS the application an attempt is made to run it. It doesn't work but that is a separate issue about which I'll raise Glassfish issues.

Other than the time I wasted trying to find out how to JWS enable the application its not a huge issue. Just a bit confusing. That is assuming that it is only a visual thing and that every other aspect of the JWS enablement has been completed. (That I won't be able to determine till I get JWS of the application to work).

There is a workaround and that is, in the admin server, to undeploy the application, deploy the application (which doesn't offer the option to enable JWS), and then redeploy the application (which does offer the option to JWS enable it). However having done this the applications fails to JWS in the same way. But it at least clears up the ambiguity about whether the application is JWS enabled.

(This may actually be a Glassfish issue but given that when the application is redeployed as above it shows as JWS enabled it is more likely a NetBeans issue.)
Comment 1 TomasKraus 2012-11-22 15:42:29 UTC
Adding Jiri into cc list to test this with 7.3 if he has some time.
Comment 2 Jiri Skrivanek 2012-11-23 09:40:04 UTC
My steps:
- create new application client from template
- deploy it to GlassFish server
- go to Services tab
- right-click GlassFish server node and choose "View Domain Admin Console"
- in browser in left menu go to "Applications|ApplicationClient1"
- Java Web Start is not enabled

Product Version: NetBeans IDE Dev (Build 201211230002)
Java: 1.7.0_10-ea; Java HotSpot(TM) 64-Bit Server VM 23.6-b04
Runtime: Java(TM) SE Runtime Environment 1.7.0_10-ea-b15
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Comment 3 martinandersson.com 2013-04-19 22:00:34 UTC
Yeah I can confirm that this is a real hassle on NetBeans IDE 7.3 and GlassFish 3.1.2.2. The trick to redeploy works for me. However, if I deploy a web start application in a EAR package, all done through GlassFish admin console, all works fine too. So I'm not required to "redeploy", deploying straight from scratch works. But deploying through NetBeans fails utterly. Nor can I right click on my web start project, choose "properties" and see in any way that my project is a web start application. It is as if NetBeans miss this?


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo