Download JAR files tagged by connector with all dependencies

Magja is a java connector for access the Magento API (http://www.magentocommerce.com/support/magento_core_api), with that you will be able to manipulate the magento products (images include), categories, customers, orders, and much more. Just you have to do its create a properties file with the connection parameters for the magento installation. For more information visit the project page.

Customized version of the ActiveMQ Maven Plugin that registers publishable transport connector addresses in the Maven properties so that dynamic allocation of ports can easily be achieved. This project provides a port of the updates to the currently-released ActiveMQ version 5.10.0; the updates are expected to be released with ActiveMQ version 5.12.0, after which this version will no longer be maintained. See also AMQ-5499 (https://issues.apache.org/jira/browse/AMQ-5499).

Interfaces to be implemented by Domains, Connectors and Events which handle intatiation of Services and Proxies, classes for registration of bundles and services, classes for localization, classes that save connector properties (Persistence) and finally classes that enable the web application to have access to OSGI bundles. This bundle contains only the model and interface descriptions of all those services. In theory someone can take only a minor number of openengsb bundles, the api and create the rest of the system on his own.

Magja is a java connector for access the Magento API (http://www.magentocommerce.com/support/magento_core_api), with that you will be able to manipulate the magento products (images include), categories, customers, orders, and much more. Just you have to do its create a properties file with the connection parameters for the magento installation. For more information visit the project page.

Interfaces to be implemented by Domains, Connectors and Events which handle intatiation of Services and Proxies, classes for registration of bundles and services, classes for localization, classes that save connector properties (Persistence) and finally classes that enable the web application to have access to OSGI bundles. This bundle contains only the model and interface descriptions of all those services. In theory someone can take only a minor number of openengsb bundles, the api and create the rest of the system on his own.

A secure, REST administrative connector that can be used locally or remotely using any Java developer kit. This connector enables remote access from a Java client or directly through an HTTPS call. The administrator and reader roles protect the connector. The connector requires TLS to keep the communication confidential. The HTTPS port used by the connector is defined through the default HTTP endpoint. This feature supersedes the restConnector-1.0 feature. It enables the REST handler configuration APIs. When this feature is combined with features supporting configuration validation, the corresponding REST handler validation APIs are enabled.

The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system. It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java to SAP System as well as SAP System to Java calls. - All SAP Connectors are licensed without additional license fees as part of the respective solution or component license. However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems / SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed. - The redistribution of any connector is not allowed. - All SAP users accessing application functionality through the relevant connector are required to be licensed under a respective solution or component license. To use the SAP JCo with the jco-jar project, you need to either install the SAP JCo jar downloaded from SAP to your local Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b): (a) mvn install:install-file -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=com.github.easonjim -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.11 -Dpackaging=jar -Dfile=path/to/sapjco3.jar

The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system. It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java to SAP System as well as SAP System to Java calls. - All SAP Connectors are licensed without additional license fees as part of the respective solution or component license. However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems / SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed. - The redistribution of any connector is not allowed. - All SAP users accessing application functionality through the relevant connector are required to be licensed under a respective solution or component license. To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b): (a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=com.sap.conn.jco.sapjco3 -Dversion=3.0.15 -Dpackaging=jar -Dfile=sapjco3.jar

The SAP Java Connector (SAP JCo) is a toolkit that allows a Java application to communicate with any SAP system. It combines an easy to use API with unprecedented flexibility and performance. The package supports both, Java to SAP System as well as SAP System to Java calls. - All SAP Connectors are licensed without additional license fees as part of the respective solution or component license. However, please note that each connector may be used only for connecting external (non-SAP) applications to SAP Systems / SAP Solutions. Scenarios, in which two external (non-SAP) applications are integrated via an SAP Connector, are not allowed. - The redistribution of any connector is not allowed. - All SAP users accessing application functionality through the relevant connector are required to be licensed under a respective solution or component license. To use the SAP JCo with the Hibersap project, you need to either install the SAP JCo jar downloaded from SAP to your local Maven repository (variant a) or deploy it to e.g. an enterprise Maven repository like Nexus or Artifactory (variant b): (a) mvn install:install-file -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0.12 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0.12 -Dpackaging=jar -Dfile=sapjco3.jar