Bug 168571 - Ws import fails to get imported types ...
Ws import fails to get imported types ...
Status: RESOLVED FIXED
Product: webservices
Classification: Unclassified
Component: JAX-WS
6.x
All All
: P3 (vote)
: 7.4
Assigned To: Milan Kuchtiak
issues@webservices
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-14 18:48 UTC by sandi_ro
Modified: 2013-07-11 08:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sandi_ro 2009-07-14 18:48:19 UTC
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.
Comment 1 sandi_ro 2009-07-14 19:13:01 UTC
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. 
Comment 2 sandi_ro 2009-07-14 19:20:50 UTC
I suspect svn client to cause memory probelms as I did recently enabled svn for projects and before this never
encountered memory problems. 
Comment 3 sandi_ro 2009-07-15 15:09:21 UTC
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.   
Comment 4 sandi_ro 2009-07-15 17:01:18 UTC
An idea would be to run wsimport related tasks in separate vm thus isolating problems and help further study ? 
Comment 5 Denis Anisimov 2010-11-02 11:06:10 UTC
This is related to bug #75967
Comment 6 Denis Anisimov 2011-10-07 06:06:22 UTC
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.
Comment 7 Milan Kuchtiak 2013-07-11 08:09:56 UTC
See the fix for bug 75967


By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo