Start line:  
End line:  

Snippet Preview

Snippet HTML Code

Stack Overflow Questions
Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
 package org.apache.marmotta.platform.core.servlet;
This filter is currently only used to indicate that the LMF server has been started successfully.

User: sschaffe

 public class MarmottaPostStartupFilter implements Filter {
     private Logger log;
     @Inject @Any
     private Event<SystemStartupEventstartupEvent;

Called by the web container to indicate to a filter that it is being placed into service. The servlet container calls the init method exactly once after instantiating the filter. The init method must complete successfully before the filter is asked to do any filtering work.

The web container cannot place the filter into service if the init method either
1.Throws a ServletException
2.Does not return within a time period defined by the web container

     public void init(FilterConfig filterConfigthrows ServletException {
         // if the system is already configured, we can safely trigger a startup event
         if(.getBooleanConfiguration("",false)) {
             // SystemStartupEvent());
         if(.hasBuildInfo()) {
             .warn("Apache Marmotta Core Version {} has started up successfully!".getModuleVersion());
         } else {
             .warn("Apache Marmotta Core (Development Version) has started up successfully!");
         .warn("You can access the system now at the URL {}""http://"+.getServerName()+":"+.getServerPort()+.getServerContext()+"/");

The doFilter method of the Filter is called by the container each time a request/response pair is passed through the chain due to a client request for a resource at the end of the chain. The FilterChain passed in to this method allows the Filter to pass on the request and response to the next entity in the chain.

A typical implementation of this method would follow the following pattern:-
1. Examine the request
2. Optionally wrap the request object with a custom implementation to filter content or headers for input filtering
3. Optionally wrap the response object with a custom implementation to filter content or headers for output filtering
4. a) Either invoke the next entity in the chain using the FilterChain object (chain.doFilter()),
* 4. b) or not pass on the request/response pair to the next entity in the filter chain to block the request processing
* 5. Directly set headers on the response after invocation of the next entity in the filter chain.

     public void doFilter(ServletRequest requestServletResponse responseFilterChain chainthrows IOExceptionServletException {

Called by the web container to indicate to a filter that it is being taken out of service. This method is only called once all threads within the filter's doFilter method have exited or after a timeout period has passed. After the web container calls this method, it will not call the doFilter method again on this instance of the filter.

This method gives the filter an opportunity to clean up any resources that are being held (for example, memory, file handles, threads) and make sure that any persistent state is synchronized with the filter's current state in memory.

    public void destroy() {
        //To change body of implemented methods use File | Settings | File Templates.
New to GrepCode? Check out our FAQ X