Struts using DAO Design Pattern Tutorail

Can anybody give me a link for the Struts using DAO Design Pattern tutorial
sample tutorial

http://javaboutique.internet.com/tutorials/ApacheDAOs/
Found by using google: strust dao pattern tutorial
There are more good links using that search...

Similar Messages

Struts using DAO Design Pattern ..?Please give an example..... URGENT......

Dear all,
I have to develop an application in Struts by using DAO design pattern ..........
Please give an example on Struts using DAO...................
Thank you
Please

I'm glad you asked. It means Read The Flaming Manual. That'd be the struts manual by the way.

How to generate report from two tables using DAO design pattern?

Hi,
Iam using struts with DAO pattern for my application. According to DAO design im creating model class for each table in my database with getter,setter methods. i have no problem when im generating report from one table. but if have i have to join two tables whatis the better way for doing that? is it good practise to create a new model contains properties from both the tables?
Please help me
Thanks in Advance
Rajesh

Dear Rajesh,
As per the pattern you are creating equivalent java objects for every database table under consideration in which each db field will become a private attribute and public getter and setter methods.
If you have to display data from one table the above approach is sufficient enough.
But in case your database is normalised ..lets take an example of Bank having Branch and Accounts tables. We dont need to repeat the whole information of the branch for every account in that branch. so we prefer to have a branch id in that table....this approach lot of insertion/deletion/updatation anomlies that may exists with the database...
now lets come back to our topic....we shall create two java objects 1) Branch 2) Account.....
When ever u just need to display simple report u can do it staright forward,,,,,now if u want to display branch information along with the account information....the two objects just created are not sufficient
So i suggest u the following approaches
1) Create an attribute of type Branch in the Accounts Object......
This shall serve the purpose of displaying the Btranch information
2) Create a collection object of type ( Vector or ArrayList) which can have objects of Account in the Branch Object,,,
Now its upto u how shall u fill up the objects with appropriate sql queries.
The method that i mentioned is followed by Oracle Toplink and Hibernate ....which provide Object to relation mapping layers.
Any queries ...revert back to me...
Mahesh

DAO design pattern & Transaction boundaries

I am using a tool to generate a JDBC tier that applies the DAO design pattern. However, the generated code is based on "autocommit"-strategy, i.e. there is no conn.setautocommit(false)-statement in the code.
I have added statement so that I can handle the transaction by myself. The DataAccessObject-implementation class does however close the connection before returning. I would like to execute the commit outside of the DAO-implementation.
Anyone who have been experiencing the same problem?
Best regards
Lasse Bergstr�m

I'm not sure if I fully understand your question.
However, we usually implement such a scenario by doing autocommit false on the connection object and then passing it to the DAO. Finally do a commit on the connection in the calling class.

DAO Design pattern

Hi,
what is the advantages of DAO Design pattern over other design patterns?
Can anybody tel me

valooCK wrote:
NANDA wrote:
Hi,
what is the advantages of DAO Design pattern over other design patterns?
Can anybody tel methe answer is none!
DAO stands for data access object, it is a non oo pattern, oo is data centric, it makes sense for data to access data. it is something created by poor procedural minds who can never understand what oo is.
you may occasionary use it as a collection of functionalities or utilities, but thou shalt never use in as a pattern in oop!There are as-yet undiscovered tribes living in the Amazon, who knew you were going to say that
@OP: Please ignore this troll, he doesn't even understand the very basics of OO, as can be demonstrated in the following thread
http://forum.java.sun.com/thread.jspa?threadID=5273397&tstart=0
Just ignore him. He only wants attention. He hasn't got the faintest idea how to write even "Hello World", let alone actually do any OO design

Calling standard funtion module in BSP using MVC Design pattern

HI Everyone,
I am trying to create one BSP application using MVC Design pattern,
I want to call standard function module LSO_TRAINING_GET_DETAIL_C, in my BSP Model class,
can any one tell me how to do this?
I want to do the model binding also,like i want to retrive data on the frontend bsp screen from the above function module.
Thanks,
Vinay
Edited by: vinay kumar on Jul 3, 2008 12:02 AM

