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 <sa...@opensource.lk> on 2004/12/02 13:40:54 UTC
Issues on windows for 1.4 alpha
We have encountered the following issues on windows in the tag for release
1.4 alpha.
1. Samples/doclitbase fails on windows on invoking echoStringArray
operation.
2. Dolitfaultclient /Rpcfaultclient was not building. The existing source
was replaced with generated source and that fixed the build problem.
Now when running it gives an AxisTransportException.
3. Stub base test hangs on running
4. Thread safe client does not compile.
5. WSDL2Ws does not generate source for uddiinquire test.
Some other problems and Issues were fixed and were committed to the HEAD.
sanjaya.
Re: Issues on windows for 1.4 alpha
Posted by sanjaya singharage <sa...@opensource.lk>.
Right, this was tested again and it is a non issue. Thanks.
sanjaya.
----- Original Message -----
From: "nithyakala" <ni...@opensource.lk>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Sent: Friday, December 03, 2004 8:45 AM
Subject: Re: Issues on windows for 1.4 alpha
> Hi Sanjay,
>
>
> WSDL2Ws do generates source for uddiinquire test on Linux platform.
> Since the tool is independent of the platform ...I think it should
> generates the stubs and skeletons on windows platform tooo.
>
>
> Regards,
> Nithya
>
>
>
>
>
>
> On Thu, 2004-12-02 at 18:40, sanjaya singharage wrote:
> > We have encountered the following issues on windows in the tag for
release
> > 1.4 alpha.
> >
> > 1. Samples/doclitbase fails on windows on invoking echoStringArray
> > operation.
> >
> > 2. Dolitfaultclient /Rpcfaultclient was not building. The existing
source
> > was replaced with generated source and that fixed the build problem.
> > Now when running it gives an AxisTransportException.
> >
> > 3. Stub base test hangs on running
> >
> > 4. Thread safe client does not compile.
> >
> > 5. WSDL2Ws does not generate source for uddiinquire test.
> >
> > Some other problems and Issues were fixed and were committed to the
HEAD.
> >
> > sanjaya.
> >
> >
>
>
Re: Issues on windows for 1.4 alpha
Posted by sanjaya singharage <sa...@opensource.lk>.
Hi samisa,
could I know to which problem you are refering to?
sanjaya.
----- Original Message -----
From: "Samisa Abeysinghe" <sa...@yahoo.com>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>;
<ni...@opensource.lk>
Sent: Friday, December 03, 2004 9:35 AM
Subject: Re: Issues on windows for 1.4 alpha
> There were few problems in Client.cpp - it had not been updated in sync
with header file location
> changes and .hpp header extention. I fixed those and commited. Now it
generates code, compiles and
> runs on Linux.
>
> Samisa...
>
> --- nithyakala <ni...@opensource.lk> wrote:
>
> > Hi Sanjay,
> >
> >
> > WSDL2Ws do generates source for uddiinquire test on Linux platform.
> > Since the tool is independent of the platform ...I think it should
> > generates the stubs and skeletons on windows platform tooo.
> >
> >
> > Regards,
> > Nithya
> >
> >
> >
> >
> >
> >
> > On Thu, 2004-12-02 at 18:40, sanjaya singharage wrote:
> > > We have encountered the following issues on windows in the tag for
release
> > > 1.4 alpha.
> > >
> > > 1. Samples/doclitbase fails on windows on invoking echoStringArray
> > > operation.
> > >
> > > 2. Dolitfaultclient /Rpcfaultclient was not building. The existing
source
> > > was replaced with generated source and that fixed the build problem.
> > > Now when running it gives an AxisTransportException.
> > >
> > > 3. Stub base test hangs on running
> > >
> > > 4. Thread safe client does not compile.
> > >
> > > 5. WSDL2Ws does not generate source for uddiinquire test.
> > >
> > > Some other problems and Issues were fixed and were committed to the
HEAD.
> > >
> > > sanjaya.
> > >
> > >
> >
> >
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Find what you need with new enhanced search.
> http://info.mail.yahoo.com/mail_250
>
Re: Issues on windows for 1.4 alpha
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
There were few problems in Client.cpp - it had not been updated in sync with header file location
changes and .hpp header extention. I fixed those and commited. Now it generates code, compiles and
runs on Linux.
Samisa...
--- nithyakala <ni...@opensource.lk> wrote:
> Hi Sanjay,
>
>
> WSDL2Ws do generates source for uddiinquire test on Linux platform.
> Since the tool is independent of the platform ...I think it should
> generates the stubs and skeletons on windows platform tooo.
>
>
> Regards,
> Nithya
>
>
>
>
>
>
> On Thu, 2004-12-02 at 18:40, sanjaya singharage wrote:
> > We have encountered the following issues on windows in the tag for release
> > 1.4 alpha.
> >
> > 1. Samples/doclitbase fails on windows on invoking echoStringArray
> > operation.
> >
> > 2. Dolitfaultclient /Rpcfaultclient was not building. The existing source
> > was replaced with generated source and that fixed the build problem.
> > Now when running it gives an AxisTransportException.
> >
> > 3. Stub base test hangs on running
> >
> > 4. Thread safe client does not compile.
> >
> > 5. WSDL2Ws does not generate source for uddiinquire test.
> >
> > Some other problems and Issues were fixed and were committed to the HEAD.
> >
> > sanjaya.
> >
> >
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
Re: Issues on windows for 1.4 alpha
Posted by nithyakala <ni...@opensource.lk>.
Hi Sanjay,
WSDL2Ws do generates source for uddiinquire test on Linux platform.
Since the tool is independent of the platform ...I think it should
generates the stubs and skeletons on windows platform tooo.
Regards,
Nithya
On Thu, 2004-12-02 at 18:40, sanjaya singharage wrote:
> We have encountered the following issues on windows in the tag for release
> 1.4 alpha.
>
> 1. Samples/doclitbase fails on windows on invoking echoStringArray
> operation.
>
> 2. Dolitfaultclient /Rpcfaultclient was not building. The existing source
> was replaced with generated source and that fixed the build problem.
> Now when running it gives an AxisTransportException.
>
> 3. Stub base test hangs on running
>
> 4. Thread safe client does not compile.
>
> 5. WSDL2Ws does not generate source for uddiinquire test.
>
> Some other problems and Issues were fixed and were committed to the HEAD.
>
> sanjaya.
>
>
Re: Issues on windows for 1.4 alpha
Posted by John Hawkins <HA...@uk.ibm.com>.
Hi Sanjaya,
If you can raise JIRA's with the details in then people can allocate them
so we know who's working on what.
John Hawkins
"sanjaya
singharage"
<sanjayas@opensou To
rce.lk> "Apache AXIS C Developers List"
<ax...@ws.apache.org>
02/12/2004 12:40 cc
Subject
Please respond to Issues on windows for 1.4 alpha
"Apache AXIS C
Developers List"
We have encountered the following issues on windows in the tag for release
1.4 alpha.
1. Samples/doclitbase fails on windows on invoking echoStringArray
operation.
2. Dolitfaultclient /Rpcfaultclient was not building. The existing source
was replaced with generated source and that fixed the build problem.
Now when running it gives an AxisTransportException.
3. Stub base test hangs on running
4. Thread safe client does not compile.
5. WSDL2Ws does not generate source for uddiinquire test.
Some other problems and Issues were fixed and were committed to the HEAD.
sanjaya.
Re: init() issues
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Re init():
http://nagoya.apache.org/jira/browse/AXISCPP-282
This is an issue yet to be fixed.
Samisa...
--- sanjaya singharage <sa...@opensource.lk> wrote:
> I think this work is incomplete. The session stuff existing in the code
> (except for the new client side session stuff) were done with future needs
> in mind. Therefore any scoping on engine objects should be rethinked and
> redone if necessary in my opinion.
>
> I have been working on the client side SOAP Header based sessions. The
> relevant sample can now talk with a session scoped Axis Java service (though
> there are some crashing problems on the c++ client). I would be making a
> post with how this was enabled and it needs to be improved. You might want
> to have a look at that sample to see what is needed to maintain
> interoperability with Axis Java Sessions.
>
> sanjaya.
>
> ----- Original Message -----
> From: "Steve Hardy" <st...@connectux.com>
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Sent: Thursday, December 02, 2004 7:01 PM
> Subject: init() issues
>
>
> > Hi guys,
> >
> > I may be completely wrong here, but what is the point of the init()
> > function on the webservice being called from the GetClassInstance in the
> > generated Wrapper classes, as well as being called directly from the
> > AxisEngine. I have been looking at the scoping and there doesn't seem to
> > be a difference in scoping as to when the init() function is called. Is
> > this by design or am I on completely the wrong track here?
> >
> > My idea would have been that:
> >
> > - Object is created when needed for the first time
> > - init() is called when the object is used in a new scope (so, at
> > load-time, at session switch time for session scope,
> > and before each invoke() for request scope)
> >
> > As far as I can see, init() is now always called before each invoke().
> >
> > Am I also correct in seeing that the session code is incomplete, although
> > there is quite some (untested?) code (like SessionScopeHandlerPool.cpp) to
> > handle session-based requests? Is anybody working on this at the moment?
> > If nobody is, are there any foreseeable problems with adding this support,
> > as it doesn't seem to be much work to me, and would definitely be a big
> > improvement ... ? I'd be glad to put in some work to get the session
> > scoping to work ...
> >
> >
>
>
>
__________________________________
Do you Yahoo!?
All your favorites on one personal page � Try My Yahoo!
http://my.yahoo.com
Re: init() issues
Posted by sanjaya singharage <sa...@opensource.lk>.
I think this work is incomplete. The session stuff existing in the code
(except for the new client side session stuff) were done with future needs
in mind. Therefore any scoping on engine objects should be rethinked and
redone if necessary in my opinion.
I have been working on the client side SOAP Header based sessions. The
relevant sample can now talk with a session scoped Axis Java service (though
there are some crashing problems on the c++ client). I would be making a
post with how this was enabled and it needs to be improved. You might want
to have a look at that sample to see what is needed to maintain
interoperability with Axis Java Sessions.
sanjaya.
----- Original Message -----
From: "Steve Hardy" <st...@connectux.com>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Sent: Thursday, December 02, 2004 7:01 PM
Subject: init() issues
> Hi guys,
>
> I may be completely wrong here, but what is the point of the init()
> function on the webservice being called from the GetClassInstance in the
> generated Wrapper classes, as well as being called directly from the
> AxisEngine. I have been looking at the scoping and there doesn't seem to
> be a difference in scoping as to when the init() function is called. Is
> this by design or am I on completely the wrong track here?
>
> My idea would have been that:
>
> - Object is created when needed for the first time
> - init() is called when the object is used in a new scope (so, at
> load-time, at session switch time for session scope,
> and before each invoke() for request scope)
>
> As far as I can see, init() is now always called before each invoke().
>
> Am I also correct in seeing that the session code is incomplete, although
> there is quite some (untested?) code (like SessionScopeHandlerPool.cpp) to
> handle session-based requests? Is anybody working on this at the moment?
> If nobody is, are there any foreseeable problems with adding this support,
> as it doesn't seem to be much work to me, and would definitely be a big
> improvement ... ? I'd be glad to put in some work to get the session
> scoping to work ...
>
>
init() issues
Posted by Steve Hardy <st...@connectux.com>.
Hi guys,
I may be completely wrong here, but what is the point of the init()
function on the webservice being called from the GetClassInstance in the
generated Wrapper classes, as well as being called directly from the
AxisEngine. I have been looking at the scoping and there doesn't seem to
be a difference in scoping as to when the init() function is called. Is
this by design or am I on completely the wrong track here?
My idea would have been that:
- Object is created when needed for the first time
- init() is called when the object is used in a new scope (so, at
load-time, at session switch time for session scope,
and before each invoke() for request scope)
As far as I can see, init() is now always called before each invoke().
Am I also correct in seeing that the session code is incomplete, although
there is quite some (untested?) code (like SessionScopeHandlerPool.cpp) to
handle session-based requests? Is anybody working on this at the moment?
If nobody is, are there any foreseeable problems with adding this support,
as it doesn't seem to be much work to me, and would definitely be a big
improvement ... ? I'd be glad to put in some work to get the session
scoping to work ...