Just another Wordpress blogger blogging on Wordpress.
I am going to show an example of writing a cross-plaform game for GP2X/GP2X F-200 and Windows Mobile. I’ll test it out on a GP2X F-200, Palm Treo 750W and AT&T 8125 smartphone. It will also be playable on Windows and Linux, too.
Continue reading “Use Game Editor to create a cross-platform game for GP2X F-200 and Windows Mobile”
While working with iReport, I wanted to test my report with a default Collection value for my Hibernate Query.
The HQL is something like this,
SELECT person.fullName as personName
FROM Person person
WHERE person.id in ($P{people})
Continue reading “Instantiating an iReport Collection parameter from an Array in one line”
I have a project for Facebook which I’ve done a little work on. But, at this juncture I need to decide whether to proceed with Ruby or PHP. PHP is the sanctioned tool for Facebook – since they seem to have abandoned all other development tools. Ruby on Rails is the most beloved tool of the web. Every developer turns into a poet and philosopher after getting RoR on themselves.
So, I got the beta PDF of Developing Facebook Platform Applications with Rails from Pragmatic Programmers. So far, the book is a pleasure to read.
Continue reading “Currently Reading: Developing Facebook Platform Applications with Rails”
Currently, I am reading The Definitive Guide to iReport.
I am working on a project to integrate JasperReports into our existing application. The great vision is to be able to upload reports which our customers write themselves. Right?
When it comes to JNDI Datasources, you really need a fast way to test outside of the container without changing all of your configuration just because your testing.
One of the problems with using a JNDI Datasource is Unit Testing outside of the container. Testing in the container is a pain and it’s slow if you are fixing bugs or just testing to make sure what you have works after a few changes. It’s OK for system tests.
Another option might be to have one set of configuration for the container and one for Unit Testing. An example might be to have two files controlled by your classpath or even worse, one file which you comment/uncomment to get the datasource you need. Then hope you package up the right configuration for the release.
What you really need a fast way to test outside of the container without changing all of your configuration just because your testing. Thankfully, spring provides a nice way to test your application outside of the container. Just bind your resource to a SimpleNamingContext mock and voila!
Continue reading “JUnit Testing JNDI Datasources: Thinking outside of the Container”
You must be logged in to post a comment.