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,
  PRIMARY KEY  (`memoTitle`)
) ENGINE=InnoDB;

CREATE TABLE `memorandum` (
  `fromPer` varchar(255) NOT NULL,
  `to_person` varchar(50) default NULL,
  `memoTitle` varchar(255) NOT NULL,
  PRIMARY KEY  (`fromPer`),
  KEY `memoTitle` (`memoTitle`),
  CONSTRAINT `memorandum_ibfk_1` FOREIGN KEY (`memoTitle`) REFERENCES
`memotype` (`memoTitle`) ON DELETE CASCADE
) ENGINE=InnoDB;

Am creating entities using appfuse:gen-model. Am getting the two entities
but by default am getting id generators on top of get methods of primary
keys whereas they should not be auto generated values. Anyway am removing
those generator strategies from the primary key fields and using appfuse:gen
in core and web modules for generating the code. 

The test cases were failing in web module, so i used -Dmaven.test.skip=true
while mvn install

And given the command mvn cargo:start -Dcargo.wait=true for starting the
tomcat........... and opened the browser.

I was expecting a combo box for memoTitle in memorandumForm.html screen to
select memoType from memoTypes which are already there. But there is no
field memoTitle at all in that screen. It has only two fields fromPer and
toPer.

Did appfuse doesnt have support for parent child relationships? And is there
a way to specify to consider all entities in com.mycompany.app.model package
like "*" in appfuse:gen instead of using appfuse:gen for each entity in
application?



-- 
View this message in context: 
http://www.nabble.com/Is-it-possible-to-use-parent-and-child-entities-with-appfuse-tf4927572s2369.html#a14103452
Sent from the AppFuse - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to