Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Received-SPF: pass (hermes.apache.org: domain of Chris.Campbell@assetsmart.com
 designates 64.52.11.126 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Axis Client Stubs running within Component Services
Date: Thu, 6 Jan 2005 14:57:32 -0800
Message-ID: <1D04F32D608E8349BCC7E35CA9B3321C07861F@mailsrv1.assetsmart.local>
Thread-Topic: Axis Client Stubs running within Component Services
Thread-Index: AcTz7rocBa7HDrHXT2qJPiPBAldKiQAUnoVQ
From: "Christopher J. Campbell" <Chris.Campbell@AssetSmart.com>
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>

One big issue in COM+ apps that do any network or file system
interaction is the "Identify" configuration under which the application
runs.  The default system account has very minimal privileges.

I have found that configuring the app as a "Library" type (vs "Server")
temporarily in Component Services can be helpful in troubleshooting
issues, as you can then perform interactive tests within a single
foreground process space i.e. command-prompt window.  If there is an
error MessageBox that can't be displayed when running as a background
server app due to lack of a display context, you will likely be able to
see it in Library app mode.  (I've mainly been using ActiveState Perl to
create simple test scripts, but you can of course use VB, VC++, ASP or
whatnot.)

I have not actually tried integrating AxisCPP client code into COM+
components as of yet, but may do so soon depending on the direction some
pending projects lean towards. Please keep us posted if you learn
anything significant!

Cheers,
	ChrisC

=20

-----Original Message-----
From: John Hambilton [mailto:john.hambilton@blueyonder.co.uk]=20
Sent: Thursday, January 06, 2005 4:50 AM
To: axis-c-user@ws.apache.org
Subject: Axis Client Stubs running within Component Services

Hello,

I've just started trying to get automatically generated C++ client stubs
running with Component Services. When I call the component I get the
following in the application event log:

The system has called a custom component and that component has failed
and generated an exception. This indicates a problem with the custom
component. Notify the developer of this component that a failure has
occurred and provide them with the information below.=20
Component Prog ID:=20
Server Application ID: {C65DBF8A-6099-4201-9E7E-7ED1D53DA90C}
Server Application Name: TEST
The serious nature of this error has caused the process to terminate.
Exception: E06D7363
Address: 0x7C4EA4E1
Call Stack:=20
KERNEL32!RaiseException + 0x55
MSVCRT!_CxxThrowException + 0x34
AxisClient!axiscpp::Stub::s_Initialize(void) + 0xEFD9
AxisClient!initialize_module + 0x150
AxisClient!axiscpp::Call::Call(void) + 0xA2
AxisClient!axiscpp::Stub::Stub(char const *,enum AXIS_PROTOCOL_TYPE) +
0x9F TEST!DllGetClassObject + 0x88FB TEST!DllGetClassObject + 0x10EFA
OLEAUT32!DispCallFunc + 0x15D OLEAUT32!ClearCustData + 0x588
TEST!DllGetClassObject + 0x18230 TEST!DllGetClassObject + 0x181A1
OLEAUT32!UserEXCEPINFO_free_local + 0x57D  + 0xEC87CAF4

Has anybody else had any success with COM+ and Axis? Has anybody tried
it? I've had the stubs working within a COM component outside of
Component Services. I'm just trying to get an idea of how difficult the
task of running within component services is going to be.

Cheers,

John