Re: [The Java Posse] Re: ORMs and Immutability

2012-01-03 Thread Ricky Clarkson
ue, 3 Jan 2012 05:23:55 To: The Java Posse Reply-To: javaposse@googlegroups.com Subject: [The Java Posse] Re: ORMs and Immutability I think my discovery of the day is in a CSV parser that has a comment about how if the code below were written in C then it would use goto in order to jump quickly fro

[The Java Posse] Re: ORMs and Immutability

2012-01-03 Thread Carl Jokl
I think my discovery of the day is in a CSV parser that has a comment about how if the code below were written in C then it would use goto in order to jump quickly from one large section to another but as goto is not available in Java, instead it throws an exception to quickly jump to another part

[The Java Posse] Re: ORMs and Immutability

2011-12-28 Thread Roland Tepp
I cant but help but thinking, this might just be a prime candidate for Daily WTF article... neljapäev, 22. detsember 2011 17:52.28 UTC+2 kirjutas Carl Jokl: > > This is probably my favourite like from the JIRA comment but I will > take out the name of the company from the package: > > "Hmmm ..

[The Java Posse] Re: ORMs and Immutability

2011-12-23 Thread Sebastian Himberger
Hi Carl, I posted a message to this thread but it somehow got lost. We have the same problem in a current project but we are not using a ORM but JSON for storage. We are using a builder to deserialize the JSON and create a immutable object out of it. I have an experiment up on GitHub. Maybe it

[The Java Posse] Re: ORMs and Immutability

2011-12-23 Thread Carl Jokl
Back to the subject of Immutability with domains. What occurred to me is that there is a difficulty in any domain relationship where Domain A has a reference to Domain B and Domain B holds a reference back to Domain A (where you don't want any duplication of objects). Due to any standard database l

[The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Sebastian Himberger
Hi Carl, we had a simmilar problem in the project and basically use a builder for mapping (in this case JSON data) to an immutable class. We just pass the builder to the mapper instead of the actual bean and it"s get filled with the correct values. So theoretically it is possible. The tools jus

[The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Carl Jokl
That is where I acknowledge my own fault in that on company time I am at their digression as to what I should be spending it on. I think he had every right to be angry about that because I wish I had just done it all in my own time. One difficulty is that I have a desktop for work and security won'

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Graham Allan
Hey Carl, Not to be too harsh to someone who can't give their side of the story, but from your account it sounds like your supervisor is a dick. It's fair enough to get annoyed if you're spending time on non-prioritised stuff - they pays their money they takes their choice. But if it's mostly on

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Ricky Clarkson
c 2011 05:45:03 To: The Java Posse Reply-To: javaposse@googlegroups.com Subject: [The Java Posse] Re: ORMs and Immutability The demonstration domain classes that I had been working on went down like a lead balloon. My supervisor thought the whole endeavour was a waste of time and could not see any ben

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread ags
Don't worry, List> happens to me too ;-) On Thu, Dec 22, 2011 at 2:45 PM, Carl Jokl wrote: > The demonstration domain classes that I had been working on went down > like a lead balloon. My supervisor thought the whole endeavour was a > waste of time and could not see any benefit. I was in the wr

[The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Carl Jokl
The demonstration domain classes that I had been working on went down like a lead balloon. My supervisor thought the whole endeavour was a waste of time and could not see any benefit. I was in the wrong genuinely for having spent too much time on it. Not that I originally intended to but it took a

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Ricky Clarkson
, but then I think in code rather than SQL. -Original Message- From: "Fabrizio Giudici" Sender: javaposse@googlegroups.com Date: Thu, 22 Dec 2011 12:26:50 To: Reply-To: javaposse@googlegroups.com Subject: Re: [The Java Posse] Re: ORMs and Immutability On Thu, 22 Dec 2011 0

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-22 Thread Fabrizio Giudici
On Thu, 22 Dec 2011 00:51:51 +0100, Ricky Clarkson wrote: My current client dislikes Hibernate (not that I'm proposing it) because most of their technical staff have DB experience more than straight programming experience; even the Business Analysts can talk in SQL. They worry that if Hibern

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-21 Thread Ricky Clarkson
My current client dislikes Hibernate (not that I'm proposing it) because most of their technical staff have DB experience more than straight programming experience; even the Business Analysts can talk in SQL. They worry that if Hibernate does something they don't expect they won't be able to make

Re: [The Java Posse] Re: ORMs and Immutability

2011-12-21 Thread Martijn Verburg
Hi Carl, I think that Hibernate (like any framework) has its place. It gets mocked probably more because of the countless abuses of it by developers who haven't quite understood it properly ("I can do foobar.save(); that is all I need to know"). Cheers, Martijn On Wednesday, 21 December 2011, Ca

[The Java Posse] Re: ORMs and Immutability

2011-12-21 Thread Carl Jokl
In all seriousness though, is this how badly Hibernate is viewed these days? Having an ORM seemed to make sense to me and still does in theory. I know in practice I have hit plenty of obscure cases or problems in Hibernate but I am not sure I would throw it all out as a waste of time just yet and a