Mario,

The bugs encountered here are known issues, but it sounds like you've found a solution. If you'd like to modify your local forge installation so that you can generate working scaffolding for the time being, I'd suggest editing the following JAR files (you'll have to modify the JAR contents.

$FORGE_HOME/lib/forge-scaffold.jar/org/jboss/seam/forge/jpa/PersistenceUtil.jv
$FORGE_HOME/lib/forge-scaffold.jar/org/jboss/seam/forge/scaffold/templates/view.xhtml

Or, you can check out the Alpha3 branch of the code and build a new JAR locally with your changes:

https://github.com/seam/forge/tree/1.0.0.Alpha3

Also, if you are feeling generous, could you upload your modified, working files to the related issues? :) That would help us fix this for the next release!

https://issues.jboss.org/browse/SEAMFORGE-47
https://issues.jboss.org/browse/SEAMFORGE-48

Thanks very much!
~Lincoln

On Tue, Apr 12, 2011 at 5:48 PM, Mario Marques Junior <mario@scale.com.br> wrote:
I used forge to create an entity in my project, and I have to do changes
to work properly.

In view.xhtml, I put the Save button inside <c:if test="rendered
condition"> (removing the rendered condtion from the <h:commandButton>),
also send parameter edit=false to the Cancel button.

In PersistenceUtil.java, I put getEntityManager().joinTransaction(); on
delete() and save().

I want to know if I should add other configuration so that I can stick
with the default code generated or if I have to do this changes for
every scaffolding.

Forge 1.0.0.Alpha3
JBossAS 6
Hibernate

Thanks,

Mario Marques Junior

_______________________________________________
forge-users mailing list
forge-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-users



--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"