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 59487 - [client] NPE after call websvc operation
Summary: [client] NPE after call websvc operation
Status: VERIFIED WORKSFORME
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: Martin Grebac
URL:
Keywords:
Depends on:
Blocks: 59972
  Show dependency tree
 
Reported: 2005-06-01 12:57 UTC by Lukas Jungmann
Modified: 2005-11-30 21:19 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
messages.log (39.54 KB, text/plain)
2005-06-01 12:58 UTC, Lukas Jungmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lukas Jungmann 2005-06-01 12:57:54 UTC
[build 200505311800]

1. create IDE-generated websvc client from
http://www.progem.bg/BGTrans/services.wsdl
2. create servlet
3. in servlet: "websvc client resources | Call websvc operation"

=>
"Errors occured during operation invocation creation. Some code may not have
been  generated correctly. Unexpected null pointer exception: null"
Comment 1 Lukas Jungmann 2005-06-01 12:58:33 UTC
Created attachment 22424 [details]
messages.log
Comment 2 _ pcw 2005-06-01 19:26:36 UTC
I tried this in a current (~5/28/05) trunk build and had no problems.  Client
was generated via directly download from the specified URL.  What build was this?
Comment 3 Petr Blaha 2005-06-01 19:44:14 UTC
Hi, I was able to reproduce the issue in daily build 20050531 too. I guess that
the issue is caused by JMI migration. Yes, static stub client was created
directly from URL.
Comment 4 Martin Grebac 2005-06-02 09:27:38 UTC
Yes, this is caused by JMI migration. I'll look at it. 
Comment 5 Lukas Hasik 2005-06-17 09:31:47 UTC
Guys, please note that this issue is q-build stopper
http://qa.netbeans.org/q-builds/Q-build-report-200506142000.html Please fix ASAP
and commit also to QBE200506142000 branch, don't forget that it's your
responsibility to check if the fix is good enought and safe. 
Comment 6 Pavel Fiala 2005-06-20 14:59:02 UTC
I cannot reproduce the issue in build 200506142000. Probably the issue was
solved as part of solution of another related issue.
Comment 7 Lukas Jungmann 2005-11-30 21:19:18 UTC
v.