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 119901

Summary: ClassNotFoundException: org.netbeans.modules.websvc.webservices.ProjectWebServicesSupportProvider
Product: webservices Reporter: Dan Kolar <dkolar>
Component: JAX-RPCAssignee: bhate <bhate>
Status: RESOLVED FIXED    
Severity: blocker CC: mkuchtiak
Priority: P3 Keywords: RANDOM
Version: 6.x   
Hardware: All   
OS: All   
URL: http://statistics.netbeans.org/exceptions/detail.do?id=5538
Issue Type: DEFECT Exception Reporter: 5538
Attachments: stacktrace

Description Dan Kolar 2007-10-24 13:46:00 UTC 
Build: NetBeans IDE Dev (Build 071024)
VM: Java HotSpot(TM) 64-Bit Server VM, 1.5.0_13-ea-b01
OS: Linux, 2.6.9-42.0.0.0.1.ELsmp, amd64

User Comments: 
Created simple web project on JBoss 5 beta 2
Comment 1 Dan Kolar 2007-10-24 13:46:09 UTC 
Created attachment 51569 [details]
stacktrace
Comment 2 Milan Kuchtiak 2007-10-24 16:50:20 UTC 
There is something strange with your IDE.
Are all those modules - especially web services, really updated ?

Looks like there is a module containing the following file:
META-INF/services/org.netbeans.modules.websvc.spi.webservices.WebServicesSupportProvider
with the following content:
org.netbeans.modules.websvc.webservices.ProjectWebServicesSupportProvider

The file org.netbeans.modules.websvc.webservices.ProjectWebServicesSupportProvider was already removed.

Dan, please can you provide more information ?

Passing Ajit for evaluation.
Comment 3 bhate 2007-10-24 19:19:23 UTC 
Another issue like this was reported by Jon Baker, just after move of jaxrpc to update center. However, it was not
reproducible with next developer build or new user dir.
Dan can you try with a fresh user dir?
Comment 4 bhate 2007-10-29 20:51:08 UTC 
I think another missmatched nightly build and update center modules issue.
This should not be the case with beta2 or FCS builds. Also its very random.
post FCS.
Comment 5 bhate 2008-01-24 20:11:57 UTC 
The exception has never occurred in 6.0 and later builds.
marking this fixed.