java-platform | modular expansion of the java development platform | Object-Relational Mapping library

 by   xiangxik Java Version: Current License: Apache-2.0

kandi X-RAY | java-platform Summary

kandi X-RAY | java-platform Summary

java-platform is a Java library typically used in Utilities, Object-Relational Mapping, Spring Boot, Spring, Hibernate, JPA applications. java-platform has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

此工程不更新了,请移步到最新的工程 ,Based on servlet3.1, the realization of modular expansion of the java development platform, using spring mvc, spring-jpa, spring-data, querydsl, shiro, fastjson, beetl, infinispan, redis and other open source technologies. 基于servlet3.1,实现模块化扩展的java开发平台,采用spring, spring mvc, jpa, spring data, querydsl, shiro, fastjson, beetl, infinispan, redis等开源技术。

            kandi-support Support

              java-platform has a low active ecosystem.
              It has 25 star(s) with 27 fork(s). There are 7 watchers for this library.
              It had no major release in the last 6 months.
              There are 2 open issues and 0 have been closed. On average issues are closed in 1582 days. There are no pull requests.
              It has a neutral sentiment in the developer community.
              The latest version of java-platform is current.

            kandi-Quality Quality

              java-platform has 0 bugs and 0 code smells.

            kandi-Security Security

              java-platform has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              java-platform code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              java-platform is licensed under the Apache-2.0 License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              java-platform releases are not available. You will need to build from source code and install.
              Build file is available. You can build the component from source.
              java-platform saves you 12397 person hours of effort in developing the same functionality from scratch.
              It has 24988 lines of code, 1908 functions and 427 files.
              It has medium code complexity. Code complexity directly impacts maintainability of the code.

            Top functions reviewed by kandi - BETA

            kandi has reviewed java-platform and discovered the below as its top functions. This is intended to give you an instant insight into java-platform implemented functionality, and help decide if they suit your requirements.
            • Initialize the application
            • Inits the application
            • Initialize extension
            • Find application
            • Submit a payment to view
            • Method used to calculate fee
            • Upload an image
            • Zoom an image to the destination file
            • Jackson entity manager factory bean
            • The DruidDataSource bean
            • Writes the JSON representation of the node
            • Gets all configurations
            • Test pipeline
            • Test for pipelined shards
            • Resolves the filter parameter
            • Writes the object to the specified serializer
            • Implements serialization
            • Test sharded JedJedPool
            • Upload a multipart file
            • Test pipelined shard pool
            • Get an OAuth user
            • Writes the given object to the given serializer
            • Creates a new entity
            • Handle the request
            • Get an Oauth user
            • Returns the parameter map to be used as parameter
            Get all kandi verified functions for this library.

            java-platform Key Features

            No Key Features are available at this moment for java-platform.

            java-platform Examples and Code Snippets

            No Code Snippets are available at this moment for java-platform.

            Community Discussions


            Why is Swing supported in newer JavaSE versions, but not JavaFX?
            Asked 2020-Jul-30 at 03:14

            I find JavaFX from my perspective more modern and better to use than Swing.

            I read a document about the future of JavaFX written by an Oracle employee and came across a sentence:

            Oracle is reaffirming that Swing and AWT remain core Java SE technologies to Oracle across all Java SE releases and support timelines.

            Why is Swing supported in newer JavaSE versions, but not JavaFX?



            Answered 2020-Jul-30 at 03:14

            That is a business question.

            One answer is that they wanted to be able to separate the JavaFX release cycle from the main Java SE release cycle. Though as it turns out JavaFX is following the new Java SE release cadence.

            A second answer is that separating them possibly makes project governance simpler.

            But why JavaFX and not Swing?

            Again, business reasons:

            • JavaFX is perceived as more "niche" than Swing is. So splitting it out is perceived as more acceptable.

            • Swing (and AWT) are widely used technologies in old projects. And by old, I mean "mature" / "legacy" projects that have been around for over 20 years. Separating Swing is more likely to break more old projects.

              Major changes that "break" old customer code or practices are bad for Oracle's business model. They annoy corporate customers who pay substantial Java license fees, who might be considering a "strategic" switch to some other language.

            • Swing (and AWT) are not under active development, and hence they won't normally present such a drag on the main Java SE schedule as JavaFX may do.

            Anyway, this is all moot. The decision to split out JavaFX and not Swing was made years ago. It happened. Live with it.



            Netbeans 11.3 "Cannot perform Show Javadoc here"
            Asked 2020-Apr-13 at 20:01

            Showing Javadoc for standard libraries (java.base, ...) is working fine in my setup.

            But including Javadoc for additional libraries fails all the time. I am looking for a hint, what can be done to fix this problem or to get more output for the root cause of this problem.

            I have the following source code:



            Answered 2020-Apr-13 at 19:22

            TLDR: I experienced similar problems to you, but there is a fairly simple workaround:

            • Download and unzip the source of the Fazecast code.
            • In NetBeans Use Tools > Library Manager to reference the locally unzipped source.

            Here are the details:

            • Go to and select the option to download the zip file, as shown in the top right of the screen.
            • The downloaded file is named Unzip that. The *.java source files for the project will be in the unzipped directory ...\Fazecast-jSerialComm-v2.6.1-0-gf3d1e89\Fazecast-jSerialComm-f3d1e89\src\main\java\com\fazecast\jSerialComm.
            • In NetBeans select Tools > Library Manager then click New Library... to create an entry for Fazecast. Then, for that new entry:
              • Click the Classpath tab and click the Add JAR/Folder... button, and navigate to your download of jSerialComm-2.6.1.jar.
              • Click the Sources tab and navigate to the parent directory of the com.fazecast package in the unzipped source directory. In my case this was D:\Downloads\FazecastJSerialComm\Fazecast-jSerialComm-v2.6.1-0-gf3d1e89\Fazecast-jSerialComm-f3d1e89\src\main\java
              • It's counterintuitive, but you don't need to enter anything on the Javadoc tab!

            Once you have done that, close and reopen your source file that's calling Fazecast methods and the javadoc should work. Here's an example for SerialPort.getCommPorts(), where I inserted HELLO WORLD!!! in the javadoc of that method to demonstrate that the local source was being accessed:


            • My environment was Windows 10, NetBeans 11.3 and JDK 14, and I created a simple Ant project.
            • You could open an issue report with Fazecast on the issue of not being able to access the online javadocs from NetBeans, since I don't think that is a NetBeans issue. You could also ask them to consider providing a downloadable javadoc file for jSerialComm.
            • An additional benefit of linking to the Fazecast source in NetBeans is that you can open their code by clicking the Open source in editor icon in the javadoc window, as shown in the screen shot above. Navigate > Go to Source or CTRL + Shift + B also work if the cursor is on a Fazecast method.



            How to use gradle BoM with annotation processor?
            Asked 2020-Mar-02 at 15:07

            I’m trying to define all my dependencies in a bill of materials (BoM) platform module so the other modules in my multi-module project can use the same versions. All works fine except the kapt dependencies. In those I get this error:



            Answered 2020-Mar-02 at 15:07

            you are missing kapt platform(project(':bom'))

            kapt doesn't include dependencies from implementation, so it doesn't include the platform either



            Parent gradle module with java-platform plugin
            Asked 2019-Dec-15 at 16:53

            I have the following build.gradle file:



            Answered 2019-Dec-15 at 16:50

            publications must be inside the publishing block. And you can't use from since your project isn't a Java project, but a platform. So it should be



            How to share common test dependency version in Gradle?
            Asked 2019-Nov-19 at 13:52

            I'm following this Gradle User Guid with kotlin DSL, trying to make sub projects to use the dependency version specified in root project. Here is part of the root build.gradle.kts:



            Answered 2019-Nov-19 at 13:52

            As answered in the comments already, you are missing a reference to the platform in your subproject:



   Received fatal alert: handshake_failure inside docker container
            Asked 2019-May-26 at 11:36

            I'm running a local test against a remote endpoint with the following code:



            Answered 2019-May-17 at 17:46

            "Handshake failure" often means there is no overlap between the server's TLS level (e.g. TLS1.2) and cipher suites, and what your WebSphere can handle.

            I'd run a test like against the server, then look at your QoP settings in WebSphere Security > SSL certificate and key management > SSL configurations

            java.lang.RuntimeException: Received fatal alert: handshake_failure



            Publish BOM (as pom.xml) using gradle plugin java-platform
            Asked 2019-Apr-16 at 10:24

            I am setting up a project specific BOM that will "inherit" definitions from other BOMs (available as pom.xml) and also define own managed dependendies.

            I tried the following (as stated in the java-platform docs) in my build.gradle.kts:



            Answered 2019-Apr-16 at 10:24

            You are defining the BOM as a constraint, but that is most likely not what you want to do. A constraint on a platform will just say that if that dependency enters the graph elsewhere it should use the platform part of it and the version recommendation from the constraint.

            If you expect that constraints of that BOM to be visible to the consumers of your platform, then you need to add the BOM as a platform dependency by doing something like:



            Gradle java-platform plugin and platform definition
            Asked 2019-Feb-13 at 10:06

            I'm trying to use the java-platform plugin to share dependency constraints in a multi-module project. What I would like to do is set up a module named platform which I can import using platform(project(":platform")) in other modules. Additionally I would like to import a BOM into my platform project using platform("group-id:of-the-bom:and-version").

            An example is the following structure:



            Answered 2019-Feb-13 at 10:06

            Importing a BOM in Gradle means that you want to depend on the BOM to get its provided constraints applied.

            What you add by default to a platform are constraints. But constraints only appear in a graph if and only if there is a matching dependency declaration. Also constraints only inform about the module targeted. They never bring any transitive information.

            So what you need to do is declare that your platform project depends on the BOM. It will then export its constraints as expected.



            Confusion about TLS 1.2 and jdk version
            Asked 2018-Jul-09 at 08:29

            I understand that TLS 1.2 isn't supported by JDK 6. But I'm a little confused as to what this means exactly.

            In my project, I've set my apache httpclient to use TLSv1.2 like this. My project is compiled with mvn which uses jdk 1.6 to run. Maven -source and -target are set to 1.6.

            I use jdk1.7/bin/java to call my application. And I see that my connection is using TLSv1.2.

            So does this mean that the word "supported" is referring to the JVM version that is running the application and not the JVM that compiled the project?


            Apache httpclient’s TLS version is not bound by JDK version?



            Answered 2018-Jul-09 at 08:27

            Your link Diagnosing TLS, SSL, and HTTPS doesn't provide perfect information, but it's not bad. It suggests reading the JSSE Reference Guides (and we will all suggest that) where are explained "is supported" and "is implemented" features. More or less clearly unfortunately. Remember that JSSE was designed to be pluggable with other security implementations, this means that the runtime can decide a couple of things and you can see different behaviours.



            Jarsigner issue with jre/lib/ext removal
            Asked 2017-Dec-03 at 12:35

            According to this article :

            the jre/lib/ext removed in Java 9.

            My problem is that I am using Jarsigner which in previous Java versions found my provider jar in the jre/lib/ext folder.



            Answered 2017-Nov-23 at 02:10

            The changes to the installed JDK/JRE image brings along runtime images which consists of directories including -

            conf — contains .properties, .policy, and other kinds of files intended to be edited by developers, deployers, and end users. These files were formerly found in the lib directory or its subdirectories.

            The file within JDK9 (located under .../Home/conf/security) lists out the SunPKCS11 provider amongst the list of default providers


            Community Discussions, Code Snippets contain sources that include Stack Exchange Network


            No vulnerabilities reported

            Install java-platform

            You can download it from GitHub.
            You can use java-platform like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the java-platform component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer For Gradle installation, please refer .


            For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • HTTPS


          • CLI

            gh repo clone xiangxik/java-platform

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Consider Popular Object-Relational Mapping Libraries

            Try Top Libraries by xiangxik


            by xiangxikJavaScript


            by xiangxikJava


            by xiangxikJava


            by xiangxikHTML