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.
A default enterprise application with an enterprise application client fails to run the application client. The default enterprise application will install on glassfish v3 and display the index page (Hello World!). But if you try and run the app-client the following error is produced. org.glassfish.appclient.client.acc.UserError: ACC007: The app client directory C:\u\WebSpun\src\java\netbeans\JWSv3\JWSv3-app-client does not contain a manifest; the app client container cannot process it. Java Result: 1
I installed netbeans 6.8 on a laptop and I can run the app-client of an enterprise application from a fresh project. I rebooted the server with the original problem, created additional "new" enterprise applications with an app-client and get the same error.
Okay, so MAYBE with sges v3 you cannot simply run an Enterprise Application Client without an ACC. I tried to start up the app via Java Web Start. I get the error, "Unable to launch application". The java console shows ### Java Web Start Error: #### Unable to load resource: http://localhost:10050/__JWSappclient/__system/__dyn/__system.jnlp.
I created an Enterprise Application Client Project. If I try and run the Main.java (left click run), I get the same error as reproted. Note: under sges v2.1 that would work. If I run the "Application Client Project", I do get the main to run. Hmmmm.
(In reply to comment #3) > I created an Enterprise Application Client Project. If I try and run the > Main.java (left click run), I get the same error as reproted. Note: under > sges v2.1 that would work. If I run the "Application Client Project", I do > get the main to run. Vince, appclient deployment changed for v3 and so my first guess is that running main class was not updated? Pass the issue back to me if it is not deployment problem. Thanks. Lowering priority to P2 as there is workaround available.
This is coming back at you... The thing that changed in app clients was how the client is executed. It looks like 'run-single' has always been wrong and not due to the AS. Here is the test that I did... registered a v3 server. create an app client project that targets that server. run the project the server starts. the app appears to run.. undeploy the project. stop the server run the main file. the server does not start. The project does not deploy. running the project fails. One thing I noticed... The run target does not look like it EVER used the carproject:java task... which is what is being used by 'run-single'.
*** Bug 179845 has been marked as a duplicate of this bug. ***
Vince, Re. - "The thing that changed in app clients was how the client is executed" - and that's exactly what this problem is about no? In d30ed5212d39 and 19132b288e45 you fixed project execution and similarly need to be changed other actions. Right now Project Debug and Run Single File both fail with "org.glassfish.appclient.client.acc.UserError: ACC007". Debug Single File fails with yet different error - should be adjusted to match execution of Single File once that one was fixed. I have not tried Run Test or Debug Test but these should just run unit tests against tested class and should not require EE environment (is it true?).
Yes. I did not make changes that would correct functionality which was broken before I came on the scene.
*** Bug 183190 has been marked as a duplicate of this bug. ***
The original problem reported by dbritton: > A default enterprise application with an enterprise application client fails > to run the application client. was fixed as issue 164776. The problem reported by Vince: > registered a v3 server. > create an app client project that targets that server. > run the project > the server starts. the app appears to run.. > undeploy the project. > stop the server > run the main file. > the server does not start. The project does not deploy. running the project > fails. has never ever worked and I'm trying to figure out what to do about it. Because main problem was resolved in issue 164776 I'm lowering priority of this issue.
This should work in 6.10 Milestone1. Was fixed while implementing issue 171153.
thufir, as I asked you in other issue: could you please stop reopening old issues? Just file a new one for current NB release with a description of what's wrong.