We are also about to do Analytics but Analytics is an end to end. Data Source to UI aspect. Thinking aloud if you were to use Wicket you would have to hand-build any BI operations like Drill Down etc.
For this reason we are considering using BIRT. And beside Analytics should be UI agnostic as thats more a Business Intelligence operation and creating Home grown UI's isn't what I'd put my money on "beyond a point". I built some WebSerivice to work with Google charts but I realized the futility of it and its inability to scale (the effort required to make it scale) for more advanced things like DRILL-DOWN (interactive maps) etc. Irrespective if Wicket folks provide it or not, perhaps choose a pure BI tool and integrate that instead. My 2 cents (or whatever currency applies) ----- Software documentation is like sex: when it is good, it is very, very good; and when it is bad, it is still better than nothing! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Analytics-for-Wicket-applications-tp4678055p4678056.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
