jmetzner 02/04/14 15:49:38
Added: java/scratchpad/webapp/WEB-INF/openorb/config OpenORB.dtd
OpenORB.xml default.xml
Log:
Workaround for Tomcat (set the openorb.home System Property)
Revision Changes Path
1.1
xml-xindice/java/scratchpad/webapp/WEB-INF/openorb/config/OpenORB.dtd
Index: OpenORB.dtd
===================================================================
<!--
Redistribution and use of this software and associated
documentation ("Software"), with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain copyright statements
and notices. Redistributions must also contain a copy of this
document.
2. Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
3. The name "Exolab" must not be used to endorse or promote
products derived from this Software without prior written
permission of Intalio Inc. For written permission, please
contact [EMAIL PROTECTED]
4. Products derived from this Software may not be called "Exolab"
nor may "Exolab" appear in their names without prior written
permission of Intalio Inc. Exolab is a registered trademark of
Intalio Inc.
5. Due credit should be given to the Exolab Project
(http://www.exolab.org/).
THIS SOFTWARE IS PROVIDED BY INTALIO AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL INTALIO OR
ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Copyright 2000 (C) Intalio Inc. All Rights Reserved.
$Id: OpenORB.dtd,v 1.1 2002/04/14 22:49:38 jmetzner Exp $
Date Author Changes
-->
<!--
This is a DTD for the OpenORB config file. It can be used when verifying
OpenORB configurations, but is optional to reference from config files.
When used in public doctypes the public reference:
"-//www.openorb.org//OpenORB Config//EN" may be used.
-->
<!ENTITY % ns "http://www.openorb.org/config/3.0/OpenORB.dtd"; >
<!--
Document root element. Profile gives the ID of the default profile and
may define a base reference for the links within the document.
-->
<!ELEMENT OpenORB (description?,(module|profile)*)>
<!ATTLIST OpenORB
xmlns CDATA #FIXED "%ns;"
profile IDREF "default"
xml:base CDATA #IMPLIED
>
<!--
A module defines a namespace for it's properties
and can have an initializer. It may also import other modules.
-->
<!ELEMENT module (description?,(property|import|propalias)*)>
<!ATTLIST module
xmlns CDATA #FIXED "%ns;"
name ID #REQUIRED
initializer NMTOKEN #IMPLIED
>
<!--
Define a short alias for certain common properites to use on the
command line.
-->
<!ELEMENT propalias EMPTY>
<!ATTLIST propalias
xmlns CDATA #FIXED "%ns;"
name NMTOKEN #REQUIRED
alias NMTOKEN #REQUIRED
>
<!--
The associations element defines default profiles for specific users.
-->
<!ELEMENT associations (association)*>
<!ATTLIST associations
xmlns CDATA #FIXED "%ns;"
>
<!--
If the user.name java system property matches
-->
<!ELEMENT association EMPTY>
<!ATTLIST association
xmlns CDATA #FIXED "%ns;"
user NMTOKENS #REQUIRED
profile IDREF #REQUIRED
>
<!--
Define a property. The actual property name will be prefixed with
"<modulename>." unless the root attribute is true.
-->
<!ELEMENT property (description?)>
<!ATTLIST property
xmlns CDATA #FIXED "%ns;"
name NMTOKEN #REQUIRED
value CDATA "true"
root (true|false) "false"
>
<!--
Import a module or profile. Properties defined within the import statement
will use the module name from the imported module for prefixing.
Modules in this config file, in other config files and in properties files
can be loaded.
When importing a profile or properties from a properties file it is not
possible to define properties as child elements of the import statement,
this results in an error.
Usage examples:
<import module="mod" />
This imports the module with name 'mod' from the current config file.
<import profile="pro" />
This imports the profile 'pro' from the current config
file. Profile imports can be used only by profiles.
<import xlink:href="http://www.myhost.com/openorb/OpenORB.xml#mod"; />
This imports the module/profile named 'mod' from the config file
obtained from the given URL. This, and any other href can import
both modules and profiles, however imported profiles cannot set
properties as child elements.
<import xlink:href="#mod" />
<import xlink:href="../OpenORB.xml#mod" />
Use the base URL of this document. The base URL for this document will
either be a href to the document itself, or whatever is set by the
xml:base attribute of the OpenORB element.
<import xlink:href="resource:/org/openorb/config/OpenORB.xml#mod" />
The resource protocol causes it's file to be loaded using the java
getSystemResource function, loading the file off the classpath.
<import
xlink:href="resource://org.openorb.ReleaseInfo/config/OpenORB.xml#mod" />
<import
xlink:href="resource://org.openorb.ReleaseInfo//org/openorb/config/OpenORB.xml#mod"
/>
This version of the resource protocol uses the getResource funtion on
the Class object named org.openorb.ReleaseInfo to generate the URL for
the target.
<import xlink:href="${openorb.home}config/OpenORB.xml#mod" />
${openorb.home} gets expanded to the URL property setting of
openorb.home, which is generaly "resource:/org/openorb/", and the
remainder of the href is resolved relative to it. Any property value
which has been set before the import can be used in the expansion.
This includes the java system properties, openorb.home and
openorb.config. Any property appearing at position 0 must be a URL
property.
<import xlink:href="${openorb.home}config/${user.name}/OpenORB.xml#mod" />
A variation of the above, here the second property is resolved as a
string.
<import xlink:href="${openorb.config}RMIoverIIOP.xml" />
Import all the modules imported by the default profile in the given
config file. Note that as ${openorb.config} appears at the start of
the href the RMIoverIIOP.xml file will be a URL relative to the
config URL.
<import xlink:href="${user.home}extra.properties" />
Import all the properties contained in the java properties file
"extra.properties" contained in the user's home directory. This style
of import element cannot have property child elements.
<import xlink:href="${user.home}extra.properties#module" />
Import all the properties, prefixing "module." to all the properties
within the file. This import style can have property child elements.
-->
<!ELEMENT import (description?,property*)>
<!ATTLIST import
xmlns CDATA #FIXED "%ns;"
module IDREF #IMPLIED
profile IDREF #IMPLIED
xmlns:xlink CDATA #FIXED "http://www.w3.org/1999/xlink";
xlink:type (simple) #FIXED "simple"
xlink:href CDATA #IMPLIED
>
<!--
Profiles can be selected from the command line and provide entry points
for the configurator.
Profiles may extend preexisting profiles within this config file using
the extends attribute, and within other property files using the
xlink:href
attribute. The allowable hrefs are a subset of those allowed in the import
statement; the target must be a profile and the file must be an xml file.
-->
<!ELEMENT profile (description?,import*)>
<!ATTLIST profile
xmlns CDATA #FIXED "%ns;"
name ID #REQUIRED
extends IDREF #IMPLIED
xmlns:xlink CDATA #FIXED "http://www.w3.org/1999/xlink";
xlink:type (simple) #FIXED "simple"
xlink:href CDATA #IMPLIED
>
<!-- Description of module, profile, property or import -->
<!ELEMENT description (#PCDATA|p)* >
<!ATTLIST description
xmlns CDATA #FIXED "%ns;"
>
<!-- Paragraph mark in description -->
<!ELEMENT p EMPTY>
<!ATTLIST p
xmlns CDATA #FIXED "%ns;"
>
1.1
xml-xindice/java/scratchpad/webapp/WEB-INF/openorb/config/OpenORB.xml
Index: OpenORB.xml
===================================================================
<!-- ================================================================== -->
<!-- = OpenORB XML profile = -->
<!-- = (c) 2000, 2001, Exolab = -->
<!-- ================================================================== -->
<!--
<!DOCTYPE OpenORB
PUBLIC "-//www.openorb.org//OpenORB Config//EN"
"http://www.openorb.org/config/OpenORB.dtd";>
-->
<OpenORB profile="default"
xmlns="http://www.openorb.org/config";
xmlns:xlink="http://www.w3.org/1999/xlink";
>
<description>
This is the default config file, as found in the jar file. It can be
copied into the user's home directory and modified.<p/>
Users are reccomended to modify the corbaloc reference to the
NameService, found in the BasicRefs profile, so that it locates the
name service.
</description>
<!-- ====================================================================
-->
<!-- The user modified profile. This is imported into all the below
-->
<!-- profiles to set some common user modifyable properties
-->
<!-- ====================================================================
-->
<profile name="user-mods" >
<import xlink:href="${openorb.home}config/default.xml#InitRef">
<property name="NameService"
value="corbaloc::[EMAIL PROTECTED]:2001/NameService" />
</import>
</profile>
<!-- ====================================================================
-->
<!-- DEFAULT PROFILE
-->
<!--
-->
<!-- This profile is the default profile used by OpenORB when starting.
-->
<!--
-->
<!-- This profile extends another profile named "default" available
-->
<!-- in the default.xml file. In addition, it provides a way to overload
-->
<!-- the property that defines the CORBA URL to find the Naming Service
-->
<!--
-->
<!-- ====================================================================
-->
<profile name="default"
xlink:href="${openorb.home}config/default.xml#default">
<description>
The default profile loads the POA, iiop and some basic initial references.
</description>
<import profile="user-mods" />
</profile>
<!-- ====================================================================
-->
<!-- Example of a profile which extends another.
-->
<!-- This profile extends the default, and sets debug logging to highest
-->
<!-- level.
-->
<!-- ====================================================================
-->
<profile name="debug" extends="default" >
<description>
Activates debugging mode.
</description>
<import xlink:href="${openorb.home}config/default.xml#openorb" >
<property name="debug" value="5" />
<property name="useStaticThreadGroup" value="true" />
</import>
</profile>
<!-- ====================================================================
-->
<!-- Example of a profile which imports modules.
-->
<!-- This profile activates only the BOA, and not the POA.
-->
<!-- ====================================================================
-->
<profile name="boa-only" >
<description>
This profile uses the BOA instead of the POA.
</description>
<import xlink:href="${openorb.home}config/default.xml#BOA" />
<import xlink:href="${openorb.home}config/default.xml#iiop" />
<import xlink:href="${openorb.home}config/default.xml#BasicRefs" />
<import profile="user-mods" />
</profile>
<!-- ====================================================================
-->
<!-- Activate only the client side ORB. This just extends a profile of
-->
<!-- the same name in the default.xml file.
-->
<!-- ====================================================================
-->
<profile name="client-only"
xlink:href="${openorb.home}config/default.xml#client-only">
<description>
Activates only the client side ORB.
</description>
</profile>
<!-- ====================================================================
-->
<!--
-->
<!-- The following profiles are only used with OpenORB services
-->
<!-- and extensions. If you don't use any services and extensions
-->
<!-- don't take care of them.
-->
<!--
-->
<!-- ====================================================================
-->
<!-- ====================================================================
-->
<!-- TRANSACTION PROFILE
-->
<!--
-->
<!-- This profile must be used for transactional applications. It
-->
<!-- requires the OpenORB OTS service.
-->
<!--
-->
<!-- ====================================================================
-->
<profile name="ots" extends="default">
<description>
The ots profile loads the OTS interceptors required for the
management of distributed transaction. This profile must be used
on server and client sides for transaction applications.
</description>
<import xlink:href="${openorb.home}config/ots.xml#ots" />
</profile>
<!-- ====================================================================
-->
<!-- PERSISTENT PROFILE
-->
<!--
-->
<!-- This profile must be used for persistent applications. It
-->
<!-- requires the OpenORB PSS service.
-->
<!--
-->
<!-- ====================================================================
-->
<profile name="pss" extends="default">
<description>
The pss profile loads the PSS intializer required for persistence
management. This profile must be used on server side when a server
application is using the PSS.
</description>
<import xlink:href="${openorb.home}config/pss.xml#pss" />
</profile>
<!-- ====================================================================
-->
<!-- TRANSACTION & PERSISTENT PROFILE
-->
<!--
-->
<!-- This profile must be used for persistent and transactional
-->
<!-- applications. It requires the OpenORB PSS and OTS services.
-->
<!--
-->
<!-- ====================================================================
-->
<profile name="transactionalpss" extends="default">
<description>
This profile is used for transactional and persistent server
applications. It must be used on the server side only.
</description>
<import xlink:href="${openorb.home}config/ots.xml#ots" />
<import xlink:href="${openorb.home}config/pss.xml#pss" />
</profile>
</OpenORB>
1.1
xml-xindice/java/scratchpad/webapp/WEB-INF/openorb/config/default.xml
Index: default.xml
===================================================================
<!-- ================================================================== -->
<!-- = OpenORB XML profile = -->
<!-- = (c) 2000, Exolab = -->
<!-- ================================================================== -->
<!--
<!DOCTYPE OpenORB
PUBLIC "-//www.openorb.org//OpenORB Config//EN"
"http://www.openorb.org/config/OpenORB.dtd";>
-->
<OpenORB profile="default"
xmlns="http://www.openorb.org/config";
xmlns:xlink="http://www.w3.org/1999/xlink";
>
<description>
This config file contains all the modules available to users of
OpenORB. Users may import modules from this file into their
configuration and modify the properties.
</description>
<!-- ********************************************************** -->
<!-- default modules -->
<!-- ********************************************************** -->
<!-- ********************************* -->
<!-- openorb.server module -->
<!-- ********************************* -->
<module name="openorb.server">
<description>
Properties affecting the orb server side. This module has no
initializer and does not have to be imported.
</description>
<property name="enable" value="true">
<description>
Enable the ORB server side. The server side may be disabled for
a client only orb.
</description>
</property>
<property name="alias" value="">
<description>
The server alias. This is used in persistent references. All
servers listening on the same port, on the same host, with the
same server alias can accept requests to persistent targets
created previous incarnations of the same server.<p/>
The command line alias -ORBSrvName=name can be used rather than
-ORBopenorb.server.name=name, regardless of if this module is
imported.
</description>
</property>
<propalias name="alias" alias="SrvName" />
<property name="maxQueueSize" value="0x7FFFFFFF" >
<description>
Maximum number of incomming requests to queue before replying
with TRANSIENT exceptions.
</description>
</property>
<property name="maxManagerHeldRequests" value="0x7FFFFFFF" >
<description>
Maximum number of requests that an adapter with a manager in the
HOLDING state can hold before incomming requests are replied to
with TRANSIENT exceptions
</description>
</property>
<property name="minThreadPoolSize" value="2">
<description>
Minimum number of active threads in the request thread pool.
The thread pool will never shrink beyond this size.
</description>
</property>
<property name="maxThreadPoolSize" value="10">
<description>
Maximum number of pool threads. The thread pool will never grow
beyond this size.
</description>
</property>
<property name="reapCloseDelay" value="600000">
<description>
Reaper close time in ms. If a channel is unused for at least
this time it will be closed to conserve resources. The thread
pool also has a chance to shrink each time this event occours.
</description>
</property>
<!-- properties not usualy modified by users -->
<property name="serverManagerClass"
value="org.openorb.net.ServerManagerImpl">
<description>
Server manager class. There is no alternative at present.
</description>
</property>
</module>
<!-- ************************* -->
<!-- openorb.client module -->
<!-- ************************* -->
<module name="openorb.client">
<description>
Properties affecting the orb client side. This module has no
initializer and does not have to be imported.
</description>
<property name="reapPauseDelay" value="120000">
<description>
Reaper pause time in ms. If a channel is unused for at least
this time it will be closed to conserve resources.
</description>
</property>
<property name="enable" value="true">
<description>
Enable the client side. Server only orbs are possible however
certain POA functionality will be unavailable.
</description>
</property>
<!-- properties not usualy modified by users -->
<property name="clientManagerClass"
value="org.openorb.net.ClientManagerImpl">
<description>
Client manager class. There is no alternative at present.
</description>
</property>
</module>
<!-- ************************* -->
<!-- openorb.pi module -->
<!-- ************************* -->
<module name="openorb.pi">
<description>
Properties affecting the portable interceptors. There are
currently no alternatives to the defaults for these
properties. This module has no initializer and does not have to be
imported.
</description>
<!-- properties not usualy modified by users -->
<property name="ORBInitInfoClass" value="org.openorb.PI.OpenORBInitInfo"
/>
<property name="ServerManagerClass"
value="org.openorb.PI.SimpleServerManager" />
<property name="ClientManagerClass"
value="org.openorb.PI.SimpleClientManager" />
<property name="IORManagerClass" value="org.openorb.PI.SimpleIORManager"
/>
</module>
<!-- *********************** -->
<!-- openorb module -->
<!-- *********************** -->
<module name="openorb">
<description>
Misc other properties. This module has no initializer and does not
have to be imported.
</description>
<property name="dynany.enable" value="true">
<description>
Enable the use of the DynamicAnyFactory.
</description>
</property>
<property name="kernel.ORBConnectorClass"
value="org.openorb.CORBA.kernel.OpenORBConnector">
<description>
Define the orb connector class. There is currently no
alternative.
</description>
</property>
<property name="defaultInitRef" value="">
<description>
The default initial reference. This is used by
resolve_initial_references when no other specific reference is
available. The default behaviour is to have no default
reference.<p/>
The command line alias -ORBDefaultInitRef=str can be used rather
than -ORBopenorb.defaultInitRef=str, regardless of if this
module is imported.
</description>
</property>
<propalias name="defaultInitRef" alias="DefaultInitRef" />
<!-- debuging properties -->
<property name="debug" value="0">
<description>
Set the orb debug level<p/>
The command line alias -ORBDebug=n can be used rather than
-ORBopenorb.debug=n, regardless of if this module is imported.
</description>
</property>
<propalias name="debug" alias="Debug" />
<property name="useStaticThreadGroup" value="false">
<description>
Use static ThreadGroups for the orb threads. Can be useful to
set to true when debugging the use of multiple orbs used in one
app as it avoids large numbers of thread groups being created.
</description>
</property>
</module>
<!-- ************************** -->
<!-- InitRef module -->
<!-- ************************** -->
<module name="InitRef">
<description>
Module containing default initial references. To add more initial
services import and define properties with unique identifiers.
Example import:<p/>
<![CDATA[<import
xlink:href="${openorb.home}config/default.xml#InitRef">]]>
<![CDATA[ <property name="NameService" value="corbaloc::[EMAIL
PROTECTED]/NameService" />]]>
<![CDATA[</import>]]><p/>
Also see the defaultInitRef property, defined in the openorb
module.
</description>
<propertyset/>
</module>
<!-- ********************** -->
<!-- compiler module -->
<!-- ********************** -->
<module name="compiler" >
<propertyset prefix="idl" >
<description>
The compiler module defines a single property set which allows
additional include directories for the openorb compiler. Each
extra idl include directory property starts with idl and must
have a unique extension. Example of import statement, adding an
include: <p/>
<![CDATA[<import
xlink:href="${openorb.home}config/default.xml#compiler">]]>
<![CDATA[ <property name="idl.xxx" value="URL" />]]>
<![CDATA[</import>]]>
<p/>
The include dir "${openorb.home}idl" is always present in the
compiler include path, it always appears last in the include
list.
</description>
</propertyset>
</module>
<!-- *********************** -->
<!-- BOA module -->
<!-- *********************** -->
<module name="BOA" initializer="org.openorb.adapter.boa.BOAInitializer" >
<description>
The BOA module. Import this module to use the BOA.
</description>
</module>
<!-- ************************ -->
<!-- POA module -->
<!-- ************************ -->
<module name="POA" initializer="org.openorb.adapter.poa.POAInitializer">
<description>
The POA module. Import this module to use the POA.
</description>
</module>
<!-- ************************* -->
<!-- Forward Adapter module -->
<!-- ************************* -->
<module name="CorbalocService"
initializer="org.openorb.adapter.fwd.ForwardInitializer" >
<description>
The corbaloc adapter module. When loaded it is possible to
resolve corbaloc style addresses if they are registered.
</description>
</module>
<module name="ForwardAdapter" >
<description>
The ForwardAdapter module has been renamed CorbalocService.
</description>
<import module="CorbalocService" />
</module>
<!-- *********************************** -->
<!-- Default Corbaloc service -->
<!-- *********************************** -->
<profile name="DefaultCorbalocService">
<description>
This profile loads the CorbalocService module, and sets the port
number in iiop to 683, the default port.
</description>
<import module="CorbalocAdapter" />
<import module="iiop" >
<property name="port" value="683" />
</import>
</profile>
<profile name="InitialReferencesService">
<description>
Initial references service has been renamed CorbalocService.
</description>
<import module="DefaultCorbalocService" />
</profile>
<!-- **************************** -->
<!-- BasicRefs profile -->
<!-- **************************** -->
<profile name="BasicRefs">
<description>
Basic initial references. Just set the default initial reference.
</description>
<import module="openorb" >
<property name="defaultInitRef"
value="corbaname:rir:#InitialReferences" />
</import>
</profile>
<!-- *********************** -->
<!-- iiop module -->
<!-- *********************** -->
<module name="iiop" initializer="org.openorb.iiop.IIOPProtocolInitializer">
<description>
The IIOP protocol is the basic interoperability protocol between
all orbs. It should be included in all profiles.
</description>
<!-- Properties controlling what endpoints are published in IORs. -->
<property name="hostname" value="">
<description>
Hostname to publish in IORs. If empty string or unspecified the
published hostname will be determined by the publishIP setting.
</description>
</property>
<property name="publishIP" value="auto">
<description>
Publish IP address in IORs instead of hostname. The default
setting of 'auto' will publish the IP address if the hostname is
not a fqdn (does not contain a . ). If true the IP address is
always used. For all other values the hostname is used. If the
hostname property is set this overrides this setting.
</description>
</property>
<propertyset prefix="alternateAddr">
<description>
This property set defines alternate IIOP endpoints which are
published in IORs. These are generaly servers on different targets.
Each defined alternative should have a unique prefix.
</description>
</propertyset>
<!-- properties controlling the incomming server side. -->
<property name="listenAddress" value="0.0.0.0">
<description>
Address to listen on on multi-homed host. Defaults to 0.0.0.0,
all local addresses.
</description>
</property>
<property name="port" value="0">
<description>
Port for the iiop transport to listen on. Defaults to 0, any
available port.<p/>
Command line alias Port is available.
</description>
</property>
<propalias name="port" alias="Port" />
<!-- properties controlling bidirectional iiop -->
<property name="allowBidir" value="true">
<description>
Allow bidirectional IIOP. For BiDirectional IIOP to be available
at all this property must be set to true. It is set to true by
default, since activating BiDirectional IIOP requires setting
server and client side policies.
</description>
</property>
<property name="biDirOnlyServer" value="false">
<description>
When both allowBiDir and biDirOnlyServer are true, the server side
orb will not listen for incomming requests. All incomming requests
must be recieved over a bidirectional channel.
</description>
</property>
<!-- Properties not usualy modified by users -->
<property name="CDRInputStreamClass"
value="org.openorb.iiop.CDRInputStream">
<description>
CDRInputStream class. This is modified by the RMIoverIIOP
module.
</description>
</property>
<property name="CDROutputStreamClass"
value="org.openorb.iiop.CDROutputStream">
<description>
CDRInputStream class. This is modified by the RMIoverIIOP
module.
</description>
</property>
<property name="IIOPTransportServerInitializerClass"
value="org.openorb.iiop.IIOPTransportServerInitializer">
<description>
Server transport. This is modified by security services.
</description>
</property>
<property name="TransportClientInitializerClass"
value="org.openorb.iiop.IIOPTransportClientInitializer">
<description>
Client transport. This is modified by security services.
</description>
</property>
</module>
<!-- ********************************************************** -->
<!-- Default profiles -->
<!-- ********************************************************** -->
<profile name="default" >
<description>
The default profile load the POA, iiop and some basic initial
references.
</description>
<import module="POA" />
<import module="iiop" />
<import profile="BasicRefs" />
</profile>
<profile name="boa-only" >
<description>
This profile uses the BOA instead of the POA.
</description>
<import module="BOA" />
<import module="iiop" />
<import module="BasicRefs" />
</profile>
<profile name="client-only">
<description>
This profile enables only the client side orb.
</description>
<import module="openorb.server">
<property name="enable" value="false"/>
</import>
<import module="iiop" />
<import module="BasicRefs" />
</profile>
</OpenORB>
