A feature that JSF needs

I've noticed for some time now that there are just some things that are hokey in JSF.

If you're like me, you almost always have your forms setup like this:

<h:outputLabel for="pvalue" value="Value"/>
<h:inputText value="#{propertyAction.propValue}" id="pvalue"/>

Now if there's a validation on this input, you need to mark the label (otherwise users get a really bizarre error message that they won't understand)

<h:outputLabel for="pvalue" value="Value"/>
<h:inputText value="#{propertyAction.propValue}" id="pvalue" label="Value"/>

And if you're using a bundle, it'll look something like this:

<h:outputLabel for="pvalue" value="${msgs['value']}"/>
<h:inputText value="#{propertyAction.propValue}" id="pvalue" label="${msgs['value']}"/>

So why can't JSF be smart enough to realize "Ok, I have an outputLabel for this input type, it has a validation error, let me use that label instead." and make the label attribute optional and can override the outputLabel in this case.

Why does IT get ignored?

So I work in the IT field, to me that means more than just programming or support, it's about building a solution with the business.

Is it me or is the later part not happening anymore? With the adoption of SaaS or the businesses leaning towards more off the shelf products, it seems like the result is that IT not involved in a lot of the decision making and it's simply handed off and said "here, do this." There's no business analyst involved, there's no research on how to implement it or how to integrate it with existing systems.

I can whole heartedly understand the business wanting to be able to do it themselves, but I'm not sure it's a good idea. We're IT because we're good at computering (computering, able to work with and understand elements in the computer realm). The business side doesn't always understand the ramifications of their needs. In the world of distributed computing, the idea that a system is standalone is nonexistent. From the basic automatic uploading of a file via FTP to web service communication, it's all related.

Sometimes it seems like IT is okay with the idea that the business just goes on and operates. I think it's in part to how expenditures work. What happened to the days of IT sitting down with the business, finding what they want then plan out do we build it, outsource it, or buy it?