Problem while migrating from JSF1.1 to JSF1.2

Question

I'm facing the following issues while migrating from WAS 6.1 to WAS7.0
For this I have upgraded Jsf 1.1 to 1.2 and webmodule to 2.5, and following errors I'm having...
1. Description     The method getExceptionMessageString(String) is undefined for the type Util
2. Description The method getMyForm(UIComponent) in the type CommandLinkRenderer is not applicable for the arguments (FacesContext, UICommand)     
3. Description     The method getName() is undefined for the type HtmlBasicRenderer.Param     LinkRendererWithName.java
4. Description     The method getParamList(UIComponent) in the type HtmlBasicRenderer is not applicable for the arguments (FacesContext, UICommand)
5. Description     The method getValue() is undefined for the type HtmlBasicRenderer.Param     LinkRendererWithName.java
Any alternative methods to those above methods in JSF1.2?
or am I need to upgrade any of the jaf dependencies?
Any suggestions are appreciated.
Thanks

Answer 1

i_oss wrote:
But you should consider implementing your Renderers only using the API and not extending the com.sun.faces.* implementation classes, or you might end up changing your code again on your next jsf updates.Hm, good thinking. I didn't think about the split between the API and the implementation.
OT question on that subject: is it really good design to have that split? JSF, JAXB, JAX-WS, even CDI has an API and an implementation part to it. But do we really need that? In the case of JSF, you have Mojarra and Myfaces (and some other obscure JSF implementation I believe). But why would you use Myfaces over Mojarra since they both solve the same problem and are both actively developed? Why do we have to deal with API/implementation conflict hell that you can often find when using JAXB, especially in a Mavenized environment? We have Weld as the implementation for CDI. What would move anyone to make a 'competing' implementation of it?
For something like JPA I can at least understand it; the persistence providers were already there before JPA saw the light of day. There was no need for Sun to create a competing implementation, so they provided the API in stead. But in all other cases... I just don't get it.