BTW the web service client was originally configured to have SSL, username and password.   After deleting the client and
re-adding it, it doesn't get as far as asking me if I want to accept SSL cert or input username/password.  It just
freezes for 20-30 seconds then closes the wizard.  I can access the WSDL using a web browser. 

I reverted to NetBeans 6.0.1 and do not have this problem anymore.

I'm trying it with 6.1 ML now.  I'm having trouble just getting it to generate a client. There seem to be other bugs,
such as WEB-INF/wsdl/MyService.wsdl has to exist so it can delete it before continuing.  I think I reported that
earlier.  I got it to think it regenerated the client but I can't do a build, and still tons of red errors in my code
where I try to use the generated classes.

I think this issue is in fact web application version of Issue 129645, which I reported earlier. Ryan, confirm please,
that web application with error code is still compilable and deployable, just for sure. 

I think there are two issues being reported in this ticket.  The first is after a clean/build, the build fails.  I
wasn't able to get it to regenerate a web service client.  The second is about the red error lines in code editor.  
This morning I tried again to capture more detail for you. 


The build directory contains the web serivce client generated code and binaries.  When I try to do a build, I get this
error:

D:\dev\FolioService\FolioServiceClientDemo\nbproject\build-impl.xml:384:
D:\dev\FolioService\FolioServiceClientDemo\web\WEB-INF\wsdl\FolioService-config.xml not found.
BUILD FAILED (total time: 0 seconds)


Project tree node\Web Pages\WEB-INF contains a wsdl directory with only FolioService.wsdl.  

Next I did a clean/build and got the same error. It didn't appear to regenerate the web service client.  

Next I told it to refresh the web service client. I entered the URL, accepted SSL certificate and entered a valid
username/password.  New client was generated, but can't do a build because of missing FolioService-config.xml.

Next I deleted the web service client from the Web Service Clients tree node, then did a clean.  I recreated a web
service client by providing the URL of WSDL, package name, and accepted the SSL certificate. The project will now build.

I opened my source code that uses the web service client, and all lines that referenced it or one of its classes were
red. Code completion did not work for those classes.

Closed then re-opened IDE.  Still my source code has red errors everywhere. I am able to do a build.

I did a clean/build, and it worked. This is not consistent with what was happening when I opened this ticket.  

Even though I can build, I can't write code because the editor doesn't know about the web service client classes or
provide code completion. 

Someone else MAY be experiencing effects of this bug too through Maven2 & CFX generated client:

http://www.nabble.com/Netbeans-6.1,-maven-2,-junit-and-cxf-td17814535.html

See also the issue 129645

Fix:
http://hg.netbeans.org/main?cmd=changeset;node=df6ba7a302c3

Would it be possible to release this in NB 6.1 Patch 3 instead of NB 6.5?  If not, I will have to skip NB 6.1 entirely
and use NB 6.0.1 until fall/winter 2008 when NB 6.5 is released.  Thanks.

Red error lines still reproducible in both trunk (build 200806300002) and M1. Reopening.

I I found after some investigation, the code completion doesn't work in case the first JAX-RPC client is created in a
project. The workarond is close and open the project or create another client.

The solution is probably to refresh the children of jax-rpc artifacts folder after a client is created.

Fixed.

Diff:
http://hg.netbeans.org/main?cmd=changeset;node=7066b7d02ed3

Integrated into 'main-golden', available in build *200808281401* on http://bits.netbeans.org/dev/nightly/
Changeset: http://hg.netbeans.org/main/rev/7066b7d02ed3
User: mkuchtiak@netbeans.org
Log: #135841: ignit CC when JAX-RPC client is created