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 David Richards <d_...@comcast.net> on 2004/10/22 23:52:44 UTC
New user issues on Windows
I grabbed the latest CVS contents yesterday and set out to build and install Axis and the sample calculator service under Apache 2.0. These are the issues I ran into...
1) The .sln and .vcproj files are apparently very out of date. If no one is going to maintain them, just get rid of them. In fact, it may be easier to just have the .dsw files anyway to avoid having to maintain parallel sets of workspace and project files.. I ended up just importing the .dsw files into VS .NET and all was good.
2) The "Axis C++ Windows Developers Guide" is similarly outdated.
a) It talks about the AXIS_HOME environment variable (I discovered via the debugger that it's now AXISCPP_DEPLOY)
b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have been changed. Fortunately these are listed in the template axiscpp.conf_win
c) It doesn't talk about AxisTransport, Axis2Transport, or the AxisXMLParser projects and how they need to be deployed. I successfully used the result of Axis2Transport and AxisXMLParserExpat. It would be help ful to have some documentation of all the projects in the workspace and what they do.
d) I assume section 4.4 is obsolete (using Xerces rather than Expat).
3) The Post Buld step od AxisServer still references the AXIS_HOME environment variable.
4) There is at least one (src/common/Packet.cpp) obsolete source file hanging around. I found this because the VC7 project files still reference it. It wasn't used in the VC6 project files, though the Packet.h file is.
5) There is a "handlers" directory in the "deploy" source tree. Does this have a purpose in the actual deployed system?
Other than killing a bunch of time getting through some of the documentation inconsistencies, things went pretty well. Now to see how well it all works...
Dave Richards
Re: New user issues on Windows
Posted by Roshan Weerasuriya <ro...@opensource.lk>.
hi Dave,
>5) There is a "handlers" directory in the "deploy" source tree. Does
>this have a purpose in the actual deployed system?
This is used to include prewritten sample handler dlls. Currently there
are no sample handlers put in here.
But you can find 2 sample handers in the samples folder. They are for
users to have a look and get a idea.
Roshan
On Sat, 2004-10-23 at 03:52, David Richards wrote:
> I grabbed the latest CVS contents yesterday and set out to build and
> install Axis and the sample calculator service under Apache 2.0.
> These are the issues I ran into...
>
> 1) The .sln and .vcproj files are apparently very out of date. If no
> one is going to maintain them, just get rid of them. In fact, it may
> be easier to just have the .dsw files anyway to avoid having to
> maintain parallel sets of workspace and project files.. I ended up
> just importing the .dsw files into VS .NET and all was good.
>
> 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> a) It talks about the AXIS_HOME environment variable (I
> discovered via the debugger that it's now AXISCPP_DEPLOY)
> b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> been changed. Fortunately these are listed in the template
> axiscpp.conf_win
> c) It doesn't talk about AxisTransport, Axis2Transport, or the
> AxisXMLParser projects and how they need to be deployed. I
> successfully used the result of Axis2Transport
> and AxisXMLParserExpat. It would be help ful to have some
> documentation of all the projects in the workspace and what they do.
> d) I assume section 4.4 is obsolete (using Xerces rather than
> Expat).
>
> 3) The Post Buld step od AxisServer still references the AXIS_HOME
> environment variable.
>
> 4) There is at least one (src/common/Packet.cpp) obsolete source file
> hanging around. I found this because the VC7 project files still
> reference it. It wasn't used in the VC6 project files, though the
> Packet.h file is.
>
> 5) There is a "handlers" directory in the "deploy" source tree. Does
> this have a purpose in the actual deployed system?
>
> Other than killing a bunch of time getting through some of the
> documentation inconsistencies, things went pretty well. Now to see
> how well it all works...
>
>
> Dave Richards
>
Re: New user issues on Windows
Posted by Roshan Weerasuriya <ro...@opensource.lk>.
hi Dave,
I think these "VC++ 7" project files are not upto date. I don't have
VC++ 7 with me to correct it. Any one who has can make them uptodate.
Roshan
On Tue, 2004-10-26 at 11:48, David Richards wrote:
> Distribution.sln, Apache2_0Module.vcproj and AxisServerDLL.vcproj are all
> bad. They reference non-existent files and the XML parser stuff is missing.
> I didn't try building the other projects as I didn't need them.
>
> Seems like a good idea to remove the VC7 solution/project files. VS.NET can
> import the VC6 project files anyway. That's what I did and things worked
> without a problem - except for the AxisServerDLL.dsp file which still
> contains the line (twice - Release and Debug):
>
> PostBuild_Cmds=copy ..\bin\AxisServer_D.dll "%AXIS_HOME%\libs\."
>
> which uses the obsolete AXIS_HOME.
>
> Dave Richards
>
>
> ----- Original Message -----
> From: "sanjaya singharage" <sa...@opensource.lk>
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Sent: Monday, October 25, 2004 4:54 AM
> Subject: Re: New user issues on Windows
>
>
> > >1) The .sln and .vcproj files are apparently very out of date. If no
> > >one
> > is going to maintain them, just get rid of them. In fact, it may be
> > easier
> > to just have the .dsw files >anyway to avoid having to maintain parallel
> > sets of workspace and project files.. I ended up just importing the .dsw
> > files into VS .NET and all was good.
> >
> > Which vc projects are these? Basically I am using the vc projects at the
> > moment.
> >
> > sanjaya.
> >
>
>
>
Re: New user issues on Windows
Posted by David Richards <d_...@comcast.net>.
Distribution.sln, Apache2_0Module.vcproj and AxisServerDLL.vcproj are all
bad. They reference non-existent files and the XML parser stuff is missing.
I didn't try building the other projects as I didn't need them.
Seems like a good idea to remove the VC7 solution/project files. VS.NET can
import the VC6 project files anyway. That's what I did and things worked
without a problem - except for the AxisServerDLL.dsp file which still
contains the line (twice - Release and Debug):
PostBuild_Cmds=copy ..\bin\AxisServer_D.dll "%AXIS_HOME%\libs\."
which uses the obsolete AXIS_HOME.
Dave Richards
----- Original Message -----
From: "sanjaya singharage" <sa...@opensource.lk>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Sent: Monday, October 25, 2004 4:54 AM
Subject: Re: New user issues on Windows
> >1) The .sln and .vcproj files are apparently very out of date. If no
> >one
> is going to maintain them, just get rid of them. In fact, it may be
> easier
> to just have the .dsw files >anyway to avoid having to maintain parallel
> sets of workspace and project files.. I ended up just importing the .dsw
> files into VS .NET and all was good.
>
> Which vc projects are these? Basically I am using the vc projects at the
> moment.
>
> sanjaya.
>
Re: New user issues on Windows
Posted by Roshan Weerasuriya <ro...@opensource.lk>.
hi,
>Which vc projects are these? Basically I am using the vc projects at
the
> moment.
These are "VC++ 7" files. The correspondence in VC++7 to VC++ 6 is :
.sln/.vcproj and .dsw/.dsp.
Roshan
On Mon, 2004-10-25 at 15:54, sanjaya singharage wrote:
> >1) The .sln and .vcproj files are apparently very out of date. If no one
> is going to maintain them, just get rid of them. In fact, it may be easier
> to just have the .dsw files >anyway to avoid having to maintain parallel
> sets of workspace and project files.. I ended up just importing the .dsw
> files into VS .NET and all was good.
>
> Which vc projects are these? Basically I am using the vc projects at the
> moment.
>
> sanjaya.
>
> ----- Original Message -----
> From: "John Hawkins" <HA...@uk.ibm.com>
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Sent: Monday, October 25, 2004 3:05 PM
> Subject: Re: New user issues on Windows
>
>
> >
> >
> >
> >
> > There was mention in the original note of the msdev project too. who uses
> > this now - is it kept up to date? I know that the ANT build is used here -
> > does anyone else still use this? It's crazy to have this overhead if it's
> > not used
> >
> > John Hawkins
> >
> >
> >
> >
> >
> > rangika@opensourc
> > e.lk
> > To
> > 25/10/2004 07:38 "Apache AXIS C Developers List"
> > <ax...@ws.apache.org>
> > cc
> > Please respond to
> > "Apache AXIS C Subject
> > Developers List" Re: New user issues on Windows
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Dave,
> >
> > I got the latest CVS contents & checked the windows developers guide.
> >
> > > 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> > > a) It talks about the AXIS_HOME environment variable (I discovered
> > > via the debugger that it's now AXISCPP_DEPLOY)
> >
> > It doesn't talk about AXIS_HOME environment variable but it talks about
> > AXISCPP_DEPLOY.
> >
> > > b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> > > been changed. Fortunately these are listed in the template
> > > axiscpp.conf_win
> >
> > AXISLOGPATH is not mentioned in the win dev guide.It talks abt
> > "logpath".Axis C++ 1.3 uses logpath.
> >
> > > c) It doesn't talk about AxisTransport, Axis2Transport, or the
> > > AxisXMLParser projects and how they need to be deployed.
> >
> > It does talk abt AxisTransport and AxisXMLParser. But it doesn't mention
> > abt Axis2Transport. We will have to put it there.
> >
> > >3) The Post Buld step od AxisServer still references the AXIS_HOME
> > > environment variable.
> >
> > The Post Buld step of AxisServer does not refer to the AXIS_HOME
> > environment variable.The environment variable AXIS_HOME is not used in
> > the win dev guide.
> >
> > Can you pls recheck the win dev guide to see the problems that you found
> > are still existing.
> >
> > Thanks for your information.
> >
> > Regards,
> > Rangika
> >
> >
> >
> >
> >
> >
> >
> > I grabbed the latest CVS contents yesterday and set out to build and
> > > install Axis and the sample calculator service under Apache 2.0. These
> > > are the issues I ran into...
> > >
> > > 1) The .sln and .vcproj files are apparently very out of date. If no
> > one
> > > is going to maintain them, just get rid of them. In fact, it may be
> > > easier to just have the .dsw files anyway to avoid having to maintain
> > > parallel sets of workspace and project files.. I ended up just importing
> > > the .dsw files into VS .NET and all was good.
> > >
> > > 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> > > a) It talks about the AXIS_HOME environment variable (I discovered
> > > via the debugger that it's now AXISCPP_DEPLOY)
> > > b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> > > been changed. Fortunately these are listed in the template
> > > axiscpp.conf_win
> > > c) It doesn't talk about AxisTransport, Axis2Transport, or the
> > > AxisXMLParser projects and how they need to be deployed. I
> > > successfully used the result of Axis2Transport and
> > > AxisXMLParserExpat. It would be help ful to have some documentation
> > > of all the projects in the workspace and what they do.
> > > d) I assume section 4.4 is obsolete (using Xerces rather than
> > > Expat).
> > >
> > > 3) The Post Buld step od AxisServer still references the AXIS_HOME
> > > environment variable.
> > >
> > > 4) There is at least one (src/common/Packet.cpp) obsolete source file
> > > hanging around. I found this because the VC7 project files still
> > > reference it. It wasn't used in the VC6 project files, though the
> > > Packet.h file is.
> > >
> > > 5) There is a "handlers" directory in the "deploy" source tree. Does
> > this
> > > have a purpose in the actual deployed system?
> > >
> > > Other than killing a bunch of time getting through some of the
> > > documentation inconsistencies, things went pretty well. Now to see how
> > > well it all works...
> > >
> > >
> > > Dave Richards
> > >
> >
> >
> >
> >
>
>
>
Re: New user issues on Windows
Posted by sanjaya singharage <sa...@opensource.lk>.
>1) The .sln and .vcproj files are apparently very out of date. If no one
is going to maintain them, just get rid of them. In fact, it may be easier
to just have the .dsw files >anyway to avoid having to maintain parallel
sets of workspace and project files.. I ended up just importing the .dsw
files into VS .NET and all was good.
Which vc projects are these? Basically I am using the vc projects at the
moment.
sanjaya.
----- Original Message -----
From: "John Hawkins" <HA...@uk.ibm.com>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Sent: Monday, October 25, 2004 3:05 PM
Subject: Re: New user issues on Windows
>
>
>
>
> There was mention in the original note of the msdev project too. who uses
> this now - is it kept up to date? I know that the ANT build is used here -
> does anyone else still use this? It's crazy to have this overhead if it's
> not used
>
> John Hawkins
>
>
>
>
>
> rangika@opensourc
> e.lk
> To
> 25/10/2004 07:38 "Apache AXIS C Developers List"
> <ax...@ws.apache.org>
> cc
> Please respond to
> "Apache AXIS C Subject
> Developers List" Re: New user issues on Windows
>
>
>
>
>
>
>
>
>
>
> Hi Dave,
>
> I got the latest CVS contents & checked the windows developers guide.
>
> > 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> > a) It talks about the AXIS_HOME environment variable (I discovered
> > via the debugger that it's now AXISCPP_DEPLOY)
>
> It doesn't talk about AXIS_HOME environment variable but it talks about
> AXISCPP_DEPLOY.
>
> > b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> > been changed. Fortunately these are listed in the template
> > axiscpp.conf_win
>
> AXISLOGPATH is not mentioned in the win dev guide.It talks abt
> "logpath".Axis C++ 1.3 uses logpath.
>
> > c) It doesn't talk about AxisTransport, Axis2Transport, or the
> > AxisXMLParser projects and how they need to be deployed.
>
> It does talk abt AxisTransport and AxisXMLParser. But it doesn't mention
> abt Axis2Transport. We will have to put it there.
>
> >3) The Post Buld step od AxisServer still references the AXIS_HOME
> > environment variable.
>
> The Post Buld step of AxisServer does not refer to the AXIS_HOME
> environment variable.The environment variable AXIS_HOME is not used in
> the win dev guide.
>
> Can you pls recheck the win dev guide to see the problems that you found
> are still existing.
>
> Thanks for your information.
>
> Regards,
> Rangika
>
>
>
>
>
>
>
> I grabbed the latest CVS contents yesterday and set out to build and
> > install Axis and the sample calculator service under Apache 2.0. These
> > are the issues I ran into...
> >
> > 1) The .sln and .vcproj files are apparently very out of date. If no
> one
> > is going to maintain them, just get rid of them. In fact, it may be
> > easier to just have the .dsw files anyway to avoid having to maintain
> > parallel sets of workspace and project files.. I ended up just importing
> > the .dsw files into VS .NET and all was good.
> >
> > 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> > a) It talks about the AXIS_HOME environment variable (I discovered
> > via the debugger that it's now AXISCPP_DEPLOY)
> > b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> > been changed. Fortunately these are listed in the template
> > axiscpp.conf_win
> > c) It doesn't talk about AxisTransport, Axis2Transport, or the
> > AxisXMLParser projects and how they need to be deployed. I
> > successfully used the result of Axis2Transport and
> > AxisXMLParserExpat. It would be help ful to have some documentation
> > of all the projects in the workspace and what they do.
> > d) I assume section 4.4 is obsolete (using Xerces rather than
> > Expat).
> >
> > 3) The Post Buld step od AxisServer still references the AXIS_HOME
> > environment variable.
> >
> > 4) There is at least one (src/common/Packet.cpp) obsolete source file
> > hanging around. I found this because the VC7 project files still
> > reference it. It wasn't used in the VC6 project files, though the
> > Packet.h file is.
> >
> > 5) There is a "handlers" directory in the "deploy" source tree. Does
> this
> > have a purpose in the actual deployed system?
> >
> > Other than killing a bunch of time getting through some of the
> > documentation inconsistencies, things went pretty well. Now to see how
> > well it all works...
> >
> >
> > Dave Richards
> >
>
>
>
>
Re: New user issues on Windows
Posted by John Hawkins <HA...@uk.ibm.com>.
There was mention in the original note of the msdev project too. who uses
this now - is it kept up to date? I know that the ANT build is used here -
does anyone else still use this? It's crazy to have this overhead if it's
not used
John Hawkins
rangika@opensourc
e.lk
To
25/10/2004 07:38 "Apache AXIS C Developers List"
<ax...@ws.apache.org>
cc
Please respond to
"Apache AXIS C Subject
Developers List" Re: New user issues on Windows
Hi Dave,
I got the latest CVS contents & checked the windows developers guide.
> 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> a) It talks about the AXIS_HOME environment variable (I discovered
> via the debugger that it's now AXISCPP_DEPLOY)
It doesn't talk about AXIS_HOME environment variable but it talks about
AXISCPP_DEPLOY.
> b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> been changed. Fortunately these are listed in the template
> axiscpp.conf_win
AXISLOGPATH is not mentioned in the win dev guide.It talks abt
"logpath".Axis C++ 1.3 uses logpath.
> c) It doesn't talk about AxisTransport, Axis2Transport, or the
> AxisXMLParser projects and how they need to be deployed.
It does talk abt AxisTransport and AxisXMLParser. But it doesn't mention
abt Axis2Transport. We will have to put it there.
>3) The Post Buld step od AxisServer still references the AXIS_HOME
> environment variable.
The Post Buld step of AxisServer does not refer to the AXIS_HOME
environment variable.The environment variable AXIS_HOME is not used in
the win dev guide.
Can you pls recheck the win dev guide to see the problems that you found
are still existing.
Thanks for your information.
Regards,
Rangika
I grabbed the latest CVS contents yesterday and set out to build and
> install Axis and the sample calculator service under Apache 2.0. These
> are the issues I ran into...
>
> 1) The .sln and .vcproj files are apparently very out of date. If no
one
> is going to maintain them, just get rid of them. In fact, it may be
> easier to just have the .dsw files anyway to avoid having to maintain
> parallel sets of workspace and project files.. I ended up just importing
> the .dsw files into VS .NET and all was good.
>
> 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> a) It talks about the AXIS_HOME environment variable (I discovered
> via the debugger that it's now AXISCPP_DEPLOY)
> b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> been changed. Fortunately these are listed in the template
> axiscpp.conf_win
> c) It doesn't talk about AxisTransport, Axis2Transport, or the
> AxisXMLParser projects and how they need to be deployed. I
> successfully used the result of Axis2Transport and
> AxisXMLParserExpat. It would be help ful to have some documentation
> of all the projects in the workspace and what they do.
> d) I assume section 4.4 is obsolete (using Xerces rather than
> Expat).
>
> 3) The Post Buld step od AxisServer still references the AXIS_HOME
> environment variable.
>
> 4) There is at least one (src/common/Packet.cpp) obsolete source file
> hanging around. I found this because the VC7 project files still
> reference it. It wasn't used in the VC6 project files, though the
> Packet.h file is.
>
> 5) There is a "handlers" directory in the "deploy" source tree. Does
this
> have a purpose in the actual deployed system?
>
> Other than killing a bunch of time getting through some of the
> documentation inconsistencies, things went pretty well. Now to see how
> well it all works...
>
>
> Dave Richards
>
Re: New user issues on Windows
Posted by ra...@opensource.lk.
Hi Dave,
I got the latest CVS contents & checked the windows developers guide.
> 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> a) It talks about the AXIS_HOME environment variable (I discovered
> via the debugger that it's now AXISCPP_DEPLOY)
It doesn't talk about AXIS_HOME environment variable but it talks about
AXISCPP_DEPLOY.
> b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> been changed. Fortunately these are listed in the template
> axiscpp.conf_win
AXISLOGPATH is not mentioned in the win dev guide.It talks abt
"logpath".Axis C++ 1.3 uses logpath.
> c) It doesn't talk about AxisTransport, Axis2Transport, or the
> AxisXMLParser projects and how they need to be deployed.
It does talk abt AxisTransport and AxisXMLParser. But it doesn't mention
abt Axis2Transport. We will have to put it there.
>3) The Post Buld step od AxisServer still references the AXIS_HOME
> environment variable.
The Post Buld step of AxisServer does not refer to the AXIS_HOME
environment variable.The environment variable AXIS_HOME is not used in
the win dev guide.
Can you pls recheck the win dev guide to see the problems that you found
are still existing.
Thanks for your information.
Regards,
Rangika
I grabbed the latest CVS contents yesterday and set out to build and
> install Axis and the sample calculator service under Apache 2.0. These
> are the issues I ran into...
>
> 1) The .sln and .vcproj files are apparently very out of date. If no one
> is going to maintain them, just get rid of them. In fact, it may be
> easier to just have the .dsw files anyway to avoid having to maintain
> parallel sets of workspace and project files.. I ended up just importing
> the .dsw files into VS .NET and all was good.
>
> 2) The "Axis C++ Windows Developers Guide" is similarly outdated.
> a) It talks about the AXIS_HOME environment variable (I discovered
> via the debugger that it's now AXISCPP_DEPLOY)
> b) The axiscpp.conf directives AXISLOGPATH and WSDDFILEPATH have
> been changed. Fortunately these are listed in the template
> axiscpp.conf_win
> c) It doesn't talk about AxisTransport, Axis2Transport, or the
> AxisXMLParser projects and how they need to be deployed. I
> successfully used the result of Axis2Transport and
> AxisXMLParserExpat. It would be help ful to have some documentation
> of all the projects in the workspace and what they do.
> d) I assume section 4.4 is obsolete (using Xerces rather than
> Expat).
>
> 3) The Post Buld step od AxisServer still references the AXIS_HOME
> environment variable.
>
> 4) There is at least one (src/common/Packet.cpp) obsolete source file
> hanging around. I found this because the VC7 project files still
> reference it. It wasn't used in the VC6 project files, though the
> Packet.h file is.
>
> 5) There is a "handlers" directory in the "deploy" source tree. Does this
> have a purpose in the actual deployed system?
>
> Other than killing a bunch of time getting through some of the
> documentation inconsistencies, things went pretty well. Now to see how
> well it all works...
>
>
> Dave Richards
>