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 88379 - Edit WS Attributes feature don't work
Summary: Edit WS Attributes feature don't work
Status: VERIFIED FIXED
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P1 blocker (vote)
Assignee: Roderico Cruz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-01 08:52 UTC by Jaroslav Pospisil
Modified: 2019-06-12 18:49 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Pospisil 2006-11-01 08:52:21 UTC
Netbeans 6.0 M4, JDK 1.5.0_10

Edit Web Service Attributes feature for WS client and WS from WSDL don't work.
There's no exception(at least that wasn't in log before I click Edit WS
Attributes from context menu) ,no warning,no error, simply nothing occurs and I
checked this affects both Bundled Tomcat and glassfish.
Comment 1 Petr Jiricka 2006-11-15 14:58:14 UTC
Needs to be fixed, however we need to first rewrite the web service support to
Retouche, right?
Comment 2 Milan Kuchtiak 2006-11-15 16:56:11 UTC
The action is implemented in websvc/core module that is actually disabled.
I am working on JMI -> Retouche migration.

Nevertheless, currently, the module is compilable and user can create WS Client.
However, there is a problem WSEditAttributesAction :

(EditWSAttributesCookie)activatedNodes[0].getCookie(EditWSAttributesCookie.class);
returns null.

Theoretically, this action should work (doesn't depend on Retouche, I think).
Comment 3 Roderico Cruz 2006-11-16 00:17:50 UTC
Will look at this.
Comment 4 Jaroslav Pospisil 2006-11-16 08:51:51 UTC
The reason I filled this issue is that WSDL customizer doesn't work in Milestone
4 build already a then there was no Retouche,so it should work there. I think
this problem was caused by merge from NB5.5 branch. I know it's now priority to
fix web services first, but I'm afraid that reason for this issue could remain
even after that, so if it does,at least we'll know, where to search for problem. 
Comment 6 Jaroslav Pospisil 2007-01-11 15:34:54 UTC
VERIFIED in 200701101900
Comment 7 cmp80 2019-06-12 18:49:08 UTC
La información no es buena