Servlet, JSP, EJB

Hi!
I have some general questions about jsp and servlets. I develop an internetbased portfoliosystem which uses ejb to extract data from an oracle database.
q1: How can I create a controlling servlet for page direction?
q2: How can my jsp file connect to my ejb (session bean)? Can I do it directly or must I go through an AccessBean? (if accessbean, how do I do that?)
Sincirely,
Nicolai
Answers/examples may also be sent to: [email protected]

1 For a controller servlet you can use a servlet controller model, ie the presentation logic is in the JSP pages , which submits request to the servlet which does appropriate processing and then redirects the flow to another JSP.
2. Your JSP file can connect to EJBs directly through the remote handle of the bean obtained by JNDI lookups. However the JSP gets cluttered with the JNDI lookup codes.If the HTML programmer is different from Java programmer then go for accessor beans.

Similar Messages

Good books for learning Java(Servlets,JSP,EJB,etc.,),Javascript.

Hi Experts,
Can you suggest me some good books on java , javascript.The books should include the internals of Servlets,JSP,EJB.
Thanks
vishal

http://forum.java.sun.com/thread.jspa?forumID=54&threadID=756427&start=7
http://forum.java.sun.com/thread.jspa?forumID=54&threadID=751055
http://forum.java.sun.com/thread.jspa?forumID=54&threadID=743429
http://forum.java.sun.com/thread.jspa?forumID=54&threadID=742997&start=11
http://forum.java.sun.com/thread.jspa?forumID=54&threadID=750775&start=24
Just a simple search for this forum....
It took me 10 seconds tofind these..
JJ

How to run servlets, jsp, ejb..?

dear friends,
i will be happy if anyone suggest how to run jsp, servlets, ejb. and also do give the proper server to run these. it will be helpful if u give the URL's . An early reply is helpful. thanx and bye for now. my email id is [email protected]

this is the site where i learn jsp from :
http://www.jsptut.com/

Ejb + servlet + jsp

Hallo everybody,
i try to develop an application with servlet jsp and ejbs but i don't have enough information about this thema.
for example i want to make a simple login szenario :
user type the name and passwd and the system contact with the db and show a wellcome page if the login is succesfull and an error page if the login is unsuccessfull.
which component does was??
the first page can be a html form and post the name and passwd to a servlet.
in this case servlet can make a connection with the DB and can forward the user to next page or error page. BUT where should i use EJB? can i realize the db connection with ejb ? if yes how can interact the servlet with the ejb and how can i store the information (for example address of user) which i have taken from the DB?
thanks a lot

Thanks for the antwort
this means that the servlet connected to DB and execute the sql to authenticate user??
and the second part is my bigger problem :)
what does it mean "it will pass the control
to the enterprise java bean which will be housing the business logic for your application."
what does a java bean really do? how can i find information about them?
and is ther an example in which i can see how servlets, jsps and beans interact??
thanks

Where should the support classes of servlets, JSPs and EJBs be placed

          Hi
          Could you please tell me where the support classes (simple
          java classes) used by servlets, JSPs and EJBs should be placed.
          I find that my application does not work if I place all the
          support classes of a servlet under $MYSERVER/clientclasses. I need to place some in $MYSERVER/clientclasses and some in
          $MYSERVER/servletclasses. But I figured this out my trial and error and I could not find any logical explanation why some of them should go into $MYSERVER/clientclasses and others into
          $MYSERVER/servletclasses.
          Thanks
          Regards
          Pratima


you can put 'em in weblogic classpath
          Kumar
          Pratima Nambiar wrote:
          > Hi
          > Could you please tell me where the support classes (simple
          > java classes) used by servlets, JSPs and EJBs should be placed.
          > I find that my application does not work if I place all the
          > support classes of a servlet under $MYSERVER/clientclasses. I need to place some in $MYSERVER/clientclasses and some in
          > $MYSERVER/servletclasses. But I figured this out my trial and error and I could not find any logical explanation why some of them should go into $MYSERVER/clientclasses and others into
          > $MYSERVER/servletclasses.
          >
          > Thanks
          > Regards
          > Pratima

