Originally posted by madhavi mahi:
Hi All,
Please let me know (If anybody have attended an interview in [ company X ])what type of questions will be asked in [ company X ] for 2+ years experienced in java & J2EE.
Thanks,
Madhavi
[ April 08, 2008: Message edited by: Ulf Dittmer ]
Originally posted by Prad Dip:
Can someone pass me tutorial link. I could not see anything in the sun site.
Originally posted by Prad Dip:
Can you tell us the resosurces over which applets gain control over ? thanks
Originally posted by Ulf Dittmer:
Careful now. There are two things called "plugin" in this context, and I'm almost certain that Stuart is asking about one (the Java-enabling plugin for web browsers), and you (Rahesh) are talking about the other one (the plugin for NetBeans that helps JavaFX development).
Note that the NetBeans plugin is not required for developing with JavaFX, nor is NetBeans itself (even though you could certainly get that impression from the OpenJFX web site). A regular Java 5 JDK is sufficient.
Originally posted by Ulf Dittmer:
I don't really see how. The Java client sandbox is rather more secure than executing JavaScript in a browser.
Originally posted by Ulf Dittmer:
One of the aims of JavaFX (and of the "Consumer JRE") is to address some of the drawbacks of applets. It still makes sense to offload processing to the client; keeping a farm of servers that run web applications is expensive. So it depends on your perspective whether it's a good thing or a bad thing to run code on the client. What's not in doubt is that Java (applets or JavaFX) can provide a richer client environment than HTML/CSS/DOM/JavaScript.
Originally posted by Ulf Dittmer:
It's too early to tell which niche -if any- the various JavaFX technologies will come to occupy. There hasn't been formal release with a stable API yet, so nobody is yet using it on a large scale. Plus, JavaFX is a family of technologies (at least Sun has said that it will be), so there may be very different shapes of it yet to come.