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 "Fred Preston (JIRA)" <ax...@ws.apache.org> on 2005/10/05 18:04:47 UTC
[jira] Created: (AXISCPP-849) Stub compilation problems when WSDL contains complexTypes and elements of the same name
Stub compilation problems when WSDL contains complexTypes and elements of the same name
---------------------------------------------------------------------------------------
Key: AXISCPP-849
URL: http://issues.apache.org/jira/browse/AXISCPP-849
Project: Axis-C++
Type: Bug
Components: WSDL processing - RPC, WSDL processing - Doc
Environment: n/a
Reporter: Fred Preston
When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
<xsd:complexType name="aName">
<xsd:sequence>
<xsd:element name="aName" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
This gets turned into the following stub code...
class STORAGE_CLASS_INFO aName
{
public:
xsd__string aName;
And when this is compiled, the following error (and others) results:-
"type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
[jira] Updated: (AXISCPP-849) Stub compilation problems when WSDL
contains complexTypes and elements of the same name
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
nadir amra updated AXISCPP-849:
-------------------------------
Comment: was deleted
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Issue Type: Bug
> Components: WSDL processing - Doc, WSDL processing - RPC
> Environment: n/a
> Reporter: Fred Preston
> Assigned To: nadir amra
> Fix For: 1.6 Final
>
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Closed: (AXISCPP-849) Stub compilation problems when WSDL
contains complexTypes and elements of the same name
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
Fred Preston closed AXISCPP-849:
--------------------------------
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Type: Bug
> Components: WSDL processing - RPC, WSDL processing - Doc
> Environment: n/a
> Reporter: Fred Preston
> Assignee: Fred Preston
> Fix For: 1.6 Alpha
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
[jira] Reopened: (AXISCPP-849) Stub compilation problems when WSDL
contains complexTypes and elements of the same name
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
nadir amra reopened AXISCPP-849:
--------------------------------
Assignee: nadir amra (was: Fred Preston)
I am re-opening this issue because it is not a complete fix. Although the "fix" resolves variable name clashes with the class it is contained in, it does not resolve clashes with other classes.
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Issue Type: Bug
> Components: WSDL processing - Doc, WSDL processing - RPC
> Environment: n/a
> Reporter: Fred Preston
> Assigned To: nadir amra
> Fix For: 1.6 Alpha
>
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Closed: (AXISCPP-849) Stub compilation problems when WSDL
contains complexTypes and elements of the same name
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
nadir amra closed AXISCPP-849.
------------------------------
Fix Version/s: 1.6 Final
(was: 1.6 Alpha)
Resolution: Fixed
Fixed this so that we now go through all the externalized classes and if there is a match, an underscore is added to the end of the identifier name.
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Issue Type: Bug
> Components: WSDL processing - Doc, WSDL processing - RPC
> Environment: n/a
> Reporter: Fred Preston
> Assigned To: nadir amra
> Fix For: 1.6 Final
>
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXISCPP-849) Stub compilation problems when WSDL contains complexTypes and elements of the same name
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
Fred Preston resolved AXISCPP-849:
----------------------------------
Resolution: Fixed
I now believe this to be complete. I've written a Unit Test to check the function (UT_SameComplexTypeAndElementName).
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Type: Bug
> Components: WSDL processing - Doc, WSDL processing - RPC
> Environment: n/a
> Reporter: Fred Preston
> Assignee: Fred Preston
> Fix For: 1.6 Alpha
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
[jira] Updated: (AXISCPP-849) Stub compilation problems when WSDL contains complexTypes and elements of the same name
Posted by "John Hawkins (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
John Hawkins updated AXISCPP-849:
---------------------------------
Fix Version: 1.6 Alpha
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Type: Bug
> Components: WSDL processing - Doc, WSDL processing - RPC
> Environment: n/a
> Reporter: Fred Preston
> Assignee: Fred Preston
> Fix For: 1.6 Alpha
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
[jira] Assigned: (AXISCPP-849) Stub compilation problems when WSDL contains complexTypes and elements of the same name
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=all ]
Fred Preston reassigned AXISCPP-849:
------------------------------------
Assign To: Fred Preston
In Progress
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Type: Bug
> Components: WSDL processing - RPC, WSDL processing - Doc
> Environment: n/a
> Reporter: Fred Preston
> Assignee: Fred Preston
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
[jira] Commented: (AXISCPP-849) Stub compilation problems when WSDL
contains complexTypes and elements of the same name
Posted by "nadir amra (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-849?page=comments#action_12460635 ]
nadir amra commented on AXISCPP-849:
------------------------------------
Actually, when there is a conflict between a variable identifier and a class, "_Ref" is added to the variable identifier. This is to be consistent with what was done previously, although inconsistently.
In addition, previously you would get methods with "_Ref" appended to the name (for example, getDueDate_Ref()). This will no longer be the case. That is, the generated method will be getDueDate(), which I think is the desired outcome.
> Stub compilation problems when WSDL contains complexTypes and elements of the same name
> ---------------------------------------------------------------------------------------
>
> Key: AXISCPP-849
> URL: http://issues.apache.org/jira/browse/AXISCPP-849
> Project: Axis-C++
> Issue Type: Bug
> Components: WSDL processing - Doc, WSDL processing - RPC
> Environment: n/a
> Reporter: Fred Preston
> Assigned To: nadir amra
> Fix For: 1.6 Final
>
>
> When a WSDL contains a CompexType name and an element name that are the same, the generated code does not compile. For example, if a WSDL/XSD contains the following code...
> <xsd:complexType name="aName">
> <xsd:sequence>
> <xsd:element name="aName" type="xsd:string"/>
> </xsd:sequence>
> </xsd:complexType>
> This gets turned into the following stub code...
> class STORAGE_CLASS_INFO aName
> {
> public:
> xsd__string aName;
> And when this is compiled, the following error (and others) results:-
> "type(s) preceeding 'aName' (constructor with return type, or illegal redefinition of current class name?)"
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org