| Enterprise Java Community: J2EE Patterns Forum |
[Site]
[XML]
|
|
Description: Enterprise Java Community is a developer community, containing up-to-date news, discussions, patterns, resources, and media
Last Update: 06:47:30 03/04/2006
|
| |
Additional Info
First Fetched: 00:18:32 01/31/2004
Last Updated: 06:47:30 03/04/2006
Headlines
<<
>>
1
2
3
|
|
|
Project described in [1],[2] has been modified to work asstandalone OC4J's Web Application on remote Linux Box.View references [1],[2] in pattern section.
|
|
|
|
|
|
What is Design Pattern?where can i get good documentation for Design Pattern
|
|
|
|
|
|
Here I present some refactoring patterns to help people to understand HOW to refactor their programs. I would appreciate all the help you can bring me about the contruction of these.<img src="http://feeds.feedburner.com/techtarget/tsscom/j2eepatterns?g=13"/>
|
|
|
|
|
|
To prevent too much logic from being placed in the JSP page directly which makes things harder to debug as it will be mixed in with other HTML.One other alternative is to create separate pages for each state. However, to reduce code duplication we can put all of the buttons on the same page just hide or show them as needed.
|
|
|
|
|
|
Often in many of the JUnit based test suite(s) it was observered that test data and test cases to execute under the suite(s) are hard-coded with in the program. It will be very difficult if one wants to change the test data or add/remove the test case entries in the suite.
|
|
|
|
|
|
You are iterating over a collection or array using the enhanced for loop, and you need to have access to the iterator or index variable in order to make some operation with it.
|
|
|
|
|
|
You are iterating over a collection or array in a ugly old manner. Solution: Replace the iteration code with a for-each loop
|
|
|
|
|
|
We have a Problem of Data Access to Multiple Data Sources (Siebel,Active Directory , Oracle ) simlatenously. IConnection Interface, which will encapsulate the methods for Data Operation, Add, Update, delete, execute and get. Different type of connection can have the concrete implementation differently
|
|
|
|
|
|
Persistent Domain Objects Pattern gives a solution to the, often-observed, tight-coupling of the persistence and application logic code. PDO decouples those by extracting the details of the persistence implementation and hiding it behind an interface, employing Dependency Injection techniques. The resulting code is cleaner, easier to test, more extensible.
|
|
|
|
|
|
Persistent Domain Objects Pattern gives a solution to the, often-observed, tight-coupling of the persistence and application logic code. PDO decouples those by extracting the details of the persistence implementation and hiding it behind an interface, employing Dependency Injection techniques. The resulting code is cleaner, easier to test, more extensible.
|
|
|
|
|
|
This refactoring introduces an adapter to the code to move data extraction logic to the adapter.
|
|
|
|
|
|
This refactoring introduces an adapter to the code to move data extraction logic to the adapter.<img src="http://feeds.feedburner.com/techtarget/tsscom/j2eepatterns?g=5"/>
|
|
|
|
|
|
This pattern implements the idea of viewstate used in ASP.NET application. It addresses the problem of storing the viewing state at the presentation layer especially when dynamic complex user interaction is required.
|
|
|
|
|
|
This pattern implements the idea of viewstate used in ASP.NET application. It addresses the problem of storing the viewing state at the presentation layer especially when dynamic complex user interaction is required.
|
|
|
|
|
|
Problem: synchronizing CRUD operations over mutiple data sources (i.e. multiple databases)Solution: The Synchronizing Data Access Object (SDAO) design pattern adds a second layer of abstraction. Extending the traditional Data Access Object design pattern, the SDAO acts on multiple Data Sources, rather than one specific DataSource.
|
|
|
|
|
|
Problem: synchronizing CRUD operations over mutiple data sources (i.e. multiple databases)Solution: The Synchronizing Data Access Object (SDAO) design pattern adds a second layer of abstraction. Extending the traditional Data Access Object design pattern, the SDAO acts on multiple Data Sources, rather than one specific DataSource.
|
|
|
|
|
|
pls give methe Difference between FrameWork and DesignPatternrelation between FrameWork and DesignPattern
|
|
|
|
|
|
This web pattern defines a cross domain cookie provider to get around the two dot rule for cookie domains. The pattern is implemented using pure HTTP and is totally transparent to all upstream and downstream participants. Useful for implementing single sign on, browser tagging, or sessioning. Cross domain cookies cannot contain volatile data.<img src="http://feeds.feedburner.com/techtarget/tsscom/j2eepatterns?g=8"/>
|
|
|
|
|
|
This web pattern defines a cross domain cookie provider to get around the two dot rule for cookie domains. The pattern is implemented using pure HTTP and is totally transparent to all upstream and downstream participants. Useful for implementing single sign on, browser tagging, or sessioning. Cross domain cookies cannot contain volatile data.
|
|
|
|
|
|
Unlike EJB CMP, Hibernate allows you to persist private fields and proprerties in objects. This allows you to encapsulate some domain (business) logic in your persistent objects, avoiding the <a href="http://www.martinfowler.com/bliki/AnemicDomainModel.html" target="_blank">anemic domain model"</a> antipattern.
|
|
|
|
|
|
Unlike EJB CMP, Hibernate allows you to persist private fields and proprerties in objects. This allows you to encapsulate some domain (business) logic in your persistent objects, avoiding the anemic domain model" antipattern.
|
|
|
|
|
|
This pattern (it's more of a framework, based on a simple concept) adresses multi-profile (users, roles, groups, etc) access to applications. It allows to define "actions" that will be executed at run-time for some "objects" in the application and for some "profiles".This allows for example to have custom web pages upon who's browsing them with a clear design.
|
|
|
|
|
|
a combination of known patterns (Service Locator, business delegate and EJB home factory) with a little extra,the EJBServices class encapsulates ejb's Jndi Names and Home Clases
|
|
|
|
|
|
This pattern combines EJB Command pattern with EJB 2.1 Timer service. With it you can execute arbitrary scheduled tasks with just one Session bean.
|
|
|
|
|
|
Dynamic UI and Business Tier
|
|
|
|
|
|
A problem met by many application designers - Distributed Collections and Sets - This paper focus on an example from the financial world, the order book and how it can be implemented using JavaSpaces. A mission-critical data repository, which requires access in very short time and may be scanned and searched thousands of times per second, requires a unique and original approach, here is one.
|
|
|
|
|
|
Forget DAO classes since now. Use GQO best practice to avoid unnecessary development of DAO classes and also gain more.
|
|
|
|
|
|
This lets ur webapplication single user login enabled.This lets a user cannot login if he has already logged in using another broswer or even another client
|
|
|
|
|
|
The Pattern tries to address a problem of handling transactions across user interactions.
|
|
|
|
|
|
An aspect is a cross-cut concern through entire application. There's been contraversy on the best approach (AOP, Spring etc ) to achieve implementation of the cross-cut concern. Here's another take on it using plain design pattern. The pattern itself is not much, but main purpose is to explicitly acknowledge that this is indeed a formal pattern that can be used in software development.
|
|
|
|
