JBossDeveloper

OK, I am not able to figure out how to reproduce this. Please attach a runnable test case to reproduce this here:

http://jira.jboss.com/jira/browse/JBSEAM-248

Did anybody send Gavin a test case? If not, you (Gavin) need a example app, is it right?

@Newlukai Yes, I'm from germany. If you want to know it exactly, Magdeburg ;-).

Nope, I do not yet have any test.

Gavin,

I'm having the same issues as Newlukai, and as this person stated it appears somewhat random, but it related to the combination of @DataModelSelection, and @DataModelSelectionIndex.

Below you will find three fragment; simplified code, modified component.java from the seam project, and the logged output.

Please let me know if anything else would be helpful.

simplified ScheduleBean to show annotations

@Stateful
@Name("scheduleEditor")
@LoggedIn
@Interceptors(SeamInterceptor.class)

@PersistenceContext
private EntityManager em;

@In
private transient FacesContext facesContext;

@In
private transient Context sessionContext;

@In(required = true)
private Customer currentCustomer;

@DataModel
private List activityLogs;

@DataModelSelectionIndex
private int activityLogIndex;

@DataModelSelection
@Out(scope = ScopeType.CONVERSATION, required = false)
private ActivityLog activityLog;

@Create
public void initialize() {
}

@SuppressWarnings("unchecked")
@Factory("activityLogs")
public void find() {
}


@Destroy
@Remove
public void destroy() {
}

added log.info statements to component.java

for (Field field: selectionFields)
{
log.info("@DataModelSelection field: " + field.toString());
Annotation ann = dataModelSelectionFieldAnnotations.get(field);
log.info("@DataModelSelection ann: " + ann.toString());
String name = createUnwrapper(ann).getVariableName(ann);
log.info("@DataModelSelection name: " + name);
if ( name.length() == 0 )
{
if ( hasMultipleDataModels )
{
throw new IllegalStateException( "Missing value() for @DataModelSelection with multiple @DataModels" );
}
name = defaultDataModelName;
}
Field existing = dataModelSelectionFields.put( name, field );
if (existing!=null)
{
throw new IllegalStateException("Multiple @DataModelSelection fields for: " + name);
}
}

Logged results:
05:16:49,144 INFO [Component] Component: scheduleEditor, scope: CONVERSATION, type: STATEFUL_SESSION_BEAN, class: com.aftertherun.bean.schedule.ScheduleBean, JNDI: atrapp/ScheduleBean/local
05:16:49,144 INFO [Component] @DataModelSelection field: private int com.aftertherun.bean.schedule.ScheduleBean.activityLogIndex
05:16:49,144 INFO [Component] @DataModelSelection ann: @org.jboss.seam.annotations.datamodel.DataModelSelectionIndex(value=)
05:16:49,144 INFO [Component] @DataModelSelection name:
05:16:49,144 INFO [Component] @DataModelSelection field: private com.rocksolid.beans.ActivityLog com.aftertherun.bean.schedule.ScheduleBean.activityLog
05:16:49,144 INFO [Component] @DataModelSelection ann: @org.jboss.seam.annotations.datamodel.DataModelSelection(value=)
05:16:49,144 INFO [Component] @DataModelSelection name:
05:16:49,144 ERROR [[/]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener
java.lang.IllegalStateException: Multiple @DataModelSelection fields for: activityLogs
at org.jboss.seam.Component.initMembers(Component.java:536)
at org.jboss.seam.Component.(Component.java:199)
at org.jboss.seam.Component.(Component.java:159)
at org.jboss.seam.Component.(Component.java:154)
at org.jboss.seam.Component.(Component.java:149)
at org.jboss.seam.init.Initialization.addComponent(Initialization.java:381)
at org.jboss.seam.init.Initialization.addComponents(Initialization.java:343)
at org.jboss.seam.init.Initialization.init(Initialization.java:195)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:32)

Oh yes, this will not work anymore, after the stuff I did to generalize the databinding architecture (@DataModelSelection and @DataModelSelectionIndex are now no longer handled by special code). You can have one or the other, but you can't have both at the same time.

If this is really a problem, add an issue to JIRA and I can see what I can do about it.