Spring Security is a powerful and highly customizable authentication and access-control framework. It is the de-facto standard for securing Spring-based applications
Spring Security is one of the most mature and widely used Spring projects. Founded in 2003 and actively maintained by SpringSource since, today it is used to secure numerous demanding environments including government agencies, military applications and central banks. It is released under an Apache 2.0 license so you can confidently use it in your projects.
Spring Security is also easy to learn, deploy and manage. Our dedicated security namespace provides directives for most common operations, allowing complete application security in just a few lines of XML. We also offer complete tooling integration in SpringSource Tool Suite, plus our Spring Roo rapid application development framework. The Spring Community Forum and SpringSource offer a variety of free and paid support services. Spring Security is also integrated with many other Spring technologies, including Spring Web Flow, Spring Web Services, SpringSource Enterprise, SpringSource Application Management Suite and SpringSource tc Server.
"Errai is a framework for building GWT applications
Errai offers a set of components for building rich web applications using The Google Web Toolkit. The framework provides a unified federation and RPC infrastructure with true, uniform, asynchronous messaging across the client and server."
"We'll be covering all aspects of mobile application development! This includes the latest HTML5 technologies used in the mobile web, and in hybrid application frameworks like the Apache Cordova. All the way to JBoss AS based services, mobile RichFaces/JSF2, tooling, and native application support, and prototyping. "
This post is to introduce the EMFT Texo project to you. The Texo project delivers code/artifact generation from ecore/xsd models for (web) server environments with additional runtime functionality. Texo aims to eventually also provide code generation solutions for the web client.
"The Qt SOAP project provides basic web service support with version 1.1 of the SOAP protocol.
The SOAP (Simple Object Access Protocol) component recognizes the XML standard for describing how to exchange messages. Its primary usage is to invoke web services and get responses from Qt-based applications.
These classes make it easy to construct, send, receive and process SOAP messages on the client side."
"The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock this data and free it from silos that exist in applications today. OData does this by applying and building upon Web technologies such as HTTP, Atom Publishing Protocol (AtomPub) and JSON to provide access to information from a variety of applications, services, and stores.
Project Info
odata4j is a new open-source toolkit for building first-class OData producers and first-class OData consumers in Java. "
Apache Shiro (pronounced "shee-roh", the Japanese word for 'castle') is a powerful and easy-to-use Java security framework that performs authentication, authorization, cryptography, and session management and can be used to secure any application - from the command line applications, mobile applications to the largest web and enterprise applications.
Shiro provides the application security API to perform the following aspects (I like to call these the 4 cornerstones of application security):
Authentication - proving user identity, often called user 'login'.
Authorization - access control
Cryptography - protecting or hiding data from prying eyes
Session Management - per-user time-sensitive state
Shiro also supports some auxiliary features, such as web application security, unit testing, and multithreading support, but these exist to reinforce the above four primary concerns.
"Qworum defines a new type of service that is used for modularizing web applications. Qworum services are interactive, just like conventional websites. In addition, Qworum services are callable, much like traditional RPC services. "
Vaadin is a Rapid Application Development (RAD) framework for RIA applications. I only know it for a few months but since I started experimenting with it, I'm really in favor of it.
I see a lot of advantages compared to Sun's Java EE standard front-end framework JSF.
First of all Vaadin is a java library, so you only have to write Java to build a complete frontend. No need for a specific frontend language, no need for converters (for comboboxes),… This also implies that you can use the full Java power on the frontend side and that's an huge advantage because frontend code is now type-safe and easily refactorable. You can unit test your frontend with JUnit. You can also use all existing java libraries on the frontend side, for example LOG4J.
Another advantage is the fact that Vaadin is easy to learn (JSF isn't!) and to use: it's straigtforward. It feels like developing desktop apps and for me developing desktop apps feels much more intuitive than developing web-apps the way I'm used to.
Vaadin uses convention over configuration. No need to register new components, validators or whatever in different xml files. Themes have a default folder and a default folder structure.
Vaadin is very well documented. There's the book of Vaadin wich explains every aspect of the framework very clear. On the site there's a blog, a FAQ section, a wiki, a forum, examples with Java source code, …
It's very easy to extend. Want to create your own Validator? Just implement an interface or extend another Validator and use it. Want to create your own custom server side component? Just extend the CustomComponent class or extend from another component. There's also an add-on directory where you can download UI components, data components, tools, themes, …
"Besides a rich user interaction many applications need to display a big amount of data sets as diagrams or reports as part of their applications. In order to bridge the gap the BIRT project was created as part of the eclipse ecosystem. BIRT is an open source Eclipse-based reporting system that integrates with your Java/J2EE application to produce compelling reports. That BIRT integrates well with classic RCP applications is a well known fact. But the need for rich internet applications is still growing. And here the RAP comes into play. As a platform for developing Web 2.0 applications with the same patterns as for RCP it paves the way for single sourcing applications running on both platforms. In this talk we will show how to integrate diagrams and reports known from BIRT into RAP applications. Topics covered include how to setup the environment to let BIRT and RAP play well together. In addition we will give advices how to use the reports inside RAP applications and which problems may arise. As a final outcome of we will know everything to bring reporting capabilities into RAP applications. "
Couchbase: The End of the Trade-off Game
Before Couchbase, ops teams managing web applications faced tough compromises when it came to databases. Screaming speed or durable, safe data storage. Super scale out virtually overnight or scaling up with lots of hardware upgrades. Bleeding-edge NoSQL or safe, but inflexible relational solutions.
Couchbase eliminates those trade-offs. We supply extraordinary speed with complete safety and incorruptibility. A growth path that will never force you to rethink your application infrastructure from datacenter deployments to mobile devices - one continuous, synchronized flow. Solutions that complement your other systems - including your RDBMS. Technology that meets the needs of developers and conforms to the mission-critical demands of ops teams.
This really is the beginning of a new era of NoSQL solutions.
Couchbase: database solutions for a post-relational world. Learn more.
"JAX-WS Reference Implementation Project. This project provides the core of Metro project, inside GlassFish community
This project develops and evolves the code base for the reference implementation of the Java API for XML Web Services (JAX-WS) specification. The current code base supports JAX-WS 2.0 and JAXWS 2.1 but the project will track future versions of the JAX-WS specifications."
Magnolia, the open source content management vendor that delivers simplicity on an enterprise scale, today announced the release of Magnolia CMS 4.4, with new tools that enable enterprise web authors to collaborate in the quick creation of professional-grade, multi-lingual sites.
Front End Development or Client-Side Development is the practice of coding in technologies like HTML, CSS, and Javascript in a website. The practice involves converting Data into a Graphical Interface for a user to view and interact. Growth in Front-end development is excellent and there are plenteous opportunities available, especially because companies now want their customers to have a good experience while using their Web applications. Want to get hired as a Front End Developer in 2019? Acquire skills in Front End Development, Build live Projects and Get Guaranteed Interviews with edWisor.
"Community Dashboard Framework (CDF) is a project that allows you to create friendly, powerful, fully featured dashboards on top of the Pentaho BI server. Former Pentaho dashboards had several drawbacks from a developer's point of view. The developing process was awkward, it required know-how of web technologies and programming languages, and basically it was time-consuming. CDF emerged as a need for a framework that overcame all those difficulties. The final result is a powerful framework featuring the following:
. It is based on Open Source technologies.
. It separates logic (JavaScript) of the presentation (HTML, CSS)
. It features a life cycle with components interacting with each other
. It uses AJAX
. It is extensible, which gives the users a high level of customization: . Advanced users can extend the library of components.
. They also can insert their own snippets of JavaScript and jQuery code.
CDF can be used:
. As part of a Pentaho solution. This is the most common scenario.
. In a standalone mode as an alternative to the Pentaho User Console
. Integrated with Portlets, PHP applications, intranet portals and even desktop applications. "
There is a list of 20 jsp interview questions. If you know any jsp interview question that has not been included here, post your question in the Ask Question section. 1)What is JSP? Java Server Pages technology (JSP) is used to create dynamic web page.It is an extension to the servlet.A JSP is internally converted into servlet.
Last weekend while pondering the question "Is Scala ready for the enterprise?" I decided to write a simple Java EE 6 app entirely in Scala, without using any Java. I had three main reasons for doing this: one was just to see how easy/difficult it would be to write everything in Scala (it was easy). Another was to document the process for others journeying down the same road (the entire project is on github). Finally, I wanted to identify advantages of using Scala instead of Java that are specific to Java EE apps (I found several).
Background
The specific app I created was an adaptation of the Books example from Chapter 10 of Beginning Java™ EE 6 Platform with GlassFish™ 3. It's a simple web app that displays a list of books in a database and lets you add new books. Although it's a pretty trivial app, it does touch on several important Java EE 6 technologies: JPA 2.0, EJB 3.1 and JSF 2.0.
Last week I decided to challenge Scala's downscalability by trying to replace a Groovy script with a Scala pendant.
In this article you will read about this little experiment and a comparision of the Scala result with the Groovy predecessor.
But first some background about the script:
Some time ago my company introduced a new spam notification system. When it thinks that a mail contains spam, it keeps it in quarantine and once or twice a day sends an email to the recipient (me) reporting all the kept mails, together with an intranet web link for each to release it.
Here you see an example of such a mail (note: I have my mails displayed in plain text format):