Tapestry for Nonbelievers
A new article by I. Drobiazko and R. Zubairov introduces v. 5 of the Apache Tapestry component-oriented web framework. The tutorial shows how to create a component and covers IoC in Tapestry and Ajax.
Presentation
Good News: We have re-worked our video infrastructure to provide more reliable service. Please email bugs at infoq.com with any problems.
Recorded at:
Event Patterns
Posted by Ian Cartwright on May 17, 2007 04:25 PM
Summary
Ian Cartwright presents some of his work (developed with Martin Fowler) on Event Patterns, including: Event Sourcing, Event Collaboration, Parallel Model, and Retroactive Event. These patterns can be used in scenarios where a sequence of domain model changes may need to be recorded, reversed, corrected, or simply observed.
Bio
Ian Cartwright is a consultant and ThoughtWorks and worked with Martin Fowler on distilling these event patterns.
About the conference
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
Ian Cartwright presents some of his work (developed with Martin Fowler) on Event Patterns, including: Event Sourcing, Event Collaboration, Parallel Model, and Retroactive Event. These patterns can be used in scenarios where a sequence of domain model changes may need to be recorded, reversed, corrected, or simply observed.
Bio
Ian Cartwright is a consultant and ThoughtWorks and worked with Martin Fowler on distilling these event patterns.
About the conference
JAOO is the premier European developer conference on software technology, methods and best practices. The conference presents in-depth presentations and tutorials by researchers, engineers and trend-setters in software engineering and technology.
RelatedVendorContent
Evaluation Guide: Is Your SCM Tool Ready for Agile?
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Introducing the SpringSource Application Platform
Snapshots from SOA Governance: Artifacts, People, Processes, Repositories
Related Sponsor
Keynotes by industry leaders; Grady Booch, Steve Mills, Dr. Daniel Sabbah and William Shatner. Over 300 highly technical sessions, workshops and tracks. Register!
Unlimited undo
by
Mikko Apo
Posted
May 17, 2007 4:34 PM
patterns!
by
Joost de Vries
Posted
May 19, 2007 12:19 PM
State transitions as event transaction model
by
William Homan-Muise
Posted
May 21, 2007 3:17 PM
-
A few years ago I had a similar solution in a university project. The program was supposed have undo with one step undo history, but I was determined to make the undo unlimited. The easiest way to implemented that was with events, or transactions. Events could hold sub events, so the changes to the model could be rewound on micro (detailed) or on macro level. Sometimes I've been thinking how the same solution would work as a backend solution for large scale enterprise data. Storing the change information would be nice step up from having just the current state of the model available in the database. Every change in the model could be stored as event. The event could contain more information about the transaction than just the change data: user id, transaction ids, session state and application's context. With that info the event log would have more uses than "just" containing the changes, it would serve as an automatically generated application/system log. Event's authentication data could would provide accountability for all actions. Also, as a convinient side effect the system would support data's revision history out of the box. No more need to manually reimplement different aspects of data's revision history. Hooking something like this to the integration layer would be nice. Persistance APIs like JPA could also generate the event log automatically. That way the system would be nicely transparent (from the application's point of view) and there wouldn't be any need for changes to support the event log.
-
Interesting; I was recently saying to a colleague that I felt that the patterns movement seems to have dried up years ago. Maybe that is because the hype moved on, or maybe because making knowledge explicit is hard work that mostly benefits others, I don't know. I still feel that patterns are a wonderful way to create knowledge: ie make explicit what people have been doing wrestling with real world problems. (if I'm not right in saying that the patterns movement dried up I'd love to see some some pointers) So, this is very interesting.
-
We have developed a product that collects events from network devices and uses a state machine model to capture complex and long running transactions. It is currently being used in the VoIP and Municipal WiFi markets for monetization, revenue assurance, alerting/notification and analytics. It is based upon the JBI container.
3 comments
Reply