This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
Hi Vishal- I went thru the link. Your "chip factory" GUI doesn't look so overwhelming. Why don't you stay with only J2EE, with HTML/DHTML/JSP as the front-end view, and EJB for the business methods ? I have worked with Swing and I know it can result in pretty GUIs, but I am not at all sure how to interact a Swing client with the EJB backend. Someone said that one has to use RMI. Will it be then that the Swing client, ALSO acting as a RMI stub, has to call the RMI skeleton/server method which, in turn, will act as a client to the EJBs? I want to know more about this. Also I was reading somewhere that Swing should be avoided with the app server beans code (to avoid implicit multithreading), but then may be it is ok on the client side. I have personally found Swing to be very slow on Solaris (I had a large menu/submenu hierarchy, it was with Java 1.3). Thanks, Sudd