The java-bidder-framework from onealtang

java-bidder-framework's Introduction

set up the ant deploy properties
--------------------------------
- edit integration/tomcat/deploy.properties
	- to set the war file name
	- to set the location of the webapps directory

set up the ready handler on tomcat other similar application servers
--------------------------------------------------------------------
- The ReadyHandlerServlet is responsible for replyiing with an ascii value of "1"
- Located in integration/tomcat/source com.appnexus.integration.servlet
- Set up web.xml in integration/tomcat/WEB-INF
- Included in source package

set up servlet mappings on tomcat other similar application servers
-------------------------------------------------------------------
- Always use only one servlet for handling requests: com.appnexus.integration.servlet.RequestHandlerServlet
- Different requests (bid, notify, etc...) are determined inside this servlet and mapped to correct action handler
- Default setup included integration/tomcat/WEB-INF/web.xml
- web.xml maps NotifyHandler, BidHandler, ClickHandler, PixelHandler
  to the same servlet: com.appnexus.integration.servlet.RequestHandlerServlet
- Modify web.xml if servlet uri needs to be mapped differently. For instance some may have /BidRequest rather
  than /BidHandler

build and deploy
----------------
- if using a clean directive stop tomcat:
    - linux> /etc/init.d/tomcat5 stop
    - windows> catalina stop
- ant [clean] deploy

build distribution only
-----------------------
- if using a clean directive stop tomcat:
    - linux> /etc/init.d/tomcat5 stop
    - windows> catalina stop
- ant [clean] dist

running tomcat
--------------
linux> /etc/init.d/tomcat5 start
windows> catalina start | run

using ReadyMonitor (testing)
----------------------------
- Ready Monitor mimics the Impression Bus's request to a servlet awaiting "1" ascii values in return
- edit ReadyMonitor/config/config.properties
	- to send requests to the URL of choice
	- to set the ping frequency
- running
    - cd into ReadyMonitor/dist
    - linux> sh ReadyMonitorRunner.sh
    - windows> ReadyMonitorRunner.bat


using RequestMaker (testing)
----------------------------
- Ready Monitor mimics the Impression Bus's requests to a BidHandler, NotifyHandler, ClickHandler, PixelHandler
- Looks in a directory called requests (in working directory) and randomly chooses a file which is in json format
- Sends randomly chosen request (from above) to URI specified in config/config.properties
- running
    - cd into RequestMaker/dist
    - linux> sh RequestMakerRunner.sh
    - windows> RequestMakerRunner.bat

java-bidder-framework's People

Watchers

java-bidder-framework's Issues

What is the rationale behind the JSonStAX architecture?

The JSON parsing classes seem rather rigid and particularly difficult to debug. 
What was the original design rationale behind using a JSonJacksonStAX model? 
Since much of the code is now obsolete with respect to the AppNexus API, is 
there any reason to maintain it? google-gson, while it uses reflection, is much 
simpler to use and significantly less prone to error.

Original issue reported on code.google.com by [email protected] on 27 Dec 2012 at 8:41

index goes out of bounds in LucidDataHandler.write()

Here's the relevant piece of code:

LucidDataHandler.java, lines 26-39

for (int i = 0; i <= ld.getLucidLevels().size(); i++) {
    LucidLevelData data = ld.getLucidLevels().get(i);
    ...
}

When i reaches ld.getLucidLevels().size(), ld.getLucidLevels().get(i)
throws java.lang.IndexOutOfBoundsException. Changing the equality operator
in loop test from "<=" to "<" should fix the problem.

Original issue reported on code.google.com by [email protected] on 24 Jul 2009 at 4:08

Recommend Projects