Internal Website Search

131-140 of 200 resultsRefresh

significant performance decrease

usedSolutionObjectTypeVersion; @OneToMany(fetch=FetchType.LAZY) public List<Action> actions = new ArrayList<Action>(); @OneToMany(fetch=FetchType.LAZY) public List<ObjectNode> childNodes = new ArrayList<ObjectNode>(); @OneToMany(fetch=FetchType.LAZY) public List

persisting object with long[][] arrays of array

; @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) public long[] time;     @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private long[][] a1;     @OneToMany(fetch = FetchType.EAGER, cascade = CascadeType.ALL) private long[][] a2;  

Once served to JSF page via @EJB query bean, many list fields are null (but same query ok after fresh persist in @PostConstruct)

() { return ownedElements; } private Element owner; @ManyToOne(fetch = FetchType.LAZY ... your application) is that indeed detachment might be the problem here. Try setting the fetch type of  ... ="code">ownedElements relationship is defined as LAZY (the default fetch type for to-many

getReference(entityClass, primaryKey)

"> Get an instance, whose state may be lazily fetched. If the requested instance does not exist

Persistent.loadFetchGroup

Name of the fetch-group to use when this member ... > Returns: the name of the load fetch group

Persistent.defaultFetchGroup

defaultFetchGroup Whether this member is in the default fetch group ... > whether this member is in the default fetch group

fetchShortField(fieldNumber)

class="description"> Fetch one field from the field manager. This field will be stored in

fetchObjectField(fieldNumber)

class="description"> Fetch one field from the field manager. This field will be stored in

fetchStringField(fieldNumber)

class="description"> Fetch one field from the field manager. This field will be stored in

fetchBooleanField(fieldNumber)

> Fetch one field from the field manager. This field will be stored in