I think the best way to find out if your approach is reasonable is to
try it and see if it works. ;-)
Matt
On 12/1/07, Mani_N <[EMAIL PROTECTED]> wrote:
>
>
> Please let me know what am thinking is a good approach or not? And please
> let me know if there are any better approaches for achieving
>
Please let me know what am thinking is a good approach or not? And please
let me know if there are any better approaches for achieving
this
Mani_N wrote:
>
>
> Thanks Matt.
>
> I am thinking of following below approach for a project we are going to
> start. Please let me know if
Thanks Matt.
I am thinking of following below approach for a project we are going to
start. Please let me know if this approach wont make any problems in future
or is there any better approach of achieving this.
1. Identify all the entities and their relations(like one-to-many,
many-to-one etc.
You shouldn't need to generate DAOs, Managers, etc. for the child. If
you're managing the object from the parent, you should be able to use
the Parent's DAO for everything. If you do end up needing a DAO and
Managers for the child, you don't need to write Java code to do that
- you can do i
So how about dao's and manager's that are generated by appfuse:gen for 2
related entities (like parent and child) Will they have support for
this.
Suppose Memotype is Parent and Memorandum is child
How to write a sample test case in core module to test
Memorandum.getMemotype().getMemoTi
Comments below...
On Dec 1, 2007, at 3:06 AM, Mani_N wrote:
Hi,
Environment Used:
Maven: 2.0.7
Pattern: Spring MVC Modular
Appfuse: 2.0.1
Java: 1.5
Database: MYSQL
Persistence Framework: Hibernate
I have two tables with following structure..
CREATE TABLE `memotype` (
`memoTitle` varch
Hi,
Environment Used:
Maven: 2.0.7
Pattern: Spring MVC Modular
Appfuse: 2.0.1
Java: 1.5
Database: MYSQL
Persistence Framework: Hibernate
I have two tables with following structure..
CREATE TABLE `memotype` (
`memoTitle` varchar(255) NOT NULL,
`memo_desc` varchar(50) default NULL,
PRI
