JavaServer Faces - How to migrate from JSF 1.1.01 to JSF 1.2
Hello guys,
Here in my company we are trying to migrate from 1.1.01 to 1.2 but we have some customs components , here one of our customs components.
publicclass ColumnItemsTagextends com.sun.faces.taglib.BaseComponentTag{
// proprietary code
}
But in JSF 1.2 do not exists anymore this class: com.sun.faces.taglib.BaseComponentTag.
Here some others problems:
Util.LIFECYCLE_ID_ALREADY_ADDED_ID;//This constant doesn't exist anymore
Util.NULL_PARAMETERS_ERROR_MESSAGE_ID;//This constant doesn't exist anymore
Util.renderPassThruAttributes(x,y,z);//This method doesn't exist anymore
Util.getExceptionMessageString( x );//This method doesn't exist anymore
What I need to do OR What can I do to solve these problems ?
Thanks in advice.
# 1
You take a risk of running into problems like you're describing anytime you extend or reference implementation specific classes.
Best I can say if you wish to continue this practice, is to get the 1.2 source bundle and make the appropriate changes.
Thought I highly recommend writing your own equivalents to allow you to be portable across implementations.
# 2
Thanks for reply rlubke,
[quote]
You take a risk of running into problems like you're describing anytime you extend or reference implementation specific classes.
[/quote]
So the best choice is make my component independent of specification / implementation right ?
[quote]
Best I can say if you wish to continue this practice, is to get the 1.2 source bundle and make the appropriate changes.
[/quote]
No way. I'll not continue with this practice. Btw these components are made by some guys that not work here now.
[quote]
Thought I highly recommend writing your own equivalents to allow you to be portable across implementations.
[/quote]
Thank for the advice.
So , what can I do to solve this "litle" problem in a easy way? Can you be more specific ?
Thank you.
# 3
So the best choice is make my component independent
of specification / implementation right ?
As long as your component complies with the specification, it should run on any specification compliant runtime.
No way. I'll not continue with this practice. Btw
these components are made by some guys that not work
here now.
Good choice.
[quote]
Thought I highly recommend writing your own
equivalents to allow you to be portable across
implementations.
[/quote]
Thank for the advice.
So , what can I do to solve this "litle" problem in a
easy way? Can you be more specific ?
No matter what, there is going to be work involved. Since the RI source is open sourced under the CDDL, you should be able to leverage its source as long as you follow the CDDL guidelines.
# 4
No matter what, there is going to be work involved. Since the RI source is open sourced under the CDDL, you should be able to leverage its source as long as you follow the CDDL guidelines.
Thank you a ton rlubke.
Tomorrow I'll talk with my manager and we will take some decisions.
Thank you again man.
Cya.
