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 87236 - Unable to handle nested elements in WSDL editor templates
Summary: Unable to handle nested elements in WSDL editor templates
Status: NEW
Alias: None
Product: xml
Classification: Unclassified
Component: WSDL Tools (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@xml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-16 19:36 UTC by Alexander Fung
Modified: 2007-02-01 01:11 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Fung 2006-10-16 19:36:37 UTC
Many extensibility elements have nested sub-elements.  The WSDL Editor's "New
WSDL  Editor Wizard" can't seem to handle nested sub-elements when using the
template feature.  Please see the description below:

Hi,

We are supporting the following hierachy for extensiility elements in JDBC BC as
given below, (Sorry for long mail).

 Binding
        BindingOperation
                 JDBCOperation
                        Jdbc:input
                                jdbc:sql

In this case i have designed my template.xml file as given below, 

 Binding
        BindingOperation
                 JDBCOperation
                        Jdbc:input
                        jdbc:sql                                   
<template name="SelectOperation">
      <wsdlElement name="Binding">
           <extensionElement name="binding">
           </extensionElement>
      </wsdlElement>
      <wsdlElement name="BindingOperation">
           <extensionElement name="operation">
           </extensionElement>
      </wsdlElement>
       <wsdlElement name="BindingOperationInput"> 
            <extensionElement name="input" >
                <extensionAttr name="operationType" defaultValue="select" />
                <extensionAttr name="numberOfRecords" defaultValue="Please
specify a value" />       
           </extensionElement>   
           <extensionElement name="sql" >
               <extensionAttr name="paramOrder" defaultValue="Please specify
parameter order" />
               <extensionAttr name="sql" defaultValue="Please specify sql
statement" /> 
               <extensionAttr name="PKName" defaultValue="Please specify PKName
Column" />
               <extensionAttr name="FlagColumn" defaultValue="Please specify
Flag Column Name" /> 
           </extensionElement> 
      </wsdlElement>
      <wsdlElement name="ServicePort">
          <extensionElement name="address" >
               <extensionAttr name="jndiName"  defaultValue="Please specify a
value"/> 
          </extensionElement>
      </wsdlElement>
  </template>

i am not getting the element jdbc:sql under jdbc:input instead i am getting the
jdbc:sql as sibling to the element jdbc:input.

I tried by adding the jdbc:sql element as part of extension element jdbc:input as,

<wsdlElement name="BindingOperationInput"> 
            <extensionElement name="input" >
                <extensionAttr name="operationType" defaultValue="select" />
                <extensionAttr name="numberOfRecords" defaultValue="Please
specify a value" />       
               <extensionElement name="sql" >
                   <extensionAttr name="paramOrder" defaultValue="Please specify
parameter order" />
                   <extensionAttr name="sql" defaultValue="Please specify sql
statement" /> 
                   <extensionAttr name="PKName" defaultValue="Please specify
PKName Column" />
                   <extensionAttr name="FlagColumn" defaultValue="Please specify
Flag Column Name" /> 
               </extensionElement> 
           </extensionElement>  
</wsdlElement>

In this case i am not getting jdbc:sql view in the design model of wsdl
document. I guess we do not have support for nested elements in this case. I am
wondering whether this is the way to do or is there any other element which I
can make use so that the element <jdbc:sql> becomes child element

Is there any API or the documentation where I can look at how can I design of
the template.xml in my own way for the jdbc?  Can you please point me where can
I look for?
Comment 1 bchandrakanth 2006-10-17 11:00:37 UTC
we "BC Developers" also need support to extend the wsdl wizard ie., 
during\after 4th step 'Concrete Configuration', so that each binding component 
may allow the user to configure BC specific information. For example, in MSMQ 
BC the user can specify the "Queue Name" and other attributes. In the current 
implementation this is done in the WSDL Editor after the WSDL Wizard generates 
the wsdl.
Comment 2 Ritesh Adval 2006-12-14 20:36:37 UTC
We should fix this in Gavotte so adding a dependency from umbrella bug.
Comment 3 Shivanand Kini 2007-02-01 01:11:19 UTC
Alex, Can you update whether this is still required.