Apple

On Dec 14, 2010, at 3:25 PM, Jesse Tayler wrote:

Makes sense, to use init() but how to safely handle the authenticated user?

I see there's a clazz setup used in BugTracker which seems to set a currentUser() which I'm guessing is a safe way to access the authenticated user (if I set it somewhere) and locally set an author or assignee relationship and otherwise get info from the current user.

I see this clazz setup in the bug tracker eo templates, but I don't have those on my EREOs and don't know where they come from.

I'm try to follow that code through, but maybe if someone has a basic explanation that would be great.

If you want to use the same stuff as bug tracker, you'll need to use ERCoreBusinessLogic and set up your user class.

https://services.wocommunity.org/wowodc/HelloD2W/Sources/com/wowodc2010/helloD2W/Session.java

	/*
	 * To use ERCoreUserPreferences requires:
	 *
	 * 1. Implement ERCoreUserInterface on your user entity
	 *
	 * 2. Set up the user entity when the app starts with
	 * ERCoreBusinessLogic.sharedInstance().addPreferenceRelationshipToActorEntity()
	 *
	 * 3. Set the user as the actor at login (obviously) and on awake/sleep
	 *
	 * 4. (optional) Implement a custom preference handler and set it with the property
	 * er.corebusinesslogic.ERCoreUserPreferences.handlerClassName
	 *
	 */

Ramsey

On Dec 14, 2010, at 2:28 PM, Ramsey Gurley wrote:

Hi Jesse,

On Dec 14, 2010, at 1:16 PM, Jesse Tayler wrote:

I'm implementing a method to populate new EOs with default values before save.

I see lots of ERXEnterpriseObject methods beyond awakeFromInsertion,

I would recommend init() instead of awakeFromInsertion. init() was added to fix a bug where awakeFromInsertion gets called twice after a cascade delete fails validation... or something (^_^)

including nice looking things like DidInsertProcessor and so forth.

I'd like to use the D2W rules to set values like "active" = "true" or "author" = "session.user"

The d2wContext of your page is generally unavailable in your EO unless you use thread locals.

If you DO find yourself using thread locals in your model, I would suggest you consider how you use them carefully so you don't end up with a model that is totally dependent on one application.

Does anyone have some overview advice for those new to the more modern ER frameworks in terms of how to implement this common concept I'm after?

ERXEntityClassDescription has some stuff for initializing values. So does migrations.

Ramsey

thanks for thoughts or insights --

References:
	>Quick ERXEnterpriseObject newly inserted Question -- (From: Jesse Tayler <email@hidden>)
	>Re: Quick ERXEnterpriseObject newly inserted Question -- (From: Ramsey Gurley <email@hidden>)
	>Re: Quick ERXEnterpriseObject newly inserted Question -- (From: Jesse Tayler <email@hidden>)