The info for this project is still a work in progress. Please be patient!
So I’ve been (slowly) working on converting my budgeting app from Python/Django to Java. I really like Django, but this web app doesn’t really fit in the Django paradigm the way I initially thought. Oh well, it’s a good opportunity to do more programming.
Anyway, as I have been doing the migration I decided to use RESTEasy to do the URL mapping. I’m a big fan of pretty URLs for any site, and RESTEasy makes the whole process nice and easy (or so I thought).
I decided that the nice way to go was with a completely annotation based system (CDI with annotations and RESTEasy Path annotations). Unfortunately the RESTEasy documentation doesn’t do a good job of documenting how to run with both a servlet filter, and annotations (you’ll see their example web.xml snippet has the servlet filter with a JAX-RS Application class). The documentation does say that you can add a configuration switch to have RESTEasy scan for annotations, but it lists them as context-params for the servlet based approach.
After trying a number of different combinations without any luck, I went the debugging route. Slapping the RESTEasy source in my Eclipse project, I ran through the code to find where the configuration switches were loaded with the servlet filter. Luckily it didn’t take too long to find that context-params can be translated to init-params inside the filter element. This resulted in the following:
<filter> <filter-name>Resteasy</filter-name> <filter-class>org.jboss.resteasy.plugins.server.servlet.FilterDispatcher</filter-class> <init-param> <param-name>resteasy.scan</param-name> <param-value>true</param-value> </init-param> </filter> <filter-mapping> <filter-name>Resteasy</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>
I would like to say that a lot has happened in the two months since my last post, and while I can say that thing have been great, not a whole lot has changed.
Things are still going well at work. I’m getting new responsibilities all the time (which I love), and I’m really starting to get into the groove of things. I’m still enjoying my project and all the cool little side projects I get to do. A good friend from MSU who worked with me at Jackson moved to Chicago recently, so that’s a bit of a bummer.
Still loving my new phone, which totally rocks.
Had central air installed at my place by the awesome Jim Horn (I hope that’s the right url), which is seriously nice.
I’m sure there’s more stuff in there, but I’m bored of writing this post already. oke bye.
please bring a Chick-fil-A to Michigan. Seriously, Michigan would be much better if there were Chick-fil-A’s everywhere. Then, the slickdeals free spicy chicken sandwich on Friday would not have gone to waste for me. I have many other requests, but this one is important…
As I’m sure you can guess, YouTube decided not to hire me. While it does make the moving away decision much easier (and everyone that wants us to stay here much happier), I still think that YouTube made a mistake on me.
I found out Monday April 26th, and the following morning I wrote out a 1200+ word post explaining why I thought I was a good fit (yeah, I definitely didn’t post that). While that might have made me feel a bit better, I’m sure that I’m the only person it would have helped.
Having had quite a bit of time to think about it, I still think that I would have fit well. I have been a web developer for almost a decade (their main interface is a website), I know programming in Adobe Flash really well (hello?), and I’m all about Python (the language their backend is written in). My only thought is that the interview process doesn’t do me justice.
Oh well, maybe I’m meant to stay in Lansing…