Description
JWt is a Java library for developing web applications. It provides a pure
Java component-driven approach to building web applications,
and renders either using Ajax or plain HTML.
Unlike JSF, there is no concept of a page and no split between page
"views" and reusable "components", making reuse unpractical. Instead,
everything is a widget that can be resued in other widgets.
For more information, see the homepage.
jwt alternatives and similar libraries
Based on the "Web Frameworks" category.
Alternatively, view jwt alternatives based on common mentions on social networks and blogs.
-
Vaadin
Vaadin 6, 7, 8 is a Java framework for modern Java web applications. -
Ninja
Ninja is a full stack web framework for Java. Rock solid, fast and super productive. -
Bootique
Bootique is a minimally opinionated platform for modern runnable Java apps. -
Takes
True Object-Oriented Java Web Framework without NULLs, Static Methods, Annotations, and Mutable Objects -
ZK
ZK is a highly productive Java framework for building amazing enterprise web and mobile applications -
Firefly
Firefly is an asynchronous web framework for rapid development of high-performance web application. -
mangoo I/O
An Intuitive, Lightweight, High Performance Full Stack Java Web Framework. -
Free enterprise Java CMS
Java CMS engine. Host and develop multiple websites inside a single instance through the GUI and benefit from features like A/B testing, affiliate tracking tools, and a high performance template engine with CSS stylesheets processing & scripts minification.
Collect and Analyze Billions of Data Points in Real Time
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of jwt or a related project?
Popular Comparisons
README
What is JWt ?
JWt is a Java library for developing web applications. It provides a pure Java component-driven approach to building web applications, and renders either using Ajax or plain HTML.
Unlike JSF, there is no concept of a page and no split between page "views" and reusable "components", making reuse unpractical. Instead, everything is a widget that can be resued in other widgets.
For more information, see the homepage.
Dependencies
The library requires a Servlet 2.5 or 3.0 container. When deployed in a servlet 3.0 container, it is able to use asynchronous I/O functionality to improve scalability when using server push features.
If you want to use the PDF rendering support (the WPdfImage and WPdfRenderer classes), then you also need to add PdfJet[http://pdfjet.com/] to your project.
Building
It can be as simple as:
ant
Demos, examples
The homepage contains various examples.
Maven
The ant build file has a separate target to generate maven pom files:
ant mvn
To install the two artifacts in your local repository, do:
mvn install:install-file -Dfile=dist/jwt-3.3.2.jar -DpomFile=jwt-3.3.2.pom
mvn install:install-file -Dfile=dist/jwt-auth-3.3.2.jar -DpomFile=jwt-auth-3.3.2.pom
The corresponding dependency blocks are:
<dependency>
<groupId>eu.webtoolkit</groupId>
<artifactId>jwt</artifactId>
<version>3.3.2</version>
</dependency>
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.5</version>
</dependency>
There are a number of optional dependencies for JWt, needed only depending on what features you use
<!-- optional, for JWT Auth -->
<dependency>
<groupId>eu.webtoolkit</groupId>
<artifactId>jwt-auth</artifactId>
<version>3.3.2</version>
</dependency>
<!-- optional, for PDF Rendering -->
<dependency>
<groupId>com.pdfjet</groupId>
<artifactId>pdfjet</artifactId>
<version>4.75</version>
</dependency>
<!-- optional, for CSS stylesheet support in XHTML renderer -->
<dependency>
<groupId>org.antlr</groupId>
<artifactId>antlr4-runtime</artifactId>
<version>4.7.2</version>
</dependency>
<!-- optional, for server-side WebGL fallback -->
<dependency>
<groupId>org.jogamp.jogl</groupId>
<artifactId>jogl-all</artifactId>
<version>2.0-rc11</version>
</dependency>
<!-- optional, for server-side WebGL fallback -->
<dependency>
<groupId>org.jogamp.gluegen</groupId>
<artifactId>gluegen-rt-main</artifactId>
<version>2.0-rc11</version>
</dependency>
<!-- may be needed if your J2EE container doesn't provide this -->
<dependency>
<groupId>org.apache.geronimo.javamail</groupId>
<artifactId>geronimo-javamail_1.4_mail</artifactId>
<version>1.8.1</version>
<scope>provided</scope>
</dependency>