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 80650 - function id() does not work
Summary: function id() does not work
Status: VERIFIED WORKSFORME
Alias: None
Product: soa
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: PC All
: P1 blocker (vote)
Assignee: Gabriel Badescu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-19 19:28 UTC by Victoria Zhukovskaya
Modified: 2006-09-08 20:03 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Victoria Zhukovskaya 2006-07-19 19:28:39 UTC 
WinXp, Coke060716

1. Create Synchrounouse BPEL Project
2. There is
	<element name="typeA">
		<complexType>
                        <sequence>
			 <element name="paramA" type="xsd:string" minOccurs="0" maxOccurs="18"
id="MyID1"></element>
                         <element name="paramE" type="xsd:string" minOccurs="0"
maxOccurs="1"></element>
			</sequence>
		</complexType>
        </element>
3.Add assign activity:            
	     <assign name="IDTest">
               <copy>
               <from>concat('ID',
count(id('MyID1')))</from><to>$outputVar.resultType/paramE</to>
               </copy>
             </assign>  
4. inptut.xml has 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:syn="http://www.mycomp.org/BPELMapperSampleSchemaNamespace">
  <soapenv:Body>
    <syn:typeA>
      <syn:paramOperation>6</syn:paramOperation>
      <syn:paramA>String1</syn:paramA>
      <syn:paramA>String2</syn:paramA>
      <syn:paramA>String3</syn:paramA>
      <syn:paramA>String4</syn:paramA>
      <syn:paramA>String5</syn:paramA>
      <syn:paramA>String6</syn:paramA>
      <syn:paramE>Hello World!</syn:paramE>      
    </syn:typeA>
  </soapenv:Body>
</soapenv:Envelope>
5.Deploy and test project

Result of test is <faultcode>SOAP-ENV:Server</faultcode>
Comment 1 Joshua Sandusky 2006-07-21 20:00:08 UTC 
when bpel code that is syntactically correct causes runtime faults, the issue is
either a configuration or runtime issue

this is not a mapper issue if the bpel code that is being generated by the
mapper is syntactically correct
Comment 2 Joshua Sandusky 2006-07-25 17:36:44 UTC 
Can a new Subcomponent be created for the BPEL Service Engine?

This bug should then be assigned to that new subcomponent.
Comment 3 Gabriel Badescu 2006-09-07 01:05:32 UTC 
Please re-test with the latest build
Comment 4 lchang 2006-09-08 20:03:10 UTC 
Reopened into Bugtraq:  6468822