|
I'd guess that you would implement your own IRequestFactory and
manually write the access log from there. You have access to the
servlet and if you wanted to turn wicket requests into meaningful,
trackable information (I know exactly what you are talking about),
you'd have to manually write out an access log that matches something
your tracking software can read (like standard Apache log format).
Once you have the http servlet, you have the HTTP method, IP address,
and all the other headers. As far as the actual request URL you could
write anything based on the Page/Resource that the WebRequest is
processing. You could, for example, rewrite all requests to
com.mysite.MyPage as
http://mysite.com/com/mysite/MyPage?param1=value1.. with the params
generated from the PageParameters. One a side note, I am more used to using WSS, where you just change the tag information in the js code and WSS tracks the requests into different categories that you specify. URLs are not important because it's the JS tag that determines where the request is categorized. Would be very easy to do with a custom component. Aaron Korbinian Bachl wrote: What example do you mean ? - i only found the javadoc http://wicket.sourceforge.net/apidocs/wicket/protocol/http/RequestLogger.htm l so far...what i mean is following: imagine you have a page that sells/ adverts something - now you want to know how many visitors you have, on what pages (what params) they are, how many are doing certain actions or giving up and on what stage... in classical way, the webserver creates a log where he puts the URLs, time, IP etc. in which then can be examined by trackingsoftware like e.g: NetTracker, Webstat etc. - but they wont work with wicket as we have no classical URLs hope you now understand what i mean-----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Im Auftrag von Juergen Donnerstag Gesendet: Samstag, 28. Oktober 2006 11:13 An: wicket-user@lists.sourceforge.net Betreff: Re: [Wicket-user] wicket & tracking/ controlling When you go to the example, there is this little red (i) in the top left corner. It'll open a page with all the information maintained by RequestLogger. IResponseFilter and it is implementations might be an option/starting point for you as well. While re-reading your mail, I'm not sure it is what you ask for. What information do you get from other web apps in the webservers log which you don't get for Wicket apps? Your example given, the visitors, can be retrieved, no difference. Time to respond, who, when etc, no difference. What you won't get is the Page and wicket specific information of course. I'm not aware of any wiki entry or so, but I might not be up-to-date on that. A base page, as you suggested, might be a good starting point, as many relevant information are available. Though events (submit, etc.) must be logged differently. Juergen On 10/28/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote: |
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
