This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 75280

Summary: [headless] Browser not opened because deploy.ant.client.url not set
Product: serverplugins Reporter: Jiri Skrivanek <jskrivanek>
Component: Sun Appserver 9Assignee: Vince Kraemer <vkraemer>
Status: NEW ---    
Severity: blocker CC: pslechta
Priority: P4    
Version: 5.x   
Hardware: PC   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Jiri Skrivanek 2006-04-20 13:18:41 UTC
Browser is not opened when you try to run enterprise application from command
line. It is because property deploy.ant.client.url is not set. To reproduce:

- Go to Runtime view and add Glassfish server instance.
- Start Glassfish server.
- Create a new Enterprise Application project from template (use Glassfish server).
- Create a new session bean in enclosed EJB project.
- Open command line and go to project folder.
- Execute 'ant run' command. Enterprise application is successfully
deployed but default browser is not opened. Output is the following:

-display-browser-cl:
     [echo] Launching ${deploy.ant.client.url}

run-display-browser:
--------------------------------------------------------------------

Build 20060419-1103, JDK1.5.0_06, WindowsXP.
Comment 1 Jiri Skrivanek 2006-04-20 13:29:14 UTC
For application client project it is similar:

${deploy.ant.client.url}${client.urlPart}
Comment 2 Vince Kraemer 2006-05-11 21:03:39 UTC
need to parse sun-application.xml (if present) to construct
${deploy.ant.client.url}.

If the ${deploy.ant.client.url} is not defined by doing that, then you need to
parse application.xml to construct the ${deploy.ant.client.url}.

may be doable with ant's xmlproperty task.
Comment 3 Vince Kraemer 2006-05-12 21:09:03 UTC
regarding the app client note....  should not open browser when using an app
client anyway, right?
Comment 4 Jiri Skrivanek 2006-05-15 08:02:46 UTC
Yes, app client should not open browser. I think it is already fixed that script
doesn't try to open it.
Comment 5 Vince Kraemer 2006-09-11 19:15:24 UTC
no changes ready for check in today -- 5.5 code freeze
Comment 6 pslechta 2008-07-11 11:47:17 UTC
Is this issue still valid?
Comment 7 Vince Kraemer 2008-07-11 14:58:25 UTC
yes.
Comment 8 Vince Kraemer 2008-10-18 00:07:28 UTC
No user reports.

will apply for v3 in the 7.0 time frame.

Leaving priority set.
Comment 9 Vince Kraemer 2008-10-25 01:54:01 UTC
this is not a p3 for the 7.0 time frame.
Comment 10 Vince Kraemer 2008-12-24 21:57:01 UTC
not worth worrying about in 7.0 time frame