view release on metacpan or  search on metacpan

MICO/mapping.pod  view on Meta::CPAN

If the implementation of a interface in addition from the
implementation of a base interface, then the module
for the interface being implemented must appear in the @ISA 
array before the base interface implementation. 

For instance, when implementing the following IDL:

  module Foo {
     interface A { long foo(); };
     interface B : A { long bar(); }
  }

with the following Perl code;

  package MyA;

  @MyA::ISA = qw(Foo::A);
 
  sub foo {
      return 1;
  }  

  package MyB;

  @MyA::ISA = qw(Foo::B MyA);
 
  sub bar {
     return 2;
  } 

  sub new {
     my $self = bless {};
  }

C<Foo:B> must come first in C<MyB>'s C<@ISA>.

=head2 Implementing operations and attributes

Operations and attributes are implemented exactly as expected 
from the client-side mapping. That is, the operation is called
with the same parameters as a client would use to 
invoke the operation.

=head2 PortableServer routines

In general, the POA routines map from their description in the .IDL
file as specified above. One major exception to this rule is the
policy objects and the create_POA routine. There are no policy
objects, instead, the create_POA routine is variadic, with the
additional arguments being key-value pairs specifying Policy values.

For instance,

  $root_poa->create_POA ("MyPOA", undef,
			 id_assignment => 'MULTIPLE_ID',
		         lifetime => 'PERSISTENT');

=head2 Mapping for ServantManager

The opaque Cookie type maps to an arbitary Perl value.

=back

=head1 AUTHOR

Owen Taylor <otaylor@redhat.com>

=head1 SEE ALSO

perl(1).

=cut