summaryrefslogtreecommitdiff
path: root/bridges/test/java_uno/nativethreadpool/readme
blob: c137ed162372ea7e9108d3674e5da5f108a07002 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
#*************************************************************************
#
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
# 
# Copyright 2000, 2010 Oracle and/or its affiliates.
#
# OpenOffice.org - a multi-platform office productivity suite
#
# This file is part of OpenOffice.org.
#
# OpenOffice.org is free software: you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License version 3
# only, as published by the Free Software Foundation.
#
# OpenOffice.org is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU Lesser General Public License version 3 for more details
# (a copy is included in the LICENSE file that accompanied this code).
#
# You should have received a copy of the GNU Lesser General Public License
# version 3 along with OpenOffice.org.  If not, see
# <http://www.openoffice.org/license.html>
# for a copy of the LGPLv3 License.
#
#*************************************************************************

Test that a Java URP bridge started in a native process uses the same thread
pool as a C++ URP bridge.  This test currently only works on Linux Intel.

There are two processes involved.  The client starts as a native process.  It
first loads a Java component (Relay) via the in-process JNI bridge, which in
turn starts to accept incomming URP connections.  The native part of the client
then connects to the server, retrieves a thread-local token from it, and checks
the token for correctness.  The server simply waits for a connection from the
native part of the client, creates a connection to the Java part of the client,
and routes all requests from the native part of the client to the Java part of
the client.  The Java part of the client in turn uses the in-process JNI bridge
to obtain the thread-local token.