Hi Vinay,
If you want to call the FM on some user action , ie on some event than you have to do it in
DO_HANDLE_EVENT method of your controller class.
For eg. if you want to call the FM on click of the button, you can do some thing like:
DATA: button_event TYPE REF TO cl_htmlb_event_button.
IF htmlb_event IS NOT INITIAL.
IF htmlb_event->name = 'button'.
      button_event ?= htmlb_event.
     IF htmlb_event->server_event CP 'press'.
          call function LSO_TRAINING_GET_DETAIL_C
                                    exporting
                                     param_exp = val1
                                    importing
                                       param_imp = val2.
              endif.
      endif.
endif.
here press is the OnClick event of the button.
Now you can use this VAL2 , in the view .You can use the HTMLB:TABLEVIEW element , if your FM's importing param is a table.
Hope it helps a bit,
BE,
Anubhav.

How can I develop a web application using EJB design pattern?

I have searched over the web and found quite a lot of tutorials on how to use the EJB design pattern.
I know that there will be a home interface, EJB object interface and a SessionBean.
But the tutorials often only cover a single class, this made me unable to get a complete picture of how EJB design pattern can be implemented into a whole system.
I am now required to devleop an online shopping web application using EJB and JSP page.
I think I will need to create a lot of classes: Member, ShoppingCart, Product...etc.
What I want to ask is that, do I need to create a home interface, EJB object interface and a SessionBean for each of these classes?
I really need some ideas on how to develop this system using EJB + JSP pages.
Many thanks to you all.

For every EJB that you want to create, you will need to code a home and remote interface and a bean class.
You could start getting your ideas here
http://www.theserverside.com/books/wiley/masteringEJB/
http://www.coreservlets.com

Are there any Client/Server Application (using sockets) design patterns?

Hi,
The title of the post nearly says it all. I am searching for different design patterns related with the development of a client/server application. I understand that there must be any different ways on how a client/server application can be developed.
Regards,
Sim085
Disclaimer:
When I enter in the Socket forum on this site I recieve this message "Thank you for any participation in this forum. Due to a lack of relevant activity, we have decided to archive this forum on June 16, 2006. For future posts on this topic, we suggest you use the Networking forum" and I am not allowed to create a new post! However I can see posts done yesterday! All i did is add the forum in 'my forums'. Does this happen to you people as well?

Hi Sim085...How are you?
So look this:
http://forum.java.sun.com/thread.jspa?threadID=5148926&tstart=75
I don�t know if is what you want...but I hope in this^^
Ok man...If you have one example for help you is better.
[ ]

Using DAO ,TO Pattern without EJB

Hi,
I am developing a web application without EJB. I understand those patterns need not use EJB framework. However, it smees to me that without EJB, the role of TO may be simpler.
In my design, the meaning of TO is to separate the layer between business tier and data access tier. Upon doing some back-end enquiry, the DAO create related TO which can be translate to the business / veiw objects. And the caching will be done on Web tier but not TO layer instead.
Am I right? Would you please give some comments? Thanks a lot.

What is the best way to allow the client to
interact
with Entity objects, without exposing them. ShouldI
implement Value objects that are easily serialized
for transfer across the network?
If you are not using EJB or a distributed
architecture, you do not need DTO's or VO's. They
are an odious construct used to obviate the
shortcomings of remote method calls over anetwork.
I strongly disagree.
They are an obvious and easy model used when the
following characteristics of a system exist.
- Different layers.
- Related data items that are moved throughout the
layers.
- Different usage of the related data items by
different layers.
Yes, I agree. Note the qualification 'if you are not using a distributed architecture'.
None of that has anything to do with remote method
calls over a network. Point of fact the first time I
used them was in a stand alone application with no
network traffic except that needed by the database
driver itself.
Simply create your domain model objects as POJO's
s (plain ole Java objects). Persist and retrieve
your objects via DAO's (data access objects).Your
service layer (facade) will sit on top of thedomain
model, encapsulating method calls into logicalunits
of work.
And how exactly do you move the customer
name/customer address from the DAO to the GUI level?I am assuming the dedicated remoting product the OP specifid, Hessian, will handle moving between the tiers, or at least between the controller/view and the business tier.
- Saish

