could of course just use Paul Wilson's or mapper now that I also want to use the UI mapper
You really use the UI mapper? So far I am not sure whether to stay away from it like hell (and all similar approaches) or whether it is usable at all.
My main problem is that our UI elements (PowerNodes, mostly) are really tuned to the end, and the functionality of the forms is pretty complex. I am not sure a UI mapper actually provides anything usefull there. I really like the work Paul does, but I doubt
the usefullness besides some back end forms that can look ugly.
Thona: I'm actually considering looking into the EntityBroker, somehow people think that the Beta label on NHibernate (and open source altogether) is a bad thing. A main factor is also service.
Well, depending on what features you look for the EntityBroker is propably the most powerfull solution you CAN have. It really depends on wwhat you need, particularly. We are also responsive to larger paying customers :-) Our remoting support is about the
best I can think of (PowerNodes would not be possible with another CMS - the whole Remoting story that the EntityBroker supports was done for PowerNodes and the requirements there are really extreme, with disc based cross transaction
caches, and stuff like this, simply due to the nature of the data) and we are the only one I know of now putting in a retry-logic for deadlocks (customer request, do NOT ask me whether it makes sense). The branch for the 2004.1 version goes out the next days
- right now I am redoing the whole build logic to automate it (Nant), then it branches off 2004.1 and some features have to go in that are required - from one of our larger customers as well as PowerNodes.
What we have to do is finally put the EntityBroker 2004 on our website (which is being reworked right now) and get
our marketing story better.
On a side note... I can see that your new PowerNodes cms works out of Denmark?! How come? (I'm from DK myself, so it's just out of curiousity)
Well, the story is that it is not my new PowerNodes. It is PowerNodes. It is not a THONA prodct - it is a product made from a danish company, with danish employees, working out of denmark, financed by danish investors. We
do the whole development, but are technically a contractor - albeit a special one. They are a separate entity, the project originated from them (as a matter of fact it started as a consulting job for a DAL in their old CMS, then got
bigger) and is right now looking for some venture capital to fund version 2. That is the story behind it.
thona
Member
20 Points
2923 Posts
Re: NHibernate and servicelayer
Apr 28, 2005 02:31 PM|LINK
could of course just use Paul Wilson's or mapper now that I also want to use the UI mapper
You really use the UI mapper? So far I am not sure whether to stay away from it like hell (and all similar approaches) or whether it is usable at all.
My main problem is that our UI elements (PowerNodes, mostly) are really tuned to the end, and the functionality of the forms is pretty complex. I am not sure a UI mapper actually provides anything usefull there. I really like the work Paul does, but I doubt the usefullness besides some back end forms that can look ugly.
Thona: I'm actually considering looking into the EntityBroker, somehow people think that the Beta label on NHibernate (and open source altogether) is a bad thing. A main factor is also service.
Well, depending on what features you look for the EntityBroker is propably the most powerfull solution you CAN have. It really depends on wwhat you need, particularly. We are also responsive to larger paying customers :-) Our remoting support is about the best I can think of (PowerNodes would not be possible with another CMS - the whole Remoting story that the EntityBroker supports was done for PowerNodes and the requirements there are really extreme, with disc based cross transaction caches, and stuff like this, simply due to the nature of the data) and we are the only one I know of now putting in a retry-logic for deadlocks (customer request, do NOT ask me whether it makes sense). The branch for the 2004.1 version goes out the next days - right now I am redoing the whole build logic to automate it (Nant), then it branches off 2004.1 and some features have to go in that are required - from one of our larger customers as well as PowerNodes.
What we have to do is finally put the EntityBroker 2004 on our website (which is being reworked right now) and get our marketing story better.
On a side note... I can see that your new PowerNodes cms works out of Denmark?! How come? (I'm from DK myself, so it's just out of curiousity)
Well, the story is that it is not my new PowerNodes. It is PowerNodes. It is not a THONA prodct - it is a product made from a danish company, with danish employees, working out of denmark, financed by danish investors. We do the whole development, but are technically a contractor - albeit a special one. They are a separate entity, the project originated from them (as a matter of fact it started as a consulting job for a DAL in their old CMS, then got bigger) and is right now looking for some venture capital to fund version 2. That is the story behind it.