Re: mapping java => C++ objects

On 2007-08-12 16:27:13 -0400, "arun.darra@[EMAIL PROTECTED]
" 
<arun.darra@[EMAIL PROTECTED]
> said:
> Hi,
> 
> you can use "attribute's" to represent ur simple bean.
> Ur IDL will look something like this:
> 
> sample.idl :
> 
> interface Sample
> {
>    attribute String val;
> };
> 
> when this idl file is compiled by a idl compiler it will generate
> automatically a getter and a setter (like your bean).


Actually , that generates the declaration for a getter/setter which 
then needs to be implemented in my Impl class. Thats fine, but its just 
a bunch of boiler plate code to write.

> 
> I have used omniORB its pretty cool and easy to use,
> but I have one question for u - howcome ur using JacORB (on java side)
> instead the std SunORB (that comes as part of the JDK), any specific
> reason?

We're mainly using it as it is what jboss uses as its orb in their 
application server. So far it performs well enough and is fairly 
painless to use. I've heard mixed reviews about sun's orb 
implementation on a few lists. I've yet to hear a compelling enough 
reason to push for a reconfiguration of our app servers.