Hopefully I’ll get round to posting an article on the actual repositories soon.

Why did you decide to check for IsReadOnly as well as IsPrimaryKey? What difference does it make to the getter? Was it so that the primary key would be settable like Mike mentioned?

Also, I’d like to second that I’d be interested in knowing how you implemented the base repository class. I’m having difficulty finding resources the define the repository pattern outside of MVC, so I’d be very interested to see how someone else has tackled it.

Thanks again for some awesome work,
Sam.

And more specifically, do you have a specification or query pattern implementation in your repositories (i.e.: GetBySpec(ISpecification spec) …). Something like that.

That has traditionally been the bigger challenge I’ve seen with using interfaces in your entity model.

I suppose that since you are bringing in the LLBLGen dll into your BL with EntityList, maybe you could wrap the specification pattern around some of the llbl functionality.

Without being able to completely remove LLBL from the BL (kind of ironic, given the name), I currently continue to opt to use the adapter entity classes as-is, same with EF STEs if I’m using Entity Framework. So, I get married to the ORM in a way in a project, but it provides the flexibility in the querying abstraction.

Would love to hear your views on this.

The templates attached to this post mitigate that issue since the entities all implement their own defined interfaces. This means the UI is not exposed to ANY LLBLGEN functionality.

For example, instead of the repository returning an OrderEntity (LLBLGEN entity) it returns an IOrderEntity which is implemented by the LLBLGEN entity but doesn’t expose all the LLBLGEN properties and methods.

Hope this explanation helps.

We are going to develop a 3-tier application using WPF,Oracle 11g,LLBLGen 3.0. Do you have a idea for generating Business objects for LLBLGen entties? My client is suggesting to use DAL entities in BL also and return it to UI. But I didn’t like that as it will strongly couple the DAL to UI. Do you have a sample implementation of BL based on LLBLGen entities?

An entry on your repositories would be much appreciated!

Mike

My specific repositories are sub-classes of a base repository which generically handles the boring stuff (GetById, Save – update/insert, Delete).

I’ll post a blog entry soon on my implementation of the base repository class.

Regards,
Rohland

Thanks for sharing this solution – I’m sure a lot of work went into this!

I’m currently looking at LLBL for my next project and was wondering if you could share some thoughts on how you implemented the repositories themselves? I’ve tried (without success) to create a basic generic repository but I just can’t get it to work with LLBL. Did you create a specific repository for each of your entities (roots)?

Thanks again,

Mike

< [If IsNullable]>< [If IsValueType]>< [TypeOfField]>?< [Else]>< [TypeOfField]>< [EndIf]>< [Else]>< [TypeOfField]>< [EndIf]> < [EntityFieldName]> {get;< [If IsReadOnly ]>< [If IsPrimaryKey ]>set;< [EndIf]>< [Else]>set;< [EndIf]>}< [NextForeach]>

The only thing I’m trying to figure out now is that one of our databases has a table with a read only field. The resulting entity has no setter, but the template generates one and then the compiler throws an error saying that we’ve missed the implementation. I’m going to tweak it and see what I can come up with. I’ll let you know what I find out if you’re interested.

Thanks again for a great template. It’s really opened my eyes as to what’s possible with LLBLGen.