Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

Buk Lau

Greenhorn
+ Follow
since Nov 06, 2002
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Buk Lau

When submitting a form to a servlet, I process the input parameters and then use:
rd = getServletContext().getRequestDispatcher(URL);
rd.forward(request, response);
to forward to the appropriate jsp page.
I notice that other websites (in general) have the parameter values in the URL, like www.dictionary.com:
http://dictionary.reference.com/search?q=servlet
I am using Tomcat 4.1.29 and it doens't do that. Does Tomcat have a setting to turn this on? If so, why would I want to turn it on (and why would I not want to use it?
Thanks in advance,
Buk
16 years ago
Is this the "normal" way of doing things?:
I have a jsp page that submits to a servlet where the results are tabulated. I then use response.sendRedirect() to display the results in another JSP page using either request.setAttribute() or session.setAttribute().
--
The reason I'm asking is because I've come across posts where people use response.getWriter() to out.println() the results.
Which way is "correct"? I didn't use the response.getWriter() approach because I the display of the results depended upon the results itself and I didn't want to recompile the servlet if i wanted to change the display of results. I'm also unaware of pro's and con's of either approach.
So again, is the approach I took the "normal" way of doing this type of application?
Thanks in advance,
Buk
16 years ago
When would you use one over the other and why?
Thanks in advance,
Buk
16 years ago
Hi,
I used JBuilder X to create my EJBs and a session facade to access my entity beans and a "business delegate" in front of the session facade so that my client code doesn't have to worry about the EJB details. I am using JBoss 3.2.3 to host the EJBs. Everything compiles fine, but at runtime, I had a "java.lang.NoClassDefFoundError: org/jnp/interfaces/NamingContextFactory" error. I then added jnp-client.jar to my classpath and now I'm getting "java.lang.NoClassDefFoundError: org/jboss/logging/Logger" error. I wanted my client code to not have to worry about the Application Server related details. What am I doing wrong?
Thanks in advance -
Buk