You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Franz Fehringer <fe...@isogmbh.de> on 2006/04/05 10:23:17 UTC
last wsdl2ws reorganization / AXISCPP-918
Hello,
With the last svn up i saw that the wsdl2ws sources got reorganized thus
overwriting my simple fix for AXISCPP-918.
So i wonder if AXISCPP-918 could perhaps resolved/remedied for the most
simple cases?
See my last comment to AXISCPP-918.
It would be really great for me, if AXISCPP-918 could be attacked (i
understand well that not all of my issues can be resolved with 1.6),
since this is currently the last and only issue, for which i have either
to patch wsdl2ws locally or postprocess the generated sources.
Many thanks in advance
Franz
Re: last wsdl2ws reorganization / AXISCPP-918
Posted by Franz Fehringer <fe...@isogmbh.de>.
Thanks, i'll be back on this issue soon.
Franz
Adrian Dick schrieb:
> Hi,
>
> Ah! I was using the wrong view on Jira, so missed your patch first time
> round.
>
> I have now applied and tested the patch using our existing testcases
> without any problems.
> So it has now been committed and should be available in the next nightly
> build.
>
> I do agree that we will need to revisit this patch when we look at
> providing more complete support for extension/restriction of data types,
> including the addition of a specific testcase for this behaviour/function.
>
> I will update AXISCPP-918 to reflect the inclusion of this patch, but I'm
> currently having difficulty connecting to Jira.
>
> Regards,
> Adrian
> _______________________________________
> Adrian Dick (adrian.dick@uk.ibm.com)
>
>
> Franz Fehringer <fe...@isogmbh.de> wrote on 05/04/2006 15:46:43:
>
>
>> Hello Adrian,
>>
>> My fix is contained in my comment to AXISCPP-918 (scroll to the bottom of
>>
>
>
>> http://issues.apache.org/jira/browse/AXISCPP-918).
>> It consists of only four lines and copes only with the most simple
>> and special case.
>> But perhaps someone with the knowledge of you could augment it to a
>> more complete solution?
>> For my purposes even this little four lines make a big improvement
>> (i would have to postprocess several generated sources without it).
>>
>> Greetings
>>
>> Franz
>>
>>
>> Adrian Dick schrieb:
>> Hi,
>>
>> You mention that you have a simple fix ... is this by post processing, or
>> do you have a WSDL2Ws path?
>> If the latter, we would be very grateful if you're in a position to make
>> this available for inclusion to Axis C++.
>>
>> Incidentally, I see from the WSDL attached to AXISCPP-918 that you're
>>
> using
>
>> doc/literal. The latest refactoring basically promoted a few of the
>> cpp/literal classes upto cpp, incorporating a small number of changes for
>> the unavoidable differences between doc/literal and rpc/encoded
>>
> artefacts.
>
>> So, I would expect no change in your produced cpp/hpp files (except
>>
> perhaps
>
>> minor formatting), while any WSDL2Ws patch files may need to be reworked
>>
> to
>
>> the new location - but the patch content is probably still good.
>>
>> Regards,
>> Adrian
>> _______________________________________
>> Adrian Dick (adrian.dick@uk.ibm.com)
>>
>>
>> Franz Fehringer <fe...@isogmbh.de> wrote on 05/04/2006 09:23:17:
>>
>>
>> Hello,
>>
>> With the last svn up i saw that the wsdl2ws sources got reorganized thus
>> overwriting my simple fix for AXISCPP-918.
>> So i wonder if AXISCPP-918 could perhaps resolved/remedied for the most
>> simple cases?
>> See my last comment to AXISCPP-918.
>> It would be really great for me, if AXISCPP-918 could be attacked (i
>> understand well that not all of my issues can be resolved with 1.6),
>> since this is currently the last and only issue, for which i have either
>> to patch wsdl2ws locally or postprocess the generated sources.
>>
>> Many thanks in advance
>>
>> Franz
>>
>> [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM]
>>
>>
>>
>> [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM]
>>
>
>
Re: last wsdl2ws reorganization / AXISCPP-918
Posted by Adrian Dick <ad...@uk.ibm.com>.
Hi,
Ah! I was using the wrong view on Jira, so missed your patch first time
round.
I have now applied and tested the patch using our existing testcases
without any problems.
So it has now been committed and should be available in the next nightly
build.
I do agree that we will need to revisit this patch when we look at
providing more complete support for extension/restriction of data types,
including the addition of a specific testcase for this behaviour/function.
I will update AXISCPP-918 to reflect the inclusion of this patch, but I'm
currently having difficulty connecting to Jira.
Regards,
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
Franz Fehringer <fe...@isogmbh.de> wrote on 05/04/2006 15:46:43:
> Hello Adrian,
>
> My fix is contained in my comment to AXISCPP-918 (scroll to the bottom of
> http://issues.apache.org/jira/browse/AXISCPP-918).
> It consists of only four lines and copes only with the most simple
> and special case.
> But perhaps someone with the knowledge of you could augment it to a
> more complete solution?
> For my purposes even this little four lines make a big improvement
> (i would have to postprocess several generated sources without it).
>
> Greetings
>
> Franz
>
>
> Adrian Dick schrieb:
> Hi,
>
> You mention that you have a simple fix ... is this by post processing, or
> do you have a WSDL2Ws path?
> If the latter, we would be very grateful if you're in a position to make
> this available for inclusion to Axis C++.
>
> Incidentally, I see from the WSDL attached to AXISCPP-918 that you're
using
> doc/literal. The latest refactoring basically promoted a few of the
> cpp/literal classes upto cpp, incorporating a small number of changes for
> the unavoidable differences between doc/literal and rpc/encoded
artefacts.
> So, I would expect no change in your produced cpp/hpp files (except
perhaps
> minor formatting), while any WSDL2Ws patch files may need to be reworked
to
> the new location - but the patch content is probably still good.
>
> Regards,
> Adrian
> _______________________________________
> Adrian Dick (adrian.dick@uk.ibm.com)
>
>
> Franz Fehringer <fe...@isogmbh.de> wrote on 05/04/2006 09:23:17:
>
>
> Hello,
>
> With the last svn up i saw that the wsdl2ws sources got reorganized thus
> overwriting my simple fix for AXISCPP-918.
> So i wonder if AXISCPP-918 could perhaps resolved/remedied for the most
> simple cases?
> See my last comment to AXISCPP-918.
> It would be really great for me, if AXISCPP-918 could be attacked (i
> understand well that not all of my issues can be resolved with 1.6),
> since this is currently the last and only issue, for which i have either
> to patch wsdl2ws locally or postprocess the generated sources.
>
> Many thanks in advance
>
> Franz
>
> [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM]
>
>
>
> [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM]
Re: last wsdl2ws reorganization / AXISCPP-918
Posted by Franz Fehringer <fe...@isogmbh.de>.
Hello Adrian,
My fix is contained in my comment to AXISCPP-918 (scroll to the bottom
of http://issues.apache.org/jira/browse/AXISCPP-918).
It consists of only four lines and copes only with the most simple and
special case.
But perhaps someone with the knowledge of you could augment it to a more
complete solution?
For my purposes even this little four lines make a big improvement (i
would have to postprocess several generated sources without it).
Greetings
Franz
Adrian Dick schrieb:
> Hi,
>
> You mention that you have a simple fix ... is this by post processing, or
> do you have a WSDL2Ws path?
> If the latter, we would be very grateful if you're in a position to make
> this available for inclusion to Axis C++.
>
> Incidentally, I see from the WSDL attached to AXISCPP-918 that you're using
> doc/literal. The latest refactoring basically promoted a few of the
> cpp/literal classes upto cpp, incorporating a small number of changes for
> the unavoidable differences between doc/literal and rpc/encoded artefacts.
> So, I would expect no change in your produced cpp/hpp files (except perhaps
> minor formatting), while any WSDL2Ws patch files may need to be reworked to
> the new location - but the patch content is probably still good.
>
> Regards,
> Adrian
> _______________________________________
> Adrian Dick (adrian.dick@uk.ibm.com)
>
>
> Franz Fehringer <fe...@isogmbh.de> wrote on 05/04/2006 09:23:17:
>
>
>> Hello,
>>
>> With the last svn up i saw that the wsdl2ws sources got reorganized thus
>> overwriting my simple fix for AXISCPP-918.
>> So i wonder if AXISCPP-918 could perhaps resolved/remedied for the most
>> simple cases?
>> See my last comment to AXISCPP-918.
>> It would be really great for me, if AXISCPP-918 could be attacked (i
>> understand well that not all of my issues can be resolved with 1.6),
>> since this is currently the last and only issue, for which i have either
>> to patch wsdl2ws locally or postprocess the generated sources.
>>
>> Many thanks in advance
>>
>> Franz
>>
>> [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM]
>>
>
>
Re: last wsdl2ws reorganization / AXISCPP-918
Posted by Adrian Dick <ad...@uk.ibm.com>.
Hi,
You mention that you have a simple fix ... is this by post processing, or
do you have a WSDL2Ws path?
If the latter, we would be very grateful if you're in a position to make
this available for inclusion to Axis C++.
Incidentally, I see from the WSDL attached to AXISCPP-918 that you're using
doc/literal. The latest refactoring basically promoted a few of the
cpp/literal classes upto cpp, incorporating a small number of changes for
the unavoidable differences between doc/literal and rpc/encoded artefacts.
So, I would expect no change in your produced cpp/hpp files (except perhaps
minor formatting), while any WSDL2Ws patch files may need to be reworked to
the new location - but the patch content is probably still good.
Regards,
Adrian
_______________________________________
Adrian Dick (adrian.dick@uk.ibm.com)
Franz Fehringer <fe...@isogmbh.de> wrote on 05/04/2006 09:23:17:
> Hello,
>
> With the last svn up i saw that the wsdl2ws sources got reorganized thus
> overwriting my simple fix for AXISCPP-918.
> So i wonder if AXISCPP-918 could perhaps resolved/remedied for the most
> simple cases?
> See my last comment to AXISCPP-918.
> It would be really great for me, if AXISCPP-918 could be attacked (i
> understand well that not all of my issues can be resolved with 1.6),
> since this is currently the last and only issue, for which i have either
> to patch wsdl2ws locally or postprocess the generated sources.
>
> Many thanks in advance
>
> Franz
>
> [attachment "feh.vcf" deleted by Adrian Dick/UK/IBM]