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 166945 - New WSDL wizard inside EJB project doesn't "see" schema files in the default package.
Summary: New WSDL wizard inside EJB project doesn't "see" schema files in the default ...
Status: RESOLVED WONTFIX
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker with 4 votes (vote)
Assignee: Shivanand Kini
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-11 21:17 UTC by Jun Qian
Modified: 2016-07-07 09:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
new WSDL wizard in EJB project (85.79 KB, image/png)
2009-06-11 21:21 UTC, Jun Qian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jun Qian 2009-06-11 21:17:36 UTC
Steps to reproduce:

1. Create a new EJB project
2. Create a new XSD file and define some elements
3. Create a new WSDL. In the abstract configuration step, try to change the Input part1's element/type. In the "Select
Element or Type" window, we don't see the elements defined in our XSD file (see snapshot).

The above steps work in BPEL project.


Product Version: NetBeans IDE 6.5.1 (Build 200905151554)
Java: 1.6.0_03; Java HotSpot(TM) Client VM 1.6.0_03-b05
System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Userdir: C:\GlassFishESBv21RC2\.netbeans\glassfishesb
Comment 1 Jun Qian 2009-06-11 21:21:04 UTC
Created attachment 83464 [details]
new WSDL wizard in EJB project
Comment 2 Jun Qian 2009-06-12 00:58:21 UTC
Only XSDs defined in the default package don't work. If the XSD is defined in a package other than the default package,
then it is available in the WSDL wizard.
Comment 3 Shivanand Kini 2009-06-12 18:57:53 UTC
*** Issue 166576 has been marked as a duplicate of this issue. ***
Comment 4 Jun Qian 2009-06-12 21:06:37 UTC
The same issue is observed in CompApp project.
Comment 5 Shivanand Kini 2009-07-17 01:29:34 UTC
In order to fix this generically across projects, we have to use the LogicalViewProvider view, and get the xsd/wsdl from 
the related folders. All other folders are ignored.

For example, anything outside of src/test folders are generally ignored, if the LogicalViewProvider is not able to show it 
in the projects view.

This approach is used in import customizer, to populate the view based on LogicalViewProvider. The only difference in wsdl 
tools approach is to reduce number of nodes, and serialize the folder structure into one node (this reduces the click 
count).
Comment 6 Shivanand Kini 2009-07-17 01:49:32 UTC
Committed into soa-dev65
http://hg.netbeans.org/soa-dev65/rev/aedbf11db3b5
Comment 7 jlautz 2009-10-30 22:36:45 UTC
Attempted to verify with Glassfish 2.2  build 20091029-0719 with 
NETBEANS_BUILD=200910252201
NETBEANS_VERSION=6.7.1
SOA_BUILD=091028

I noticed the following behavior reproducing the EJB scenario:

=> Every few times I pull up the Type or Element dialog (from the property dialog, or in a wizard), I either see the
.xsd file twice in the by File list of the Type or Element dialog (screenshot attached), or no .xsd files at all
(screenshot attached). I never see the just one .xsd I actually have.

I see similar behavior with Compapp, although I've only seen one or zero .xsds where there should be one, not two.

Sometimes it settles into producing the same 2x .xsd file or no .xsd file behavior repeatedly. Sometimes waiting for a
minute or so reverts to showing the .xsd file 2x (a less-severe bug, IMHO). 

Comment 8 Martin Balin 2016-07-07 09:56:10 UTC
This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue.

Thanks for your cooperation,
NetBeans IDE 8.2 Release Boss