Menu

[r835]: / trunk / php-java-bridge / debian / control  Maximize  Restore  History

Download this file

122 lines (111 with data), 5.8 kB

  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
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
Source: php-java-bridge
Section: web
Priority: optional
Maintainer: Andre Felipe Machado <andremachado@techforce.com.br>
Build-Depends: debhelper (>= 5), libncurses5-dev (>= 5.5-2 ), libselinux1-dev (>= 1.30 ), libsepol1-dev (>= 1.12.24 ), php5-dev (>= 5.1.0 ) , automake (>= 1.6.3 ) | automake1.7 | automake1.8 | automake1.9, sun-java6-jdk (>= 1 ), locales (>= 2.3.6.ds1-4 ), gcc (>= 3.2 ), make (>= 1 ), liblucene-java, libitext-java, dpatch, libtomcat5.5-java, libaprutil1-dev, libapr1-dev, libtcnative-1, php-pear
Standards-Version: 3.8.0
XBS-Homepage: http://php-java-bridge.sourceforge.net
Package: php-java-bridge
Architecture: any
Depends: ${shlibs:Depends}, sun-java6-jre, liblucene-java, libitext-java, php5-cli, php5-cgi, libaprutil1, libapr1, libtcnative-1
Conflicts: php-java-bridge-j2ee
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package installs C implementation as php modules.
The bridge C implementation is deprecated and unmaintained.
It is kept here for historical purposes.
You must modify your installation to use the J2EE version
as soon as possible.
Package: php-java-bridge-j2ee
Architecture: all
Depends: sun-java6-jre, tomcat5.5, liblucene-java, libitext-java, libapache2-mod-jk, php5-cli, php5-cgi, libaprutil1, libapr1, libtcnative-1
Conflicts: php-java-bridge
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package installs the bridge J2EE server
implementation.
Package: php-java-bridge-docs
Architecture: all
Depends:
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package installs user documentation.
Package: php-java-bridge-j2ee-docs
Architecture: all
Depends:
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package installs J2EE server user documentation.
Package: php-java-bridge-devel
Architecture: all
Depends: sun-java6-jdk, liblucene-java, libitext-java, php-java-bridge | php-java-bridge-j2ee
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package Contains the development documentation.
Also the development files needed to create java applications
with embedded PHP scripts.
Package: php-java-bridge-j2ee-selinux
Architecture: all
Depends: sun-java6-jre, tomcat5.5, liblucene-java, libitext-java, php-java-bridge-j2ee
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm security
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package installs the bridge J2EE server
SE Linux rules contained in the package devel,
examples/security/module directory.
This package works only for tomcat5.5 and SELinux default policy.
Other J2EE server or policy should compile and install from your
modified source.
Package: php-java-bridge-selinux
Architecture: all
Depends: sun-java6-jre, tomcat5.5, liblucene-java, libitext-java, php-java-bridge
Description: XML-based net connection protocol between PHP-Java / ECMA 335 vm security
The PHP/Java Bridge is an optimized, XML-based network
protocol which can be used to connect a native script
engine with a Java or ECMA 335 virtual machine.
It is more than 50 times faster than local RPC via SOAP,
uses less resources on the web-server side and it is faster
and more reliable than a communication via the Java Native
Interface.
This Debian package installs the bridge deprecated C version
SE Linux rules contained in the package devel,
examples/security/module directory.
The bridge C implementation is deprecated and unmaintained.
It is kept here for historical purposes.
You must modify your installation to use the J2EE version
as soon as possible.
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.