bookmarks  36

  •  

    We have used Spring Roo in a web project and show how we generated an early prototype and transistioned to early development and then to production code.
    7 years ago by @gresch
    (0)
     
     
  •  

    spring-roo-addons Useful SpringRoo addons that provide XML/JSON binding (jaxb), HTTP content negotiation, RESTful configurations and more
    7 years ago by @gresch
    (0)
     
     
  •  

    When using JUnit in Spring there are several features added that many developers are not aware of. First, if you are including the Spring Context in your tests, it becomes an Integration Test, no longer a Unit Test.
    8 years ago by @gresch
    (0)
     
     
  •  

    "WaveMaker makes Java Point and Click — you can build a web application without using a single acronym!"
    8 years ago by @gresch
    (0)
     
     
  •  

    Another article from vmware's CTO on Plattform as a Service
    8 years ago by @gresch
    (0)
     
     
  •  

    Welcome to JaValid JaValid is an open source framework for validating your Java business objects. JaValid is licensed under the Eclipse Public License 1.0. JaValid 1.2 is the latest release. JaValid is an annotation-based validation framework, which allows you to annotate your Java objects to introduce validation. JaValid can be used in any type of Java application (standalone application, web application etc). The framework currently provides full integration with the Spring Framework, Java Server Faces, Facelets, and any database. The framework can be extended easily, by means of extensions, and also allows you to add your own validation constraints in addition to the ones shipping with the framework. The framework is documented well (both the source and the general documentation), so check it out. To learn more, have a look on the documentation page. The source and distributions are hosted on sourceforge, go to the downloads directly here. You may also want to check out the weblog, which contains some useful information, including several examples. Have fun using JaValid!
    10 years ago by @gresch
    (0)
     
     
  •  

    The WaveMaker platform consists of two components: WaveMaker Visual Ajax Studio™ for developing rich internet applications and WaveMaker Rapid Deployment Server™ for deploying applications into a standard and secure Java environment.
    10 years ago by @gresch
    (0)
     
     
  •  

    Impala allows you to divide a large Spring-based application into a hierarchy of modules. These modules can be dynamically added, updated or removed. Because Impala-based applications are genuinely modular, they are much easier to maintain than vanilla Spring applications. Impala radically boosts productivity of Spring application development. This is enabled by the dynamic module loading capability, the seamless integration with Eclipse, and the efficient mechanisms for running Spring integration tests, both individually and within suites. When writing applications you only rarely need to restart your JVM, allowing your application changes to be reflected almost instantly. No long restart waits required! Impala also features a build system, based on ANT, and dependency management capabilities, which you can optionally use. For up to date news on development of Impala, see the project blog. Impala is developed under the Apache Licence, Version 2.
    10 years ago by @gresch
    (0)
     
     
  •  

    I have been playing with flex for a couple of weeks now,and i am trying to use flex as the UI and keeping the backend in Java with as usal Spring,Hibernate stack. So in this series i will create a getting started project(CRUD contact management) using Spring,Hibernate/MySQL,Cairngorm as the UI MVC framework,GraniteDS for remoting and Tomcat as the server . For now i will create an eclipse based project and later move that to maven. The base intention of this project is to setup a prototype with all the above technologies defined and explore all the aspects of GraniteDS features to serve as the POC for other developers if they are willing to try it.
    10 years ago by @gresch
    (0)
     
     
  •  

    For application development we use spring and hibernate. For rapid application development there are many pitfalls around. Our mission is to provide a framework that handles all default settings and allows us to quickly start with the development tasks our customers are interested in. So the framework tries to support you by: * Providing a maven based development environment which uses a proven dependency configuration for fast composition of a working base setup. * Several utilities were needed during application development extending functions from other utility libraries, e.g. Apache commons. * Providing a module concept for easy setup and extension of a base application * Providing reusable and extendable components for common tasks such as application setup, user management, security, history and reporting. * Providing a base UI implementation based on JSF/MyFaces/MyFaces Trinidad Where to start For starting have a look at the quick start tutorial. Within this tutorial a small database application is developed using the most important features provided by the framework.
    10 years ago by @gresch
    (0)
     
     
  •  

    Any enterprise-class application that interacts with databases needs to take care of transactional integrity across database tables, databases, and components. Typically you achieve this either by using the heavy plumbing of application servers or by leveraging the Java Transaction API (JTA) at code level. Both approaches have their merits and demerits. In the case of application servers, someone has to pay for all the infrastructure services, but the server platform does provide an out-of-the-box solution for cross-cutting concerns like security, transaction, and persistence. Server infrastructures like those provided by BEA or IBM address the full process associated with architecture, prototype, design, development, packaging, deployment, and monitoring. If instead you go for direct JTA API integration at the application code level, you don't need to pay for the additional server infrastructure, but you may end up with business logic mixed with infrastructure-level code. It is in this context that you need to think of lightweight containers that will help you wire application logic components with infrastructure services like transaction handling without the necessity of having a full-blown application server. Spring is one such lightweight container that uses Aspect Oriented Programming (AOP) techniques for integrating cross-cutting services with components. This article walks you through a running example implemented using a mix of three powerful, complementary J2EE technology frameworks: Spring, Hibernate, and JOTM.
    10 years ago by @gresch
    (0)
     
     
  •  

    Spring, JPA, and JTA with Hibernate and JOTM 2007-04-24 20:35 have been struggling for a couple of hours today to modify a Spring JPA configuration with a single datasource, Hibernate as the JPA provider and the JpaTransactionManager to a configuration with two XA datasources, Hibernate as the JPA provider, and the JtaTransactionManager with JOTM as the standalone JTA provider. since the Spring and Hibernate reference manual and Javadoc documentation merely contain a number of hints on how to configure JPA with a JTA transaction manager and others are struggling as well i decided to post how i finally got it to work.
    10 years ago by @gresch
    (0)
     
     
  •  

    jBPM (Java Business Process Management) is an open source Java framework for managing workflows. This project provides: * A simple standalone Eclipse project for checkout and experimentation * Example jBPM integration with Hibernate, Spring, and Oracle XE (a free download) * Simple JUnit tests for leaning by doing * A companion powerpoint presentation in the downloads section * How-Tos in this Wiki
    10 years ago by @gresch
    (0)
     
     
  •  

    Using a Hibernate Interceptor To Set Audit Trail Properties
    10 years ago by @gresch
    (0)
     
     
  •  

    ***No, no, no - needs HibernateDaoSupport! Bad! *** "The purpose of this framework is to save the time, tedium and possible inconsistency of hand coding DAO layer objects. To this end, the framework provides a generic implementation of DAO layer objects for an application using Spring and Hibernate. The generic implementation can be extended and overwritten on a method-by-method basis for each domain object individually or across the entire layer. This means that it is always possible to write code for an exceptional case, entirely bypassing the framework, yet for the usual case no code needs to be written at all. The framework also builds on top of these generic DAOs with an interface that is easily exposed as a web service or remote object. (At The Revere Group (Open Systems division), we are using this for Adobe Flex and GWT R.I.A.s.) This becomes extremely powerful because of the extensive search options available in the framework. The search capability is what sets this generic DAO implementation apart. It uses a powerful search object with extensive filtering options, sorting, paging and result transformers. The search is simpler to use than Hibernate Criteria objects, and it can be passed to and from remote clients. This greatly simplifies the creation of flexible UI searches and filtered lists."
    11 years ago by @gresch
    (0)
     
     
  •  

    ***No, no, no - needs HibernateDaoSupport! Bad! *** Another promising GenericDao framework: "Generic DAO (a.k.a generic-dao OR gendao) is a Java package which allows a developer to skip writing DAOs for their persistence objects when they are using Spring and JDBC or Hibernate. It is a lightweight ORM package without the loss of control or increase in complexity which is experienced with some of the heavier weight ORM packages. It is designed to make it easier and faster for developers to write their DAOs without having to rewrite the same old boring save/delete/etc functions over and over for each persistent type but also not having to have implementation dependencies in their DAO interfaces. It also allows for good control over which persistent objects are usable within the DAO and is easy to extend so you can add your own DAO methods. Configuration is easily handled via spring configuration but can also be handled programmatically, however, since the package depends on the spring framework you are best off using it with spring. Generic DAO allows a developer to write their persistent objects as POJOs with no dependencies. It supports an approach between the anemic domain model (or service/manager model) methodology and the use of a rich domain model (or heavy DDD). The use of simple POJOs as persistent objects makes it easy to swap around storage mechanisms while allowing the developer to use their model objects throughout their application and even expose them for use by other applications. The package includes functionality for all the basic ORM CRUD type methods along with search methods and batch methods. The JDBC part of the package includes support for caching all the DAO methods (which could also be used with the hibernate part but hibernate has its own caching so you should probably use that). It also includes interceptor points for before and after all read and write methods. For simpler use cases, you can write your POJOs, make them persistent, create your DDL and not have to write a single line of DAO code. The package is built on and depends on the spring framework."
    11 years ago by @gresch
    (0)
     
     
  •  

    Domain Driven Design (DDD) is about mapping business domain concepts into software artifacts. Most of the writings and articles on this topic have been based on Eric Evans' book "Domain Driven Design", covering the domain modeling and design aspects mainly from a conceptual and design stand-point. These writings discuss the main elements of DDD such as Entity, Value Object, Service etc or they talk about concepts like Ubiquitous Language, Bounded Context and Anti-Corruption Layer.
    11 years ago by @gresch
    (0)
     
     
  •  

    Anvil is an Open Source Framework for creating Enterprise Portals with Flex as the Client and Java as the back end. It is being developed by Ryan Knight and Holly Edelson of Williams, James Ward of Adobe, Jon Rose of Gorilla Logic and many other great developers at Williams. We wanted Anvil to be simple to deploy in any Java environment so it uses Plain Java Objects (POJO’s), Spring and BlazeDS. This allows it to be run in any application server or servlet container. Here are some of the great features Anvil provides: 1. Single window or multi-window interface (similar to a Portal). 2. A pluggable security module which allows an enterprise to easily integrate their existing security systems into a Flex application. 3. The ability to load modules from different locations in the network for load balancing or fail-over. 4. Authorization and access control at different levels of granularity. This allows individual modules and remote services to be secured differently. 5. Common build scripts and templates to automate the building of Flex and Java. 6. A utility to auto-generating Flex code from Java. 7. A utility to auto-generate the project files for Flex Builder. 8. The ability to expose any Java class as a remote service to Flex And many other great features! We will be writing about Anvil here and would appreciate any feedback or requests!
    11 years ago by @gresch
    (0)
     
     
  •  

    Appistry Enterprise Application Fabric (EAF) is a grid-based application platform that dramatically simplifies the development and deployment of highly scalable applications in Java, Spring, .NET or C++. Unlike traditional application servers, Appistry EAF is built from the ground up for scalability. And unlike traditional grid computing, it's extremely easy to fabric-enable your applications. With Appistry EAF, customers are able to quickly and inexpensively bring new capabilities to market, with the agility, reliability and scale demanded by their businesses.
    11 years ago by @gresch
    (0)
     
     
  •  

    Pax Construct provides a Swiss Army® knife for OSGi that helps you rapidly create, build, manage and deploy many types of OSGi bundles. The core functionality is provided by a flexible Maven2 plugin that enhances and streamlines the Maven build process for OSGi, along with intelligent archetypes that adapt according to your needs. Unix and Windows scripts are available to further reduce the need to remember (and type) long command strings. These scripts come with basic help text and can bootstrap themselves from an empty system. You can use Pax Construct to create a simple first bundle in less than a minute, all the way up to managing a Spring Dynamic Modules for OSGiTM system.
    11 years ago by @gresch
    (0)
     
     

publications  

    No matching posts.
  • ⟨⟨
  • ⟩⟩