JPA DAO Design Pattern

Hi all,
I have one abstract DAO class and every sessionbean DAO will extend it.
here is sample code.
public abstract SuperDAO{
@PersistenceContext (unitName = "stars21db")
private EntityManager em;
public getEM(){
return em;
Here is Session Bean DAO
@Stateless
@Local
public class CapDaoSessionBeanBean extends SuperDAO implements CapDaoSessionBeanLocal {
public CapDaoSessionBeanBean() {
public getCustomer(){
}

Code is fine, but the wording isn't the right one. You are about to build a Facade. DAO were originally build as the ones who know how to interact with the database, with JPA this is handled by the EntityManager. Therefore the DAO pattern doesn't apply...
--olaf

DAO object Design Pattern

i have to develop a web base applecation which is database indepandent, to achive this functionlity i have to use DAO design pattern.
can some one explane me more about this............................

Data Access Object:
Java BluePrints - Data Access Object
JavaWorld: Write once, persist anywhere

ANN: New Design Pattern (DAO)

Hello,
Thanks for your overwhelming response to our previous sample applications demonstrating various [url http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/index.html]design patterns.
Continuing with the series, this month we have showcased the [url http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/dataaccesstier/index.html]Data Access Object (DAO) Design Pattern which is considered as a best practice for applications accessesing the database or the underlying persistence layer from the business tier.
The DAO implements the access mechanism required to work with the data source. The data source could be a persistent store like an RDBMS, an external service like a B2B exchange, a repository like an LDAP database, or an XML Repository. Using the scenario of web based News Application, this sample application demonstrates the effective use of this pattern.
[url http://www.oracle.com/technology/sample_code/tech/java/j2ee/designpattern/dataaccesstier/index.html]Download the sample application to learn more about this pattern.
More Sample Applications are available at [url http://www.oracle.com/technology/sample_code/index.html]
http://www.oracle.com/technology/sample_code/index.html
Thanks,
Rajat
OTN Team

Hi
This is because you are not using the latest jdbc driver version. Either use the latest ojdbc14.jar downloadable from the location given in the readme(Oracle Database 10g (10.1.0.2.0) drivers),
Or simply comment this part in the code.
Also you may just replace the close method call with ods=null;
Hope this helps
Shrinivas

Best architecture and design pattern to use

I am currently designing a moderately sized LabView application and cannot decide on the best architecture/design pattern or combinations thereof to implement.
The program basically polls an instrument connected to a serial port continuously at a 2-10Hz rate. When operator clicks a button to start a run, the polled data is then filtered, has math functions performed on the data, writes collected data to files, and produces reltime graphs and calculates point-by-point statistics. At the completion of a run, some additional data files are written. I pretty much know how to accomplish all these tasks.
What is also required is main-vi front panel interaction by the operator to access a database (via a C# dll with .Net) to query for specifications to apply in order to determine pass/fail status. Setup conditions also need to be changed from time to time by the operator and applied to the data in real time (ie- a measurement offset). I have prototyped the database portion successfully thus far.
For the main vi, I started off using the Top Level Application Using Events design pattern (Event structure within a while loop). Copious use of bundled clusters and shift registers keep the database data updated. I cannot figure out how to have the top level vi concurrently poll the serial device as outlined above. The Event structure is only active when defined control values change, and use of a timeout is no help since it prevent data from being collected while the user is accessing the database. All database and setup parameters must be applied to the data as it comes in from the serial port. Error trapping/recovery is a must.
I believe what I need is two parallel processes running under my main vi (one for database and setup, the other for polling and data processing/display, but what would be the preferred choice here?
Revert back to a polled loop in lieu of Events, use notifiers, occurrences, user-defined events, Producer-consumer loops?
It�s been about 3 years since I have had an application on this level (which used a state machine architecture), and a lot has changed in LabView (using 7.1 Prof Devel). I am currently having a mental block while trying to digest a lot of features I have never used before.
Suggestions Welcome!
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

I suggest a (3) state machine(s) architecture. The first is the user interface. Your main VI is a good start. Another state machine handles the instrument I/O (your serial polling). The third handles all data processing. The three loops run independently. Each has a wait to allow LV's scheduler to share CPU time among the loops. I like queues or functional globals for inter-loop communications.
This allows a lot of flexibility. Each portion can be tested alone. Each can have different timing and priority.
Spend some time thinking about what needs to be done and plan the structure carefully before you do any coding (except for little test programs to try new ideas).
I also like Conway and Watts "A Software Engineering Approach to LabVIEW", published
by Prentice Hall.
Lynn

ABAP objects design patterns

hi all,
 can any one send me the Design patterns used for ABAP objects programming in ABAP. eg mvc and sample code which uses the design patterns
cheers
senthil

Of course that program is not an object design pattern
(Its just a little ABAP Objects syntax demo that I wrote years ago
I don't know about a list of OO design patterns implemented in ABAP Objects.
A very simple one, a Singleton might look like this:
* cl_singleton: Eager Variant
CLASS cl_singleton DEFINITION FINAL
 CREATE PRIVATE.
PUBLIC SECTION.
 CLASS-METHODS: class_constructor,
 get_singleton RETURNING VALUE(singleton)
 TYPE REF TO cl_singleton.
PRIVATE SECTION.
 CLASS-DATA singleton TYPE REF TO cl_singleton.
ENDCLASS.
CLASS cl_singleton IMPLEMENTATION.
METHOD class_constructor.
 CREATE OBJECT singleton.
ENDMETHOD.
METHOD get_singleton.
 singleton = cl_singleton=>singleton.
ENDMETHOD.
ENDCLASS.
cl_singleton: Lazy Variant
CLASS cl_singleton DEFINITION FINAL
 CREATE PRIVATE.
PUBLIC SECTION.
 CLASS-METHODS get_singleton RETURNING VALUE(singleton)
 TYPE REF TO cl_singleton.
PRIVATE SECTION.
 CLASS-DATA singleton TYPE REF TO cl_singleton.
ENDCLASS.
CLASS cl_singleton IMPLEMENTATION.
METHOD get_singleton.
 IF cl_singleton=>singleton IS INITIAL.
 CREATE OBJECT cl_singleton=>singleton.
 ENDIF.
 singleton = cl_singleton=>singleton.
ENDMETHOD.
ENDCLASS.

Design Patterns, The Decorator

When trying to implement the classic decorator design patterns your decorator executable might look like this: 
<pre>
METHOD validate.
 DATA: Validator TYPE REF TO validation_manager.
 CREATE OBJECT:
 Validator TYPE validation_manager.
 ,Validator TYPE validate_format EXPORTING x_validator = Validator
 ,Validator TYPE validate_values EXPORTING x_validator = Validator
 ,Validator TYPE validate_relation_input EXPORTING x_validator = Validator
 ,Validator TYPE validate_relation_database EXPORTING x_validator = Validator.
 me->lst_result = validator->validate( me->lst_data ).
 WRITE: / 'Processing Validate Activity'.
ENDMETHOD. "validate</pre> 
The validate method ends up in endless resurcion in the memory. The reason is that I'm using the same variable as the resulting instanse and as parameter. It seems like the constructor treats both the result and the parameter as the same field/instanse regardless import parameter such as VALUE/REFERENCE. If I change the method to use an extra field in the method validate like:
 <pre>
METHOD validate.
 DATA:
 validator TYPE REF TO validation_manager
 ,recursive TYPE REF TO validation_manager.
 CREATE OBJECT validator TYPE validation_manager.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_format
 EXPORTING x_validator = recursive.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_values
 EXPORTING x_validator = recursive.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_relation_input
 EXPORTING x_validator = recursive.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_relation_database
 EXPORTING x_validator = recursive .
 recursive ?= validator.
 me->lst_result = validator->validate( me->lst_data ).
 WRITE: / 'Processing Validate Activity'.
ENDMETHOD. "validate</pre> 
Now the decorator engine works, but why does the first implementation not work when the same one executes fine in php, c++, delphi, java and other languages. 
If you do not know what I'm trying to discuss, look up "Design Patterns - Simply", and jump to the chapter about the decorator design pattern. I'm trying to use this design pattern for a validation manager within my Business Process Engine, which needs to be able to configure what types of validation needed for on specific process (BPMN). 

Hi Matt, Thanks for the formatting..:) I will post the complete program as it's only a prototype program. Trying to get the format under control.
</body>
Report ZDP_DECORATOR_XMP01
REPORT zdp_decorator_xmp01.
parameters: bestimpl TYPE boolean_01 default 0.
TYPES:
BEGIN OF processdata
 ,name TYPE char30
 ,street TYPE char30
 ,zip TYPE char5
 ,city TYPE char30
 ,email TYPE char50
 ,phone TYPE char20
,END OF processdata
,BEGIN OF result
 ,msgid TYPE msgid
 ,msgtyp TYPE msgty
 ,msgno TYPE msgno
 ,status TYPE char1
,END OF result.
CONSTANTS:
true TYPE boolean_01 VALUE 1
,false TYPE boolean_01 VALUE 0.
CLASS validationmanager DEFINITION
CLASS validation_manager DEFINITION.
PUBLIC SECTION.
 METHODS:
 validate
 IMPORTING
 x_data TYPE processdata
 RETURNING
 value(y_result) TYPE result.
ENDCLASS.
CLASS validationmanager IMPLEMENTATION
CLASS validation_manager IMPLEMENTATION.
METHOD validate.
 WRITE: / 'Common validation'.
ENDMETHOD. "validate
ENDCLASS.
CLASS Validate_Decorator DEFINITION
CLASS validate_decorator DEFINITION INHERITING FROM validation_manager ABSTRACT .
PUBLIC SECTION.
 DATA: validator TYPE REF TO validation_manager.
ENDCLASS.
CLASS validate_format DEFINITION
CLASS validate_format DEFINITION INHERITING FROM validate_decorator.
PUBLIC SECTION.
 METHODS:
 constructor
 IMPORTING value(x_validator) TYPE REF TO validation_manager
 ,validate REDEFINITION.
ENDCLASS.
CLASS validate_format IMPLEMENTATION
CLASS validate_format IMPLEMENTATION.
METHOD constructor.
 CALL METHOD super->constructor( ).
 me->validator = x_validator.
ENDMETHOD. "constructor
METHOD validate.
 y_result = validator->validate( x_data ).
 IF y_result-status IS INITIAL.
 WRITE: / 'Now doing the format checks'.
 ENDIF.
ENDMETHOD. "validate
ENDCLASS.
CLASS validate_values DEFINITION
CLASS validate_values DEFINITION INHERITING FROM validate_decorator.
PUBLIC SECTION.
 METHODS:
 constructor
 IMPORTING value(x_validator) TYPE REF TO validation_manager
 ,validate REDEFINITION.
ENDCLASS.
CLASS validate_values IMPLEMENTATION
CLASS validate_values IMPLEMENTATION.
METHOD constructor.
 CALL METHOD super->constructor( ).
 me->validator = x_validator.
ENDMETHOD. "constructor
METHOD validate.
 y_result = validator->validate( x_data ).
 IF y_result-status IS INITIAL.
 WRITE: / 'Now doing the values checks'.
 ENDIF.
ENDMETHOD. "validate
ENDCLASS.
CLASS validate_relation_input DEFINITION
CLASS validate_relation_input DEFINITION INHERITING FROM validate_decorator.
PUBLIC SECTION.
 METHODS:
 constructor
 IMPORTING value(x_validator) TYPE REF TO validation_manager
 ,validate REDEFINITION.
ENDCLASS.
CLASS validate_relation_input IMPLEMENTATION
CLASS validate_relation_input IMPLEMENTATION.
METHOD constructor.
 CALL METHOD super->constructor( ).
 me->validator = x_validator.
ENDMETHOD. "constructor
METHOD validate.
 y_result = validator->validate( x_data ).
 IF y_result-status IS INITIAL.
 WRITE: / 'Now doing the relation input checks'.
 ENDIF.
ENDMETHOD. "validate
ENDCLASS.
CLASS validate_relation_database DEFINITION
CLASS validate_relation_database DEFINITION INHERITING FROM validate_decorator.
PUBLIC SECTION.
 METHODS:
 constructor
 IMPORTING value(x_validator) TYPE REF TO validation_manager
 ,validate REDEFINITION.
ENDCLASS.
CLASS validate_relation_database IMPLEMENTATION
CLASS validate_relation_database IMPLEMENTATION.
METHOD constructor.
 CALL METHOD super->constructor( ).
 me->validator = x_validator.
ENDMETHOD. "constructor
METHOD validate.
 y_result = validator->validate( x_data ).
 IF y_result-status IS INITIAL.
 WRITE: / 'Now doing the relation database checks'.
 ENDIF.
ENDMETHOD. "validate
ENDCLASS.
CLASS process_execution DEFINITION
CLASS process_execution DEFINITION.
PUBLIC SECTION.
 METHODS:
 startevent
 ,getdata
 ,validate
 ,process
 ,endevent.
PRIVATE SECTION.
 DATA:
 lst_data TYPE processdata
 ,lst_result TYPE result.
ENDCLASS. "process_execution DEFINITION
CLASS process_execution IMPLEMENTATION
CLASS process_execution IMPLEMENTATION.
METHOD startevent.
 WRITE: / 'Processing startevent'.
ENDMETHOD. "startevent
METHOD getdata.
 me->lst_data-name = 'Hans Andersen'.
 me->lst_data-street = 'H.C Andersens Boulevard 112'.
 me->lst_data-zip = '1557'.
 me->lst_data-city = 'København'.
 me->lst_data-email = 'hcATandersen.dk'.
 me->lst_data-phone = '0045-31162211'.
 WRITE: / 'Processing Get_Data Activity'.
ENDMETHOD. "getdata
METHOD validate.
 DATA:
 validator TYPE REF TO validation_manager
 ,recursive TYPE REF TO validation_manager
 IF bestimpl = true.
 CREATE OBJECT:
 validator TYPE validation_manager
 ,validator TYPE validate_format EXPORTING x_validator = recursive
 ,validator TYPE validate_values EXPORTING x_validator = recursive
 ,validator TYPE validate_relation_input EXPORTING x_validator = recursive
 ,validator TYPE validate_relation_database EXPORTING x_validator = recursive.
 ELSE.
 CREATE OBJECT validator TYPE validation_manager.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_format
 EXPORTING x_validator = recursive.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_values
 EXPORTING x_validator = recursive.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_relation_input
 EXPORTING x_validator = recursive.
 recursive ?= validator.
 CREATE OBJECT validator TYPE validate_relation_database
 EXPORTING x_validator = recursive .
 recursive ?= validator.
 ENDIF.
Recursive call of the validate and it's successors
 me->lst_result = validator->validate( me->lst_data ).
 WRITE: / 'Processing Validate Activity'.
ENDMETHOD. "validate
METHOD process.
 WRITE: / 'Processing Process Activity'.
ENDMETHOD. "process
METHOD endevent.
 WRITE: / 'Processing endevent'.
ENDMETHOD. "endevent
ENDCLASS.
CLASS mainapp DEFINITION *
CLASS mainapp DEFINITION.
PUBLIC SECTION.
 CLASS-METHODS:
 main.
ENDCLASS.
CLASS mainapp IMPLEMENTATION *
CLASS mainapp IMPLEMENTATION.
METHOD main.
 DATA:
 p89 TYPE REF TO process_execution.
 CREATE OBJECT p89.
 p89->startevent( ).
 p89->getdata( ).
 p89->validate( ).
 p89->process( ).
 p89->endevent( ).
ENDMETHOD.
ENDCLASS.
START-OF-SELECTION.
mainapp=>main( ).
Edited by: Matt on Dec 22, 2009 2:03 PM Fixed formatting

Struts using DAO Design Pattern Tutorail

Similar Messages

Maybe you are looking for