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: | mapper should support soap arrayType in data mapping and wsdl:arrayType | ||
---|---|---|---|
Product: | soa | Reporter: | Ritesh Adval <radval> |
Component: | BPEL Mapper | Assignee: | Alexander Permyakov <alex02> |
Status: | NEW --- | ||
Severity: | blocker | CC: | jsandusky |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: | |
Attachments: |
Google wsdl
sample Google project email thread on support for soap encoding. |
Description
Ritesh Adval
2006-08-28 05:55:16 UTC
Created attachment 33307 [details]
Google wsdl
Also when user expands resultElement[4] he should be able to see elements defined in typens:ResultElement Attaching sample Google project which works soap encoding Created attachment 34191 [details]
sample Google project
Created attachment 34192 [details]
email thread on support for soap encoding.
This is an enhancement in mapper to support soap array. current work around is to type in xpath query in source. This should be fixed as part of support to allow user to edit node test and xpath axis. Need to support wildchar as well. changing issue type. I meant this to be enhancement , it is not fixed yet. see previous comments for structure of part and its xsd element/types. User see something like this is mapper tree: return (part) documentFiltering searchComments estimatedTotalResultsCount resultElements now here resultElements is of type typens:ResultElementArray which is defined as an extension of soapenc:Array, so if resultElements represents an array we need to allow user to create a child step on resultElements. note that since resultElements is an array, its child elements are of the type ResultElement ( this is a complex type defined) For gogogle web service to work we need to create expression something like this: $DoGoogleSearchOut1.return/resultElements/*[ 1]/URL This means following need to be supported: (a) user should be able to select resultElements in mapper tree and lauch a step editor to create this *[1]/URL step. This needs more design. At this point we do not have design to allow user to specify wildchar and also change the name of nodetest. I propose we could do following: (a) if an element is of soap array type , add an action to create location step. (b) This would show a text field where user can type in extra steps: ex user right click on resultElement and say edit step. then he types in *[ 1]/URL this will add a node resultElement*[ 1]/URL in the tree which user can map. when reverse rendering we need to add this node back into tree. Obsolete milestone, please reevaluate This one I think we need to implement. |