You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by Yuvaraj Athur Raghuvir <yu...@gmail.com> on 2007/08/08 15:32:05 UTC
Using AXIS2C from scripting environment
Hello,
I am trying to use AXIS2C from a scripting environment. I get a access
violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes
my environment to crash.
To detect the problem, I tried to build the axutil dll on VC++ express
edition only to find that the dll I create is generating error much
earlier!!
Any clues?
Regards,
Yuva
Re: Using AXIS2C from scripting environment
Posted by Yuvaraj Athur Raghuvir <yu...@gmail.com>.
Hello Nandika,
Is axiom_xml_reader_init (); an exported function? I do not find it any of
the lib files.
In this case, how should I link it? I get a linker error due to this call.
Regards,
Yuva
On 8/9/07, Nandika Jayawardana <ja...@gmail.com> wrote:
>
> Hi Yuva,
>
> There are few posibilities that might produce this error.
> Try putting
> axiom_xml_reader_init (); function at the start of your code.
> This function initializes the parser for threaded environment.
>
> Thanks
> Nandika
>
> On 8/8/07, Yuvaraj Athur Raghuvir <yu...@gmail.com> wrote:
>
> > Hello,
> >
> > I am trying to use AXIS2C from a scripting environment. I get a access
> > violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes
> > my environment to crash.
> >
> > To detect the problem, I tried to build the axutil dll on VC++ express
> > edition only to find that the dll I create is generating error much
> > earlier!!
> >
> > Any clues?
> >
> > Regards,
> > Yuva
> >
> >
>
>
> --
> nandika@wso2.com
> WSO2 Inc: http://www.wso2.com
Re: Using AXIS2C from scripting environment
Posted by Nandika Jayawardana <ja...@gmail.com>.
Hi Yuva,
There are few posibilities that might produce this error.
Try putting
axiom_xml_reader_init (); function at the start of your code.
This function initializes the parser for threaded environment.
Thanks
Nandika
On 8/8/07, Yuvaraj Athur Raghuvir <yu...@gmail.com> wrote:
> Hello,
>
> I am trying to use AXIS2C from a scripting environment. I get a access
> violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes
> my environment to crash.
>
> To detect the problem, I tried to build the axutil dll on VC++ express
> edition only to find that the dll I create is generating error much
> earlier!!
>
> Any clues?
>
> Regards,
> Yuva
>
>
--
nandika@wso2.com
WSO2 Inc: http://www.wso2.com
Re: Using AXIS2C from scripting environment
Posted by Yuvaraj Athur Raghuvir <yu...@gmail.com>.
Hello,
Enclosed is a log of the yahoo application I am trying.
1) When I try this from home, everything works fine. And I get a response.
2) At work, I work behind a firewall with a proxy server associated.
a) The yahoo_client.c responds perfectly fine. I can see the results
b) When I do it via the scripting environment I speak about, I get a
failure. The return value is null.
I replaced proxy server with IP address -> no difference
Am I missing any settings that are available via the VC++ environment but
not available when done outside the standard environment?
Regards,
Yuva
(log file enclosed)
p.s:
Error in the log file is the following:
[Thu Aug 16 14:31:20 2007] [error]
..\..\src\core\transport\http\sender\http_sender.c(528) status_code < 0
Later the log also says:
[Thu Aug 16 14:31:20 2007] [debug] ..\..\src\core\engine\engine.c(179) Axis2
engine send successful
But there is no receive....
On 8/9/07, Dumindu Pallewela <du...@wso2.com> wrote:
>
> Yuvaraj Athur Raghuvir wrote:
>
> > Can you also tell me the location from where I can download the
> following?
> > a) libapr-1.lib apr-1.lib libhttpd.lib & associated dlls
>
> These libs are in the lib/ directory of your apache installation. DLLs
> can be found inside bin/ directory. You can download apache win32
> binaries from:
> http://www.apache.org/dist/httpd/binaries/win32/
>
> > b) libcurl_imp.lib & associated dlls [should I choose with SSL or
> without?]
> We don't have SSL support for libcurl transport yet. :( However, we do
> have our own client SSL transport.
>
> Anyway you can find the libs in the directory you extracted libcurl
> package, if you downloaded it from the official site.
>
> Whether to build with SSL or without, is up to you and depends on your
> requirement.
>
> > c) httpd.lib & associated dlls
> Same as in a).
>
> > d) ssl ( I have got the installation from Shining Light Productions - is
> > this ok)?
>
> As far as it contains the necessary libs, it is fine :)
>
> Regards,
> Dumindu.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
Re: Using AXIS2C from scripting environment
Posted by Dumindu Pallewela <du...@wso2.com>.
Yuvaraj Athur Raghuvir wrote:
> Can you also tell me the location from where I can download the following?
> a) libapr-1.lib apr-1.lib libhttpd.lib & associated dlls
These libs are in the lib/ directory of your apache installation. DLLs
can be found inside bin/ directory. You can download apache win32
binaries from:
http://www.apache.org/dist/httpd/binaries/win32/
> b) libcurl_imp.lib & associated dlls [should I choose with SSL or without?]
We don't have SSL support for libcurl transport yet. :( However, we do
have our own client SSL transport.
Anyway you can find the libs in the directory you extracted libcurl
package, if you downloaded it from the official site.
Whether to build with SSL or without, is up to you and depends on your
requirement.
> c) httpd.lib & associated dlls
Same as in a).
> d) ssl ( I have got the installation from Shining Light Productions - is
> this ok)?
As far as it contains the necessary libs, it is fine :)
Regards,
Dumindu.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: Using AXIS2C from scripting environment
Posted by Yuvaraj Athur Raghuvir <yu...@gmail.com>.
Hello Nandika,
Can you also tell me the location from where I can download the following?
a) libapr-1.lib apr-1.lib libhttpd.lib & associated dlls
b) libcurl_imp.lib & associated dlls [should I choose with SSL or without?]
c) httpd.lib & associated dlls
d) ssl ( I have got the installation from Shining Light Productions - is
this ok)?
My builds fail without these.
Thanks,
Yuva
On 8/9/07, Nandika Jayawardana <ja...@gmail.com> wrote:
>
> Hi Yuvaraj,
>
> To build axis2c from vc project, use the vc2005 project solution file
> located in <AXIS2 SOURCE DIR>ides\vc\axis2c folder. It will build axis2c to
> a folder named deploy in <AXIS2 SOURCE DIR>ides\vc\axis2c directory.
>
> Regards
> Nandika
>
>
> On 8/9/07, Yuvaraj Athur Raghuvir <yu...@gmail.com> wrote:
> >
> > Hello Dinesh,
> >
> > I am trying to do exactly what the yahoo_client.c sample does from a
> > scripting language called J available here <http://www.jsoftware.com/>
> > .[1]
> >
> > 1) Running yahoo_client.c crashes at
> > axis2_svc_client_free(svc_client, env);
> > Debugging via VC revels the crash at (one of these two lines....)
> > if (transport_out->param_container)
> > {
> > axutil_param_container_free(transport_out->param_container,
> > env);
> > }
> >
> > if (transport_out->out_flow)
> > {
> > axis2_flow_free(transport_out->out_flow, env);
> > }
> >
> > Note: I added proxy statement since I work behind a firewall.
> >
> > 2) From J, I can invoke dlls. This requires parameter passing. Here, at
> > the point of
> > axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE
> > I have a crash. I notice that with yahoo_client.c at this point, the
> > parent process console window appears briefly since that address space is
> > accessed.
> >
> >
> > 3) I was hoping you will tell me when is the Transport Sender set. This
> > can give me a clue to what is causing the corruption.
> >
> > Further, my local build of axutil project causes a crash much
> > earlier....so any pointers on building axutil on VC will also be appreciated
> > since that could tell me what is causing the corruption that causes the
> > crash. I also know that my implementation in J could be the cause. So, all I
> > need is some guidance on
> > a) where is this set?
> > b) are there any configuration parameters that need to be set?
> > c) when I build local axutil project, the path separator is "/" instead
> > of "\" for windows. That could lead to the fact that the dlls relevant
> > (module\addressing\axis2_mod_addr.dll) is not getting loaded.
> >
> > Attached is the complete log file when invoked from the scripting
> > language.
> >
> > Regards,
> > Yuva
> >
> > Encl:
> >
> >
> >
> >
> > [1] http://www.jsoftware.com/
> >
> >
> > On 8/9/07, Dinesh Premalal < xydinesh@gmail.com > wrote:
> > >
> > > Hi Yuvaraj,
> > >
> > > "Yuvaraj Athur Raghuvir" < yuvaraj.a.r@gmail.com> writes:
> > >
> > > > Hello Dinesh,
> > > >
> > > > This is what the log file says:
> > > >>>
> > > > Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c (231)
> > > module name
> > > > is:addressing
> > > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c (129) Add
> > > handler
> > > > AddressingOutHandler to phase MessageOut
> > > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module
> > > name
> > > > is:addressing
> > > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c (231)
> > > module name
> > > > is:addressing
> > > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c (129) Add
> > > handler
> > > > AddressingOutHandler to phase MessageOut
> > > > [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\engine\engine.c(572) Invoking phase
> > > MessageOut
> > > > [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-
> > > src-1.0.0\
> > > > axis2c-src-1.0.0\src\core\engine\phase.c (195) Invoke the handler
> > > > AddressingOutHandler within the phase MessageOut
> > > It is quite difficult to me to understand this piece of logfile
> > > only. Could you please attach your logfile. If possible , could you
> > > please give us some rough idea about your use case. It will help us to
> > >
> > > locate possible errors.
> > >
> > > thanks,
> > > Dinesh
> > >
> > > --
> > > Dinesh Premalal
> > > http://xydinesh.wordpress.com/
> > > GPG ID : A255955C
> > > GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255
> > > 955C
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-c-user-help@ws.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-user-help@ws.apache.org
> >
> >
>
>
> --
> nandika@wso2.com
> WSO2 Inc: http://www.wso2.com
>
Re: Using AXIS2C from scripting environment
Posted by Nandika Jayawardana <ja...@gmail.com>.
Hi Yuvaraj,
To build axis2c from vc project, use the vc2005 project solution file
located in <AXIS2 SOURCE DIR>ides\vc\axis2c folder. It will build axis2c to
a folder named deploy in <AXIS2 SOURCE DIR>ides\vc\axis2c directory.
Regards
Nandika
On 8/9/07, Yuvaraj Athur Raghuvir <yu...@gmail.com> wrote:
>
> Hello Dinesh,
>
> I am trying to do exactly what the yahoo_client.c sample does from a
> scripting language called J available here <http://www.jsoftware.com/>.[1]
>
> 1) Running yahoo_client.c crashes at
> axis2_svc_client_free(svc_client, env);
> Debugging via VC revels the crash at (one of these two lines....)
> if (transport_out->param_container)
> {
> axutil_param_container_free(transport_out->param_container, env);
> }
>
> if (transport_out->out_flow)
> {
> axis2_flow_free(transport_out->out_flow, env);
> }
>
> Note: I added proxy statement since I work behind a firewall.
>
> 2) From J, I can invoke dlls. This requires parameter passing. Here, at
> the point of
> axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE
> I have a crash. I notice that with yahoo_client.c at this point, the
> parent process console window appears briefly since that address space is
> accessed.
>
>
> 3) I was hoping you will tell me when is the Transport Sender set. This
> can give me a clue to what is causing the corruption.
>
> Further, my local build of axutil project causes a crash much
> earlier....so any pointers on building axutil on VC will also be appreciated
> since that could tell me what is causing the corruption that causes the
> crash. I also know that my implementation in J could be the cause. So, all I
> need is some guidance on
> a) where is this set?
> b) are there any configuration parameters that need to be set?
> c) when I build local axutil project, the path separator is "/" instead of
> "\" for windows. That could lead to the fact that the dlls relevant
> (module\addressing\axis2_mod_addr.dll) is not getting loaded.
>
> Attached is the complete log file when invoked from the scripting
> language.
>
> Regards,
> Yuva
>
> Encl:
>
>
>
>
> [1] http://www.jsoftware.com/
>
>
> On 8/9/07, Dinesh Premalal < xydinesh@gmail.com> wrote:
> >
> > Hi Yuvaraj,
> >
> > "Yuvaraj Athur Raghuvir" < yuvaraj.a.r@gmail.com> writes:
> >
> > > Hello Dinesh,
> > >
> > > This is what the log file says:
> > >>>
> > > Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\
> > > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module
> > name
> > > is:addressing
> > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > > axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c (129) Add
> > handler
> > > AddressingOutHandler to phase MessageOut
> > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > src-1.0.0\
> > > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module
> > name
> > > is:addressing
> > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c (231) module
> > name
> > > is:addressing
> > > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
> > src-1.0.0\
> > > axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add
> > handler
> > > AddressingOutHandler to phase MessageOut
> > > [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > > axis2c-src-1.0.0\src\core\engine\engine.c(572) Invoking phase
> > MessageOut
> > > [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > > axis2c-src-1.0.0\src\core\engine\phase.c (195) Invoke the handler
> > > AddressingOutHandler within the phase MessageOut
> > It is quite difficult to me to understand this piece of logfile
> > only. Could you please attach your logfile. If possible , could you
> > please give us some rough idea about your use case. It will help us to
> > locate possible errors.
> >
> > thanks,
> > Dinesh
> >
> > --
> > Dinesh Premalal
> > http://xydinesh.wordpress.com/
> > GPG ID : A255955C
> > GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255
> > 955C
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-c-user-help@ws.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
--
nandika@wso2.com
WSO2 Inc: http://www.wso2.com
Re: Using AXIS2C from scripting environment
Posted by Yuvaraj Athur Raghuvir <yu...@gmail.com>.
Hello Dinesh,
I am trying to do exactly what the yahoo_client.c sample does from a
scripting language called J available here <http://www.jsoftware.com/>.[1]
1) Running yahoo_client.c crashes at
axis2_svc_client_free(svc_client, env);
Debugging via VC revels the crash at (one of these two lines....)
if (transport_out->param_container)
{
axutil_param_container_free(transport_out->param_container, env);
}
if (transport_out->out_flow)
{
axis2_flow_free(transport_out->out_flow, env);
}
Note: I added proxy statement since I work behind a firewall.
2) From J, I can invoke dlls. This requires parameter passing. Here, at the
point of
axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE
I have a crash. I notice that with yahoo_client.c at this point, the parent
process console window appears briefly since that address space is accessed.
3) I was hoping you will tell me when is the Transport Sender set. This can
give me a clue to what is causing the corruption.
Further, my local build of axutil project causes a crash much earlier....so
any pointers on building axutil on VC will also be appreciated since that
could tell me what is causing the corruption that causes the crash. I also
know that my implementation in J could be the cause. So, all I need is some
guidance on
a) where is this set?
b) are there any configuration parameters that need to be set?
c) when I build local axutil project, the path separator is "/" instead of
"\" for windows. That could lead to the fact that the dlls relevant
(module\addressing\axis2_mod_addr.dll) is not getting loaded.
Attached is the complete log file when invoked from the scripting language.
Regards,
Yuva
Encl:
[1] http://www.jsoftware.com/
On 8/9/07, Dinesh Premalal <xy...@gmail.com> wrote:
>
> Hi Yuvaraj,
>
> "Yuvaraj Athur Raghuvir" <yu...@gmail.com> writes:
>
> > Hello Dinesh,
> >
> > This is what the log file says:
> >>>
> > Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module
> name
> > is:addressing
> > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add handler
> > AddressingOutHandler to phase MessageOut
> > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\
> > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module
> name
> > is:addressing
> > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c (231) module
> name
> > is:addressing
> > [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add handler
> > AddressingOutHandler to phase MessageOut
> > [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > axis2c-src-1.0.0\src\core\engine\engine.c(572) Invoking phase MessageOut
> > [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> > axis2c-src-1.0.0\src\core\engine\phase.c (195) Invoke the handler
> > AddressingOutHandler within the phase MessageOut
> It is quite difficult to me to understand this piece of logfile
> only. Could you please attach your logfile. If possible , could you
> please give us some rough idea about your use case. It will help us to
> locate possible errors.
>
> thanks,
> Dinesh
>
> --
> Dinesh Premalal
> http://xydinesh.wordpress.com/
> GPG ID : A255955C
> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
Re: Using AXIS2C from scripting environment
Posted by Dinesh Premalal <xy...@gmail.com>.
Hi Yuvaraj,
"Yuvaraj Athur Raghuvir" <yu...@gmail.com> writes:
> Hello Dinesh,
>
> This is what the log file says:
>>>
> Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module name
> is:addressing
> [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add handler
> AddressingOutHandler to phase MessageOut
> [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c- src-1.0.0\
> axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231) module name
> is:addressing
> [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c (231) module name
> is:addressing
> [Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add handler
> AddressingOutHandler to phase MessageOut
> [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> axis2c-src-1.0.0\src\core\engine\engine.c(572) Invoking phase MessageOut
> [Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-src-1.0.0\
> axis2c-src-1.0.0\src\core\engine\phase.c (195) Invoke the handler
> AddressingOutHandler within the phase MessageOut
It is quite difficult to me to understand this piece of logfile
only. Could you please attach your logfile. If possible , could you
please give us some rough idea about your use case. It will help us to
locate possible errors.
thanks,
Dinesh
--
Dinesh Premalal
http://xydinesh.wordpress.com/
GPG ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org
Re: Using AXIS2C from scripting environment
Posted by Yuvaraj Athur Raghuvir <yu...@gmail.com>.
Hello Dinesh,
This is what the log file says:
>>
Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231)
module name is:addressing
[Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add
handler AddressingOutHandler to phase MessageOut
[Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231)
module name is:addressing
[Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_resolver.c(231)
module name is:addressing
[Thu Aug 09 11:27:28 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\phaseresolver\phase_holder.c(129) Add
handler AddressingOutHandler to phase MessageOut
[Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\engine\engine.c(572) Invoking phase
MessageOut
[Thu Aug 09 11:27:45 2007] [debug] c:\08.utils\axis2\axis2c-
src-1.0.0\axis2c-src-1.0.0\src\core\engine\phase.c(195) Invoke the handler
AddressingOutHandler within the phase MessageOut
<<
Regards,
Yuva
On 8/9/07, Dinesh Premalal <xy...@gmail.com> wrote:
>
> Yuvaraj,
> "Yuvaraj Athur Raghuvir" <yu...@gmail.com> writes:
>
> > Hello,
> >
> > I am trying to use AXIS2C from a scripting environment. I get a access
> > violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that
> causes my
> > environment to crash.
> What does your log file says?
>
> thanks,
> Dinesh
>
> --
> Dinesh Premalal
> http://xydinesh.wordpress.com/
> GPG ID : A255955C
> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-c-user-help@ws.apache.org
>
>
Re: Using AXIS2C from scripting environment
Posted by Dinesh Premalal <xy...@gmail.com>.
Yuvaraj,
"Yuvaraj Athur Raghuvir" <yu...@gmail.com> writes:
> Hello,
>
> I am trying to use AXIS2C from a scripting environment. I get a access
> violation at axis2_engine_send::AXIS2_TRANSPORT_SENDER_INVOKE that causes my
> environment to crash.
What does your log file says?
thanks,
Dinesh
--
Dinesh Premalal
http://xydinesh.wordpress.com/
GPG ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-user-help@ws.apache.org