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 am encountering such error , looking at file reported in error it looks like everything is ok. Is there anything else to check? I am using following setup: Product Version: NetBeans IDE 6.7 (Build 200906241340) Java: 1.6.0_14; Java HotSpot(TM) 64-Bit Server VM 14.0-b16 System: Windows XP version 5.2 running on amd64; Cp1252; en_US (nb) Userdir: C:\Documents and Settings\Administrator\.netbeans\6.7 ========================= error here ============= Created dir: C:\netbeans\testbridge\testBridgeConsole\build\generated\jax-wsCache\testBridgeManagement command line: wsimport -d C:\netbeans\testbridge\testBridgeConsole\build\generated\jax-wsCache\testBridgeManagement -extension -Xnocompile -keep -s C:\netbeans\testbridge\testBridgeConsole\build\generated\jax-wsCache\testBridgeManagement -catalog C:\netbeans\testbridge\testBridgeConsole\catalog.xml -verbose C:\netbeans\testbridge\testBridgeConsole\xml-resources\web-service-references\testBridgeManagement\wsdl\localhost_8084\Redirector\testBridgeManagement.wsdl -wsdllocation http://localhost:8084/Redirector/testBridgeManagement?wsdl parsing WSDL... [ERROR] Schema descriptor {http://ws.server.testbridge.test.com/}getAllAuditLogEntries in message part "parameters" is not defined and could not be bound to Java. Perhaps the schema descriptor {http://ws.server.testbridge.test.com/}getAllAuditLogEntries is not defined in the schema imported/included in the WSDL. You can either add such imports/includes or run wsimport and provide the schema location using -b switch.2 line 272 of file:/C:/netbeans/testbridge/testBridgeConsole/xml-resources/web-service-references/testBridgeManagement/wsdl/localhost_8084/Redirector/testBridgeManagement.wsdl ============ reported file contents ============== <xsd:schema> <xsd:import namespace="http://ws.server.testbridge.test.com/" schemaLocation="http://localhost:8084/Redirector/testBridgeManagement?xsd=1" /> </xsd:schema> </types> .... line 272 .... <message name="getAllAuditLogEntries"> <part name="parameters" element="tns:getAllAuditLogEntries" /> </message> ... xsd ... <xs:element name="getAllAuditLogEntries" type="tns:getAllAuditLogEntries" /> .... <xs:complexType name="getAllAuditLogEntries"> <xs:sequence> <xs:element name="logintoken" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType> ===========sei code ========= @WebMethod(operationName = "getAllAuditLogEntries") public List<AuditEntry> getAllAuditLogEntries(@WebParam(name = "logintoken") String logintoken ) throws AccessFault { checkAccess(logintoken); return simpleServer.getAllAuditLog(logintoken); } Thanks.
Hi, After a while trying to figure out I notice in Windows task manager about over 700MB mem usage for netbeans java vm. then I soon got a Memory error (GenPerm) and needed to restart netbeans. After that I did not receive any more errors. I think a Memory error would better describe the situation and save user's time instead of a incorrect "[ERROR] Schema descriptor is not defined " as the wsdl is correct and complete . Thanks.
I suspect svn client to cause memory probelms as I did recently enabled svn for projects and before this never encountered memory problems.
It happened again today while working to add new web methods. Restaring netbeans solved the problem and I could continue working. If this is showing up so frequently then it will get in users way by taking time to restart netbeans as ferequently and will make netbeans into a time loosing tool instead of a productivity tool. Please find some solutions for this. Thanks.
An idea would be to run wsimport related tasks in separate vm thus isolating problems and help further study ?
This is related to bug #75967
This problem is the result of insufficient memory problem. There is no simple way to avoid this issue. We can do just some workarounds like suggested run wsimport in the separate VM. But currently there is no way to do this. Probably later we will have a chance to find a way to isolate it.
See the fix for bug 75967