http://www.bibsonomy.org/rss/tag/javaBibSonomy RSS Feed for /tag/javahttp://www.sonivis.org/brightbyte2008-10-12T09:28:39+02:00visualization social-networks network-analysis java http://www.bibsonomy.org/help/doc/rest-client-javadoc/index.htmllee_peck2008-10-12T02:27:57+02:00bibsonomy api javadoc java Joda-Time provides a complete quality alternative to the JDK date and time classes. At some point however, many projects need to persist these classes to a database. One popular tool for achieving this is Hibernate. To ease the integration of Joda-Time and Hibernate, this sub-project was setup. It aims to provide the classes necessary to persist Joda-Time objects. http://joda-time.sourceforge.net/contrib/hibernate/gresch2008-10-11T22:41:32+02:00hibernate time software frameworks persistence java develop date calendar Joda-Time provides a complete quality alternative to the JDK date and time classes. At some point however, many projects need to persist these classes to a<span class="info">...<span>Joda-Time provides a complete quality alternative to the JDK date and time classes. At some point however, many projects need to persist these classes to a database. One popular tool for achieving this is Hibernate. To ease the integration of Joda-Time and Hibernate, this sub-project was setup. It aims to provide the classes necessary to persist Joda-Time objects. </span></span>***No, no, no - needs HibernateDaoSupport! Bad! *** Another promising GenericDao framework: &#034;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.&#034;http://code.google.com/p/genericdao/gresch2008-10-09T14:00:08+02:00generic hibernate software dao persistence java jdbc/orm/jdo develop spring ***No, no, no - needs HibernateDaoSupport! Bad! *** Another promising GenericDao framework: &#034;Generic DAO (a.k.a generic-dao OR gendao) is a Java package wh<span class="info">...<span>***No, no, no - needs HibernateDaoSupport! Bad! *** Another promising GenericDao framework: &#034;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.&#034;</span></span>http://www.freewebs.com/godaves/javabench_revisited/fsteeg2008-10-08T16:51:42+02:00benchmark performance c++ java (Even then... in 2004...)http://www.idiom.com/~zilla/Computer/javaCbenchmark.htmlfsteeg2008-10-08T16:51:04+02:00benchmark performance c++ java (Even then... in 2004...)With the addition of generics in Java 5, writing a custom DAO for each domain object is no longer required. There are a wide variety of articles on creating generic DAOs, but my current project uses the approach from this IBM DeveloperWorks article. This approach was choses mainly because of the clearly written article and the integration with Spring. You should be able to extend any generic DAO based on Spring to implement the stored procedure configuration.http://dotal.wordpress.com/2008/03/24/calling-stored-procedures-from-a-generic-dao/gresch2008-10-08T09:09:53+02:00hibernate db software article java_ee stored_procedures java develop howto springframework With the addition of generics in Java 5, writing a custom DAO for each domain object is no longer required. There are a wide variety of articles on creatin<span class="info">...<span>With the addition of generics in Java 5, writing a custom DAO for each domain object is no longer required. There are a wide variety of articles on creating generic DAOs, but my current project uses the approach from this IBM DeveloperWorks article. This approach was choses mainly because of the clearly written article and the integration with Spring. You should be able to extend any generic DAO based on Spring to implement the stored procedure configuration.</span></span>Thought I&#039;ve bookmarked this a long time ago... &#034;With the adoption of Java™ 5 generics, the idea of a generic typesafe Data Access Object (DAO) implementation has become feasible. In this article, system architect Per Mellqvist presents a generic DAO implementation class based on Hibernate. He then shows you how to use Spring AOP introductions to add a typesafe interface to the class for query execution.&#034;http://www.ibm.com/developerworks/java/library/j-genericdao.htmlgresch2008-10-08T09:07:42+02:00generic hibernate software article dao java_ee developerworks java develop howto springframework reference Thought I&#039;ve bookmarked this a long time ago... &#034;With the adoption of Java™ 5 generics, the idea of a generic typesafe Data Access Object (DAO) implementat<span class="info">...<span>Thought I&#039;ve bookmarked this a long time ago... &#034;With the adoption of Java™ 5 generics, the idea of a generic typesafe Data Access Object (DAO) implementation has become feasible. In this article, system architect Per Mellqvist presents a generic DAO implementation class based on Hibernate. He then shows you how to use Spring AOP introductions to add a typesafe interface to the class for query execution.&#034;</span></span>http://java.dzone.com/announcements/wiztoolsorg-restclient-21-relelee_peck2008-10-08T03:14:16+02:00BibSonomy api java http://www.bibsonomy.org/help/doc/javaclient.htmllee_peck2008-10-08T03:11:48+02:00BibSonomy api java Annogen is a framework which helps you work with JSR175 Annotations. In a nutshell, Annogen generates a proxy layer in front of your Annotations. This lets you: Override JSR175 Annotation values ...with data from XML or arbitrary plugin code that you write. Migrate JDK1.4 code to JSR175 ...by translating javadoc tags into Annotations Work with popular introspection APIs ...including Reflection, Javadoc-Doclet, QDox, and APT-Mirror.http://annogen.codehaus.org/gresch2008-10-07T17:21:38+02:00software frameworks codehaus java jsr175 develop annotations generation Annogen is a framework which helps you work with JSR175 Annotations. In a nutshell, Annogen generates a proxy layer in front of your Annotations. This lets<span class="info">...<span>Annogen is a framework which helps you work with JSR175 Annotations. In a nutshell, Annogen generates a proxy layer in front of your Annotations. This lets you: Override JSR175 Annotation values ...with data from XML or arbitrary plugin code that you write. Migrate JDK1.4 code to JSR175 ...by translating javadoc tags into Annotations Work with popular introspection APIs ...including Reflection, Javadoc-Doclet, QDox, and APT-Mirror.</span></span>The agimatec tools contain some utilities to enable generation of files, source code etc. from sql files and annotated java classes. The agimatec-dbmigrate tool is a database migration/script execution framework that can execute sql scripts, groovy scripts and provides a lot of features to assist in database schema migration. (tested with Oracle and Postgres) http://code.google.com/p/agimatec-tools/gresch2008-10-07T17:19:52+02:00migration google-code db tools software dba java develop database The agimatec tools contain some utilities to enable generation of files, source code etc. from sql files and annotated java classes. The agimatec-dbmigr<span class="info">...<span>The agimatec tools contain some utilities to enable generation of files, source code etc. from sql files and annotated java classes. The agimatec-dbmigrate tool is a database migration/script execution framework that can execute sql scripts, groovy scripts and provides a lot of features to assist in database schema migration. (tested with Oracle and Postgres) </span></span>This is an early implementation of JSR 303 (Bean Validation), a specification of the Java API for JavaBean validation in Java EE and Java SE. The technical objective is to provide a class level constraint declaration and validation facility for the Java application developer, as well as a constraint metadata repository and query API. This implementation is based on the validation framework of agimatec GmbH, that is in production for more than a year and offers additional features, like XML-based extensible metadata, code generation (JSON for AJAX applications), JSR303 annotation support. For more information refer to the Wiki at Overviewhttp://code.google.com/p/agimatec-validation/gresch2008-10-07T17:18:59+02:00google-code software frameworks validation beans java_ee java develop agimatec This is an early implementation of JSR 303 (Bean Validation), a specification of the Java API for JavaBean validation in Java EE and Java SE. The techni<span class="info">...<span>This is an early implementation of JSR 303 (Bean Validation), a specification of the Java API for JavaBean validation in Java EE and Java SE. The technical objective is to provide a class level constraint declaration and validation facility for the Java application developer, as well as a constraint metadata repository and query API. This implementation is based on the validation framework of agimatec GmbH, that is in production for more than a year and offers additional features, like XML-based extensible metadata, code generation (JSON for AJAX applications), JSR303 annotation support. For more information refer to the Wiki at Overview</span></span>Some general-purpose plugins for the maven2 build tool. For more information refer to the Wiki at Overviewhttp://code.google.com/p/agimatec-maven-plugins/gresch2008-10-07T17:17:31+02:00software maven build-tools java develop plugin Some general-purpose plugins for the maven2 build tool. For more information refer to the Wiki at Overviewhttp://puremvc.org/creckord2008-10-07T14:22:45+02:00mvc component java framework http://wiki.forum.nokia.com/index.php/Category:Javacreckord2008-10-07T14:20:22+02:00j2me phone nokia java mobile 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&#039; book &#034;Domain Driven Design&#034;, 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. http://www.infoq.com/articles/ddd-in-practicegresch2008-10-07T12:47:15+02:00aop information dozer software frameworks ddd article domain java develop spring Domain Driven Design (DDD) is about mapping business domain concepts into software artifacts. Most of the writings and articles on this topic have been bas<span class="info">...<span>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&#039; book &#034;Domain Driven Design&#034;, 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. </span></span>Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many products, not the least of which is jBPM. The best definition of BPM that I&#039;ve found is: &#034;Business Process Management (BPM) is the concept of shepherding work items through a multi-step process. The items are identified and tracked as they move through each step, with either specified people or applications processing the information. The process flow is determined by process logic and the applications (or processes) play virtually no role in determining where the messages are sent.&#034;.http://www.theserverside.com/tt/articles/article.tss?l=jBPMandSpringgresch2008-10-07T12:43:53+02:00information software jbpm article theserverside java jboss springframework methodology bpm Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many pr<span class="info">...<span>Business process management (BPM) – while also its own independent practice / school of thought – is an application of technology that is served by many products, not the least of which is jBPM. The best definition of BPM that I&#039;ve found is: &#034;Business Process Management (BPM) is the concept of shepherding work items through a multi-step process. The items are identified and tracked as they move through each step, with either specified people or applications processing the information. The process flow is determined by process logic and the applications (or processes) play virtually no role in determining where the messages are sent.&#034;.</span></span>Java toolkit which makes DAO manager creating easier. It produced DAO compatible with JPA specification. It has implemented CRUD operations and some features (active, hidden, default, etc.). It also extends standard API for criteria (like Hibernate ones). http://code.google.com/p/generic-dao/gresch2008-10-07T12:29:06+02:00generic hibernate software google dao persistence java develop Java toolkit which makes DAO manager creating easier. It produced DAO compatible with JPA specification. It has implemented CRUD operations and some featur<span class="info">...<span>Java toolkit which makes DAO manager creating easier. It produced DAO compatible with JPA specification. It has implemented CRUD operations and some features (active, hidden, default, etc.). It also extends standard API for criteria (like Hibernate ones). </span></span>Some issues connected with copying objects.http://www.agiledeveloper.com/articles/cloning072002.htmfolke2008-10-06T18:31:21+02:00c++ java oop copy constructor Some issues connected with copying objects.