sorted by: recent | see :
popular
Content Tagged with Architecture + Java
Enterprise Java Community: ZK Rich Client Framework and Agile Development
Why Cameron Smith chose ZK over other RIAs, in part to reduce technologies required to just two: Java and ZK's XML-based markup, ZUML. Includes excellent quote on value of prototyping in agile development environments: "users get to see real, understandable screens and functionalities and discuss them verbally) ... Ideally, the team will work in fairly short cycles of 1-2 weeks, roughing out new Use Cases as evolutionary prototypes, having a customer viewing, then reworking them in time for the next or next but one viewing. Done properly, both developer and user representatives can keep the "state of the conversation" reasonably warm in their heads, allowing a rich flow of communication about requirements and changes, through the iterations ... [thus reducing the need for] costly formal mechanisms (detailed written use cases, review meetings, client review of issue tracker reports at a detailed level, etc.)"
Development
Java
Programming
frameworks
architecture
extreme
agile
openArchitectureWare.org - Official openArchitectureWare Homepage
openArchitectureWare (oAW) is a modular MDA/MDD generator framework implemented in Java(TM). It supports parsing of arbitrary models, and a language family to check and transform models as well as generate code based on them. Supporting editors are based on the Eclipse platform. OAW has strong support for EMF (Eclipse Modelling Framework) based models but can work with other models, too (e.g. UML2, XML or simple JavaBeans) At the core there is a workflow engine allowing the definition of generator/transformation workflows. A number of prebuilt workflow components can be used for reading and instantiating models, checking them for constraint violations, transforming them into other models and then finally, for generating code.
Roma Framework: The new way to conceive Web Applications
Roma allows you to develop enterprise level Java applications with low effort following a real Domain Driven Design approach. It's a new way to conceive the application: anything is a POJO, from the GUI forms to the persistent objects.
open-source: del.icio.us tag/open-source
Development
Framework
Java
open-source
architecture
domain-driven-design
ddd
Welcome to Naked Objects
Naked Objects is an open source Java-based application development platform. It’s called Naked Objects because all you need to develop are your domain objects - the Naked Objects platform auto-creates an object-oriented user interface (giving you the choice of different styles) and the
underlying database (using Hibernate) .
How is security handled?. Naked Objects provides full support both for user authentication and authorisation. The user's role(s) may determine which classes of domain objects they may access, which properties, and which actions within those objects. This information may be administered via a simple file, LDAP, or relational database.
Naked Objects is available for .NET.
Hibernate: del.icio.us tag/hibernate
Java
Software
Hibernate
.NET
productivity
open-source
architecture
Building LinkedIn's Next Generation Architecture with OSGi
Over the course of the last 5 years, LinkedIn has been built using relatively simple technologies: front end web applications (Tomcat/Servlet/JSP), back-end services (Jetty/Spring Remoting), databases, replication, and JMS. Although the web site was scaling adequately, we had some big challenges to overcome: In this session, I talked about why OSGi was chosen to help us solve those challenges, the implementation progress we've made, the pitfalls that we've encountered (so far) and what we have learned in the process.
Building LinkedIn's Next Generation Architecture with OSGi
Over the course of the last 5 years, LinkedIn has been built using relatively simple technologies: front end web applications (Tomcat/Servlet/JSP), back-end services (Jetty/Spring Remoting), databases, replication, and JMS. Although the web site was scaling adequately, we had some big challenges to overcome: In this session, I talked about why OSGi was chosen to help us solve those challenges, the implementation progress we've made, the pitfalls that we've encountered (so far) and what we have learned in the process.
Newton: Component Model
I scanned through it but hardly understand it. Too abstract.
Newton: Component Model
I scanned through it but hardly understand it. Too abstract.
Page 1 | Next >>
