[oe-commits] org.oe.dev omniorb : Add a basic config file to image.

crofton commit openembedded-commits at lists.openembedded.org
Thu Oct 19 18:37:54 UTC 2006


omniorb : Add a basic config file to image.

Author: crofton at openembedded.org
Branch: org.openembedded.dev
Revision: 576d11411cdf287490200b3387241d0bf692b87e
ViewMTN: http://monotone.openembedded.org/revision.psp?id=576d11411cdf287490200b3387241d0bf692b87e
Files:
1
packages/omniorb/files/omniORB.cfg
packages/omniorb/omniorb_4.0.7.bb
Diffs:

#
# mt diff -ra64c1661a22a165515c7871d50667a1f7ea92a99 -r576d11411cdf287490200b3387241d0bf692b87e
#
# 
# 
# add_file "packages/omniorb/files/omniORB.cfg"
#  content [29b9f06f73f2b654aec5785deda02fd5aad58bfa]
# 
# patch "packages/omniorb/omniorb_4.0.7.bb"
#  from [bc6f333c3740b958a3294661a8f84fe3250e5a5c]
#    to [d62a81c508f604a2923759c51e714feace072aeb]
# 
============================================================
--- packages/omniorb/files/omniORB.cfg	29b9f06f73f2b654aec5785deda02fd5aad58bfa
+++ packages/omniorb/files/omniORB.cfg	29b9f06f73f2b654aec5785deda02fd5aad58bfa
@@ -0,0 +1,918 @@
+############################################################################
+#           omniORB (4.0 or above) configuration file                      #
+############################################################################
+
+############################################################################
+############################################################################
+############################################################################
+#                                                                          #
+#            ORB wide options                                              #
+#                                                                          #
+############################################################################
+
+############################################################################
+# Tracing level
+#     level 0 -  critical errors only
+#     level 1 -  informational messages only
+#     level 2 -  configuration information and warnings
+#     level 5 -  the above plus report server thread creation and
+#                communication socket shutdown
+#     level 10 - the above plus execution trace messages
+#     level 25 - output trace message per send or receive giop message
+#     level 30 - dump up to 128 bytes of a giop message
+#     level 40 - dump the complete giop message
+#
+#     Valid values = (n >= 0)
+#
+
+#traceLevel = 1
+
+############################################################################
+# Trace Exceptions
+#     If true, then system exceptions will be logged when they are thrown.
+#
+#     Valid values = 0 or 1
+#
+traceExceptions = 0
+
+############################################################################
+# Trace Invocations
+#     If true, then each local and remote invocation will generate a trace 
+#     message.
+#
+#     Valid values = 0 or 1
+#
+traceInvocations = 0
+
+############################################################################
+# Trace thread id
+#     If true, all trace messages include the thread id of the thread doing
+#     the logging.
+#
+#     Valid values = 0 or 1
+#
+traceThreadId = 0
+
+############################################################################
+# dumpConfiguration
+#     Set to 1 to cause the ORB to dump the current set of configuration
+#     parameters.
+#
+#     Valid values = 0 or 1
+#
+dumpConfiguration = 0
+
+############################################################################
+# maxGIOPVersion
+#
+#   Set the maximum GIOP version the ORB should support. The ORB tries
+#   to match the <major>.<minor> version as specified.
+#
+#   Valid values = 1.0 | 1.1 | 1.2
+#
+maxGIOPVersion = 1.2
+
+############################################################################
+# giopMaxMsgSize
+#
+#    This value defines the ORB-wide limit on the size of GIOP message 
+#    (excluding the header). If this limit is exceeded, the ORB will
+#    refuse to send or receive the message and raise a MARSHAL exception.
+#
+#    Valid values = (n >= 8192)
+#
+giopMaxMsgSize = 2097152    # 2 MBytes.
+
+############################################################################
+# strictIIOP flag
+#    Enable vigorous check on incoming IIOP messages
+#
+#    In some (sloppy) IIOP implementations, the message size value in
+#    the header can be larger than the actual body size, i.e. there is
+#    garbage at the end. As the spec does not say the message size
+#    must match the body size exactly, this is not a clear violation
+#    of the spec.
+#
+#    If this flag is non-zero, the incoming message is expected to
+#    be well-behaved. Any messages that have garbage at the end will
+#    be rejected.
+#    
+#    The default value of this flag is true, so invalid messages are
+#    rejected. If you set it to zero, the ORB will silently skip the
+#    unread part. The problem with this behaviour is that the header
+#    message size may actually be garbage, caused by a bug in the
+#    sender's code. The receiving thread may block forever on the
+#    strand as it tries to read more data from it. In this case the
+#    sender won't send any more as it thinks it has marshalled in all
+#    the data.
+#
+#    Valid values = 0 or 1
+#
+strictIIOP = 1
+
+############################################################################
+# lcdMode
+#
+#   Set to 1 to enable 'Lowest Common Denominator' Mode.
+#   This will disable various features of IIOP and GIOP which are
+#   poorly supported by some ORBs, and disable warnings/errors when
+#   certain types of erroneous message are received on the wire.
+#
+#   Valid values = 0 or 1
+#
+lcdMode = 0
+
+############################################################################
+# tcAliasExpand flag
+#
+#    This flag is used to indicate whether TypeCodes associated with Anys
+#    should have aliases removed. This functionality is included because
+#    some ORBs will not recognise an Any containing a TypeCode with
+#    aliases to be the same as the actual type contained in the Any. Note
+#    that omniORB will always remove top-level aliases, but will not remove
+#    aliases from TypeCodes that are members of other TypeCodes (e.g.
+#    TypeCodes for members of structs etc.), unless tcAliasExpand is set to 1.
+#    There is a performance penalty when inserting into an Any if 
+#    tcAliasExpand is set to 1. The default value is 0 (i.e. aliases of
+#    member TypeCodes are not expanded). Note that aliases won't be expanded
+#    when one of the non-type-safe methods of inserting into an Any is
+#    used (i.e. when the replace() member function or non - type-safe Any
+#    constructor is used. )
+#
+#     Valid values = 0 or 1
+#
+tcAliasExpand = 0
+
+############################################################################
+# useTypeCodeIndirections
+#
+#    If true (the default), typecode indirections will be used. Set
+#    this to false to disable that. Setting this to false might be
+#    useful to interoperate with another ORB implementation that cannot
+#    handle indirections properly.
+#   
+#    Valid values = 0 or 1
+useTypeCodeIndirections = 1
+
+############################################################################
+# acceptMisalignedTcIndirections
+#
+#    If true, try to fix a mis-aligned indirection in a typecode. This
+#    is used to work around a bug in some versions of Visibroker's Java
+#    ORB.
+#   
+#    Valid values = 0 or 1
+acceptMisalignedTcIndirections = 0
+
+############################################################################
+# scanGranularity
+#
+#   The granularity at which the ORB scans for idle connections.
+#   This value determines the minimum value that inConScanPeriod or
+#   outConScanPeriod can be.
+#
+#   Valid values = (n >= 0 in seconds) 
+#                   0 --> do not scan for idle connections.
+#
+scanGranularity = 5
+
+############################################################################
+# nativeCharCodeSet
+#
+#   set the native code set for char and string
+#
+nativeCharCodeSet = ISO-8859-1
+
+############################################################################
+# nativeWCharCodeSet
+#
+#   set the native code set for wchar and wstring
+#
+nativeWCharCodeSet = UTF-16
+
+############################################################################
+# omniORB_27_CompatibleAnyExtraction
+#
+#   In omniORB pre-2.8.0 versions, the CORBA::Any extraction operator for
+#     1. unbounded string operator>>=(char*&)
+#     2. bounded string   operator>>=(to_string)
+#     3. object reference operator>>=(A_ptr&) for interface A
+#   Return a copy of the value. The caller must free the returned
+#   value later.
+#
+#   With 2.8.0 and later, the semantics becomes non-copy, i.e. the Any
+#   still own the storage of the returned value.
+#   This would cause a problem in a program that is written to use the
+#   pre-2.8.0 semantics. To make it easier for the transition,
+#   set omniORB_27_CompatibleAnyExtraction to 1.
+#   This would revert the semantics to the pre-2.8.0 versions.
+#
+#   Valid values = 0 or 1
+#
+omniORB_27_CompatibleAnyExtraction = 0
+
+############################################################################
+# abortOnInternalError
+#
+#   If the value of this variable is TRUE then the ORB will abort
+#   instead of throwing an exception when a fatal internal error is
+#   detected. This is useful for debuging the ORB -- as the stack will
+#   not be unwound by the exception handler, so a stack trace can be
+#   obtained.
+#   It is hoped that this will not often be needed by users of omniORB!
+#
+#   Valid values = 0 or 1
+#
+abortOnInternalError = 0
+
+############################################################################
+# abortOnNativeException
+#
+#   On Windows, "native" exceptions such as segmentation faults and
+#   divide by zero appear as C++ exceptions that can be caught with
+#   catch (...). Setting this parameter to TRUE causes such exceptions
+#   to abort the process instead.
+#
+#   This parameter has no effect on other platforms.
+#
+#   Valid values = 0 or 1
+#
+abortOnNativeException = 0
+
+############################################################################
+# maxSocketSend
+# maxSocketRecv
+#
+#   On some platforms, calls to send() and recv() have a limit on the
+#   buffer size that can be used. These parameters set the limits in
+#   bytes that omniORB uses when sending / receiving bulk data.
+#
+#   The default values are platform specific. It is unlikely that you
+#   will need to change the values from the defaults.
+#
+#   The minimum valid limit is 8KB, 8192 bytes.
+#
+#   e.g. to limit to 64KB sends / receives:
+#
+#     maxSocketSend = 65536
+#     maxSocketRecv = 65536
+
+############################################################################
+# sslCAFile
+# sslKeyFile
+# sslKeyPassword
+# sslVerifyMode
+#
+#   SSL transport options
+#
+#   sslCAFile specifies the file containing the SSL Certificate
+#   Authority certificate.
+#
+#   sslKeyFile specifies the file containing the SSL key.
+#
+#   sslKeyPassword specifies the password to unlock the key.
+#
+#   sslVerifyMode specifies the verify mode, as given to
+#   SSL_CTX_set_verify. Valid values are "none", representing
+#   SSL_VERIFY_NONE, and "peer", representing SSL_VERIFY_PEER. If peer
+#   is selected, additional options "fail" and "once" can also be
+#   specified, corresponding to SSL_VERIFY_FAIL_IF_NO_PEER_CERT and
+#   SSL_VERIFY_CLIENT_ONCE respectively. e.g.
+#
+#     sslVerifyMode = peer,fail
+#
+#   These options are only available if the SSL transport is linked.
+
+
+############################################################################
+############################################################################
+############################################################################
+#                                                                          #
+#            Client Side Options                                           #
+#                                                                          #
+############################################################################
+
+############################################################################
+# InitRef
+#
+#   Specify the objects the ORB should return in response to calls to
+#   resolve_initial_references.
+#
+#   There can be more than one configuration line defining InitRef.
+#   Each line adds one initial reference to the ORB.
+#
+#   Here are some valid examples:
+#
+#   Specify the root context of the Naming Service. (Notice the end of line
+#   continuation marker '\'
+#
+#   InitRef = NameService=IOR:010000002800000049444c3a6f6d672e6f72672f436f734\
+#e616d696e672f4e616d696e67436f6e746578743a312e300001000000000000002c000000010\
+#102000c0000003139322e3136382e312e3000f90a00000c000000349568c45cb1e6780000000\
+#100000000
+#
+#   Alternatively, and more cleanly, specify the Naming service with a
+#   corbaname URI:
+#
+InitRef = NameService=corbaname::localhost
+#
+#
+#   Specify the Trading service and the interface repository using corbaloc:
+#
+#   InitRef = TradingService=corbaloc:iiop:marrow:5009/MyObjectKey
+#           = InterfaceRepository=corbaloc::1.2 at marrow:5009/Intf
+#
+#   The default for the set of initial references is empty.
+
+############################################################################
+# DefaultInitRef
+#
+#   DefaultInitRef provides a prefix string which is used to resolve 
+#   otherwise unknown names. When resolve_initial_references() is unable to 
+#   resolve a name which has been specifically configured (with InitRef),
+#   it constructs a string consisting of the default prefix, a `/' character,
+#   and the name requested. The string is then fed to string_to_object().
+#   For example, if DefaultInitRef is set up like this:
+#      DefaultInitRef = corbaloc::myhost.example.com
+#   A call to resolve_initial_references("MyService") will return the object
+#   reference denoted by `corbaloc::myhost.example.com/MyService'.
+#
+#   The default is empty.
+
+
+############################################################################
+# clientTransportRule
+#
+#    When the client receives an IOR that defines 1 or more ways to contact
+#    the server, the rules in clientTransportRule filter and prioritise
+#    the order in which the transports are used. 
+#
+#    There can be more than one configuration line of this type.
+#    Each line adds one rule to the selection process. The rules are applied
+#    in the order they are defined. The relative positions of the rules define
+#    the relative priority. The first rule has the highest priority.
+#
+#    The syntax of a rule is as follows:
+#    clientTransportRule =  [^]<address mask>      [action]+
+#
+#        <address mask> can be:
+#            1. localhost            the address is this machine
+#            2. w.x.y.z/m1.m2.m3.m4  IPv4 address with the bits selected by
+#                                    the mask. e.g. 172.16.0.0/255.240.0.0
+#            3. *                    the wildcard that matches any address
+#
+#        <action>+ can be one or more of the following:
+#            1. none              Do not use this address
+#            2. tcp,ssl,unix      Use the 3 transports in the specified order 
+#                                 if any or all of them are available
+#            3. bidir             Any connection to this address should be
+#                                 used bidirectionally.
+#
+#         The optional prefix ^ before <address mask>, if present, causes
+#         the ORB to remove previously declared clientTransportRules from
+#         its internal store before adding the current rule.
+#
+#    By default, no rule is defined. The ORB implicitly uses the following
+#    rule:
+#        clientTransportRule =     *   unix,tcp,ssl
+#    If any rule is specified, no implicit rule will be applied.
+#
+#    Given an IOR, for each of the addresses within it, the ORB matches the
+#    address to the rules. If one is found, the position of the matched rule
+#    and the action is noted. If the action is none, the address is discarded.
+#    If the action does not contain the transport the address is specified for,
+#    e.g. the action is "ssl" but the address is "tcp", the address is 
+#    discarded. Otherwise, the address and action is entered as one of the
+#    candidates to use. Having gone through all the addresses, the candidiates
+#    available are then ordered based on the priority of the matching rules and
+#    used accordingly.
+#
+#    Here are some example usages:
+#
+#    A) Restrict to only contacting server on the same host:
+#           clientTransportRule = localhost      unix,tcp
+#                               =   *            no%s
>>> DIFF TRUNCATED @ 16K






More information about the Openembedded-commits mailing list