Bundle installation - local vs prod

Generic1234

31-08-2017

Hello,

I have developed a simple Bundle with one Servlet:

@SlingServlet(

        paths={"/bin/schafbergbahn/ticker"},

        methods = "GET",

        metatype=true

        )

public class SchafbergBahnServlet extends org.apache.sling.api.servlets.SlingAllMethodsServlet {

    @Reference

    private CSVFileReaderImpl csvFileReader;

    ...

    doGet implemented

and one Service:

@Service({CSVFileReaderImpl.class})

@Component(immediate=true, metatype=true, label="Ticker Service")

public class CSVFileReaderImpl implements CSVFileReader {

protected final Logger log = LoggerFactory.getLogger(this.getClass());

  @Property(unbounded=PropertyUnbounded.DEFAULT, label="CSV path", description="csv file path")

  private static String CSV_PATH = "csvpath";

  private String csvPath;

  @Activate

  protected void activate(Map<String, Object> properties) {

    readProperties(properties);

  }

 

  protected void readProperties(Map<String, Object> properties) {

    Object obj = properties.get("csvpath");

    this.csvPath = obj.toString();

  }

...

After installation it looks like this (local at top, productiv at bottom)

AEM_LocalvsProd.png

The difference is that

  

     1. in productiv environment one Used Service is missing (CSVFileReaderImpl)

     2. Declarative Service Components are in state "satisfied" at productive environment

Local I can invoke the servlet and it works fine, at productive environment I get the following HTTP 404 error:

Resource at '/bin/schafbergbahn/ticker/' not found: No resource found


Apache Sling

Does anyone know what I can do in order to get it work at productiv environment?

Thanks!

Hannes

Accepted Solutions (1)

Accepted Solutions (1)

Diego_Fontan

31-08-2017

  1. as smacdonald2008 and feike_visser said, you have to make sure both instances are the same, hence your local environment must have SP1 (if that the case)
  2. make sure also in term of configuration all instances are same as well.

Answers (3)

Answers (3)

Feike_Visser1

Employee

31-08-2017

Also there is a diff in your env, SP1 is installed on prod.

I would recommend to also use "nosamplecontent", and install SP1 locally to reproduce the issue locally.

smacdonald2008

31-08-2017

Make sure that the 2 instances are the same - same service packs installed, etc. The only thing that would explain the difference is that they are not the same some how.