|
Hi all, > 3.Passer peak ahead. > Can we look ahead (without pulling) what
element is the next? > Advantage of this is can keep the current
DeSerializer code as it is. > Still additional check logic will be in
generated code. 1. To achieve this we can have add method to the DeSerializer code call
"peakNextElement ()". From "peakNextElement ()" we can get which is
the next element and it can use by the generated code. 2. In this "peakNextElement ()" method will call new method “peak
()”, which it is in XMLParserXerces.cpp file. This “peak ()” method will return the next
node. 3. To avoid to loose next element we have to change the “next ()”
method to check whether “peak ()” is called before and if it called
then avoid call parseNext(m_ScanToken). Do you guys have any comments on this? Thanks Chinthana Subject: [jira] Commented: (AXISCPP-623) Support for the WSDL construct "all" [
http://issues.apache.org/jira/browse/AXISCPP-623?page=comments#action_63752 ] Chinthana Danapala commented on AXISCPP-623: -------------------------------------------- There are two kinds of changes that we have to looking in to this. 1. WSDL tool changes 2. DeSerializer changes. 1.) WSDL tool 1.1 How to decide if we have an "all" construct
in WSDL? 1.2 When we come crosses "all" construct
generate the code accordingly. Changes should be in DeSerialization part of the
complex types. 2.) DeSerializer 2.1 Decide minOccurs 0 or 1. If 1 then get (use current code.) If 0 then check & get 2.2 Check & get Here there are 3 possible changes. 1.We can have a
list of element stored and can compare with the pulled one and select the
matched one. E.g. List
Pulled one A
B B--> C D Here we sellect
the B from the list. But in this
option have additional check logic in generated code for each element. Also
have to change current DeSerializer code. 2.Also we can go
element in sequence order and if it is not matched with pulled one then go to
next. But here need to figure out how to recover pulled element. 3.Passer peak
ahead. Can
we look ahead (without pulling) what element is the next?
Advantage of this is can keep the current DeSerializer code as it is.
Still additional check logic will be in generated code. > Support for the WSDL construct "all" > ------------------------------------ > > Key:
AXISCPP-623 > URL: http://issues.apache.org/jira/browse/AXISCPP-623 > Project: Axis-C++ > Type: New Feature > Components: WSDL processing > Versions: 1.5 Final > Environment: All > Reporter: Dushshantha Chandradasa > Attachments: AllConstructTest.wsdl > > Axis C++ doesn't support the WSDL construct "all". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira |
- RE: [jira] Commented: (AXISCPP-623) Support for the ... Chinthana C. Dinapala
- RE: [jira] Commented: (AXISCPP-623) Support for... Chinthana C. Dinapala
- RE: [jira] Commented: (AXISCPP-623) Support for... Samisa Abeysinghe
