ning-service-skeleton-log4j

Jetty-based service skeleton

License

License

Categories

Categories

Jetty Container Application Servers
GroupId

GroupId

com.ning.jetty
ArtifactId

ArtifactId

ning-service-skeleton-log4j
Last Version

Last Version

0.1.7
Release Date

Release Date

Type

Type

jar
Description

Description

ning-service-skeleton-log4j
Jetty-based service skeleton
Project Organization

Project Organization

Ning, Inc.

Download ning-service-skeleton-log4j

How to add to project

<!-- https://jarcasting.com/artifacts/com.ning.jetty/ning-service-skeleton-log4j/ -->
<dependency>
    <groupId>com.ning.jetty</groupId>
    <artifactId>ning-service-skeleton-log4j</artifactId>
    <version>0.1.7</version>
</dependency>
// https://jarcasting.com/artifacts/com.ning.jetty/ning-service-skeleton-log4j/
implementation 'com.ning.jetty:ning-service-skeleton-log4j:0.1.7'
// https://jarcasting.com/artifacts/com.ning.jetty/ning-service-skeleton-log4j/
implementation ("com.ning.jetty:ning-service-skeleton-log4j:0.1.7")
'com.ning.jetty:ning-service-skeleton-log4j:jar:0.1.7'
<dependency org="com.ning.jetty" name="ning-service-skeleton-log4j" rev="0.1.7">
  <artifact name="ning-service-skeleton-log4j" type="jar" />
</dependency>
@Grapes(
@Grab(group='com.ning.jetty', module='ning-service-skeleton-log4j', version='0.1.7')
)
libraryDependencies += "com.ning.jetty" % "ning-service-skeleton-log4j" % "0.1.7"
[com.ning.jetty/ning-service-skeleton-log4j "0.1.7"]

Dependencies

compile (1)

Group / Artifact Type Version
commons-lang : commons-lang jar 2.6

provided (2)

Group / Artifact Type Version
log4j : log4j jar 1.2.16
org.weakref : jmxutils jar 1.12

Project Modules

There are no modules declared in this project.

Build Status

To see an example of an application using this skeleton, see how the maven-jetty-plugin is configured (relevant files under src/test/).

Guice

As a bare minimum, you should install and/or extend com.ning.jetty.core.modules.ServerModule, and add the following dependency:

    <dependency>
        <groupId>com.ning.jetty</groupId>
        <artifactId>ning-service-skeleton-core</artifactId>
    </dependency>

Filters

  1. Request and Response utilities

    com.ning.jetty.utils.filters.PeepingTomRequestWrapper and com.ning.jetty.utils.filters.PeepingTomResponseWrapper wrap HttpServletRequestWrapper and ServletResponseWrapper respectfully and cache certain attributes. You can use these classes in your filters to look into the request and/or response streams and various attributes (e.g. response code or headers).

    See com.ning.jetty.eventtracker.filters.TrackerFilter for an example on how to use them.

  2. TrackerFilter

    You can use the provided TrackerFilter to send request logs to your log aggregating system. A default implementation is provided for the collector via the eventtracker library. See com.ning.jetty.eventtracker.CollectorTracker.

    In addition to the eventtracker system properties, you can set the name of the event via com.ning.core.eventtracker.requestLogEventName (RequestLogEvent by default).

Servlets

  1. LogInvalidResourcesServlet

    The com.ning.jetty.core.servlets.LogInvalidResourcesServlet will log any request and return a 404 to the client. This is useful as a back-end servlet for Guice for example (the Guice filter requires a back-end servlet).

  2. HttpProxyServlet

    The com.ning.jetty.utils.servlets.HttpProxyServlet can be used to proxy request to a remote host. The remote host needs to be provided by implementing the ServiceFinder interface.

Log4j

  1. LogLevelCounterAppender

    The com.ning.jetty.log4j.LogLevelCounterAppender log4j appender can be used to gather statistics on a per logger and level basis (via JMX).

    To use it, configure your log4j.xml:

    <appender name="LOG_LEVEL_COUNTER" class="com.ning.jetty.log4j.LogLevelCounterAppender"/>
    <root>
        <priority value="WARN"/>
        <appender-ref ref="LOG_LEVEL_COUNTER"/>
    </root>
    

Misc.

  1. Adding healthchecks

To add healthchecks, you need to extend com.yammer.metrics.core.HealthCheck and register them.

  1. Available providers

You can use com.ning.jetty.jdbi.guice.providers.DBIProvider to create DBI objects for your dao. This provider will setup metrics and BoneCP for you.

Versions

Version
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.22
0.0.21
0.0.20
0.0.19
0.0.18
0.0.17
0.0.16
0.0.15
0.0.14
0.0.12
0.0.11
0.0.10
0.0.9
0.0.8