<?xml version="1.0" encoding="UTF-8"?><!-- generator="WordPress/2.5" -->
<rss version="0.92">
<channel>
	<title>Rockhopper Blog</title>
	<link>http://rockhoppertech.com/blogs</link>
	<description>Java development tips</description>
	<lastBuildDate>Wed, 10 Mar 2010 13:58:57 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>Apache Wink</title>
		<description>Apache Wink is an incubating project that will allow you to write RESTful JAX-RS (JSR-311) web apps - like Jersey.

Read what Dr. Fielding has to say about what is REST and what's not.

DeveloperWorks has a recent article on Apache Wink. They do a commendable thing by giving instructions on how ...</description>
		<link>http://rockhoppertech.com/blogs/archives/67</link>
			</item>
	<item>
		<title>jetty maven version 7 beta woes</title>
		<description>So I gave the beta of the jetty maven plugin a try.

What I had was this:

&#60;groupId&#62;org.mortbay.jetty&#60;/groupId&#62;
&#60;artifactId&#62;maven-jetty-plugin&#60;/artifactId&#62;
&#60;version&#62;6.1.19&#60;/version&#62;


I changed it to this which is the most current available version in the repos:


&#60;artifactId&#62;jetty-maven-plugin&#60;/artifactId&#62;
&#60;version&#62;7.0.0.1beta3&#60;/version&#62;


N.B. for maximum cognitive dissonance the jetty guys thought it would be a good idea to swap some words in the ...</description>
		<link>http://rockhoppertech.com/blogs/archives/66</link>
			</item>
	<item>
		<title>Spring, BasicDataSource and OpenJPA</title>
		<description>So you want to use Spring with commons BasicDataSource and OpenJPA? There is an interesting gotcha.

Let's start with just the DriverManager DataSource for comparison. In your spring context you define the datasource like this:
&#60;bean id="dataSource"
class="org.springframework.jdbc.datasource.DriverManagerDataSource"
p:driverClassName="org.hsqldb.jdbcDriver"
p:url="jdbc:hsqldb:hsql://localhost:9001/testdb" p:username="sa"
p:password="" /&#62;
Then your EntityManager Factory:
&#60;bean id="entityManagerFactory"
class="org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean"&#62;
&#60;property name="dataSource" ref="dataSource" /&#62;
&#60;property name="persistenceUnitName" value="jpamaven-test" /&#62;
&#60;property name="loadTimeWeaver"&#62;
&#60;bean
class="org.springframework.instrument.classloading.SimpleLoadTimeWeaver" /&#62;
&#60;/property&#62;

&#60;property name="jpaVendorAdapter"&#62;
&#60;bean ...</description>
		<link>http://rockhoppertech.com/blogs/archives/65</link>
			</item>
	<item>
		<title>Spring Test Framework CoC suggestion</title>
		<description>Let's say you're using JUnit 4 and the Spring Testing classes (the 2.5+ versions) for your unit tests. You can specify parameters as shown in the TransactionConfiguration annotation as shown in this example. But you can also get away with leaving them out in a nod to the uberhip Convention ...</description>
		<link>http://rockhoppertech.com/blogs/archives/64</link>
			</item>
	<item>
		<title>Multiple Persistence Units - Websphere v7, OpenJPA</title>
		<description>Want to do something exotic like specifying two persistence units in your persistence.xml file? Perhaps one local and one JTA managed. Maybe even go whole hog and do that to write unit tests?


In Websphere v7 (RAD 7.5) when you have multiple PUs in persistence.xml it barfs like this:

[7/8/09 10:01:55:149 EDT] ...</description>
		<link>http://rockhoppertech.com/blogs/archives/63</link>
			</item>
	<item>
		<title>JSF 2.0</title>
		<description>JSF 2.0 is out.

But there is still no maven love here: https://maven-repository.dev.java.net/nonav/repository/javax.faces/jars/

But over at JBoss we have something close:
&#60;dependency&#62;

&#60;groupId&#62;javax.faces&#60;/groupId&#62;

&#60;artifactId&#62;jsf-api&#60;/artifactId&#62;

&#60;version&#62;2.0.0-PR2_3&#60;/version&#62;

&#60;/dependency&#62;

&#60;dependency&#62;

&#60;groupId&#62;javax.faces&#60;/groupId&#62;

&#60;artifactId&#62;jsf-impl&#60;/artifactId&#62;

&#60;version&#62;2.0.0-PR2_3&#60;/version&#62;

&#60;/dependency&#62;
is in this repository:
&#60;repository&#62;

&#60;id&#62;maven.jboss.com&#60;/id&#62;

&#60;name&#62;jboss Repository for Maven&#60;/name&#62;

&#60;url&#62;http://repository.jboss.org/maven2&#60;/url&#62;

&#60;/repository&#62;
Looks like the ManagedBean annotation does not work though. So I tried it with the mojarra jars and did the mvn install:file chacha. Still no go.

So ...</description>
		<link>http://rockhoppertech.com/blogs/archives/62</link>
			</item>
	<item>
		<title>Oracle buys Sun</title>
		<description>It's official. Oracle will buy Sun. </description>
		<link>http://rockhoppertech.com/blogs/archives/61</link>
			</item>
	<item>
		<title>Jersey 1.0 and jetty:run</title>
		<description>If you are using maven and jetty you are probably simply invoking jetty:run with your Jersey web service.

Jersey is the JAX-RS (JSR 311) Reference Implementation for building RESTful Web services

The problem is you get this exception:
The ResourceConfig instance does not contain any root resource classes.
But you are sure you do ...</description>
		<link>http://rockhoppertech.com/blogs/archives/60</link>
			</item>
	<item>
		<title>Swing Drag and Drop on non supported components</title>
		<description>The 1.4 release of Java SE introduced a much needed overhaul for the Drag and Drop subsystem. I sweated blood back in 1999 to make it reasonably work for a client's requirements. That led to an hour long 1999 JavaOne talk (that was before the marketing crap seeped into JavaOne) ...</description>
		<link>http://rockhoppertech.com/blogs/archives/59</link>
			</item>
	<item>
		<title>Spring autowiring Struts 1 Actions</title>
		<description>That's right. Struts 1. Not hip. Not happenin'. But in the real world you might have bills to pay and a pair-programmer to feed.

The docs are a bit sketchy with Spring 2.5 stuff.

First you set up your service layer in web.xml
&#60;context-param&#62;

&#60;description&#62;Used by ContextLoaderListener&#60;/description&#62;

&#60;param-name&#62;contextConfigLocation&#60;/param-name&#62;

&#60;param-value&#62;/WEB-INF/spring-service-layer.xml&#60;/param-value&#62;

&#60;/context-param&#62;&#60;listener&#62;

&#60;description&#62;spring. looks for /WEB-INF/applicationContext.xml unless you set contextConfigLocation ...</description>
		<link>http://rockhoppertech.com/blogs/archives/57</link>
			</item>
</channel>
</rss>
