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 147416 - Service Bridge wizard not using the correct WSDL
Summary: Service Bridge wizard not using the correct WSDL
Status: VERIFIED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: XSLT (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Vitaly Bychkov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-16 19:59 UTC by andyloh
Modified: 2008-10-17 23:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Verified project (19.47 KB, application/x-compressed)
2008-10-17 23:53 UTC, rpoon 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description andyloh 2008-09-16 19:59:23 UTC 
Observed with the 9/10 and 9/15 GFESB builds.  I attempted to create a Service Bridge using the Service Wizard.  I made
sure the different WSDL operations were selected in the We Implement (HelloXSLTBridgeWSDLOperation) and We Call
(HelloXSLTWSDLOperation) fields.  After finishing the wizard, I checked the transformmap.xml source code and observed
(as Kevan had suggested) that the same WSDL operation was invoking itself.  This resulted in an OutOfMemoryError when I
attempted to run the test.

    <import namespace="http://j2ee.netbeans.org/wsdl/HelloXSLTBridge/HelloXSLTBridgeWSDL"
location="../../HelloXSLTBridge/src/HelloXSLTBridgeWSDL.wsdl"/>
    <service name="Service1" portType="ns1:HelloXSLTBridgeWSDLPortType">
        <operation opName="HelloXSLTBridgeWSDLOperation" inputVariable="inOpVar1" outputVariable="outOpVar1">
            <transform file="InXslFile1.xsl" source="$inOpVar1.part1" result="$inInvokeVar1.part1" name="InTransform1"/>
            <invoke inputVariable="inInvokeVar1" outputVariable="outInvokeVar1" name="Invoke1"
portType="ns1:HelloXSLTBridgeWSDLPortType" opName="HelloXSLTBridgeWSDLOperation"/>
            <transform file="OutXslFile1.xsl" source="$outInvokeVar1.part1" result="$outOpVar1.part1" name="OutTransform1"/>
        </operation>
    </service>
Comment 1 andyloh 2008-09-16 20:00:08 UTC 
Keyword NO65 added.
Comment 2 Vitaly Bychkov 2008-09-17 00:18:12 UTC 
Fixed in soa-dev.
Changeset: eaa3a09ce0a2.
Comment 3 rpoon 2008-10-17 23:52:22 UTC 
Verified with build: \\thumper\50builds\gfesb\v2\nightly\20081015-1408

Verified with the following steps:

1) Create a new XSLT based on the XSLT sample 'HelloXSLTransformation' (and call it 'rp_HelloXSLTransformation')
2) Create a new WSDL 'HelloXSLTBridgeWSDL' (with 'HelloXSLTWSDLOperation').
3) Create a new XSL Service with:
      Service Type:  Serve bridge
      Under 'We Implement', operation = HelloXSLTWSDLOperation
      Under 'Call call', operation = HelloXSLTWSDLOperation

Once the XSL Service is finished, verified that in the transformmap.xml source, the same WSDL operation does not 
invoking itself (see source code below):

    <import namespace="http://j2ee.netbeans.org/wsdl/HelloXSLTransformation/HelloXSLTWSDL" 
location="HelloXSLTWSDL.wsdl"/>
    <import namespace="http://j2ee.netbeans.org/wsdl/rp_HelloXSLTransformation/HelloXSLTBridgeWSDL" 
location="HelloXSLTBridgeWSDL.wsdl"/>
    <service name="rpService1" portType="ns1:HelloXSLTBridgeWSDLPortType">
        <operation opName="HelloXSLTBridgeWSDLOperation" inputVariable="inOpVar1" outputVariable="outOpVar1">
            <transform file="InXslFile1.xsl" source="$inOpVar1.part1" result="$inInvokeVar1.part1" name="InTransform1"/>
            <invoke inputVariable="inInvokeVar1" outputVariable="outInvokeVar1" name="Invoke1" 
portType="ns2:HelloXSLTWSDLPortType" opName="HelloXSLTWSDLOperation"/>
            <transform file="OutXslFile1.xsl" source="$outInvokeVar1.part1" result="$outOpVar1.part1" 
name="OutTransform1"/>
        </operation>
    </service>
Comment 4 rpoon 2008-10-17 23:53:08 UTC 
Created attachment 72166 [details]
Verified project