- This topic has 3 replies, 3 voices, and was last updated 13 years, 3 months ago by
.
-
Posts
-
Using MyEclipse 10 for Spring. While doing scaffolding i made sure to uncheck a few fields that I don’t want to show in UI. For example, ID or Version fields should not be presented. However, when I finished scaffolding and compiled new GWT app, the fields were in the UI. I can take them out manually, but then I have to go into Requestor and Service implementation and Domain, etc to remove fields.
It also appears that scaffolding does not implement 1:M reslationship properly. I have 1:M relationship defined in my db via Foreign Keys. Even when I did ER diagram in a new perspective, it showed proper relationship. However, scaffolding implements 1:M and then M:M in the parent object.
Please help
Hi avishnev,
I’ve tried this in my ME4S 10 environment and am not seeing the same behavior. One thing to note is that when you un-check fields on the “Customize User Interface” panel of the scaffolding wizard, the change only applies to the list views. By design all fields continue to show on the edit forms.
Can you confirm whether the un-checked fields do or do not show in the lists?
Regarding the 1:M relationship. I scaffolded two tables that had a foreign key relationship. The tables are Alpha and Beta where the Beta table contains the key from the Alpha table. Therefore each Beta can have only one Alpha but each Alpha can have many Betas. This is a 1:M relationship from Alpha to Beta. At runtime in my scaffolded application, if I select an Alpha, I see a list of Betas (1:M). If I select a Beta, I can only select one Alpha (M:1). These are the expected user interface elements. If you’re seeing something different than that, I’d need more specifics on how to reproduce the problem.
Hi ,
I had same issue. I don’t want to ID fields in UI. how are the places do i need change it?
Do you guys have any customization documentation?HELP….
Sai
The ID’s are in the edit forms to avoid the generated code having to make possibly invalid assumptions about how the keys should be set in your data model. The GWT UI scaffolding is intended to generate an example of a user interface that you can modify to suit your needs.
Your options are to modify the generated code or modify the jet templates used to generate the code. If you modify the code templates, then you’ll need to deal with any of the ramifications of your changes, such as knowing how and where to set the ID values for your entities.
As far as modifying the templates goes, here is a tutorial that should get you started:
You should be able to identify any code templates that need to be changed by finding the associated code in the generated app and then deducing the template that created that code.
