ACM Home Page
Please provide us with feedback. Feedback
Combining software transactional memory with a domain modeling language to simplify web application development
Full text PdfPdf (189 KB)
Source International Conference On Web Engineering; Vol. 263 archive
Proceedings of the 6th international conference on Web engineering table of contents
Palo Alto, California, USA
SESSION: Session 12: design and development methods II table of contents
Pages: 297 - 304  
Year of Publication: 2006
ISBN:1-59593-352-2
Authors
João Cachopo  INESC-ID/Technical University of Lisbon, Lisboa, Portugal
António Rito-Silva  INESC-ID/Technical University of Lisbon, Lisboa, Portugal
Sponsor
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 16,   Downloads (12 Months): 67,   Citation Count: 2
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1145581.1145640
What is a DOI?

ABSTRACT

Current best practices on web application development build on a plethora of design patterns, frameworks, and tools to support commontasks such as handling requests from the user and persisting domain entities: Even the simplest web applications need suchthings. Thus, web application developers are forced to learn anenormous amount of technology before they can start being productivein the development process.This paper proposes a simpler approach to the development of web applications, based on the combination of two elements. First, the use of Software Transactional Memory to bring the transactionsemantics into the programming language level. Second, we propose an object-oriented Domain Modeling Language to specify the domain model.This domain model is transformed into classes that haveinterfaces that an object-oriented programmer would expect, but the objects of these classes are transparently transactional andpersistent.This approach significantly reduces both the effort and the errorsmade during the development of new applications. Rather thandealing with multiple configuration files and tools, which have norelation to the domain problem, programmers can concentrate exclusively on an object-oriented model of the problem they want to solve. By using this approach, we can delay, or completely avoid,the commitment to a particular technology.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
2
 
3
J. Cachopo and A. Rito-Silva. Versioned boxes as the basis for memory transactions. In Workshop on Synchronization and Concurrency in Object-Oriented Languages (SCOOL05), San Diego, USA, Oct. 2005. Available at http://hdl.handle.net/1802/2101.
 
4
 
5
 
6
 
7
FénixEDU, 2005. Home page at http://fenixedu.sourceforge.net.
 
8
 
9
 
10
11
12
13
14
 
15
Hibernate. Home page at http://www.hibernate.org. \bibitemIbatis:URL iBATIS. Home page at http://ibatis.apache.org/.
 
16
JPetStore. Available at the iBATIS Home page at http://ibatis.apache.org/. \bibitemJVSTM:URL JVSTM, 2005. Home page at http://www.esw.inesc-id.pt/jcachopo/jvstm.
 
17
 
18
Object/Relational Bridge -- OJB. Home page at http://db.apache.org/ojb.
 
19
OMG Model Driven Architecture. Home page at http://www.omg.org/mda.
 
20
Prevayler. Home page at http://www.prevayler.org.
21
 
22
 
23
SUN Microsystems, Inc., Palo Alto, California, USA. Java 2 Platform Enterprise Edition Specification, v. 1.4, final release edition, November 2003.
 
24
D. Thomas. UML - Unified or Universal Modeling Language? Journal of Object Technology, 2(1):7--12, January-February 2003.
 
25
xPetstore. Home page at http://xpetstore.sourceforge.net.


Collaborative Colleagues:
João Cachopo: colleagues
António Rito-Silva: colleagues