http://weblogs.java.net/blog/marklittle/ en-us 2006-03-02T13:25:45-08:00 http://weblogs.java.net/blog/marklittle/archive/2006/03/transactions_ar_1.html In this article I'll describe why you shouldn't overlook the potential usefulness of transactions within your application, even if you're not using distributed transactions. J2EE marklittle 2006-03-02T13:25:45-08:00 http://weblogs.java.net/blog/marklittle/archive/2006/02/when_and_why_ar_1.html Interoperability fests/workshops have become very popular recently, particularly in the area of Web Services. However, they are more widely useful and should be an active part of a developer's testing arsenal whilst building relevant systems, rather than an afterthought as is often the case. Testing marklittle 2006-02-01T03:09:42-08:00 http://weblogs.java.net/blog/marklittle/archive/2005/05/transactions_an.html Over the years I've seen many complaints about using transactions (e.g., via the JTA) for a number of reasons, including performance degredation, assumptions are impact on application development etc. You don't get something for nothing (there really is no such thing as a free lunch), so there's always a trade-off to be made with transactions: guaranteed completion even in the presence of failures. In this entry I'll look at why you shouldn't look to trade off some transaction properties; either use them all or don't use transactions. J2EE marklittle 2005-05-11T12:53:05-08:00 http://weblogs.java.net/blog/marklittle/archive/2005/05/a_session_conte.html In this entry I'll take a look at the OASIS WS-Context specification that's being developed by Sun, Oracle and others. It's an important component in the Web Service stack and unlike some aspects of WS-Addressing, facilitates the loosely coupled nature of SOA. Web Services and XML marklittle 2005-05-07T14:44:20-08:00