> HI Experts,
>
[quoted text clipped - 20 lines]
>
> Thanks in adavance
It depends on what you mean by a "COM+ Server Component", ie, is this guy
actually expected to access COM++ services, or is it just something being
used by a COM++ Service.
I know that remark sounds dumb, but I'm asking because if your component is
going to be doing COM++ stuff (highly technical wording here <g>) you would
have already discovered by now that you needed to 'hook' or or somehow
facilitate COM++, and the answer would be obvious - Yes, I need to address
this issue.
Take a peek at this:
http://support.microsoft.com/kb/238274#appliesto
The article deals mostly with creating components that work with IIS/MTS,
but will get you started on the buzz words you can use to find further
information by Googling.
The real PITA with COM++ component development is debugging them. So
check-out the multiple COM++ debug articles, we will gleam a ton of
information between the lines.
In any case, COM++ covers a great deal of groung, we need to know more about
what it is you are really trying to do before providing any details.
hth
-ralph
pkiran - 22 Jun 2008 15:40 GMT
Hi Ralph,
Thanks for the reply.
Hi Brian,
Thanks for the reply.
basically I am Java programmer.
In my project requirement, I need to interface with COM+ objects from Java
space.
COM+ objects returns the ADODB.recordset object .
COM client objects( another dll file ) gets the reference of recordset and
populates the data into a collection object. if I interface with COM client
components, I have to do very little coding else very tough to interface with
COM+ objects as it returns the recordset object.
in this situation, I feel converting com client part would be easier than
interfacing with COM+ object.
To convet COM client to COM+ component ,
is it ok create an appliaction in COM+ Component Servcies and copy this dll.
Is these steps are sufficient to convert COM client to COM+ Server.
I observered with COM+ class files properties are
Databinding Behaviour = 0-VBNone
DataSourceBahavior = 0-VBNone
Instancing = 5-multiuse / ( only one file has instancing propety - 6
Global multiUse )
MTSTransactionmode = 2-RequiresTransaction
Persistable = 0 - NotPersistable.
Client part class files are having the following properties
Databinding Behaviour = 0-VBNone
DataSourceBahavior = 0-VBNone
Instancing = 5-multiuse
MTSTransactionmode = 0-NotAnMTSObject
Persistable = 1 - Persistable.
Should I have to change these propeties before converting the COM compnent
to COM+ component. Please guide me
thanks
pkiran
> > HI Experts,
> >
[quoted text clipped - 49 lines]
> hth
> -ralph