XAF NonPersistent Objects FAQs

Question 1

Does this work with XAF Blazor?

Accepted Answer

Yes, however, XAF Blazor requires an explicit [Key] property (typically a Guid) on non-persistent classes for proper object identification and UI rendering.

Question 2

Why do I get a SessionMixingException?

Accepted Answer

This usually happens when a non-persistent object inherits from an XPO persistent base class or when you try to mix persistent and non-persistent objects in the same Object Space without proper isolation.

Question 3

How do I prevent the 'Save Changes' dialog for non-persistent objects?

Accepted Answer

You should use the RemoveFromModifiedObjects method on the NonPersistentObjectSpace after creating or populating the object to clear the 'dirty' state.

Question 4

How do I refresh data in a non-persistent ListView?

Accepted Answer

You can trigger a refresh by calling View.ObjectSpace.Refresh(), which re-fires the ObjectsGetting event to reload data from your external source or API.

Question 5

What is the difference between [NonPersistent] and [DomainComponent]?

Accepted Answer

In XAF, [DomainComponent] is used for non-persistent business classes managed by NonPersistentObjectSpace, while [NonPersistent] is an XPO attribute that excludes properties or classes from database mapping.

XAF NonPersistent Objects

주요 기능

사용 사례

XAF NonPersistent Objects

주요 기능

사용 사례