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:
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.
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…
I’m currently working on a project that has given me the lovely opportunity to revisit the holy hell that is Tomcat. It’s fine and all, but it can be a real bitch to you. So I have a fine mix of JPA 2 (via EclipseLink 2.0.0), Spring 3.0.0, and AspectJ 1.6.6 running on Tomcat 6.0.20. I have been trying to get persisted HttpSessions to autowire with AspectJ injecting Spring beans back into the JSF beans (also managed by Spring) when the sessions were deserialized. Things look kind of like this…
I saw some retarded shit in my access log that looked like another spam bot that needed to be blocked, but after a little research, it seems to be a semi-legit piece of garbage called Surphace. After a very brief bit of research, it appears as though AOL is responsible.
I had thought that all of the stupid VCs were done chasing stupid ideas with stupid names, but I guess they’re still at it. Oh! Wait! Maybe they were on to something! Surphace has a URL shortener! … and surphing! I wonder if it’s too late to sell a flaming bag of shit to some VC firm (or AOL). It would be better than this thing.
© 2000-2010 cum grano salis — nobody likes a clever bastard
Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 United States License
