Injection vs. property

[gstacey]

I'm fairly new to Seam. I have a small project working and I like working with it so far, but I have a best practices type question...

Is it better to inject properties into your beans or just use getters/setters?

e.g.

@Name("groupEditor")
public class EditGroupBean implements EditGroup
{
...
 private Group myGroup;

 public Group getGroup()
 {
 return myGroup;
 }

 public void setGroup(Group group)
 {
 myGroup = group;
 }
...
}

accessed via groupEditor.group.propertyName

or

@Name("groupEditor")
public class EditGroupBean implements EditGroup
{
...
 @In (required=false)
 @Out (required=false)
 private Group group;
...
}

accessed via group.propertyName

Are there advantages / disadvantages to either approach?

Thanks

[gstacey]

Bump...

I'm very curious to know if there are any inherent advantages / disadvantages to either approach.

[smithbstl]

I think its more up to personal preference and how you want your code organized. Bijection can be nice from the standpoint of shorter component names and your jsf more straightforward because you can refer to entities directly. But if you overdo this, your backing beans can get confusing because now you don't know where everything this being injected from.

Again, code organization is the biggest concern (for me anyway)

[delphi'sghost]

Wasn't there something about outjecting entity beans being a bit of a hog, with the preference being to use properties instead of outjection?

[pmuir]

Making Entities seam components isn't cluster safe IIRC

[samdoyle]

Making Entities seam components isn't cluster safe IIRC

So you recommend not using injection/bijection?