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.
| Summary: | Make generated web service client code visible to the user. | ||
|---|---|---|---|
| Product: | webservices | Reporter: | tonybeckham <tonybeckham> |
| Component: | JAX-WS | Assignee: | Roderico Cruz <rcruz> |
| Status: | NEW --- | ||
| Severity: | blocker | CC: | dkonecny, kaktus, petertliu, pjiricka |
| Priority: | P3 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Issue Type: | ENHANCEMENT | Exception Reporter: | |
| Bug Depends on: | 105645 | ||
| Bug Blocks: | |||
| Attachments: |
Screen shot of project navigator w/ red "x" problem
Web App Client project Web App service project |
||
|
Description
tonybeckham
2007-04-25 22:08:43 UTC
Created attachment 41672 [details]
Screen shot of project navigator w/ red "x" problem
Created attachment 41673 [details]
Web App Client project
Created attachment 41674 [details]
Web App service project
I think this issue could be related to the issue #101387. I will look at it more. In my opinion "... because it appears that the sample is broken when in fact it is not." is not a reason why it should be P1. Regarding to http://qa.netbeans.org/bugzilla/bug_priority_guidelines.html it is more P3. As you said, the project can be built and deployed. I agree that the red x is confusing but I also believe that all user will try to build the project to find what is wrong and if they see the project is working they will not panic. I made it a P1 per discussion w/ peterliu. If he has no problem with the priority I am OK with it. I have found that the most effective way to resolve the issue is to drill down the configuration node of the project in project navigator and simply open StockService.wsdl. Once you do that "x"'s go away. Ok, thanks for the additional information. The red x feature was implemented outside of web project so this project is not directly responsible for this icon badgeing. I will discuss it with the responsible developer. Actually, the method to get the badges away doesn't work all the time. I haven't been able to nail down a consistent way to get rid of them. After some point they just go away. Obsolete milestone, please reevaluate This problem was improved by fix of issue 101387 but there are still some minor issues given by current implementation of web services support in NB, e.g. Java files generated from WSDL are stored in build folder and therefore clean removes them and therefore code completion gets broken and files gets annotated as having compilation error although building them will pass. This will require redesign of the artifact generation. Changing the milestone to future. Since this requires a redesign of the ws client generation, changing to an enhancement. Also changing the Summary text. moving opened issues where TM != dev to TM=TBD |