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 "sanjaya singharage (JIRA)" <ax...@ws.apache.org> on 2004/12/06 13:07:44 UTC

[jira] Created: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Building of some samples fail in the 1.4 alpha windows binary
-------------------------------------------------------------

         Key: AXISCPP-310
         URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
     Project: Axis-C++
        Type: Bug
  Components: Samples  
    Versions: 1.4 Alpha    
 Environment: windows
    Reporter: sanjaya singharage


since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56372 ]
     
Mark Whitlock commented on AXISCPP-310:
---------------------------------------

Which samples fail to build? I tried building interoptests/base on windows, which uses xsd__hexBinary and that compiled and linked successfully. Some time ago I created AxisUserAPI.cpp with the intention of fixing AXISCPP-149 "memory cleaning of generated C++ array code" which I hope to complete in 1.5. When I created it, I intended that AxisUserAPI.cpp would not be shipped. Please give more details of the problem you are experiencing.

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Roshan Weerasuriya (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56419 ]
     
Roshan Weerasuriya commented on AXISCPP-310:
--------------------------------------------

We can have the following solution for this:

What ever the implementations at AxisUserAPI.cpp (i.e it has only the Constructor and DeStructor implemenations), could be implemented as "inline" functions (implicitly by implementing those in the class declaration itself), in side the AxisUserAPI.hpp. In this way again the user doesn't need any Axis Library implementations to build his/her webservice. But again here you get static linking, But I hope that would be ok, since it is very less code.

Any comments?

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56550 ]
     
Samisa Abeysinghe commented on AXISCPP-310:
-------------------------------------------

In my understanding, we cannot do a 100% static linking because of the paser and transport abstraction layers.
Those abstraction layers always load the libs dynamically, form the location of the libs specified in axiscpp.conf.

If we really want to do a static linking, then we may have to come up with a mechanism to disable the dynamic loading of the parser and transport and link them statically. (In other words, skip SOAPTransportFactory and XMLParserFactory in case of static linking)

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56584 ]
     
Mark Whitlock commented on AXISCPP-310:
---------------------------------------

Hi Samisa,
I think we are misunderstanding one another. I'm not suggesting statically linking the transport/XML libraries with the Axis runtime. I was wondering how the generated service could avoid being linked (dynamically or statically)with the Axis server libraries. I understand that is because all the C++ methods that the generated service uses are virtual so all linking is done at runtime. In C, a struct full of function pointers is used to invoke Axis methods. So the methods in AxisUserAPI.cpp must be included in AxisUserAPI.hpp since the service would not be able to call them if they were in the axis server library. I still don't understand *why* axis was designed so that services didn't have to be linked with the axis server library.

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56369 ]
     
Samisa Abeysinghe commented on AXISCPP-310:
-------------------------------------------

I dont get this :( Can't we solve the problem by including AxisUserAPI.hpp in include\axis?

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "sanjaya singharage (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56252 ]
     
sanjaya singharage commented on AXISCPP-310:
--------------------------------------------

What can we do to solve this situation? One quick solution that can be offered for the 1.4 release would be to include the relevant source files needed to build these samples. 

The other solution would be to remove this dependancy or isolate the dependancy for building the web service.

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Roshan Weerasuriya (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56420 ]
     
Roshan Weerasuriya commented on AXISCPP-310:
--------------------------------------------

We can have the following solution for this:

What ever the implementations at AxisUserAPI.cpp (i.e it has only the Constructor and DeStructor implemenations), could be implemented as "inline" functions (implicitly by implementing those in the class declaration itself), in side the AxisUserAPI.hpp. Then we will have to remove the AxisUserAPI.cpp since it is no needed any more in this apporach.

In this way again the user doesn't need any Axis Library implementations to build his/her webservice. But again here you get static linking, But I hope that would be ok, since it is very less code. 

Any comments?

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Closed: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/AXISCPP-310?page=history ]
     
Samisa Abeysinghe closed AXISCPP-310:
-------------------------------------

    Resolution: Fixed

This is no more applicable as include/axis/AxisUserAPI.hpp has been changed to include xsd__hexBinary and xsd__base64Binary

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://issues.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Roshan Weerasuriya (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56416 ]
     
Roshan Weerasuriya commented on AXISCPP-310:
--------------------------------------------

We don't expect the WebService writer to use any Axis Libraries (eg: AxisServer.lib etc for linking) when he build his/her WebService. This was done to avoid static linkage of Axis Library code, to the WebService. Therefore when ever there was a requirement to the WebService to access to any of the Axis library code, we provided that throught virtual interfaces, and let the code to be dynamicaly linked at runtime.

Therefore earlier there was no requirement to provide any of the Axis Library implementatoins when building a webservice. (i.e no need of the AxisLibs or any of the Axis implementation files i.e cpp's at link time) Hence we didn't add any of the Axis Library source files to the binary distributions.

But now since the "xsd__base64Binary", "xsd__hexBinary" and "AnyType" implementations are moved into the "AxisUserAPI.cpp", when ever a webservice writer use any of these types, he has to provide the implementation of those (via AxisServer.lib or via directly adding the AxisUserAPI.cpp to the project) inorder to build it. (we didn't wanted the user to do this according to the earlier plans) 

But any how, since we don't give any of the sources in the binary distribution, there is a problem to the user to build those samples. They are:
 - base  Server sample
 - doclitbase Server sample

I am telling abt Windows, I am not sure abt linux. But I heard somewhere that in linux it is dynamic linking by default,  but I am not sure abt linux. Some one can comment on linux.

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Commented: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Mark Whitlock (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=comments#action_56442 ]
     
Mark Whitlock commented on AXISCPP-310:
---------------------------------------

Thank you for your helpful explanation.

+1 to deleting AxisUserAPI.cpp and inlining the methods into AxisUserAPI.hpp.

The methods that I intend to add to xsd_hexBinary and others are a destructor that deletes the storage and an operator[] method. Since these are small I will inline them into AxisUserAPI.hpp.

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


[jira] Updated: (AXISCPP-310) Building of some samples fail in the 1.4 alpha windows binary

Posted by "Roshan Weerasuriya (JIRA)" <ax...@ws.apache.org>.
     [ http://nagoya.apache.org/jira/browse/AXISCPP-310?page=history ]

Roshan Weerasuriya updated AXISCPP-310:
---------------------------------------

    Comment: was deleted

> Building of some samples fail in the 1.4 alpha windows binary
> -------------------------------------------------------------
>
>          Key: AXISCPP-310
>          URL: http://nagoya.apache.org/jira/browse/AXISCPP-310
>      Project: Axis-C++
>         Type: Bug
>   Components: Samples
>     Versions: 1.4 Alpha
>  Environment: windows
>     Reporter: sanjaya singharage

>
> since in the binary distribution the source is not provided the build of some samples fail when attempting a build. This happens because in some samples the AxisUserAPI.cpp have to be included which uses xsd__base64Binary or xsd__hexBinary.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira