Download JAR files tagged by functionality with all dependencies

iServe Integrated Engine provides a complete an integrated local version of iServe to be used within Java Applications. This module provides integrated programmatic access for the deployment and interaction with iServe engines. iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities.

iServe is what we refer to as service warehouse which unifies service publication, analysis, and discovery through the use of lightweight semantics as well as advanced discovery and analytic capabilities. iServe provides the typical features of service registries and additional functionality that exploits service descriptions, service annotations and further data gathered and derived from the analysis of these descriptions, data crawled from the Web, periodic monitoring and user activities. iServe builds upon lessons learnt from research and development on the Web and on service discovery algorithms to provide a generic semantic service registry able to support advanced discovery over both Web APIs and WSDL services described using heterogeneous formalisms.

GroupDocs.Total for Cloud is a suite of RESTful APIs that allows developers to seamlessly add powerful document collaboration functionality to their web/mobile applications or sites. With GroupDocs.Total, you can enable end users to view, collaboratively annotate, compare, convert, e-sign, assemble and securely share over 50 document and image types (including PDF and Microsoft Office) on the web, all without having to install any 3rd-party office software or browser plugins. With this SDK, you can easily customize and integrate GroupDocs’ document collaboration tools into your web or mobile Java application.

Scala classes to allow more elegant use of Multiverse from Scala. Atm the functionality is quite limited since not a lot of effort was put in the Scala integration. For the 0.6 release Multiverse should be able to work with in Scala written transactional objects configured with the Multiverse annotations. So that would reduce the need for this library, although in Scala they want to have special Scala 'interfaces' that provide some syntactic sugar to use java collections in Scala. So this module would be the good location for that. If anyone would like to help improving the Multiverse/Scala integration, please don't hesitate to join.

This subproject is an extension of the Struts tag library. Each JSP custom tag in this library is a subclass of an associated tag in the Struts tag library. One difference is that this tag library does not use "rtexprvalues", it uses the expression evaluation engine in the Jakarta Taglibs implementation of the JSP Standard Tag Library (version 1.0) to evaluate attribute values. In addition, some of the Struts tags were not ported to this library, as it was determined that their functionality was entirely supplied by the JSTL. These particular Struts tags, and the reason for their non-porting will be described in the documentation for this library. In order to fully understand the correct utilization of this library, you must understand the use and operation of the Struts tag library, and the use and operation of the JavaServer Pages Standard Tag Library (hereafter called the "JSTL"), along with the expression language (sometimes called the "EL") used for evaluating attribute values.

This is a fork of jfreechart. The purpose is to the build it with the Java module sytem and Java 17. This to be able to use it in building java applications with reduced runtimes. Three servlet classes have been removed as they depended on the automatic module servlet.api. No functionality has beed added. All credit to the original project. Introduzing the module system has broken the unit tests. Everything seems to work as expected though. If you stumble upon this, then it might be useful if you need to use jfreechart in a Java module application. This project will not be maintained though. It looks like jfreechart is adopting the module system and that it might be released soon. jfreechart with Java 11 and modules for java fx applications was recently released. JFreeChart is a class library, written in Java, for generating charts. Utilising the Java2D API, it supports a wide range of chart types including bar charts, pie charts, line charts, XY-plots, time series plots, Sankey charts and more.

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

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 -Dpackaging=jar -Dfile=path/to/sapjco3.jar (b) mvn deploy:deploy-file -DrepositoryId=[your.repo.id] -DgroupId=org.hibersap -DartifactId=sapjco3 -Dversion=3.0 -Dpackaging=jar -Dfile=sapjco3.jar