Yes, math does work.  And I can view all the web services available.
But
when I try to hit my services, I get "Failed in creating DLL".  See
below:

[Fri Jan 25 13:39:40 2008] [debug]
..\..\src\core\engine\req_uri_disp.c(101) Checking for service using
target endpoint address : httplocalhost80/axis2/services/aewebservices70
[Fri Jan 25 13:39:40 2008] [debug] ..\..\util\src\utils.c(57)
service_str 1: services/aewebservices70
[Fri Jan 25 13:39:40 2008] [debug] ..\..\util\src\utils.c(59)
service_str 2: /aewebservices70
[Fri Jan 25 13:39:40 2008] [debug]
..\..\src\core\engine\req_uri_disp.c(131) Service found using target
endpoint address
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler AddressingInHandler within the phase Transport
[Fri Jan 25 13:39:41 2008] [info]  Starting addressing in handler
.........
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler addressing_based_dispatcher within the phase
Transport
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(660)
Invoking phase PreDispatch
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(660)
Invoking phase Dispatch
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler soap_message_body_based_dispatcher within the phase
Dispatch
[Fri Jan 25 13:39:41 2008] [debug]
..\..\src\core\engine\soap_body_disp.c(228) Checking for operation using
SOAP message body's first child's local name : CreatePrimaryItem
[Fri Jan 25 13:39:41 2008] [debug]
..\..\src\core\engine\soap_body_disp.c(236) Operation found using SOAP
message body's first child's local name
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler soap_action_based_dispatcher within the phase
Dispatch
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(660)
Invoking phase PostDispatch
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler dispatch_post_conditions_evaluator within the phase
PostDispatch
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler context_handler within the phase PostDispatch
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(670)
End:axis2_engine_invoke_phases
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(648)
Start:axis2_engine_invoke_phases
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(670)
End:axis2_engine_invoke_phases
[Fri Jan 25 13:39:41 2008] [error]
..\..\src\core\receivers\raw_xml_in_out_msg_recv.c(115) Impl object for
service 'aewebservices70' not set in message receiver. 100 :: Failed in
creating DLL
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(302)
Axis2 engine receive completed!
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(648)
Start:axis2_engine_invoke_phases
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(660)
Invoking phase MessageOut
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\phase.c(204)
Invoke the handler AddressingOutHandler within the phase MessageOut
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(670)
End:axis2_engine_invoke_phases
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(648)
Start:axis2_engine_invoke_phases
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(660)
Invoking phase MessageOut
[Fri Jan 25 13:39:41 2008] [debug] ..\..\src\core\engine\engine.c(670)
End:axis2_engine_invoke_phases 

-Dave.

-----Original Message-----
From: Senaka Fernando [mailto:[EMAIL PROTECTED] 
Sent: Monday, January 28, 2008 9:50 AM
To: Apache AXIS C User List
Subject: RE: [AXIS2C] Need IIS 6 instructions on how to set up Axis2/C

Hi Dave,

    Did any other sample work? for instance math? on IIS I mean.

Regards,
Senaka

> Hi Supun,
>
> I sent out a message to the list about a problem I am having getting 
> my dll to load with IIS 5.1.
>
> Do you have any ideas?  I build all my code in release mode and we use

> the same supporting dlls in our gSoap implementation so they should 
> load fine in IIS as we use gsoap in IIS as well.
>
> If I run with the simple axis2 server it works great.  Under IIS I get

> the error saying my dll failed to load.  I put all my dlls in 2
places:
> 1.  In my services directory where my services.xml and service dll is 
> located and also copied into the axis2c lib dir to see if that would 
> help.
>
> Is there a quick way to find out why this is not working?
>
> Thanks,
>
> -Dave.
>
> -----Original Message-----
> From: Supun Kamburugamuva [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 03, 2008 8:44 PM
> To: Apache AXIS C User List
> Subject: Re: [AXIS2C] Need IIS 6 instructions on how to set up Axis2/C
>
> Hi Dave,
>
> The instructions are same for the IIS 5 and IIS 6. At the moment IIS 
> module doesn't differentiate between IIS 6 and IIS 5.
>
> IIS module is built as a filter and an extension. This is the best way

> to do this in IIS 5. But in IIS 6 filters may be instantiated multiple

> times. That means multiple instances of Axis2/C. The same problem 
> existed with Apache server and I think now it is fixed for Apache in 
> Linux.
>
> There is another way that we can do this in IIS 6. In IIS 6 we can 
> drop the filter part completely and use an extension only. But last 
> time I checked on this there were several problems like multiple 
> instances, how URL dispatching works etc. As soon as possible I will 
> look in to this again and see if the module can be done in a IIS 6
specific way.
>
> Regards,
> Supun.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and 
> intended solely for the use of the individual or entity to whom they
are addressed.
> Any unauthorized review, use, disclosure or distribution is 
> prohibited. If you are not the intended recipient, please contact the 
> sender by reply e-mail and destroy all copies of the original message.
> **********************************************************************
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to