I was just going through an article on JSF and it read "JSF is a model-driven web component application framework whose event model has been compared to that of Swing."
We are currently developing an application which has some screens which are very data intesive, lots of data in tables. So we are planning to use swings instead of struts which was earlier recomended in the architecture doc because the response time we need is very small and we don't think that with struts framework and such huge data to display we will be able to achieve that.
I am pretty amazed with the fact that you are planning to use Swing for a web page? Do you mean in an applet or something? Since JSF and Struts are for web applications running on an application server, how can you plan to deal with client-side Swing for such thing?
Or am I missing something?
I believe the amount of data in tables are not a big deal, whichever frameworks you are going to use... Struts, JSF or sthing else...
Co-author of SCMAD Exam Guide, Author of JMADPlus SCJP1.2, CCNA, SCWCD1.4, SCBCD1.3, SCMAD1.0, SCJA1.0, SCJP6.0
We have the option to implement it either ways. We would have preffered implementing it as a Web Application but then rendering of the pages with huge data would make the acess to such screens slow and so we are planning to use swing.
We will use Java Web Start to access our application.
I don't believe the amount of data makes a difference. Either way, Swing or web app, the data has to travel over the network. So that's the bottleneck, not the API.
The only reason I might suggest a web app over a Swing Desktop app, since I am a pretty big fan of Swing and desktop apps, is that by doing a swing app you are putting requirements on the client PC's. They will be required to have the JRE installed on their PC's. This probably isn't an issue where you work but it is something to think about. With a web app, the users just need a web browser.
As far as Struts or JSF; it's such a toss up right now IMHO. Struts is an industry proven, mature framework with a huge user, aka support, base. JSF is the new buzz.
Personally, I prefer JSF over struts. I prefer component oriented frameworks. I even like Tapestry better than struts. Tapestry is another component oriented framework. I can just wrap my head around it a bit better I suppose. In all honesty it's all just developer preference. I don't really get into the Struts vs JSF debates. Use whichever one you feel more comfortable with and whichever one you feel like you can acomplish your task the best way possible. Both are going to be around for quite some time.
posted 15 years ago
Actually for our product we have to display hundreds of records with some 30-40 columns in a table and there can be 3 such tables in a screen. The tables will have scroll bar. So if we develop a web app we will have to fetch all the records at the time of displaying the page the first time but with swings we can fetch only a certain number of records and we will fetch others only when the user scrolls down using the scroll bar.
I hope I am communicating. Actually we had faced a similar problem in another project, which was a web-based project, and the user had reported issues that the page takes a lot of time for rendering.
Can you plz. suggest how can we avoid such issues in a web application or using swings in such scenario is a better approach.
The tables will have scroll bar. So if we develop a web app we will have to fetch all the records at the time of displaying the page the first time but with swings we can fetch only a certain number of records and we will fetch others only when the user scrolls down using the scroll bar.
Why dont you fetch them in groups for web app as well.