As of November 2006 I have relocated back to the East Coast. I can be contacted via the following address:
166 West 22nd Street Apt 1FNew York, NY 10011
My phone number is (212) 675-7507.
By the way, if you are looking for a different “Murray Williams” who lives in Arkansas, you got the wrong web site. His site can be found here.
If you would like to reach me via e-mail, you can use the form below. (This protects me from web-crawling spam harvesters.) I promise to get back to you promptly!
Hey Murray. My friend and I have written a song on How to Make a Souffle… kind of for giggles. We searched Google for a recipe and naturally your result was first. We did some heavy paraphrasing of your well formulated recipe. The song itself is not anything to make money, we may put it on a couple of music sharing websites though. My question is.. on sites that allow us to state song credit, would you like/permit us to list you as a credit for “Recipe by:”?
This is not a joke, by the way. 🙂 And thanks for the recipe.
Cheers,
-Steve
Thanks much for your recipe on Maven, JPA and Persistence (http://www.murraywilliams.com/2012/04/maven-and-jpa-programming/). I had been working towards organizing my project along these lines, but your site filled in a couple of details. However I’m still having issues getting it working. The problem is that, although I have tes test persistence.xml stored as src/test/resources/META-INF/persistence.xml, and I’ve confirmed that it’s being copied to target/test-classes/META-INF/persistence.xml, and I’ve checked with “mvn -X test” that that is at the head of the test classpath, my call to Persistence.createEntityManagerFactory(“foo”) fails with “No Persistence provider for EntityManager named foo…”. The file was working before I reorganized things the last time out. TIA if you can shed any light on this issue!
Can’t think of what the issue is off the bat, but I’m not sure it’s with the location of persistence.xml. (It could be… I’m just saying you should check other assumptions.) Is there any chance you’ve left out a dependency in your test scope?