Random notes on life, coding and politics
This took a little while to figure out!
Date startDate = new Date(); Date endDate = new Date(startDate.getTime() + (24 * 3600000 * 42));
This was expected to result with startDate being right now (Feb 20, 2013 5:17:10 PM) and the end date being six weeks later (Apr 3, 2013 6:17:10 PM), but instead end date was being computed to be earlier than the start date… Feb 13, 2013 in fact! Continue reading “Funny Bug of the Day (Java)”
Service Component Architecture (SCA) is the marriage of these two things. It essentially recognizes that some of your building blocks are going to be local, others are going to be external, all of them need to be as reusable as possible, and their internal/external exposure may change over time. In other words, it’s a SOA orchestration of services that is a fluid hybrid between the two worlds. Your code will periodically use a @Service tag to declare a service dependency. And some XML configuration file will help map out the ESB-specifics of (a) exposing necessary services or service compositions to the outside and (b) getting access to outside service dependencies that you’ll need.
Over the past several years I’ve become wildly enthusiastic about certain “trends” in software development that promote clean, agile, distributable code. The primary buzzwords I’m referring to are “SOA” (Service Oriented Architecture) and “Dependency Injection”. Heck, I’ll even throw “SOAP” into the mix, even though that’s a more specific protocol.
If I talk to other developers about these things, they look at me funny or they show disinterest or suspicion. I think some people think I’ve gone crazy over some trendy buzzwords (i.e. pointy-haired-manager syndrome) and am just trying to evangelize some lame trend that will come and go. Or there’s the classic “SOAP? Oh yeah, I tried to do something with that and got so confused and just hated it. *shiver*”
(By the way, SOAP may have some hard-to-parse standards, and the WSDL can be daunting and confusing, but it’s really simple: you are taking your XML request and wrapping it in a simple envelope that is often nothing more than a single parent <soap> tag! There are some provisions for allowing messaging meta-data to be added in a header section, but all that stuff is optional. Anyway, if you are one of those people who is afraid of SOAP, take a second look; it’s not all that bad.)
Dependency Injection and Service Oriented Architecture are interesting topics in that they really should be easier to explain. I’ve read so many books and articles, and authors have written a lot of insightful material, but I haven’t run into anyone who has been able to expose the inherent simplicity behind these things. Well, I might my hand at the task someday, but not in this blog posting. My purpose is a bit more specific… to share an insight about Service Component Architecture. Continue reading “What’s special about SwitchYard? It’s SCA.”
It cannot be overstated just how helpful it is to have a lightweight persistence system in your testing configuration. The problem with JPA annotations like @PersistenceUnit for dependency injection is that a lot of your primary code can only be run from within a full-fledged J2EE application server.
I wanted to take a moment to rant a little about Maven and JPA programming. If you haven’t switched to the Maven way of things (It took me years to give into the dark side!) or you just started doing Maven-ized projects recently, you might still be getting the hang of things.
I won’t lie: it can be relatively hard to get used to. For example, take a look at the traditional directory structure for your project:
This may look a bit complex (like the first time you looked at a Unix directory structure!?) but in fact it’s a fantastic convention. For example, it’s so amazingly easy for me to create sample data files, drop them into src/test/resources/sampleData and then pull the data will a quick Unit Test using
InputStream sampleData = getClass().getResourcesAsStream("/sampleData/myFile");
and away you go! Continue reading “Maven and JPA Programming”
Switchyard takes Web Services to the next level. Whereas JAXB2 and JAX-WS (and JAX-RS) have brought the development and deployment of Web Services to the necessary level of maturity for clean, easy and practical development, Switchyard let’s us take things to the next step: it makes Web Service Composition similarly clean and easy. And with Web Service Composition comes the entire arsenal of SOA Design Patterns.
I’m sure everyone right now thinks the biggest advances in the computer industry today are Social Media and the iPad. Or maybe they were last year’s big news and there’s something I don’t know (or yet care) about that just appeared in SXSW this year. Well, as much as I’m still chomping at the bit to do a little iOS development (I still watch the Stanford class lectures from iTunes U on my iPhone while I run the elliptical at the gym at 5:30am every morning!) I’m actually really the most excited about something else. And when I mean excited, I mean that first thing every morning I’ve been checking the JIRA “open tickets” report to see how the countdown is going. I’m talking “kid counting the days to Christmas” sort of behavior.
The countdown to what? Well, I’m glad you asked. I’ve been waiting since about November for the countdown to the release of the 0.4 version of JBoss Switchyard. Continue reading “Dependency Injection + ESB = SwitchYard (Coolest New Thing This Year)”
I finally decided to bite the bullet and try using cleaner JSP methods, including JSTL
Okay, I know I haven’t posted anything on my blog in over a year, but this falls under the OMG-Why-Couldn’t-I-find-a-straightforward-answer category. Whomever suffers the same headache I suffered will hopefully get led here by Google…
Up until now, the few times I’ve needed to cobble together a JSP file for some sort of front-end functionality, I’ve used raw, low-level JSP Scriptlets. Which means typing things like
<% if (something) { %> <some-html> <% } else { %> <some-html> <% } %>
all over the place. And if I wanted to do any looping, well forget about it! It’s a nightmare. So I’ve got these few books and articles that talk about the better ways to solve these problems using cleaner xml-y solutions, and most all of them dive into using JSTL (JSP Standard Tag Library) which is a damned standard and yet isn’t included with Tomcat. It’s one of those things that each vendor is supposed to implement independently, and yet the only implementation out there appears to be Oracle’s Glassfish implementation! (There’s an Apache JSTL project, and they say on their web page that a version 1.2 implementation (which is the stated version for the Java 6 EE standard collection, alongside Servlet 3.0 and JSP 2.2) but that webpage hasn’t been updated since October 2009!!
So apparently JSTL is so basic and simple that it’s included in the elementary pages of any JSP books, but like some bastard stepchild that nobody wants, it’s support is freakishly missing. Okay, enough bellyaching about how FUBAR that is… what about just getting the thing to run? Continue reading “Running JSTL 1.2 on Tomcat 7 using Maven”