Want to run servlets, jsp and ejb

Hi there, I have just installed Oracle9iAS on my PC and want to check how to use OAS with servlets, JSPs and ejbs, so can any one tell me where can I find some worked examples and step by step deployment process, any help would be appreciated, regards, Shabbier

If you have installed Oracle9iAS, you should be able to get to the welcome page at
http://<machine_name>:7778/
You can see J2EE demos off that page.
Also, you can find info about oracle9iAS and documentation
at http://otn.oracle.com/products/ias/content.html
OC4J info can be found at
http://otn.oracle.com/tech/java/oc4j
-Prasad

Forwarding request from JSP/Servlet to EJB

Is it possible to forward the HttpRequest,HttpResponse objects from a Servlet/JSP to an Entity/Session bean ?
ie To forward the call using RequestDispatcher/forward to a Session bean which in turn calls the entiy bean for updating DB
Ramesh

I don't think that's possible and even if it is there's an easier way. Normally you just create an instance of the session bean in a servlet and pass it the information. The session bean then calls the entity bean which updates the database. You don't have to forward the request - just pass the data to the bean.

Class not found javax.servlet.jsp.jstl.sql.Result in Richfaces

When I try to run the richfaces application using Weblogic 10.3 AS and Netbean IDE 6.9.1, I found ClassNotFoundException on javax.servlet.jsp.jstl.sql.Result class.
I class path the following libs.
commons-beanutils-core-1.8.0.jar
commons-digester-1.8.jar
commons-fileupload-1.2.1.jar
commons-io-1.2.jar
commons-logging-1.1.1.jar
glassfish.el_2.1.1.jar
glassfish.jsf_1.2.9.0.jar
javassist-3.8.0.GA.jar
jhighlight-1.0.jar
jsf-facelets.jar
jsf-api.jar
log4j-1.2.14.jar
richfaces-api-3.3.0.GA.jar
richfaces-impl-3.3.0.GA.jar
richfaces-ui-3.3.0.GA.jar
glassfish.jstl_1.2.0.1.jar
Also I try to deploy without using some jar files already exists in application server.
My web.xml configuration is-
<context-param>
<param-name>org.richfaces.SKIN</param-name>
<param-value>#{skinSelector.skin}</param-value>
</context-param>
<context-param>
<param-name>org.richfaces.CONTROL_SKINNING</param-name>
<param-value>enable</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.VIEW_HANDLERS</param-name>
<param-value>com.sun.facelets.FaceletViewHandler</param-value>
</context-param>
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>server</param-value>
</context-param>
<context-param>
<param-name>org.ajax4jsf.SKIN</param-name>
<param-value>skin_name</param-value>
</context-param>
<filter>
<display-name>RichFaces Filter</display-name>
<filter-name>richfaces</filter-name>
<filter-class>org.ajax4jsf.Filter</filter-class>
</filter>
<filter-mapping>
<filter-name>richfaces</filter-name>
<servlet-name>Faces Servlet</servlet-name>
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
<dispatcher>INCLUDE</dispatcher>
</filter-mapping>
<servlet>
<servlet-name>Faces Servlet</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>Faces Servlet</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<login-config>
<auth-method>BASIC</auth-method>
</login-config>
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
<welcome-file-list>
<welcome-file>index.jsp</welcome-file>
</welcome-file-list>
I also try to configure <library-ref>....</libray-ref> configuration in weblogic.xml and weblogic-application.xml and I also deploy JSF-2.0.war as library in application.
Please
h5.MUTU

So why didn't you think that the JSP forum here wasn't a good place to ask JSP questions like this one?
You can use <c:for-each> with a List. That's how it's designed. I don't understand why you say you can't. Perhaps you were confused by the SQL tags in JSTL. But anyway, you should just return a List from your EJB and forget about using obscure internal JSP classes.

Web Services - Servlets vs EJBs

