cum grano salis — nobody likes a clever bastard

If you’ve succumbed to not being able to get Spring Web Flow to work with your other framework of choice (I am only using ICEfaces as an example because its fresh in my head) and have to figure out how to reimplement row selection for tables and such, since you can’t readily use SWF’s OneSelectionTrackingListDataModel et al (i.e. result-type=”dataModel” in a flow configuration), there is of course an AOP solution. What can’t it do?!

I have an aspect skeleton sitting around for this, and of course you can use it if you want. (Fuck, you can use the whole library. I just have to get my SCM back online.) You just have to have everything else in place to make it go, like load-time weaving or whatever. Anyway, it’s basically the Decorator pattern, something AOP introductions… are. Here it is…

[Read the rest of this entry...]

After a few days of wasting my time with ICEfaces, I switched to RichFaces because at least it tries to integrate with other frameworks without having complete diarrhea for a code base. Seriously, it looks like ICEfaces was written by a bunch of fucking monkeys drunk on gin. Have some pride in your work, assholes. Try formatting your code and not using copy and paste from Spring to make things kind of work… I mean not work at all you fucks. Great look and feel, but total shit on the inside, like an American girl. Nice components, but unusable. You suck. Sun/Oracle is going to have a great time gutting you. Sorry, Ted.

Anyway, RichFaces doesn’t even fucking work, either. They do, however, have a great debugging component called a4j:log, which is really nothing to do with the JBoss infection, or the Exadel infection, but probably someone else in the real world. I don’t know for sure, but it’s probably from a good source. Anyway, this component will spit out your AJAX transaction and save the day. In particular, it will help to solve issues like RICHFACES DOESN’T FUCKING WORK. I don’t give a shit what a certified asshole with the most annoying British stick-up-the-ass name like Gavin says. “Oy, it works with Seam. Guffaw, ol’ chap!” Celebrity developers can suck it. The feel that they generate among other developers is sick. “Oh, so-and-so uses it, so I must waste my time using it in a different, unproven, way that is outside of the Hibernate recipe, ultimately fail, and feel bad about myself.” Not everyone on every project wants to fuck around with these broken frameworks with retarded paradigms and disgusting code that is nearly impossible to debug, unless they really know how to debug and have the time and inclination to do so. I do, so I end up patching a lot of fucked up shit that I shouldn’t have to.

Anyway, the excitement can be found in many places, including here, where Spring announces a brokeass doesn’t fucking work integration with RichFaces. But, I at least found a way to work around it…

[Read the rest of this entry...]

Apparently, it’s too much to ask to get a single line change in an open source project these days. It must be the economy. So, if you want ui:debug to work with SWF, and you happen to be using something approximately around Facelets 1.1.15, here’s the diff:

[Read the rest of this entry...]

I have been banging on this project’s view with a few different technologies. I prototyped the thing in ZK, which turned out to be a complete piece of shit after trying to get it to work in a real world scenario. (More on that later.) Now it’s all about JSF. ICEfaces has some pretty neat components and I have almost everything mocked up. Getting the flows and conversations to work with JPA is no problem with Spring Web Flow, either. The issue is getting ICEfaces into the mix.

[Read the rest of this entry...]

I’ve been hunting down bugs all day and getting next to nothing done. After finding that Spring would rather convert a String into a bunch of smaller Strings than let me do my work, I find even more. Fortunately, this one was a cinch.

Needing something to do role-based conditional processing in my JSF pages, I ended up with what looks like what may be possibly the only open source solution. (If there are more, please let me know.) It’s unfortunate that Spring decided not to support JSF for Spring Security when they support a JSP/JSTL taglib. Supposedly, Spring Security isn’t tied to any web tier technology. That doesn’t make sense. Drop the taglib, then, assholes. Move it into another package or something. It’s not like JSF tags are a difficult problem, either. Standard framework support probably belongs under Spring Security. If it’s all in one place, cohesive, and it works, people won’t be annoyed.

That being said, it’s also unfortunate that Dominik decided to go with a google code project. I don’t want to log into google for every god damned thing. There are other alternatives that aren’t complete shit. So, just out of spite, I’m not using that shitheaded issue tracker and I’m posting about it here. I’m not even going to link to it. Just set up Trac or something. You already run a site.

Anyway, the taglib is broken, so here’s the fix…

[Read the rest of this entry...]