We are a company there have a huge web application running. The system is coded in Oracle, JSP, Java, JavaScript using Backbase, where the transport for data and function calls to Oracle is done using xml.
We are thinking about changing the interface framework and that's why I'm looking at Kendo UI.
I'm managed to make extended dataSources (connected to Oracle by using the existing xml interface) in JavaScript executed from JSP (Not using libtagging) by using "new kendo.data.DataSource". I have build custom observes, grids, forms and other controls with data binding in a MVVM environment.
That all works very well. Have made all the code in js files and is using jQuery Ajax to loads interface parts.
Now to my question.
I can see in examples when running JSP in a MVVM environment, kendo UI are talking about doing the widget extension in java, making a bean and libtag it in jsp.
What benefits do I get by coding the widgets in java instead simply directly in JavaScript?
Please advice :-)
We are thinking about changing the interface framework and that's why I'm looking at Kendo UI.
I'm managed to make extended dataSources (connected to Oracle by using the existing xml interface) in JavaScript executed from JSP (Not using libtagging) by using "new kendo.data.DataSource". I have build custom observes, grids, forms and other controls with data binding in a MVVM environment.
That all works very well. Have made all the code in js files and is using jQuery Ajax to loads interface parts.
Now to my question.
I can see in examples when running JSP in a MVVM environment, kendo UI are talking about doing the widget extension in java, making a bean and libtag it in jsp.
What benefits do I get by coding the widgets in java instead simply directly in JavaScript?
Please advice :-)