Download JAR files tagged by server with all dependencies

Avalon Excalibur's DataSource package allows you to manage pooled connections in one of two ways. You can have the package handle it for you, or you can use a J2EE server's DataSource management. It provides the same kind of access regardless of which method you choose--since they are obtained through Avalon's Component Manager infrastructure. The DataSource package requires that you load the necessary driver classes at init time, but it will take care of all necessary issues from there.

The Config project is home to Sakai configuration and localization files. Config includes several versions of sakai.properties, a text file containing a series of key/value pairs that provide a convenient mechanism for defining a variety of configuration options for Sakai tools, services, supporting database and UI-related text such as copyright statement, institutional name, server name, etc. Settings in sakai.properties are read on startup; thus changes to sakai.properties only take effect after you restart Sakai's servlet container (typically Apache Tomcat).

This feature provides a gateway between mobile, cloud, and web clients and z/OS back-end systems such as CICS Transaction Server, IMS, and batch applications. It provides RESTful APIs and enables you to route HTTP requests to remote REST endpoints. It also accepts and returns JSON payloads and communicates with back-end systems by providing a data transformation service that converts JSON payloads to/from byte arrays consumable by z/OS native-language applications written in Cobol, PL/I, and C.

There are two ways to use OSGi in server-side[1]. In Carbon, what we have done is, embedding an OSGi framework inside a servlet container. So BridgeServlet delegates all the request from the servlet container to the HttpServiceServlet registered by the http.bridge bundle. This is required only when Carbon is running inside a webapp. There is a possibility to embed an HTTP server(ex. jetty) inside equinox and start a server with all our carbon bundles. This is same as running carbon inside spring DM server. For this scenario, we do not need org.wso2.carbon.http.bridge bundles and the org.wso2.carbon.bridge extension bundle. 1. http://eclipse.org/equinox/server/http_quickstart.php

To run all integration tests, you need to set up all the databases: 1) Derby: $ export DERBY_HOME=/path/to/db-derby-10.14.2.0-bin $ cd $DERBY_HOME $ mkdir databases; cd databases $ java -jar $DERBY_HOME/lib/derbyrun.jar server start 2) MS SQL Server (for official and jtds drivers): $ podman run -itd --name pax.jdbc.sqlserver -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=PaxJdbc!(*67' -e 'MSSQL_PID=Express' \ -p 1433:1433 -d mcr.microsoft.com/mssql/server:2022-latest 3) MariaDB: $ podman run --name pax.jdbc.mariadb -p 3306:3306 -e MYSQL_ROOT_PASSWORD=paxjdbc -d mariadb 4) MySQL: $ podman run --name pax.jdbc.mysql -p 3307:3306 -e MYSQL_ROOT_PASSWORD=paxjdbc -d mysql 5) PostgreSQL: $ podman run --name pax.jdbc.postgresql -e POSTGRES_USER=paxjdbc -e POSTGRES_PASSWORD=paxjdbc -p 5432:5432 -d postgres:latest 6) Oracle (a bit unofficial): $ podman run -itd --name pax.jdbc.oracle -p 1521:1521 --privileged=true oracleinanutshell/oracle-xe-11g