[prev in list] [next in list] [prev in thread] [next in thread]
List: axis-c-dev
Subject: RE: Axis c++ 1.5 release plan (draft 4)
From: "Carsten Blecken" <cblecken () macrovision ! com>
Date: 2005-01-31 18:45:39
Message-ID: D0CF470B361DB646881635F38AE189B801BFD6A2 () min ! macrovision ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Sorry for the late reply but my timezone (PST) seems to be a bit different than most \
other people here.
First of all, the changes are only related to the document literal serialization and \
code generation in cpp mode. RPC style and c stubs are unaffected.
I have had trouble running the test suite in tests/auto_build (with the two services \
I have there, it seems the request doesn't make it to the service), but I have run \
the relevant examples in samples (doclitbase, base,doclitgroupB,groupB) successfully, \
which include the mesa interoperability tests. This is insufficient for testing the \
code generation changes (since the stub are statically checked in) but it does test \
the serializer changes - that's where I got some confidence that the serializer \
changes won't wreak havoc.
More details in case somebody wants to run the changes:
The diffs for the two files representing the code generation changes are attached.
These are src/wsdl/org/apache/axis/wsdl/wsdl2ws/cpp/literal/BeanParamWriter.java
and
src/wsdl/org/apache/axis/wsdl/wsdl2ws/cpp/literal/ClientStubWriter.java
I also attached the test case I intend to add into tests/auto_build (The \
FourLevelTestDoc.wsdl into tests/auto_build/testcases/wsdl, the FourLevelTestDoc.xml \
file into tests/auto_build/testcases/wsdl, the test client FourLevelTestDocClient.cpp \
into tests/auto_build/testcases/client/cpp, the test server \
FourLevelTestDocInterface.cpp into tests/auto_build/testcases/client/cpp and the \
expected output FourLevelTestDoc.expected into tests/auto_build/testcases/output).
I will keep plugging away at this to run these on my own. BTW, so far I have trying \
to use the SimpleAxisServer - would it be better to use the apache plugin?
Thanks,
Carsten
-----Original Message-----
From: sanjaya singharage [mailto:sanjayas@opensource.lk]
Sent: Monday, January 31, 2005 5:56 AM
To: Apache AXIS C Developers List
Subject: Re: Axis c++ 1.5 release plan (draft 4)
No problem. as long as we get unconfused :). (I think there was a full stop missing \
in this reply and I have put it there to avoid further confusion :) )
Carsten, could you take note and respond please?
sanjaya.
----- Original Message -----
From: John <mailto:HAWKINSJ@uk.ibm.com> Hawkins
To: Apache AXIS C Developers List <mailto:axis-c-dev@ws.apache.org>
Sent: Monday, January 31, 2005 7:31 PM
Subject: Re: Axis c++ 1.5 release plan (draft 4)
hi,
sorry for the confusion :-)
I suggest we ask Carsten to run the regression tests to ensure that his code gen \
changes have not broken stuff on at least one platform of his choice. He can then \
decide, based on this test results, which he can discuss here if necessary, whether \
he wants to commit his changes or not. If he runs the suite and gets some errors then \
I suggest we're happy. if he breaks that suite entirely then we're not?
Running the suite should take him three hours from scratch, if he hasn't done it \
before so we should know soon whether the gen changes are viable.
If he is not able to test them (not having the services would be the obvious issue) \
then perhaps one of us can run them for him (Carsten - have you got a branch we can \
extract?).
If Carsten is not around or able to commit changes then I suggest we go alpha without \
the gen changes and do the same as above in alpha timeframe.
John Hawkins
"sanjaya singharage" <sanjayas@opensource.lk>
31/01/2005 13:09
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
cc
Subject
Re: Axis c++ 1.5 release plan (draft 4)
(If the situation is not clear, Carseten has already put his changes to the \
serializer. He has also finished the changes to the code generator but is not able to \
test them as yet, therefore he has avoided committing those changes.)
What exactly do you mean? That we go ahead with the codefreeze with the serilizer \
changes intact and let Carsten commit the code generation stuff before the final? If \
so we can codefreeze early tuesday morning and start on the release procedure.
sanjaya.
----- Original Message -----
From: <mailto:HAWKINSJ@uk.ibm.com> John Hawkins
To: <mailto:axis-c-dev@ws.apache.org> Apache AXIS C Developers List
Sent: Monday, January 31, 2005 6:45 PM
Subject: Re: Axis c++ 1.5 release plan (draft 4)
I would suggest Carsten put in his fixes asap (into the Alpha preferably?) but not \
hold up alpha or beta?
John Hawkins
"sanjaya singharage" < <mailto:sanjayas@opensource.lk> sanjayas@opensource.lk>
31/01/2005 12:27
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" < <mailto:axis-c-dev@ws.apache.org> \
axis-c-dev@ws.apache.org>
cc
Subject
Re: Axis c++ 1.5 release plan (draft 4)
So do we wait for Carsten to comment the serializer changes?
sanjaya.
----- Original Message -----
From: <mailto:HAWKINSJ@uk.ibm.com> John Hawkins
To: <mailto:axis-c-dev@ws.apache.org> Apache AXIS C Developers List
Sent: Monday, January 31, 2005 4:28 PM
Subject: Re: Axis c++ 1.5 release plan (draft 4)
Hmm, we're changing the paradigm here - putting in new code in beta !
Howver, this problem is a bug therefore I go with putting it in beta. As long as it \
comes with some good tests that broke before it was implemented and are fixed by its \
incorporation.
John Hawkins
"sanjaya singharage" < <mailto:sanjayas@opensource.lk> sanjayas@opensource.lk>
31/01/2005 08:52
Please respond to
"Apache AXIS C Developers List"
To
"Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
cc
Subject
Re: Axis c++ 1.5 release plan (draft 4)
I think the serializer changes for AXISCPP-197 should be commented out
before we go for the 1.5 codefreeze.
Can we have a quick response from the community on this?
i.e. Do we keep the serializer changes for AXISCPP-197 in the codebase for
1.5 alpha or comment it out and include both serializer and codegeneration
changes for the final?
please respond quickly guys.
sanjaya.
----- Original Message -----
From: "Carsten Blecken" <cblecken@macrovision.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Monday, January 31, 2005 12:49 PM
Subject: RE: Axis c++ 1.5 release plan (draft 4)
> Quick status update :
>
> I wasn't able to test sufficiently the code generation changes, so I
> did not commit them (i'm having problems with the testing framework
> but that's a different story).
>
> The changes to the serializer have been committed last week. These
> changes should not break the existing stubs since they mostly add
> new method overloads with prefixes for the serializer that miss them.
>
> I will try to get the code generation changes into the beta time frame
> and was hoping that it was ok to leave the serializer changes in there.
>
> Carsten
>
> -----Original Message-----
> From: Carsten Blecken
> Sent: Thursday, January 27, 2005 8:46 AM
> To: Apache AXIS C Developers List; Samisa Abeysinghe
> Subject: RE: Axis c++ 1.5 release plan (draft 4)
>
>
> Sorry for the mess everybody - I assumed friday to be the last day (my
mistake).
>
> In terms of things already committed : These are changes to the serializer
which
> add namespace and/or namespace prefixes to various methods. They are
overloaded
> methods to keep backward compatibility with current stubs. So I would say
the
> risk is not too big. There was also some refactoring being done, but I did
some
> testing on the changes.
>
> The part where I need more time are the stub/skeleton generator (which
employ the
> new methods) and the testing involved with it.
> Maybe I should hold off the generator changes until after alpha, since I
consider
> them higher risk?
>
> In terms of importance: Our current wsdl's break due to the lack of
namespace
> prefixing. Almost all more complicated doc lit wsdl's will have issues
here when
> they have data type nesting and arrays.
>
> Carsten
>
> -----Original Message-----
> From: Samisa Abeysinghe [mailto:samisa.abeysinghe@gmail.com]
> Sent: Thursday, January 27, 2005 3:37 AM
> To: Apache AXIS C Developers List
> Subject: Re: Axis c++ 1.5 release plan (draft 4)
>
>
> Part of the solution has been already commited.
> So we have to either hold off or comment out what is already commited.
>
> How critical/important is this feature?
>
> Is it practicle to tag the CVS and start on testing cycle till the
> rest of the solution is commited.
> Given that the solution is related to serializer, the risk of side
> effects is high.
>
> Thanks,
> Samisa...
>
>
> On Thu, 27 Jan 2005 09:16:35 +0000, John Hawkins <HAWKINSJ@uk.ibm.com>
wrote:
> >
> > Hmm,
> >
> > Should we hold off on alpha until it's complete?
> >
> >
> >
> >
> > John Hawkins
> >
> >
> >
> >
> > "Carsten Blecken" <cblecken@macrovision.com>
> >
> > 27/01/2005 08:39
> > Please respond to
> > "Apache AXIS C Developers List"
> > To"Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>,
> > <sanjayas@opensource.lk>
> > cc
> > SubjectRE: Axis c++ 1.5 release plan (draft 4)
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Sanjaya,
> >
> > still working on item 7). Harder than I thought. Partially committed
> > (Serializer changes) and I think I can get the rest
> > (code generator) by friday into the alpha.
> >
> > Do you want status by friday again?
> >
> > Carsten
> >
> > -----Original Message-----
> > From: sanjaya singharage [mailto:sanjayas@opensource.lk]
> > Sent: Wednesday, January 26, 2005 10:30 PM
> > To: Apache AXIS C Developers List
> > Subject: Axis c++ 1.5 release plan (draft 4)
> >
> > Hi all,
> >
> > COULD I HAVE THE STATUS OF ITEM NUMBER 7 CARSTEN, IS IT ALREAD COMMITED
IN
> > CVS? CAN WE INCLUDE IT IN 1.5 OR SHELF IT FOR THE NEXT RELEASE? OR ARE
YOU
> > PLANNING TO FIX THIS BY 1.5 FINAL? COULD I HAVE A RESPONSE CARSTEN?
> >
> >
> > MARK, WHAT IS THE STATUS OF ITEM 2? COULD YOU ALSO RESPOND?
> >
> >
> > Following the discussion I have added these items
> > -Problem with complex types which contain complex types
> > http://issues.apache.org/jira/browse/AXISCPP-197 (in progress by
carsten)
> >
> > Following the discussion I have removed the following items
> >
> > -Fault mapping (stub level)
> > -improvement of Web Site
> > a.Web-site should be made more or less like Axis-Java website for ease
of
> > use
> > b.More user oriented and less developer oriented
> > -Add support for xsd:any type (?)
> > -Ability to add custom headers (?)
> >
> >
> > sanjaya.
> >
> > =======================================================
> >
> > (fourth draft of the release plan.)
> >
> > Hi all,
> > I would like to volunteer to be the release manager for the Axis C++ 1.5
> > release.
> >
> > A draft Release Plan is presented below using the current items found in
the
> > wiki at http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/ToDo1.5 .
> > Please update the wiki of any more items that are applicable to the 1.5
> > release that developers are working on.
> >
> > Also we need to decide on dates for code freeze etc. and release dates
at
> > the bottom.
> > Please comment.
> >
> >
> >
> > This is the release plan (draft) for Axis C++ version 1.5. Given below
is a
> > snapshot
> > of all the changes for 1.5 since the 1.4 version.
> >
> > Changes from 1.4 to 1.5:
> >
> > 1. Partial C support -
> > http://issues.apache.org/jira/browse/AXISCPP-210 (in progress by Mark)
> > -C clients with stub generation for simple types
> > -Porting of some C++ tests to C
> > 2. Memory clean-up and fix -
> > http://issues.apache.org/jira/browse/AXISCPP-149 (in progress by Mark
> > Whitlock as per JIRA)
> > 3. Improve HTTP Support -
> > http://issues.apache.org/jira/browse/AXISCPP-176 (Done by Samisa as per
> > JIRA)
> > 4. "100 Continue" support in axis2 transport
> > http://issues.apache.org/jira/browse/AXISCPP-311 (Done by Samisa)
> > 5. Proxy support for axis2 transport
> > http://issues.apache.org/jira/browse/AXISCPP-325 (Done by Samisa)
> > 6. Numerous memory leak fixes (Done by Samisa)
> > 7. Problem with complex types which contain complex types
> > http://issues.apache.org/jira/browse/AXISCPP-197 (in progress by
Carsten)
> >
> > Details on these features could be found on JIRA and the AxisCpp TODO
wiki
> > page at http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/ToDo1.5
> >
> > Release Criteria:
> >
> > - Functional tests pass
> > - Test on installation procedures
> > - Test on different versions of Apache web server(1.3.xx, 2.0.xx)
> > - Test samples on different platforms (Linux, Microsoft Windows)
> > - Fix blockers and most critical bugs that applies to 1.5
> >
> > Dates:
> >
> > The following are the proposed dates for the release, opinions please:
> > Code freeze January 27, 2005
> > Release alpha version January 31, 2005
> > Release 1.5 final February 21, 2005
> >
> >
> > sanjaya.
> >
>
>
>
[Attachment #5 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1276" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>Sorry
for the late reply but my timezone (PST) seems to be a bit different than most
other people here.</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>First
of all, the changes are only related to the document literal serialization
and code generation</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>in cpp
mode. RPC style and c stubs are unaffected.</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005> </SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>I have
had trouble running the test suite in tests/auto_build (with the two services I
have there, it seems </FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>the
request doesn't make it to the service), but I have run the relevant examples in
samples (doclitbase,</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>base,doclitgroupB,groupB) successfully, which include the mesa
interoperability tests.</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>This
is insufficient for testing the code generation changes (since the stub are
statically checked in) but it</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>does
test the serializer changes - that's where I got some confidence that the
serializer changes</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>won't
wreak havoc.</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>More
details in case somebody wants to run the changes:</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>The
diffs for the two files representing the code generation changes are
attached.</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>These
are
src/wsdl/org/apache/axis/wsdl/wsdl2ws/cpp/literal/BeanParamWriter.java</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>and</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>src/wsdl/org/apache/axis/wsdl/wsdl2ws/cpp/literal/ClientStubWriter.java</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>I also
attached the test case I intend to add into tests/auto_build (The
FourLevelTestDoc.wsdl into </FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>tests/auto_build/testcases/wsdl,</FONT></SPAN><SPAN
class=038110818-31012005><FONT face=Arial color=#0000ff size=2> the
FourLevelTestDoc.xml file into
tests/auto_build/testcases/wsdl,</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>the
test client FourLevelTestDocClient.cpp into
tests/auto_build/testcases/client/cpp, </FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>the
test server FourLevelTestDocInterface.cpp into
tests/auto_build/testcases/client/cpp </FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005></SPAN><SPAN class=038110818-31012005><FONT
face=Arial color=#0000ff size=2>and the expected output
FourLevelTestDoc.expected into
tests/auto_build/testcases/output).</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff size=2>I will
keep plugging away at this to run these on my own. BTW, so far I have trying to
use the </FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>SimpleAxisServer - would it be better to use the apache
plugin?</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2>Carsten</FONT></SPAN></DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN><SPAN class=038110818-31012005><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=038110818-31012005><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> sanjaya singharage
[mailto:sanjayas@opensource.lk]<BR><B>Sent:</B> Monday, January 31, 2005 5:56
AM<BR><B>To:</B> Apache AXIS C Developers List<BR><B>Subject:</B> Re: Axis c++
1.5 release plan (draft 4)<BR><BR></FONT></DIV>
<DIV><FONT face=Arial size=2>No problem. as long as we get unconfused :). (I
think there was a full stop missing in this reply and I have put it there to
avoid further confusion :) )</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Carsten, could you take note and respond
please?</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>sanjaya.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: \
#000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style="FONT: 10pt arial">----- Original \
Message ----- </DIV> <DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=HAWKINSJ@uk.ibm.com href="mailto:HAWKINSJ@uk.ibm.com">John
Hawkins</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=axis-c-dev@ws.apache.org
href="mailto:axis-c-dev@ws.apache.org">Apache AXIS C Developers List</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Monday, January 31, 2005 7:31
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: Axis c++ 1.5 release plan
(draft 4)</DIV>
<DIV><BR></DIV><BR><FONT face=sans-serif size=2>hi,</FONT> <BR><FONT
face=sans-serif size=2>sorry for the confusion :-)</FONT> <BR><BR><FONT
face=sans-serif size=2>I suggest we ask Carsten to run the regression tests
to ensure that his code gen changes have not broken stuff on at least
one platform of his choice. He can then decide, based on this test results,
which he can discuss here if necessary, whether he wants to commit his
changes or not. If he runs the suite and gets some errors then I suggest
we're happy. if he breaks that suite entirely then we're not?</FONT>
<BR><BR><FONT face=sans-serif size=2>Running the suite should take him three
hours from scratch, if he hasn't done it before so we should know soon
whether the gen changes are viable.</FONT> <BR><BR><FONT face=sans-serif
size=2>If he is not able to test them (not having the services would be the
obvious issue) then perhaps one of us can run them for him (Carsten - have
you got a branch we can extract?).</FONT> <BR><BR><FONT
face=sans-serif size=2>If Carsten is not around or able to commit changes
then I suggest we go alpha without the gen changes and do the same as above
in alpha timeframe.</FONT> <BR><BR><BR><BR><BR><FONT face=sans-serif
size=2>John Hawkins<BR><BR></FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"sanjaya singharage"
<sanjayas@opensource.lk></B> </FONT>
<P><FONT face=sans-serif size=1>31/01/2005 13:09</FONT>
<TABLE border=1>
<TBODY>
<TR vAlign=top>
<TD bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"Apache AXIS C Developers
List"</FONT></DIV></TD></TR></TBODY></TABLE><BR></P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>"Apache AXIS C
Developers List" <axis-c-dev@ws.apache.org></FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>Re: Axis c++ 1.5
release plan (draft 4)</FONT></TD></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><BR><BR><FONT \
face=Arial size=2>(If the situation is not clear, Carseten has already put
his changes to the serializer. He has also finished the changes to the code
generator but is not able to test them as yet, therefore he has avoided
committing those changes.)</FONT> <BR><FONT size=3> </FONT> <BR><FONT
face=Arial size=2>What exactly do you mean? That we go ahead with the
codefreeze with the serilizer changes intact and let Carsten commit the code
generation stuff before the final?</FONT> <BR><FONT face=Arial size=2>If so
we can codefreeze early tuesday morning and start on the release
procedure.</FONT> <BR><FONT size=3> </FONT> <BR><FONT face=Arial
size=2>sanjaya.</FONT> <BR><FONT size=3>----- Original Message -----
</FONT><BR><FONT size=3><B>From:</B> </FONT><A
href="mailto:HAWKINSJ@uk.ibm.com"><FONT color=blue size=3><U>John
Hawkins</U></FONT></A><FONT size=3> </FONT><BR><FONT size=3><B>To:</B>
</FONT><A href="mailto:axis-c-dev@ws.apache.org"><FONT color=blue
size=3><U>Apache AXIS C Developers List</U></FONT></A><FONT size=3>
</FONT><BR><FONT size=3><B>Sent:</B> Monday, January 31, 2005 6:45 PM</FONT>
<BR><FONT size=3><B>Subject:</B> Re: Axis c++ 1.5 release plan (draft
4)</FONT> <BR><BR><FONT face=sans-serif size=2><BR>I would suggest Carsten
put in his fixes asap (into the Alpha preferably?) but not hold up alpha or
beta?</FONT><FONT size=3> <BR><BR><BR></FONT><FONT face=sans-serif
size=2><BR>John Hawkins<BR></FONT><FONT size=3><BR><BR><BR></FONT>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="43%"><FONT face=sans-serif size=1><B>"sanjaya singharage"
<</B></FONT><A href="mailto:sanjayas@opensource.lk"><FONT
face=sans-serif color=blue
size=1><B><U>sanjayas@opensource.lk</U></B></FONT></A><FONT
face=sans-serif size=1><B>></B> </FONT>
<P><FONT face=sans-serif size=1>31/01/2005 12:27</FONT><FONT size=3>
</FONT><BR>
<TABLE width="100%" border=4>
<TBODY>
<TR vAlign=top>
<TD width="100%" bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"Apache AXIS C Developers
List"</FONT></DIV></TD></TR></TBODY></TABLE>
<P></P>
<TD width="56%"><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="12%">
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top width="87%"><FONT face=sans-serif size=1>"Apache
AXIS C Developers List" <</FONT><A
href="mailto:axis-c-dev@ws.apache.org"><FONT face=sans-serif
color=blue
size=1><U>axis-c-dev@ws.apache.org</U></FONT></A><FONT
face=sans-serif size=1>></FONT><FONT size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>Re: Axis c++ 1.5
release plan (draft 4)</FONT></TD></TR></TBODY></TABLE><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="49%">
<TD
width="50%"></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><FONT
size=3><BR><BR></FONT><FONT face=Arial size=2><BR>So do we wait for Carsten
to comment the serializer changes?</FONT><FONT size=3>
<BR> </FONT><FONT face=Arial size=2><BR>sanjaya.</FONT><FONT size=3>
<BR> <BR>----- Original Message ----- <B><BR>From:</B> </FONT><A
href="mailto:HAWKINSJ@uk.ibm.com"><FONT color=blue size=3><U>John
Hawkins</U></FONT></A><FONT size=3> <B><BR>To:</B> </FONT><A
href="mailto:axis-c-dev@ws.apache.org"><FONT color=blue size=3><U>Apache
AXIS C Developers List</U></FONT></A><FONT size=3> <B><BR>Sent:</B> Monday,
January 31, 2005 4:28 PM <B><BR>Subject:</B> Re: Axis c++ 1.5 release plan
(draft 4) <BR></FONT><FONT face=sans-serif size=2><BR><BR>Hmm, we're
changing the paradigm here - putting in new code in beta !</FONT><FONT
size=3> </FONT><FONT face=sans-serif size=2><BR><BR>Howver, this problem is
a bug therefore I go with putting it in beta. As long as it comes with some
good tests that broke before it was implemented and are fixed by its
incorporation.</FONT><FONT size=3> </FONT><FONT face=sans-serif
size=2><BR><BR>John Hawkins</FONT><FONT size=3><BR><BR><BR></FONT>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="43%"><FONT face=sans-serif size=1><B>"sanjaya singharage"
<</B></FONT><A href="mailto:sanjayas@opensource.lk"><FONT
face=sans-serif color=blue
size=1><B><U>sanjayas@opensource.lk</U></B></FONT></A><FONT
face=sans-serif size=1><B>></B> </FONT>
<P><FONT face=sans-serif size=1>31/01/2005 08:52</FONT><FONT size=3>
</FONT><BR>
<TABLE width="100%" border=4>
<TBODY>
<TR vAlign=top>
<TD width="100%" bgColor=white>
<DIV align=center><FONT face=sans-serif size=1>Please respond
to<BR>"Apache AXIS C Developers
List"</FONT></DIV></TD></TR></TBODY></TABLE><BR></P>
<TD width="56%"><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="12%">
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top width="87%"><FONT face=sans-serif size=1>"Apache
AXIS C Developers List"
<axis-c-dev@ws.apache.org></FONT><FONT size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>Re: Axis c++ 1.5
release plan (draft 4)</FONT></TD></TR></TBODY></TABLE><BR><FONT
size=3><BR></FONT><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="49%">
<TD
width="50%"></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><FONT
size=3><BR><BR></FONT><FONT size=2><TT><BR><BR>I think the serializer
changes for AXISCPP-197 should be commented out<BR>before we go for
the 1.5 codefreeze.<BR>Can we have a quick response from the community on
this?<BR><BR>i.e. Do we keep the serializer changes for AXISCPP-197 in the
codebase for<BR>1.5 alpha or comment it out and include both serializer and
codegeneration<BR>changes for the final?<BR><BR>please respond quickly
guys.<BR><BR>sanjaya.<BR><BR>----- Original Message -----<BR>From: "Carsten
Blecken" <cblecken@macrovision.com><BR>To: "Apache AXIS C Developers
List" <axis-c-dev@ws.apache.org><BR>Sent: Monday, January 31, 2005
12:49 PM<BR>Subject: RE: Axis c++ 1.5 release plan (draft 4)<BR><BR><BR>>
Quick status update :<BR>><BR>> I wasn't able to test sufficiently the
code generation changes, so I<BR>> did not commit them (i'm having
problems with the testing framework<BR>> but that's a different
story).<BR>><BR>> The changes to the serializer have been committed
last week. These<BR>> changes should not break the existing stubs since
they mostly add<BR>> new method overloads with prefixes for the
serializer that miss them.<BR>><BR>> I will try to get the code
generation changes into the beta time frame<BR>> and was hoping that it
was ok to leave the serializer changes in there.<BR>><BR>>
Carsten<BR>><BR>> -----Original Message-----<BR>> From: Carsten
Blecken<BR>> Sent: Thursday, January 27, 2005 8:46 AM<BR>> To: Apache
AXIS C Developers List; Samisa Abeysinghe<BR>> Subject: RE: Axis c++ 1.5
release plan (draft 4)<BR>><BR>><BR>> Sorry for the mess everybody
- I assumed friday to be the last day (my<BR>mistake).<BR>><BR>> In
terms of things already committed : These are changes to the
serializer<BR>which<BR>> add namespace and/or namespace prefixes to
various methods. They are<BR>overloaded<BR>> methods to keep backward
compatibility with current stubs. So I would say<BR>the<BR>> risk is not
too big. There was also some refactoring being done, but I
did<BR>some<BR>> testing on the changes.<BR>><BR>> The part where I
need more time are the stub/skeleton generator (which<BR>employ the<BR>>
new methods) and the testing involved with it.<BR>> Maybe I should hold
off the generator changes until after alpha, since I<BR>consider<BR>>
them higher risk?<BR>><BR>> In terms of importance: Our current wsdl's
break due to the lack of<BR>namespace<BR>> prefixing. Almost all more
complicated doc lit wsdl's will have issues<BR>here when<BR>> they have
data type nesting and arrays.<BR>><BR>> Carsten<BR>><BR>>
-----Original Message-----<BR>> From: Samisa Abeysinghe
[mailto:samisa.abeysinghe@gmail.com]<BR>> Sent: Thursday, January 27,
2005 3:37 AM<BR>> To: Apache AXIS C Developers List<BR>> Subject: Re:
Axis c++ 1.5 release plan (draft 4)<BR>><BR>><BR>> Part of the
solution has been already commited.<BR>> So we have to either hold off or
comment out what is already commited.<BR>><BR>> How critical/important
is this feature?<BR>><BR>> Is it practicle to tag the CVS and start on
testing cycle till the<BR>> rest of the solution is commited.<BR>>
Given that the solution is related to serializer, the risk of side<BR>>
effects is high.<BR>><BR>> Thanks,<BR>>
Samisa...<BR>><BR>><BR>> On Thu, 27 Jan 2005 09:16:35 +0000, John
Hawkins <HAWKINSJ@uk.ibm.com><BR>wrote:<BR>> ><BR>> >
Hmm,<BR>> ><BR>> > Should we hold off on alpha until it's
complete?<BR>> ><BR>> ><BR>> ><BR>> ><BR>> >
John Hawkins<BR>> ><BR>> ><BR>> ><BR>> ><BR>>
> "Carsten Blecken" <cblecken@macrovision.com><BR>> ><BR>>
> 27/01/2005 08:39<BR>> > Please respond to<BR>> > "Apache
AXIS C Developers List"<BR>> > To"Apache AXIS C Developers List"
<axis-c-dev@ws.apache.org>,<BR>> >
<sanjayas@opensource.lk><BR>> > cc<BR>> > SubjectRE: Axis
c++ 1.5 release plan (draft 4)<BR>> ><BR>> ><BR>>
><BR>> ><BR>> ><BR>> ><BR>> ><BR>>
><BR>> > Hi Sanjaya,<BR>> ><BR>> > still working on
item 7). Harder than I thought. Partially committed<BR>> > (Serializer
changes) and I think I can get the rest<BR>> > (code generator) by
friday into the alpha.<BR>> ><BR>> > Do you want status by
friday again?<BR>> ><BR>> > Carsten<BR>> ><BR>> >
-----Original Message-----<BR>> > From: sanjaya singharage
[mailto:sanjayas@opensource.lk]<BR>> > Sent: Wednesday, January 26,
2005 10:30 PM<BR>> > To: Apache AXIS C Developers List<BR>> >
Subject: Axis c++ 1.5 release plan (draft 4)<BR>> ><BR>> > Hi
all,<BR>> ><BR>> > COULD I HAVE THE STATUS OF ITEM NUMBER 7
CARSTEN, IS IT ALREAD COMMITED<BR>IN<BR>> > CVS? CAN WE INCLUDE IT IN
1.5 OR SHELF IT FOR THE NEXT RELEASE? OR ARE<BR>YOU<BR>> > PLANNING TO
FIX THIS BY 1.5 FINAL? COULD I HAVE A RESPONSE CARSTEN?<BR>> ><BR>>
><BR>> > MARK, WHAT IS THE STATUS OF ITEM 2? COULD YOU ALSO
RESPOND?<BR>> ><BR>> ><BR>> > Following the discussion I
have added these items<BR>> > -Problem with complex types which
contain complex types<BR>> >
http://issues.apache.org/jira/browse/AXISCPP-197 (in progress
by<BR>carsten)<BR>> ><BR>> > Following the discussion I have
removed the following items<BR>> ><BR>> > -Fault mapping (stub
level)<BR>> > -improvement of Web Site<BR>> > a.Web-site should
be made more or less like Axis-Java website for ease<BR>of<BR>> >
use<BR>> > b.More user oriented and less developer oriented<BR>>
> -Add support for xsd:any type (?)<BR>> > -Ability to add custom
headers (?)<BR>> ><BR>> ><BR>> > sanjaya.<BR>>
><BR>> >
=======================================================<BR>> ><BR>>
> (fourth draft of the release plan.)<BR>> ><BR>> > Hi
all,<BR>> > I would like to volunteer to be the release manager for
the Axis C++ 1.5<BR>> > release.<BR>> ><BR>> > A draft
Release Plan is presented below using the current items found
in<BR>the<BR>> > wiki at
http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/ToDo1.5 .<BR>> >
Please update the wiki of any more items that are applicable to the
1.5<BR>> > release that developers are working on.<BR>>
><BR>> > Also we need to decide on dates for code freeze etc. and
release dates<BR>at<BR>> > the bottom.<BR>> > Please
comment.<BR>> ><BR>> ><BR>> ><BR>> > This is the
release plan (draft) for Axis C++ version 1.5. Given below<BR>is a<BR>>
> snapshot<BR>> > of all the changes for 1.5 since the 1.4
version.<BR>> ><BR>> > Changes from 1.4 to 1.5:<BR>>
><BR>> > 1. Partial C support -<BR>>
> http://issues.apache.org/jira/browse/AXISCPP-210 (in progress by
Mark)<BR>> > -C clients with stub generation for simple types<BR>>
> -Porting of some C++ tests to C<BR>> > 2.
Memory clean-up and fix -<BR>> >
http://issues.apache.org/jira/browse/AXISCPP-149 (in progress by
Mark<BR>> > Whitlock as per JIRA)<BR>> > 3.
Improve HTTP Support -<BR>> >
http://issues.apache.org/jira/browse/AXISCPP-176 (Done by Samisa as
per<BR>> > JIRA)<BR>> > 4. "100
Continue" support in axis2 transport<BR>> >
http://issues.apache.org/jira/browse/AXISCPP-311 (Done by Samisa)<BR>>
> 5. Proxy support for axis2 transport<BR>>
> http://issues.apache.org/jira/browse/AXISCPP-325 (Done by
Samisa)<BR>> > 6. Numerous memory leak
fixes (Done by Samisa)<BR>> > 7. Problem
with complex types which contain complex types<BR>> >
http://issues.apache.org/jira/browse/AXISCPP-197 (in progress
by<BR>Carsten)<BR>> ><BR>> > Details on these features could be
found on JIRA and the AxisCpp TODO<BR>wiki<BR>> > page at
http://wiki.apache.org/ws/FrontPage/AxisC_2b_2b/ToDo1.5<BR>> ><BR>>
> Release Criteria:<BR>> ><BR>> > - Functional tests
pass<BR>> > - Test on installation procedures<BR>> >
- Test on different versions of Apache web server(1.3.xx,
2.0.xx)<BR>> > - Test samples on different platforms (Linux,
Microsoft Windows)<BR>> > - Fix blockers and most
critical bugs that applies to 1.5<BR>> ><BR>> > Dates:<BR>>
><BR>> > The following are the proposed dates for the release,
opinions please:<BR>> > Code freeze
January 27, 2005<BR>>
> Release alpha version January 31,
2005<BR>> > Release 1.5 final
February 21, 2005<BR>> ><BR>>
><BR>> > sanjaya.<BR>>
><BR>><BR>><BR>><BR></TT></FONT><FONT
size=3><BR><BR></FONT><BR></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>
["BeanParamWriter.java.diff" (application/octet-stream)]
172c172,174
< writer.write("\tpSZ->serializeBasicArray((Axis_Array*)(¶m->"+attribs[i].get \
ParamNameAsMember()+"),"+CUtils.getXSDTypeForBasicType(attribs[i].getTypeName())+", \
\""+attribs[i].getParamName()+"\");\n");
---
> //writer.write("\tpSZ->serializeBasicArray((Axis_Array*)(¶m->"+attribs[i].g \
> etParamNameAsMember()+"),"+CUtils.getXSDTypeForBasicType(attribs[i].getTypeName())+", \
> \""+attribs[i].getParamName()+"\");\n"); // cblecken 17/01/2005
> writer.write("\tpSZ->serializeBasicArray((Axis_Array*)(¶m->"+attribs[i].getParamName()+", \
> Axis_URI_" + classname + \
> ","+CUtils.getXSDTypeForBasicType(attribs[i].getTypeName())+", \
> \""+attribs[i].getParamName()+"\");\n");
247,248c249,252
< writer.write("\tpSZ->serializeAsElement( \
\""+attribs[i].getElementNameAsString()+"\", \
(void*)&(param->"+attribs[i].getParamNameAsMember()+"), "+ \
CUtils.getXSDTypeForBasicType(attribs[i].getTypeName())+");\n"); < //Samisa
---
> // writer.write("\tpSZ->serializeAsElement( \
> \""+attribs[i].getElementNameAsString()+"\", \
> (void*)&(param->"+attribs[i].getParamNameAsMember()+"), "+ \
> CUtils.getXSDTypeForBasicType(attribs[i].getTypeName())+");\n"); // cblecken \
> 17/01/2005 writer.write("\tpSZ->serializeAsElement(\""+attribs[i].getElementNameAsString()+"\", \
> Axis_URI_" + classname + ", (void*)&(param->"+attribs[i].getParamName()+"), "+ \
> CUtils.getXSDTypeForBasicType(attribs[i].getTypeName())+");\n");
254,256c258,263
< writer.write("\tpSZ->serialize(\"<"+elm+"\", 0);\n");
< writer.write("\tAxis_Serialize_"+attribs[i].getTypeName()+"(param->"+attribs[i].getParamNameAsMember()+", \
pSZ);\n"); < writer.write("\tpSZ->serialize(\"</"+elm+">\", 0);\n");
---
> //writer.write("\tpSZ->serialize(\"<"+elm+"\", 0);\n");
> //writer.write("\tAxis_Serialize_"+attribs[i].getTypeName()+"(param->"+attribs[i].getParamNameAsMember()+", \
> pSZ);\n"); //writer.write("\tpSZ->serialize(\"</"+elm+">\", 0);\n");
> writer.write("\tpSZ->serialize(\"<\", pSZ->getNamespacePrefix(\"" + \
> type.getName().getNamespaceURI() + "\"), \":\", \""+elm+"\", 0);\n"); \
> writer.write("\tAxis_Serialize_"+attribs[i].getTypeName()+"(param->"+attribs[i].getParamName()+", \
> pSZ);\n"); writer.write("\tpSZ->serialize(\"</\", pSZ->getNamespacePrefix(\"" + \
> type.getName().getNamespaceURI() + "\"), \":\", \""+elm+"\", \">\", 0);\n");
["ClientStubWriter.java.diff" (application/octet-stream)]
597,598c597,599
< + ", cPrefixAndParamName"
< + i
---
> + ", \""
> + parameterName
> + "\""
["FourLevelTestDoc.xml" (text/xml)]
<test>
<name>FourLevelTestDoc</name>
<description>Tests four levels of tag nesting for doc style</description>
<clientLang>cpp</clientLang>
<clientCode>FourLevelTestDocClient.cpp</clientCode>
<wsdl>FourLevelTestDoc.wsdl</wsdl>
<expected>
<output>
FourLevelTestDoc.expected
</output>
</expected>
<endpoint>http://localhost:80/axis/FourLevelTestDocService</endpoint>
</test>
["FourLevelTestDoc.wsdl" (application/octet-stream)]
["FourLevelTestDoc.expected" (application/octet-stream)]
["FourLevelTestDocClient.cpp" (application/octet-stream)]
// FourLevelTestDocClient.cpp : Defines the entry point for the console application.i
//
#include <string>
using namespace std;
#include "fourLevelTestDocInterface.hpp"
#include <axis/AxisException.hpp>
int main(int argc, char* argv[])
{
int x;
char buffer1[100];
char endpoint[256];
const char* url="http://localhost:80/axis/fourLevelTestDoc";
const char* server="localhost";
const char* port="80";
url = argv[1];
try
{
sprintf(endpoint, "%s", url);
FourLevelTestDocInterface ws(endpoint);
FourthLevelElemType* fourth = new FourthLevelElemType();
fourth->SampleString = strdup("abc");
fourth->SampleInt = 1;
FourthLevelElemType_Array* fourth_array = new FourthLevelElemType_Array();
fourth_array->m_Array = fourth;
fourth_array->m_Size = 1;
ThirdLevelElemType* third = new ThirdLevelElemType();
third->FourthLevelElem = *fourth_array;
ThirdLevelElemType_Array* third_array = new ThirdLevelElemType_Array();
third_array->m_Array = third;
third_array->m_Size = 1;
SecondLevelElemType* second = new SecondLevelElemType();
second->ThirdLevelElem = *third_array;
SecondLevelElemType_Array* second_array = new SecondLevelElemType_Array();
second_array->m_Array = second;
second_array->m_Size = 1;
// SecondLevelElemType_Array in_array = new SecondLevelElemType_Array();
// in_array.m_Array = second_arr;
// in_array.m_Size = 1;
SecondLevelElemType_Array out_array;
out_array = ws.RetrieveTestDoc(*second_array);
printf("Size = %d\n", out_array.m_Size);
printf("String = %s\n", \
out_array.m_Array->ThirdLevelElem.m_Array->FourthLevelElem.m_Array->SampleString);
}
catch(AxisException& e)
{
printf("Exception : %s\n", e.what());
}
catch(exception& e)
{
printf("Unknown exception has occured\n");
}
catch(...)
{
printf("Unknown exception has occured\n");
}
return 0;
}
["FourLevelTestDocInterface.cpp" (application/octet-stream)]
/*
* This file was auto-generated by the Axis C++ Web Service Generator (WSDL2Ws)
* This file contains definitions of the web service
*/
#include "FourLevelTestDocInterface.hpp"
FourLevelTestDocInterface::FourLevelTestDocInterface()
{
}
FourLevelTestDocInterface::~FourLevelTestDocInterface()
{
}
/* This function is called by the AxisEngine when something went wrong
with the current web service request processing. Appropriate actions should
be taken here.*/
void FourLevelTestDocInterface::onFault()
{
}
/* This function is called by the AxisEngine when this web service
library is first loaded. So here we can initialize any global/static
data structures of this web service or open database connections */
void FourLevelTestDocInterface::init()
{
}
/* This function is called by the AxisEngine when this web service
library is unloaded. So we can deallocate any global/static data structures
and close database connections etc here. */
void FourLevelTestDocInterface::fini()
{
}
SecondLevelElemType_Array FourLevelTestDocInterface::RetrieveTestDoc(SecondLevelElemType_Array Value0)
{
//if (NULL == Value0)
// return 0;
char* type = Value0.m_Array[0].ThirdLevelElem.m_Array[0].FourthLevelElem.m_Array[0].SampleString;
if (type != NULL) {
if (strcmp(type, "abc")) {
throw new AxisServiceException(33);
}
}
FourthLevelElemType* fourth = new FourthLevelElemType();
fourth->SampleString = strdup("def");
fourth->SampleInt = 1;
FourthLevelElemType_Array* fourth_array = new FourthLevelElemType_Array();
fourth_array->m_Array = fourth;
fourth_array->m_Size = 1;
ThirdLevelElemType* third = new ThirdLevelElemType();
third->FourthLevelElem = *fourth_array;
ThirdLevelElemType_Array* third_array = new ThirdLevelElemType_Array();
third_array->m_Array = third;
third_array->m_Size = 1;
SecondLevelElemType* second = new SecondLevelElemType();
second->ThirdLevelElem = *third_array;
SecondLevelElemType_Array* second_array = new SecondLevelElemType_Array();
second_array->m_Array = second;
second_array->m_Size = 1;
return *second_array;
}
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic