Everit Templating HTML 1.1.0 released

I am happy to announce the version 1.1.0 of Everit Templating HTML. In this release a new attribute and an attribute enhancement were introduced.

For more information about the release notes, please see the 1.1.0 milestone page at GitHub!

Posted in Uncategorized

Everit Templating 1.0.0

I am happy to announce that Everit Templating modules are available to download from Maven Central. The following modules are available:

  • Expression API: Simple API to be able to compile and evalute expressions
  • Expression MVEL: Bridge between MVEL and Expression API
  • Templating API: Simple API to be able to compile and render templates
  • Templating Text: A very simple and amazingly fast text templating tool that implements Templating API. The library was developed based on the MVEL source but it is changed in the way that any expression language can be used that implements the Expression API.
  • Templating HTML: HTML / XML parser and templating engine that implements Templating API. This one is probably the fastest and simplest templating engine on the market. Any expression language can be used that implements Expression API.

Expression API and its implementations are available under the org.everit.expression groupId.

Templating API and its implementations are available under the org.everit.templating groupId.

Posted in Uncategorized

OSGi Blueprint Webconsole plugin 1.0.0 released

Although we switched in our OSGi environment from Blueprint to Declarative Services a year ago, we still have some projects where Blueprint is used. To help the daily work of our developers, we created a very simple Webconsole plugin that shows the actual Blueprint events.

We released this tiny plugin to maven central to help others as well: http://search.maven.org/#artifactdetails%7Corg.everit.osgi%7Corg.everit.osgi.webconsole.blueprint%7C1.0.0%7Cbundle

Source code is available at github in the Everit Archive group: https://github.com/everit-org-archive/osgi-webconsole-blueprint

webconsole_blueprint_screenshot

Tagged with: , ,
Posted in Uncategorized

Configuration chapter of Everit Cookbook is available

bzsoldos

The Configuration chapter of Everit Cookbook is available. This chapter gives a step-by-step guide of:

  • Installing Jetty with WebConsole
  • Creating configuration for components
  • Persist the configuration in the way that it is available during the build on the CI server as well

View original post

Posted in Uncategorized

CAS authentication implemented and released

attilakissit

I am happy to announce the first implementation of CAS authentication.

The artifact is available on Maven Central Repository:

<dependency>
  <groupId>org.everit.osgi</groupId>
  <artifactId>org.everit.osgi.authentication.cas</artifactId>
  <version>1.0.0</version>
</dependency>

View original post

Posted in Uncategorized

New releases of Everit Authentication

attilakissit

I am happy to announce the new releases of Everit Authentication:

The artifacts are available on Maven Central Repository.

View original post

Posted in Uncategorized

OSGi LogListener for SLF4J

attilakissit

Slf4jLogListener

Slf4jLogListener (implements LogListener) forwards all the LogEntry‘s (logged by a LogService) to an SLF4J Logger that is assigned to the bundle that created the LogEntry. The name of the used Logger is constructed from the symbolic name and the version of the bundle.

The following log level mapping is used between the OSGi LogService and the SLF4J Logger:

LogService.LOG_DEBUG (4)   --> Logger.debug(..)
LogService.LOG_INFO (3)    --> Logger.info(..)
LogService.LOG_WARNING (2) --> Logger.warn(..)
LogService.LOG_ERROR (1)   --> Logger.error(..)
other user defined         --> Logger.warn(..) with logging the
                                               original level

Usage

The OSGi bundle of the Slf4jLogListener contains a BundleActivator that automatically opens a ServiceTracker for LogReaderService services. This ServiceTracker registers an Slf4jLogListener instance to the LogReaderService services by invoking addLogListener() method on them. The registered instance is removed from the LogReaderService when the service is removed.

Just activate the org.everit.osgi.loglistener.slf4j bundle in your OSGi container, configure an SLF4J implementaion (slf4j-simple, logback, etc.) and you…

View original post 149 more words

Posted in Uncategorized

Everit Authorization 1.0.0

bzsoldos

I am happy to announce that the first stable modules of Everit Authorization is uploaded to maven-central.

The implementation is based on the concept of modularized persistence.

The modules are tested on H2, Mysql and PostgreSQL.

The documentation is available in the README file of the reference implementaiton and in the javadoc of the interfaces. 

View original post

Posted in Uncategorized

Everit Authentication implemented and released

attilakissit

I am happy to announce the first implementation of Everit Authentication! Available components are:

The artifacts are available on Maven Central Repository.

Functionalities that will be available in future releases:

  • Remember Me
  • Configurable session invalidation in case of successful form authentication
  • Authentication against different datasources/providers:
    • CAS
    • LDAP
    • OpenID
    • Certificate based

View original post

Posted in Uncategorized

Everit Authentication

attilakissit

Goals

Design and create a lightweight and modularized set of components that offer dedicated solutions of the tasks around authentication. This design provides an opportunity to build an application from simple blocks and keep the number of unused classes very low.

Requirements:

  • Modularized structure
  • Dedicated solutions for dedicated functions
  • Easy-To-Use API

Functions:

  • Session management
  • Remember Me
  • User authentication (username and password)
  • Web integration
  • Execute authenticated processes
  • Query the authenticated user of the current thread

Concept

The final goal is to execute an authenticated process and query the owner of the authenticated process while it runs. To identify a user the Resource component will be used, for more information about resources read the “Resource” chapter of the Modularized Persistence post.

Concept Concept (draft)

Entry Point

The Entry Point is the place where the user appears as the business actor in the application. In case of a web applications the Entry Point is…

View original post 1,167 more words

Posted in Uncategorized