On your way in you may have missed that JavaRanch has a policy on display names, and yours does not comply with it - please adjust it accordingly, which you can do right here. Thanks for your prompt attention to this matter.
J2EE is a big bunch of APIs, some of which you may need to use (or not, depending on your circumstances). But it sounds as if you may end up just using J2SE with JDBC, so you won't have a server, and likely won't need any J2EE APIs.
Number of machine can be 100 at most. Does it really make a difference whether the number is two or half a million? please i have no intention to hurt your feeling. whatever be the number, i have to use thread at the time of swing design, right?
so, you suggest only the use of core java and jdbc. i do not have to use j2ee api??? the problem can be implemented that way??? here is the situation again: there is a server with sql server running on it. a number of machine is connected through LAN. each machine has their own OS.
j2se is enough?? j2ee not required ??
if j2ee is used - in that scenario, which part will be good 1> servlet & jsp or 2> EJB
i have two sun certification - SCJP and SCBCD. i am not very confident on servlet and jsp
What would you use the web server for? It would have certain benefits, but it is absolutely not required in general.
A desktop application can connect to a DB using JDBC. The DB should be able to handle 100 concurrent incoming connections. If they all connect at the same time and perform complex queries, performance might not be good, but that's a different matter.
I'm getting the impression that you don't really know what J2EE is or does, which is understandable if you don't have software development experience. J2EE is a set of Java APIs which go above and beyond what the J2SE APIs provide. Usually, J2EE implies running a server of some kind, but that's not necessarily so. By itself, J2EE does neither guarantee good or bad performance. Whether it might be beneficial in your situation depends on your circumstances, about which we know nothing. You might want to dig deeper into the Sun J2EE site to learn more about it.
You don't really know what a webserver is, do you?
A webserver is not just a server in a web, but a program, which produces html-pages which can be viewed in a browser. A ftpserver is a server too, and as most well known server, acting in a/ the web too, but it isn't a webserver.
Querying a database on the local machine via jdbc is just a special case of sending a query to a host, you just use another hostname/ IP.
Without any real life software developement experience, the intermediate section might have been a better place to ask.
The answer to that question goes way beyond what can be explained in a message. You need to read up on enterprise and distributed computing.
should i use ejb technology, or servlet & jsp technology? or should i just use core java and jdbc driver.
Both are possible solutions (although I don't see what JSP would be good for). As I said before, from what you describe it sounds like Swing+JDBC might suffice.
I suggest that you do some reading about web servers, application servers, servlets/JSP and EJBs. That will give you a better idea of what these technologies do, and how they might be applied to your situation.
Hi. Since I'm no Java Expert maybe I shouldn't be posting in this thread but in this case would just want to recommend the book Head First Servlets & JSP to the guy with the problem. An excellent book on the topic. And while at it, maybe Head First EJB also..... (Go Kathy!!!) [ February 04, 2006: Message edited by: Tomas Hertzman ]