Hi,
Looking for any suggestions about the benefits of using either servlets or EJBs as web service endpoints. Very early in the design of any application, I wish to expose my business logic components as web services, is there any particular benefit to using a specific approach (i.e. using either EJBs or Servlets as the end points of the web services exposing the business logic)?
This is a totally new application so I have no considerations towards reusing old EJB code, etc. My initial thoughts favour using servlets, if only because it reduces the complexity / resources required for the application server (i.e only Web-container required, rather than Web & EJB container).
Any thoughts please?

Why do Servlets not scale as well? Surely they are
more "lightweight" than an EJB (which has all theRMI
overhead), and wouldn't it ultimately be down tothe
underlying app server anyway?Right, but servlets are just HTTP request listeners.
They aren't components, they aren't transactional,
they don't handle persistence, they don't have
naming services, they don't have queuing services.
The EJB container offers you a lot.
With that said, it's not just a choice between
servlets and EJBs. You can use POJOs and avoid EJBs
altogether if you do it right.
Or choose the best of both worlds and mix 'n match as needed.
Noone forces you to choose one over the other (at least not for any technical reasons, I'm not diving into corporate politics here).
My thought was that web services were a better wayto
expose business logic than EJBs, but if there some
solid reason why this isn't the case I like toknow.
Web services - lightweight? Maybe that's true of
REST, but certainly not SOAP. There's an argument
that says services are more heavyweight than EJBs,
because all the XML on the wire is an expensive
protocol.
SOAP is heavy on the network, but it's essentially a rather thin layer on top of other services (if properly architected).
For example we have a SOAP layer exposing a Spring application which proxies an EJB architecture.
Next to that SOAP layer sits a traditional web application (servlets) which itself has a Spring application sitting on top of it for demonstration and testing purposes.
And then there's an SDK allowing direct access to the Spring layer (and thus almost direct access to the EJB layer).
That's the beauty of a true open architecture, each component can be built on top of another and the component underneath can function just fine without it.
Look into Spring:
http://www.springframework.org
It's a lighter alternative to EJBs, and good plumbing
for any Java EE app.While Spring can serve as an alternative for EJB in places where EJB are overkill it's of course not in competition with it.
Spring is a service layer, making use of other technologies (like EJB, like AOP, like ORM) to provide data and other services (like Struts, like JSF, like JSP) to provide that data to requesters.

Desperate, help please Servlet.service() for servlet jsp threw exception

Hi,
I have completed 99.99% of project development, when I am about to deploy JSC throws "Servlet.service() for servlet jsp threw exception javax.faces.el.EvaluationException: java.lang.NullPointerException" I can't understand why.
My application was working absolutely fine, I can't understand why its throwing exception now.
I tried debuging, but i can't understand where exactly its throwing exception and whats the error.
I would really appreciate your help, I have spent almost a day trying to figure out but din't get anywhere.
here is my server.log
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2005-08-23T11:44:39.221+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_06] from [Sun Microsystems Inc.]|#]
[#|2005-08-23T11:44:42.025+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2005-08-23T11:44:42.327+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2005-08-23T11:44:44.572+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2005-08-23T11:44:44.598+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2005-08-23T11:44:44.616+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2005-08-23T11:44:51.061+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2005-08-23T11:44:53.917+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2005-08-23T11:44:54.400+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2005-08-23T11:44:56.346+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2005-08-23T11:44:58.494+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2005-08-23T11:44:58.494+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2005-08-23T11:44:59.954+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2005-08-23T11:45:01.401+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [ConverterApp] loaded successfully!|#]
[#|2005-08-23T11:45:01.407+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [ConverterApp:war-ic.war] in virtual server [server] at [converter]|#]
[#|2005-08-23T11:45:02.500+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [travelApp] loaded successfully!|#]
[#|2005-08-23T11:45:02.792+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [HelloWorldApp] loaded successfully!|#]
[#|2005-08-23T11:45:02.798+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2005-08-23T11:45:03.281+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2005-08-23T11:45:03.335+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2005-08-23T11:45:03.338+0100|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2005-08-23T11:45:03.351+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2005-08-23T11:45:03.371+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [jTravellerService] in virtual server [server] at [jTravellerService]|#]
[#|2005-08-23T11:45:03.399+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [hello-jaxrpc] in virtual server [server] at [hello-jaxrpc]|#]
[#|2005-08-23T11:45:03.427+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2005-08-23T11:45:03.428+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2005-08-23T11:45:03.637+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2005-08-23T11:45:13.214+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2005-08-23T11:45:14.087+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2005-08-23T11:45:14.268+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2005-08-23T11:45:18.600+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.12: JAX-RPC context listener initializing|#]
[#|2005-08-23T11:45:18.657+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.webservices.rpc.server.http|_ThreadID=10;|JAXRPC.JAXRPCSERVLET.14: JAX-RPC servlet initializing|#]
[#|2005-08-23T11:45:20.710+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 18080|#]
[#|2005-08-23T11:45:20.790+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 18080|#]
[#|2005-08-23T11:45:21.125+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 11043|#]
[#|2005-08-23T11:45:21.144+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 11043|#]
[#|2005-08-23T11:45:21.503+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 14848|#]
[#|2005-08-23T11:45:21.537+0100|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 14848|#]
[#|2005-08-23T11:45:21.989+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/Creator/SunAppServer8/imq/bin].|#]
[#|2005-08-23T11:45:22.003+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1124793922003|#]
[#|2005-08-23T11:45:22.009+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2005-08-23T11:45:22.012+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2005-08-23T11:45:27.303+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ResourceDeployEvent -- deploy jcp/RaveGenerated_1124793926_NFDBPool]|#]
[#|2005-08-23T11:45:28.918+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5004: Resource Deployed: [jcp:RaveGenerated_1124793926_NFDBPool].|#]
[#|2005-08-23T11:45:29.169+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ResourceDeployEvent -- deploy jdbc/jdbc/NFDB]|#]
[#|2005-08-23T11:45:29.365+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=11;|CORE5004: Resource Deployed: [jdbc:jdbc/NFDB].|#]
[#|2005-08-23T11:45:31.996+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5109: EJBC - START of EJBC for [_linnfdb]|#]
[#|2005-08-23T11:45:31.999+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Processing beans ...|#]
[#|2005-08-23T11:45:32.032+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|DPL5110: EJBC - END of EJBC for [_linnfdb]|#]
[#|2005-08-23T11:45:32.915+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|Total Deployment Time: 2082 msec, Total EJB Compiler Module Time: 37 msec, Portion spent EJB Compiling: 1%
Breakdown of EJBC Module Time: Total Time for EJBC: 37 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 19 msec (51%),
|#]
[#|2005-08-23T11:45:32.928+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=11;|deployed with moduleid = _linnfdb|#]
[#|2005-08-23T11:45:32.990+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- deploy web/_linnfdb]|#]
[#|2005-08-23T11:45:33.275+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1041:Sent the event to instance:[ModuleDeployEvent -- enable web/_linnfdb]|#]
[#|2005-08-23T11:45:33.352+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WEB0100: Loading web module [_linnfdb] in virtual server [server] at [linnfdb]|#]
[#|2005-08-23T11:45:34.837+0100|WARNING|sun-appserver-pe8.0.0_01|org.apache.commons.beanutils.MethodUtils|_ThreadID=11;|Cannot use JVM pre-1.4 access bug workaround die to restrictive security manager.|#]
[#|2005-08-23T11:45:35.346+0100|WARNING|sun-appserver-pe8.0.0_01|org.apache.commons.digester.Digester|_ThreadID=11;|[ConverterRule]{faces-config/converter} Merge(null,java.math.BigDecimal)|#]
[#|2005-08-23T11:45:35.364+0100|WARNING|sun-appserver-pe8.0.0_01|org.apache.commons.digester.Digester|_ThreadID=11;|[ConverterRule]{faces-config/converter} Merge(null,java.math.BigInteger)|#]
[#|2005-08-23T11:45:37.265+0100|INFO|sun-appserver-pe8.0.0_01|com.sun.faces.config.ConfigureListener|_ThreadID=11;|Application object verification completed successfully|#]
[#|2005-08-23T11:45:37.396+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=11;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2005-08-23T11:46:28.167+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=12;|login successfull145|#]
[#|2005-08-23T11:46:28.961+0100|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.stream.out|_ThreadID=12;|
assigned to user query|#]
[#|2005-08-23T11:46:34.715+0100|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=12;|ApplicationDispatcher[/linnfdb] Servlet.service() for servlet jsp threw exception
javax.faces.el.EvaluationException: java.lang.NullPointerException
at
com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:206)
     at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:154)
     at javax.faces.component.UISelectItems.getValue(UISelectItems.java:110)
     at com.sun.faces.util.Util.getSelectItems(Util.java:602)
     at com.sun.faces.renderkit.html_basic.MenuRenderer.getOptionNumber(MenuRenderer.java:488)
     at com.sun.faces.renderkit.html_basic.MenuRenderer.renderSelect(MenuRenderer.java:465)
     at com.sun.faces.renderkit.html_basic.MenuRenderer.encodeEnd(MenuRenderer.java:430)
     at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:720)
     at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:443)
     at com.sun.faces.renderkit.html_basic.GroupRenderer.encodeChildren(GroupRenderer.java:130)
     at javax.faces.component.UIComponentBase.encodeChildren(UIComponentBase.java:701)
     at com.sun.faces.renderkit.html_basic.HtmlBasicRenderer.encodeRecursive(HtmlBasicRenderer.java:435)
     at com.sun.faces.renderkit.html_basic.TableRenderer.encodeBegin(TableRenderer.java:113)
     at javax.faces.component.UIComponentBase.encodeBegin(UIComponentBase.java:683)
     at javax.faces.component.UIData.encodeBegin(UIData.java:681)
     at javax.faces.webapp.UIComponentTag.encodeBegin(UIComponentTag.java:591)
     at javax.faces.webapp.UIComponentTag.doEndTag(UIComponentTag.java:543)
     at com.sun.faces.taglib.html_basic.DataTableTag.doEndTag(DataTableTag.java:491)
     at org.apache.jsp.NationalFaultsDataBase_jsp._jspx_meth_h_dataTable_0(NationalFaultsDataBase_jsp.java:581)
     at org.apache.jsp.NationalFaultsDataBase_jsp._jspx_meth_h_form_0(NationalFaultsDataBase_jsp.java:331)
     at org.apache.jsp.NationalFaultsDataBase_jsp._jspx_meth_f_view_0(NationalFaultsDataBase_jsp.java:291)
     at org.apache.jsp.NationalFaultsDataBase_jsp._jspService(NationalFaultsDataBase_jsp.java:182)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:718)
     at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:478)
     at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:413)
     at org.apache.catalina.core.ApplicationDispatcher.access$000(ApplicationDispatcher.java:77)
     at org.apache.catalina.core.ApplicationDispatcher$PrivilegedForward.run(ApplicationDispatcher.java:92)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:319)
     at com.sun.faces.context.ExternalContextImpl.dispatch(ExternalContextImpl.java:322)
     at com.sun.faces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:130)
     at com.sun.jsfcl.app.ViewHandlerImpl.renderView(ViewHandlerImpl.java:181)
     at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:87)
     at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:221)
     at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:117)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:198)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at linnfdb.data.SecurityCheckFilter.doFilter(SecurityCheckFilter.java:102)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:218)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:188)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NullPointerException
     at com.sun.jsfcl.data.ResultSetPropertyResolver$ColumnData.getSelectItems(ResultSetPropertyResolver.java:303)
     at com.sun.jsfcl.data.ResultSetPropertyResolver.getValue(ResultSetPropertyResolver.java:61)
     at com.sun.faces.el.impl.ArraySuffix.evaluate(ArraySuffix.java:167)
     at com.sun.faces.el.impl.ComplexValue.evaluate(ComplexValue.java:151)
     at com.sun.faces.el.impl.ExpressionEvaluatorImpl.evaluate(ExpressionEvaluatorImpl.java:243)
     at com.sun.faces.el.ValueBindingImpl.getValue(ValueBindingImpl.java:173)
     ... 115 more
|#]
any help will be greatly appreciated. Pleaseeeeeeeeeeeeee can some get back to me.
Cheers
kumar

hi,
I just found that this exception is thrown from function
public UIViewRoot createView(FacesContext context, String viewId) {
UIViewRoot viewRoot = handler.createView(context, viewId);
context.getExternalContext().getRequestMap().put(CREATED_VIEW, viewId);
setupPageBean(context, viewRoot);
return viewRoot;
in viewHandlerImpl.java.
Has anyone got ideas about this???
Any help will be greatly appreciated.
cheers
kush

When to Use Servlet only, EJB only and, both Servlet And EJB???

I have a question, If I want to build a Web application. Sometime i found that there is no need to use EJB as Servlet already provide that functionality.
Can anyone tell me when do I use Pure Servlet? When do I use Pure EJB and, When do I use Both EJB and Servlet???
I am very interesting in it.
Thanks.
Jack

EJB and servlets are two different things. Trying to compare them doesn't really make sense. A web application is always going to need some way to process Http requests and this in Java is done accomplished through Servlets (or jsp pages which in turn also use servlets).
EJBs are the basis of distributed cross-platform objects. They are handled through name services and stored in databases. An Entity Bean can be "brought back to life" as long as it's info is stored in a database. Regardless of a server being restarted. All this database support behind an Entity Bean (transactions, queries etc.) are very transparent to the programmer. They are provided by the EJB vendor.
The class properties of a Servlet (or class-level member variables) are shared among all requests (running thread instances of the service method). That's why they should be used with a lot of caution. This feature can be very useful but if used improperly can also be very vulnerable to security and synchronization issues.
I'm not an EJB expert but this explanation should give you some idea of what EJBs are all about.

How to pass submitted Data from a servlet to EJB Session Bean in JPA

How to pass Data User submitted Data from a servlet to EJB Session Bean when using JPA :
Hi ,
I have a jsp page in which the user fills up the Data and submits it to the servlet :
Inside servlets i am getting all the parameters and setting it to the Entity Class .
Sample Entity class is shown below :
@Entity
public class Employee {
@Id private int id;
private String name;
public Employee() {}
public Employee(int id) { this.id = id; }
public int getId() { return id; }
public void setId(int id) { this.id = id; }
public String getName() { return name; }
public void setName(String name) { this.name = name; }
}After calling setters of my Entity Class .
I am using JNDI lookup to call my session Bean method and pass this Entity class to the session Bean to persist data
Please let me know what will be the right approach :
1. Passing parameters whole as a Entity Class
that is
public void insertData(Employee emp)
}Or
2. public void insertData(String Name , int ID)
}

they are both right as they both work. Easy huh?
You might argue that if you have to set a lot of fields, use the entity as otherwise you get a method with a gigantic amount of parameters.

Desgin issue, Servlets with EJBs in real life?

When designing a web application with WLS and has anyone made extensive use
of EJBs with Servlets/JSP.
Servlets and JSPs are pretty much a must for the web-app, but are EJBs
really so?. Correct me if I am wrong, the reason that we would wanna use
EJBs (especially I am talking about session EJBs), within servlets
is the fact that they are transactional (so you don't implement transaction
logic in your code), or their being clusterable, thus higher availability by
failovers, etc, ,
They are not faster than standard Java, actually.
by using EJBs in our design we're not gonna gain that much of a speed and
our development time is gonna be longer (well, if designed well, EJBs might
be good candidates for reusability),
instead they are gonna give us higher reliability and availability, along
with a cost of rather slower
responses.
I'll post an explanation of the simle load tests that I have done on the WLS
with two different architectures,
namely Servlet + Std. Java & Servlet + Stateless EJB, shortly
Any comments appreciated,
thanks,
ali.

EJBs are a tool in your arsenal. Just like Servlets -- you don't hear
developers suggesting that you avoid Servlets/JSPs and just handle port 80
directly in your own code!
Yes, they are transactional objects for Java. Half the time they are a pain
in the a** but they are better than everyone making up their own standard.
They are not faster than standard Java, actually.They are standard Java, so they are not faster. Since the container either
gens code or uses reflection or both to run them, they are typically a bit
slower than doing direct JDBC (for example) in your servlets. Also, it is
easy to get very bad performance if you don't realize how many database
operations a set of ejb invokes can be.
All in all, once you know EJBs you will probably want to use them, because
they get the job done and are pretty efficient when built correctly. Until
then, they will seem like a pain, largely because they are ;-)
Peace,
Cameron Purdy
Tangosol, Inc.
http://www.tangosol.com
+1.617.623.5782
WebLogic Consulting Available
"ali" <[email protected]> wrote in message
news:[email protected]...
When designing a web application with WLS and has anyone made extensiveuse
of EJBs with Servlets/JSP.
Servlets and JSPs are pretty much a must for the web-app, but are EJBs
really so?. Correct me if I am wrong, the reason that we would wanna use
EJBs (especially I am talking about session EJBs), within servlets
is the fact that they are transactional (so you don't implementtransaction
logic in your code), or their being clusterable, thus higher availabilityby
failovers, etc, ,
They are not faster than standard Java, actually.
by using EJBs in our design we're not gonna gain that much of a speed and
our development time is gonna be longer (well, if designed well, EJBsmight
be good candidates for reusability),
instead they are gonna give us higher reliability and availability, along
with a cost of rather slower
responses.
I'll post an explanation of the simle load tests that I have done on theWLS
with two different architectures,
namely Servlet + Std. Java & Servlet + Stateless EJB, shortly
Any comments appreciated,
thanks,
ali.

Can the servlet/jsp engine be brought down

Hello,
          Can the servlet/jsp engine be scheduled for a "in-house patch" not affecting
          the EJB Container? That means the jsp/servlet engine is brought down.
          (HotDeploy is a development feature). Does any version of WebLogic provide
          any way to do this?
          It is a single VM and I suppose that this is not possible. Just thinking out
          loud!!
          Thanks
          Gaurav


Sorry, but there's no way to apply a hot-patch to the server. Good idea, but
          very tricky to implement!
          If you were using a cluster with session-replication, you can cycle the
          servers one at a time. The other servers will pick up where the
          downed-server was working. You can then apply the patch, and bring up the
          server again. Give it a few minutes (an hour to be safe!) to replicate from
          the running server, then cycle the other server safely.
          Alex
          "Gaurav Khanna" <[email protected]> wrote in message
          news:3c7c1256$[email protected]..
          > Hello,
          >
          > Can the servlet/jsp engine be scheduled for a "in-house patch" not
          affecting
          > the EJB Container? That means the jsp/servlet engine is brought down.
          > (HotDeploy is a development feature). Does any version of WebLogic provide
          > any way to do this?
          > It is a single VM and I suppose that this is not possible. Just thinking
          out
          > loud!!
          >
          > Thanks
          > Gaurav
          >
          >
          >
          >

Javax.servlet.jsp.jstl.sql.Result and arraylist

Hi,
I try to explain my problem, I have posted in another section of forum, but perhaps this is a better place:
I'm trying to use MVC model, so I call an EJB from a servlet which returns me a javax.servlet.jsp.jstl.sql.Result object (this derive from a resultset of a query) and then I make this available to a jsp page.
I've choosen to return an javax.servlet.jsp.jstl.sql.Result object because I'd like to use this syntax:
<c:forEach var="profiloString" items="${listaProfili}" >
${profiloString.anything}
</c:forEach>Now I need to put my listaProfili object in session and permit users of my application to add and delete items from it. Finally I will update my database with the new data from listaProfili object.
If listaProfili is an arraylist I can easily add or delete item from it, but if it is a javax.servlet.jsp.jstl.sql.Result I don't know how I can do this.
If I return an arraylist object instead of an javax.servlet.jsp.jstl.sql.Result object, I can't use "<c:forEach ..." syntax.
Can anyone help me?
Thanks.

So why didn't you think that the JSP forum here wasn't a good place to ask JSP questions like this one?
You can use <c:for-each> with a List. That's how it's designed. I don't understand why you say you can't. Perhaps you were confused by the SQL tags in JSTL. But anyway, you should just return a List from your EJB and forget about using obscure internal JSP classes.

Servlet, JSP, EJB

Similar Messages

Maybe you are looking for