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.
Hi, I have a J2SE WS client application that I use to test my WS's in an EAR project. I can run the client in RC2 without problems, but when I run it in RC3 I get an error in GFv2.1. Same application, sources, project, only difference is NB 6.7 RC2 vs. RC3. See the attachments for the logs of GF and the output from the build. Iwan
Created attachment 83709 [details] GF output cut-paste from NB
Created attachment 83710 [details] Ant output cut-paste from NB
Created attachment 83711 [details] GF output cut-paste from NB
Created attachment 83712 [details] Ant output cut-paste from NB
The server log would be useful for diagnosing this issue. Please verify that you are running the same thing in both cases (rc2 and rc3). Please outline the steps you are following (in detail) to reproduce this issue. It looks like you are deploying an ent app that contains an app client and then using the Run item on the app client project... This would attempt to deploy the app client 'stand-alone' and there is likely to be a conflict between the two clients in the server's namespace.
I am doing the exact same thing in both RC2 and RC3. And yes, I am running the J2SE app which results in the build-deployment of the EAR project and the start of GF v2.1 both in RC2 and RC3. The only difference is that it works in RC2 and it doesn't in RC3. I tried running my client in RC3: - with an already running GF with deployed EAR, - with an already running GF but without the EAR deployed yet - with GF not yet running and the EAR already deployed - with GF not yet running and the EAR not yet deployed I can't get my client app to start in RC3. All of the above scenario's work in RC2. Although in that case I get an error that one of the JARs that is needed (which is created in another project) isn't available. Although it is available and it all works nicely. Iwan
step-by-step instructions of how to reproduce this issue would be helpful...
user reported that this issue was not present in 6.7 FCS. closing as WFM