ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I believe weblogic is a commercial product (I have never used it but heard of it) and so you need to pay. Apache+Tomcat is free. That's what I would use. However, if you are working for a company and they are willing to pay, then go with Weblogic.
Hello there - sorry - that was what I meant Java Server Pages (JSP) and J2ME. (I think JSP is for Java Server Pages) I would use JAVA but it would seem that JAVA requires a lot of space on the client side where it seems that the development of a JSP would produce something HTML like and not take up a lot of space on the client side. The only thing is that it would take up processing time too - am I right?
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Okay, JSP and J2ME are different unrelated beasts.
JSP is one Java technology easing the development of server side web applications, that isn't demanding any Java support on the client side.
J2ME is another Java technology allowing to develop lightweight applications on the client side, targetting PDAs, telephones and that kind of small and mobile devices, that may or may not be HTTP clients.
There is no such thing as a J2ME page, J2ME is just a lightweight Java virtual machine.
If one were to make something that is to work on a web page and also work with J2ME, then would they have to make programs using java? Is not Java large and slow so JSP would be preferred (to build the page "on the fly")?
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Quote:
If one were to make something that is to work on a web page and also work with J2ME, then would they have to make programs using java?
If you mean by "something that work on a web page" a Java Applet, then yes it can share pieces of code with a J2ME midlet, but the latter is more restricted on what it can do.
Quote:
Is not Java large and slow
Don't trust those who say that, it is no more true.
Quote:
so JSP would be preferred (to build the page "on the fly")?
Again, J2ME as nothing to do with web pages, nothing.
Moreover, JSP is something like a preprocessor that build java source code on the fly then compile the page to a servlet, so JSP is Java too. Development is faster and execution speed is as good as the one obtained with servlets.
When I mentioned "page", I was referring to a type of .java page: when creating java pages, they are static whereas the .java page (using JSP) is built "on the fly".
I was thinking that for a static page, it has to be downloaded in the person's browser. The browser would have to have enough room for whatever is being downloaded.
For the .jsp page, it is built on the fly - all the processing and resource hits would be on the server side and not on the client side as it would be for java.
Distribution: Solaris 11.4, Oracle Linux, Mint, Debian/WSL
Posts: 9,789
Rep:
Quote:
When I mentioned "page", I was referring to a type of .java page: when creating java pages, they are static whereas the .java page (using JSP) is built "on the fly".
OK, this is better described as java source files. The page term is usually associated with a web (i.e. HTML) page.
Quote:
I was thinking that for a static page, it has to be downloaded in the person's browser. The browser would have to have enough room for whatever is being downloaded.
This is not always true. Java source can represent Java applets that will be downloaded to the client's browser or Java servlets that will be executed by the server.
Applet size is seldom an issue nowadays, with the bandwidth available by xDSL users.
There is also a third technology, Java Web Start, that allows Java applications to be automatically downloaded and cached on the client side. This is overcoming many of the applet's limitations.
Quote:
For the .jsp page, it is built on the fly - all the processing and resource hits would be on the server side
Yup.
Quote:
and not on the client side as it would be for java.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.