EJB & JSP

I'm developing application using J2EE 1.3 beta version, with JDK 1.3.
The application uses JSP to access EJB, said the JSP is contained in a
Web component.
In my JSP, I do a lookup to EJB Home object (as shown on the error
message below). It works fine under beta version.
Recently, I upgraded to J2EE 1.3.1 final release version, with J2SDK
1.3.1_02. When my JSP try
to access EJB, it throw out this message.
type Exception report
message Internal Server Error
description The server encountered an internal error (Internal Server
Error) that prevented it from fulfilling this request.
exception
org.apache.jasper.JasperException: Unable to compile class for JSP
An error occured between lines: 6 and 39 in the jsp file:
/DepartmentList.jsp
Generated servlet error:
/usr/local/j2sdkee1.3.1/repository/valerian.wise-x.com/web/isodms/DepartmentList$jsp.java:77:
Class org.apache.jsp.ListSesHome not found.
ListSesHome listHome =
^
An error occured between lines: 6 and 39 in the jsp file:
/DepartmentList.jsp
Generated servlet error:
/usr/local/j2sdkee1.3.1/repository/valerian.wise-x.com/web/isodms/DepartmentList$jsp.java:78:
Class org.apache.jsp.ListSesHome not found.
(ListSesHome)PortableRemoteObject.narrow(objref,
ListSesHome.class);
^
An error occured between lines: 6 and 39 in the jsp file:
/DepartmentList.jsp
Generated servlet error:
/usr/local/j2sdkee1.3.1/repository/valerian.wise-x.com/web/isodms/DepartmentList$jsp.java:78:
Class org.apache.jsp.ListSesHome not found.
(ListSesHome)PortableRemoteObject.narrow(objref,
ListSesHome.class);
^
An error occured between lines: 6 and 39 in the jsp file:
/DepartmentList.jsp
Generated servlet error:
/usr/local/j2sdkee1.3.1/repository/valerian.wise-x.com/web/isodms/DepartmentList$jsp.java:79:
Class org.apache.jsp.ListSes not found.
ListSes listSession = listHome.create();
^
An error occured between lines: 95 and 109 in the jsp file:
/DepartmentList.jsp
Generated servlet error:
/usr/local/j2sdkee1.3.1/repository/valerian.wise-x.com/web/isodms/DepartmentList$jsp.java:135:
Class org.apache.jsp.DeptInfo not found.
DeptInfo department =
(DeptInfo)i.next();
^
An error occured between lines: 95 and 109 in the jsp file:
/DepartmentList.jsp
Generated servlet error:
/usr/local/j2sdkee1.3.1/repository/valerian.wise-x.com/web/isodms/DepartmentList$jsp.java:135:
Class org.apache.jsp.DeptInfo not found.
DeptInfo department =
(DeptInfo)i.next();
^
6 errors
at
org.apache.jasper.compiler.Compiler.compile(Compiler.java:285)
at
org.apache.jasper.servlet.JspServlet.loadJSP(JspServlet.java:551)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.loadIfNecessary(JspServlet.java:177)
at
org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.java:189)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:382)
at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at
org.apache.catalina.core.ApplicationFilterChain.access$0(ApplicationFilterChain.java:197)
at
org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:176)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:172)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:201)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2343)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:368)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1012)
at
org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1107)
at java.lang.Thread.run(Thread.java:484)
All EJB's Ref were properly defined in WAR, but it still can't access to
those classes.
I have even added in all EJB Home & Remote interface classes to the WAR
under the directory of WEB-INF/classes.
I did not put EJB class under any package with the package statement.
If package if the main problem, is here any work arround solution to
avoid packaging my EJB classes?
Thanks for help.

Package solved the problem.
Work around solution :- include import statement for classes used.

Similar Messages

  • Remove Default EJB/JSP Apps.

    Hi,
    I am wondering rather there are steps to remove the Default EJB/JSP Apps deployed in default installation.
    I only need to run servelt and web caches.
    Thanks,
    Stephen

    Weblogic 5.1 uses an architecture that is very unique. Consider it the
    exception, not the rule. You can NOT support a single deployment binary
    with WL 5.1 and other servers.
    The Weblogic 6.0 architecture is much closer to the others, and
    significantly better than the reference implementation's architecture. In
    6.0 you should be able to make a single app (EAR) that deploys to other
    servers as well.
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "martin" <[email protected]> wrote in message
    news:3a6f070e$[email protected]..
    Hi,
    I have written an application that has EJBs, and JSPs that invoke the
    EJBs. It works on WebLogic 5.1.
    I want to package this application up in such a way that it can be
    deployed on any kind of J2EE application server.
    Using JBoss, I discovered that the JSPs by default do not have access to
    the interfaces supplied in the EJBs. i.e. I have to make copies of the
    EJB's home and remote interfaces, and put them where the JSP files can
    find them.
    This messing about was not neccessary with WebLogic. WebLogic knew to look
    in the EJB JAR files.
    So my question : For compatibility, should I create multiple copies of my
    EJB's interfaces, or is WebLogic's developer-friendly behaviour the
    correct one?
    Thanks, Martin.

  • EJB, JSP on web sphere

    Hello all
    Can someone suggest a beginner's book or introductory resources for writing J2EE applications using EJB, JSP on Web Sphere 5.0?
    thanks a bunch
    Mahesh :)

    For EJBs in general, "Bitter EJB" is a great book
    it's one you can read on the bus, as opposed to a reference manual

  • Super 1.5 - source code level tracing for EJB, JSP and others

     

    Would you want to try new installation for Super 1.6?
    Please visit www.acelet.com
    Thanks.
    "Dominique Jean-Prost" <[email protected]> wrote:
    If only your installation tool was easy to use ...
    dom
    "Wei Jiang" <[email protected]> a écrit dans le message news:
    [email protected]...
    Super supports source code level tracing for Java and JSP!
    Announcement: Super 1.5 - an EJB/J2EE monitoring tool with
    SuperPeekPoke
    SuperLogging
    SuperStress
    SuperEnvironment
    It is free for development.
    You can anomyously down load it from:
    http://www.acelet.com.
    Super is a component based administration tool for EJB/J2ee.
    It provides built-in functionality as well as
    extensions, as SuperComponents. Users can install
    SuperComponents onto it, or uninstall them from it.
    Super has the following functions:
    * A J2EE/EJB monitor.
    * A gateway to EJB servers from different vendors.
    * A framework holding user defined SuperComponents.
    * A PeekPoke tool to read/write attributes from EJBs.
    * A full-featured logging/tracing tool for centralized, chronologicallogging.
    * A Stress test tool.
    * A global environment tool.
    It is written in pure Java.
    The current version support:
    * Universal servers.
    * Weblogic 5.1
    * Weblogic 6.0
    What is new:
    Version 1.50 August, 2001
    Enhancement:
    1. Source code level tracing supports EJB, JSP, java helper and other
    programs which are written in native languages (as long as you
    write correct log messages in your application).
    2. Redress supports JSP now.
    3. New installation with full help document: hope it will be easier.
    4. Support WebSphere 4.0
    Version 1.40 June, 2001
    Enhancement:
    1. Add SuperEnvironment which is a Kaleidoscope with TableView,TimeSeriesView
    and PieView for GlobalProperties.
    GlobalProperties is an open source program from Acelet.
    2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView andPieView.
    Changes:
    1. The structure of log database changed. You need delete old installationand
    install everything new.
    2. The format of time stamp of SuperLogging changed. It is not localedependent:
    better for report utilities.
    3. Time stamp of SuperLogging added machine name: better for clusteringenvironment.
    Bug fix:
    1. Under JDK 1.3, when you close Trace Panel, the timer may not bestopped
    and
    Style Panel may not show up.
    Version 1.30 May, 2001
    Enhancement:
    1. Add ConnectionPlugin support.
    2. Add support for Borland AppServer.
    Version 1.20 April, 2001
    Enhancement:
    1. Redress with option to save a backup file
    2. More data validation on Dump Panel.
    3. Add uninstall for Super itself.
    4. Add Log Database Panel for changing the log database parameters.
    5. Register Class: you can type in name or browse on file system.
    6. New tour with new examples.
    Bug fix:
    1. Redress: save file may fail.
    2. Install Bean: some may fail due to missing manifest file. Now, itis
    treated
    as foreign beans.
    3. Installation: Both installServerSideLibrary and installLogDatabasecan
    be worked
    on the original file, do not need copy to a temporary directory anymore.
    4. PeekPoke: if there is no stub available, JNDI list would be emptyfor
    Weblogic5-6.
    Now it pick up all availble ones and give warning messages.
    5. Stress: Launch>Save>Cancel generated a null pointer exception.
    Changes:
    1. installLogDatabase has been changed from .zip file to .jar file.
    2. SuperLogging: If the log database is broken, the log methods willnot
    try to
    access the log database. It is consistent with the document now.
    3. SuperLogging will not read system properties now. You can put logdatabase
    parameters in SuperLoggingEJB's deployment descriptor.
    Version 1.10 Feb., 2001
    Enhancement:
    1. Re-written PeekPoke with Save/Restore functions.
    2. New SuperComponent: SuperStress for stress test.
    3. Set a mark at the highlighted line on<font size=+0> the Source Code
    Panel (as a work-a-round for JDK 1.3).</font>
    4. Add support for WebLogic 6.0
    Bug fix:
    1. Uninstall bean does physically delete the jar file now.
    2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
    Version 1.00 Oct., 2000
    Enhancement:
    1. Support Universal server (virtual all EJB servers).
    2. Add Lost and Found for JNDI names, in case you need it.
    3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDIname
    (mainly
    for Envoys which do not support JNDI list).
    Version 0.90: Sept, 2000
    Enhancement:
    1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
    and alike) as input values.
    2. Reworked help documents.
    Bug fix:
    1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
    further time-out.
    2. MDI related bugs under JDK 1.3.
    Version 0.80: Aug, 2000
    Enhancement:
    1. With full-featured SuperLogging.
    Version 0.72: July, 2000
    Bug fix:
    1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
    Version 0.71: July, 2000
    Enhancement:
    1. Re-worked peek algorithm, doing better for concurent use.
    2. Add cacellable Wait dialog, showing Super is busy.
    3. Add Stop button on Peek Panel.
    4. Add undeploy example button.
    Bug fix:
    1. Deletion on Peek Panel may cause error under JDK 1.3. Now it worksfor
    both
    1.2 and 1.3
    Version 0.70: July, 2000
    Enhancement:
    1. PeekPoke EJBs without programming.
    Bug fix:
    1. Did not show many windows under JDK 1.3. Now it works for both 1.2and
    1.3
    Changes:
    1. All changes are backward compatible, but you may need to recompilemonitor
    windows defined by you.
    Version 0.61: June, 2000
    Bug fix:
    1. First time if you choose BUFFER as logging device, message willnot
    show.
    2. Fixed LoggingPanel related bugs.
    Version 0.60: May, 2000
    Enhancement:
    1. Add DATABASE as a logging device for persistent logging message.
    2. Made alertInterval configurable.
    3. Made pace for tracing configurable.
    Bug fix:
    1. Fixed many bugs.
    Version 0.51, 0.52 and 0.53: April, 2000
    Enhancement:
    1. Add support to Weblogic 5.1 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Context sensitive help is available for most of windows: pressF1.
    2. Fix installation related problems.
    Version 0.50: April, 2000
    Enhancement:
    1. Use JavaHelp for help system.
    2. Add shutdown functionality for J2EE.
    3. Add support to Weblogic 4.5 (support for Logging/Tracing and
    user defined GUI window, not support for regular monitoring).
    Bug fix:
    1. Better exception handling for null Application.
    Version 0.40: March, 2000
    Enhancement:
    1.New installation program, solves installation related problems.
    2. Installation deploys AceletSuperApp application.
    3. Add deploy/undeploy facilities.
    4. Add EJB and application lists.
    Change:
    1.SimpleMonitorInterface: now more simple.
    Version 0.30: January, 2000
    Enhancement:
    1. Add realm support to J2EE
    2. Come with installation program: you just install what you want
    the first time you run Super.
    Version 0.20: January, 2000
    Enhancement:
    Add support to J2EE Sun-RI.
    Change:
    1. Replace logging device "file" with "buffer" to be
    compliant to EJB 1.1. Your code do not need to change.
    Version 0.10: December, 1999
    Enhancement:
    1. provide SimpleMonitorInterface, so GUI experience is
    not necessary for developing most monitoring applications.
    2. Sortable table for table based windows by mouse
    click (left or right).
    Version 0.01 November., 1999:
    1. Bug fix: An exception thrown when log file is large.
    2. Enhancement: Add tour section in Help information.
    Version 0.00: October, 1999
    Thanks.

  • EJB+JSP versus PHP

    What is the advantage of using EJB+JSP for a web ticket selling application instead of using PHP?
    Can Java support more customer hits compare to PHP?
    Is EJB+JSP better than PHP? Why?

    I know both PHP and Java. PHP is a more rapid development tool than Java. Once you know it, it is just easier to make simple pages out of it vs Java. In some ways PHP is easier to develop in and in some ways it is harder.
    There is no real IDE for PHP. There are some tools for real time syntax checking (Komodo) and debugging, but they are not as mature as the pick of current Java IDE's.
    In reverse, there is never a need to restart a server when updating a php file unlike Java. This is not a problem with JSP's, but when you change servlets the server will unload all classes from memory and reload. This is a major pain if you are working on a production server.
    I have created a game clan site with many functions using PHP and an order processing section of someones web site. It is fine for smaller projects and is very fast to develop in, however PHP does not scale as well as Java. A large enterprise system is better suited to using Java.
    Also, PHP is a loosely typed language. This has many nuances that are different from a strongly typed language like java. OOP is definately not as powerful in PHP, as there is no private, protected and public typing of methods and fields. You can make classes and even extend classes, but it is poorly implimented IMO. I did all my PHP OOP style, but did not use any inheritance. The limitations of OOP principles is probably the most restrictive aspect of PHP that I can see.

  • Ias support for EJB, JSP/servlets,JDBC, connection pooling, XML, SOAP, load balancing etc

    Please let me know where I can find more information regarding iPlanet usage/deployment/configuring/tuning etc for support of technologies - like EJB, JSP/servlets, JDBC, connection pooling, XML, load balancing, JDBC & Transactions
    (I have already read the 'Getting Started with the iPlanet Application Server' part five and six - http://developer.iplanet.com/appserver/testdrive/partfive.jsp and partsix.jsp)(I am using the ias testdrive version).

    Hi,
    It's difficult to explain unless the J2EE architecture is understood. Also, explaining things like load balancing, Transactions, tuning, are bit vague and could blow the disk space of this site.
    To get started, the best way is to test the sample applications and the best part is you don't require internet connection to follow each steps. Install iWS and iAS, open browser, type in http://hostname:port/ias-samples/index.html. You can find links to the sample applications bundled. Please follow the steps given on deploying the application. This will enable you to a higher level.
    Regards
    Ganesh .R
    Developer Technical Support
    Sun Microsystems
    http://www.sun.com/developers/support

  • Extremely difficult to debug, about EJB, JSP

    These codes are in a JSP page, an EJB will be looked up:
    addcd.jsp
    <%!
       private CDAdder cdadder = null;
       public void jspInit() {
          try {
             InitialContext ic = new InitialContext();
             Object objRef = ic.lookup("CDAdderBean");
            CDAdderHome home = (CDAdderHome)PortableRemoteObject.narrow(objRef, CDAdderHome.class);
             cdadder = home.create();
          } catch (RemoteException ex) {
                System.out.println("Remote Exception:"+ ex.getMessage());
          } catch (CreateException ex) {
                System.out.println("Create Exception:"+ ex.getMessage());
          } catch (NamingException ex) {
                System.out.println("Unable to lookup home: " + ex.getMessage());
       public void jspDestroy() {   
             cdadder = null;
    %>
    <%
    HttpSession httpsession=request.getSession();
    httpsession.setAttribute("cdadder",cdadder); //i want to add this object to the session so that i could retrieve it and use its methods in other JSP pages.
    %>
    <form method="post" action="addtrack.jsp">
    <input type=text name="TitleOfTrack">
    <input type=text name="DurationOfTrack">
    <input type="submit">
    </form>
    ......................................addtrack.jsp
    <%
    CDAdder cdadder=(CDAdder)request.getSession().getAttribute("cdadder");// get back the object in the session
    String TitleOfTrack=request.getParameter("TitleOfTrack");
    String DurationOfTrack=request.getParameter("TitleOfTrack");
    cdadder.addTrack(new Track(TitleOfTrack,DurationOfTrack) ); //add the Track object into the arraylist using the addTrack(Track track) method in the CDAdderBean
    response.sendRedirect(addcd.jsp); //redirect back to the addcd.jsp page
    %>CDAdderBean.java
    public class CDAdderBean implements SessionBean {
         // data item to hold a reference to a passed Session context     private SessionContext ctx;
         private ArrayList tracks=new ArrayList();   << This arraylist holds the Track objects
         public void addTrack(Track track) throws RemoteException{
              tracks.add(track); //one method for adding tracks to the arraylist
         public void removeTrack(int index) throws RemoteException{
              tracks.remove(index); //another method for removing a track from the arraylist
         public ArrayList getListOfTracksAL() throws RemoteException{
    return tracks;
    ...............................Each time the user enters the required fields(title,duration) to add a track, these parameters will be passed to the addtrack.jsp, and the addtrack.jsp will retrieve the cdadder object from the session and use its addTrack method to add the track to the arraylist. And when it finishes, it will redirect back to the addcd.jsp. I got some other codes in the addcd.jsp(I did not show it as it will look very messy), anyway, the codes includes a call to the getListOfTracksAL() method which will return an arraylist of Track objects.
    my problem is that, EVERY TIME i started the sun application server, and go to the addcd.jsp, then the FIRST TIME I entered all the required fields and click submit button . I expected the parameters would be passed to the addtrack.jsp and it would add the track to the arraylist for me and then returned to addcd.jsp and the addcd.jsp would display the track that I just tried to add.
    but it didn't.
    I am sure that it DID add the track to the arraylist because i tried to print the size of the arraylist after the addTrack method was invoked.
    the most strange thing was that the addcd.jsp would display the tracks correctly after the FIRST TIME of adding a track.
    Please take a look at this link if you have time:
    http://222.166.192.130:8080/E-Music/login.jsp
    username:aaaaaa
    password:aaaaaa
    choose the role as "Admin"
    Add new music recording
    note: processor.jsp in this web server is the addtrack.jsp I was referring to.
    Many thanks to you all.

    ya
    i tried to add some println statements and noticed that:
    the first time i tried to add a track, the addTrack method was really invoked and the size of the arraylist became 1
    but when it returns to the addcd.jsp page the arraylist became empty
    but the most strange thing was that, it worked correctly AFTER the first time.
    thank you very much for your advice.

  • EJB/JSP integration?

    Hi,
    I have written an application that has EJBs, and JSPs that invoke the
    EJBs. It works on WebLogic 5.1.
    I want to package this application up in such a way that it can be
    deployed on any kind of J2EE application server.
    Using JBoss, I discovered that the JSPs by default do not have access to
    the interfaces supplied in the EJBs. i.e. I have to make copies of the
    EJB's home and remote interfaces, and put them where the JSP files can
    find them.
    This messing about was not neccessary with WebLogic. WebLogic knew to look
    in the EJB JAR files.
    So my question : For compatibility, should I create multiple copies of my
    EJB's interfaces, or is WebLogic's developer-friendly behaviour the
    correct one?
    Thanks, Martin.

    Weblogic 5.1 uses an architecture that is very unique. Consider it the
    exception, not the rule. You can NOT support a single deployment binary
    with WL 5.1 and other servers.
    The Weblogic 6.0 architecture is much closer to the others, and
    significantly better than the reference implementation's architecture. In
    6.0 you should be able to make a single app (EAR) that deploys to other
    servers as well.
    Cameron Purdy
    Tangosol, Inc.
    http://www.tangosol.com
    +1.617.623.5782
    WebLogic Consulting Available
    "martin" <[email protected]> wrote in message
    news:3a6f070e$[email protected]..
    Hi,
    I have written an application that has EJBs, and JSPs that invoke the
    EJBs. It works on WebLogic 5.1.
    I want to package this application up in such a way that it can be
    deployed on any kind of J2EE application server.
    Using JBoss, I discovered that the JSPs by default do not have access to
    the interfaces supplied in the EJBs. i.e. I have to make copies of the
    EJB's home and remote interfaces, and put them where the JSP files can
    find them.
    This messing about was not neccessary with WebLogic. WebLogic knew to look
    in the EJB JAR files.
    So my question : For compatibility, should I create multiple copies of my
    EJB's interfaces, or is WebLogic's developer-friendly behaviour the
    correct one?
    Thanks, Martin.

  • Servlet + EJB + Jsp

    Hello,
    I have an EJB CMP, called NewsBean. It's an EJB on a table News (Each line in the table is a Newspaper articles).
    I have a JSP page, to look the news list.
    And I have a servlet to prepare the data for the JSP page : The servlet call the Bean to access from the data base, the list of news
    The bean gives the list of articles with the methode findByLiNews
    My question is :
    - What must the JSP use? The EJB? Do the JSP call mybean.findByLiNews('Article1").
    - Do the servlet call the method mybean.findByLiNews?
    Di the servlet creates an other bean to be used by the JSP page?
    Thank's for your help

    I would recommnd you to follow some standard design pattern for J2EE applications. Check j2ee 1.4 tutorial for proper ways to dsign/code your apps: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/index.html
    Speaking of your particular example I'd call bean methods strait from a JSP page - it is more proper and easier, see how this is done in Duke's Bank application: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/Ebank4.html#wp79996

  • What strategy do you use for development EJB-JSP ?

    Hi all,
    I'd like to share opinion about development phase.
    In particular what is the best strategy for development
    of JSP-EJB applications?
    1. You keep JSP files unpacked under your Context and copy EJB interfaces in the /classes directory
    Pro: quick web development, no packing/unpacking of files
    Contros: proliferation of EJB interfaces both on Web side and on the EJB side
    2. keep JSP files and EJB interfaces into an .ear file and drop the ear file in the deploy directory for every modification.
    Pro: compact distribution of application, no need to keep duplicate copies of EJB interfaces
    Contros: packing/unpacking of ear/war files needed for every single modification of jsp/ejb
    What do you think?
    Thanks
    Francesco

    I certainly package the stuff in an EAR file - this EAR file contains the WAR file with my JSP/Servlet/Struts code & the required EJB interfaces. As well as the WAR file, the EAR file contains a JAR for the bean implementation. I want to correctly split this up in case I end up using a seperate EJB and Servlet container - my current seperation doesn't really allow for this at the moment. I guess this would involve building:
    1.) app-common.jar - Bean interfaces, utils, data transfer classes etc
    2.) webapp.war - Front end client code including JSP's, Servlets, Struts code etc
    3.) ejb.jar - The bean implementation
    Many containers only support deployment using an EAR file - supporting deployment of unpacked structures is not a requirement in the J2EE spec and so it will depend on whether or not. JBoss 3.0 hot deployment is fairly good so getting ant to stick my EAR file in the deploy directory after each build is normally not much bother (only the occasional full restart)

  • How to master good design with EJB and JSP?

    I use JSP to calling EJB. But the .jsp file is complex and it's difficult to maintain...I just want to work higher efficent with EJB,JSP and JavaBean. I want to know is there a good design with EJB and JSP? and is there any good material about MVC for EJB,JSP and JavaBean?

    You should read the J2EE blueprint available on this website. Better download the PDF, and print it for yourself so you can read it anytime.

  • To use JSP or EJBs

    Hi,
    We plan to develop a product on java which was earlier developed on VC++. This is a Client/server project containing User Interaction GUI screens to enter,modify & delete data. This exisiting system is a 2-tier model developed for intranet environment. Now to make the same application using java, which will be more efficient and fast. EJBs or JSPs ?? what are the factors that should be considered before one decides whether to use EJBs or JSPs ?

    Hi,
    From the way u asked the question...it seems that u will still need a beter understanding of EJBs and JSPs.
    U need to understand J2EE properly then, EJBs, JSPs, e.t.c will become clearer.
    Try this sun site technologies->J2EE there are lots and lots of tutorials and begineer tools and utilities to understand the working of J2EE in Building Enterprise applications. In some cases u need to employe both technologies. (EJBs JSPs).
    Cheers.

  • JSP, EJB in Jboss 4 with mySQL database. Error in connecting to database

    Hi, i using JBoss 4-0-1 with jsp and mySQL database. I get this example from a book using stateless session beans. However i modify it so it can connect to mySQL database.
    This is my code for jsp.
    <%@ page import="asg.MusicEJB.*,
    java.util.*,
    javax.naming.Context,
    javax.naming.InitialContext,
    javax.rmi.PortableRemoteObject" errorPage="error.jsp" %>
    <%--
         The following 3 variables appear in a JSP declaration.
         They appear outside the generated _jspService() method,
         which gives them class scope.
         Since we want to initialize our Music EJB object once
         and read the Music Collection database to get the
         recording titles once, we place this code inside
         method jspInit().
         The EJB business method getMusicList()
         returns a collection of RecordingVO objects which we
         store in ArrayList albums.
    --%>
    <%!
         MusicHome musicHome;
         Music mymusic;
         ArrayList albums;
         Properties properties=new Properties();
         public void jspInit() {
                   properties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
                   properties.put(Context.PROVIDER_URL, "localhost:3306");
                   System.out.println("............................in properties");
              try {
                   //Context initial = new InitialContext();
                   InitialContext jndiContext = new InitialContext(properties);
                   //Object ref  = jndiContext.lookup("MusicEJB");
                   Object objref = jndiContext.lookup("java:comp/env/ejb/EJBMusic");
                   musicHome = (MusicHome)PortableRemoteObject.narrow(objref, MusicHome.class);
                   mymusic = musicHome.create();
                   albums = mymusic.getMusicList();
                   System.out.println(".............................in line 64");
              } catch (Exception ex) {
                   System.out.println("Unexpected Exception............: " +
                             ex.getMessage());
                   ex.printStackTrace();
    %>
    <%--
         The following scriptlet accesses the implicit
         request object to obtain the current URL
         and saves it to the session object for later retrieval. 
         It also saves variable mymusic, so we can
         make remote calls to our Music EJB, and the collection of
         RecordingVO objects.  These variables will all be available
         to other pages within the session.
    --%>
    <%
         String requestURI = request.getRequestURI();
         session.putValue("url", requestURI);
         session.putValue("mymusic", mymusic);
         session.putValue("albums", albums);
    %>
    <html>
    <head>
    <title>Music Collection Database Using EJB & JSP Version 9.7</title>
    </head>
    <body bgcolor=white>
    <h1><b><center>Music Collection Database Using EJB & JSP</center></b></h1>
    <hr>
    <p>
    There are <%= albums.size() %> recordings.
    <form method="post" action="musicPost.jsp">
    <p>
    Select Music Recording:
    <select name="TITLE">
    <%
         // Generate html <option> elements with the recording
         // titles stored in each RecordingVO element.
         // Obtain the current title from the session object
         // (this will be null the first time).
         String title;
         String currentTitle = (String)session.getValue("curTitle");
         if (currentTitle == null) currentTitle = "";
         RecordingVO r;
         Iterator i = albums.iterator();
         while (i.hasNext()) {
              r = (RecordingVO)i.next();
              title = r.getTitle();
              if (title.equals(currentTitle)) {
                   out.println("<option selected>" + title + "</option>");
              else {
                   out.println("<option>" + title + "</option>");
    %>
    </select><p><p>
    <%--
         Provide a "View Tracks" button to submit
         the requested title to page musicPost.jsp
    --%>
    <input TYPE="submit" NAME="View" VALUE="View Tracks">
    </form>
    </body>
    </html>Message was edited by:
    chongming

    This is the deployment descriptor for the .ear file.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN' 'http://java.sun.com/dtd/application_1_3.dtd'>
    <application>
      <display-name>MusicDAOApp</display-name>
      <description>Application description</description>
      <module>
        <web>
          <web-uri>war-ic.war</web-uri>
          <context-root>music</context-root>
        </web>
      </module>
      <module>
        <ejb>ejb-jar-ic.jar</ejb>
      </module>
    <!--
      <module>
        <java>app-client-ic.jar</java>
      </module>
    -->
    </application>
    And this is the deployment for the ejb class files:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
    <ejb-jar>
      <display-name>MusicEJB</display-name>
      <enterprise-beans>
        <session>
          <display-name>MusicEJB</display-name>
          <ejb-name>MusicEJB</ejb-name>
          <home>asg.MusicEJB.MusicHome</home>
          <remote>asg.MusicEJB.Music</remote>
          <ejb-class>asg.MusicEJB.MusicBean</ejb-class>
          <session-type>Stateless</session-type>
          <transaction-type>Bean</transaction-type>
          <env-entry>
            <env-entry-name>MusicDAOClass</env-entry-name>
            <env-entry-type>java.lang.String</env-entry-type>
            <env-entry-value>asg.MusicEJB.MusicDAOCloudscape</env-entry-value>
          </env-entry>
         <env-entry>
         <env-entry-name>dbUrl</env-entry-name>
            <env-entry-type>java.lang.String</env-entry-type>
            <env-entry-value>jdbc:mysql://localhost/music</env-entry-value>
          </env-entry>
          <env-entry>
            <env-entry-name>dbUserName</env-entry-name>
            <env-entry-type>java.lang.String</env-entry-type>
            <env-entry-value>chongming</env-entry-value>
          </env-entry>
          <env-entry>
            <env-entry-name>dbPassword</env-entry-name>
            <env-entry-type>java.lang.String</env-entry-type>
            <env-entry-value>kcm82</env-entry-value>
         </env-entry>
          <security-identity>
            <description></description>
            <use-caller-identity></use-caller-identity>
          </security-identity>
        </session>
      </enterprise-beans>
    </ejb-jar>I can combine the jar and war files into a ear file. deploying is alright without any errors.
    However when i run the jsp, it prompt this error:
    You Have Encountered an Error
    Stack Trace
    java.lang.NullPointerException
         at org.apache.jsp.musicGet_jsp._jspService(org.apache.jsp.musicGet_jsp:111)
         at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
         at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
         at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
         at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
         at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
         at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
         at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
         at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
         at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
         at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
         at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
         at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
         at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
         at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
         at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
         at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
         at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
         at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
         at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
         at java.lang.Thread.run(Thread.java:595)
    How to i solve the error? I look at he catch results in the command prompt of JBoss , i found that when running, the code will be caught by the exception and display this:int.java:527)
    at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWor
    kerThread.java:112)
    at java.lang.Thread.run(Thread.java:595)
    13:55:21,375 INFO [STDOUT] Unexpected Exception............: EJBException:; nes
    ted exception is:
    javax.ejb.EJBException: getMusicList: SQLException during DB Connection:
    The url cannot be null
    13:55:21,375 INFO [STDOUT] java.rmi.ServerException: EJBException:; nested exce
    ption is:
    javax.ejb.EJBException: getMusicList: SQLException during DB Connection:
    The url cannot be null 13:55:21,375 INFO[STDOUT] at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:352)
    13:55:21,375 INFO [STDOUT] at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196)
    What can i do to solve the problem? please helpMessage was edited by:
    chongming
    Message was edited by:
    chongming
    Message was edited by:
    chongming

  • Deploy JSP/Servlet along with EJB

    how could deploy EJB with JSP/Servlet?.
    First i have
    package project.account
    1.HomeInterface class
    2.RemoteInterface class
    3.Bean class
    4.Client class
    I deployed the above bean in J2EE using Deploytool GUI.
    run the client like this
    java -classpath %CLASSPATH%;personDepClientClient.jar project.account.Client
    it displays result at prompt
    what i am asking is
    now i wrote JSP file which is kept also this project.account package
    i used the JSP file as client for the that bean.
    it is Show.jsp file(client file)
    <%@ page language="java" %>
    <%@ page import="java.util.*" %>
    <%@ page import="javax.naming.Context" %>
    <%@ page import="javax.naming.InitialContext" %>
    <%@ page import="javax.rmi.PortableRemoteObject" %>
    <%
         double balance;
    try
         Context initi = new InitialContext();
         Object ref = initi.lookup("AccountHome");
         AccountHome home = (AccountHome)javax.rmi.PortableRemoteObject.narrow(ref,AccountHome.class);
         AccountRemote vijay = home.create("200","vijay",0.00);
         vijay.credit(2000.0);
         vijay.debit(600);
         balance = vijay.getBalance();
    %>
         <tr>
    <td width="38%" height="31">
    </td>
    <td width="62%" height="31">
    <div align="center"><%= balance %></div>
    </td>
         </tr>
    <%
         AccountRemote kumar = home.create("199", "kumar", 0.00);
         kumar.credit(14000);
         AccountRemote xyz = home.findByPrimaryKey("199");
         xyz.debit(200.00);
         balance = xyz.getBalance();
    %>
         <tr>
    <td width="38%" height="31">
    </td>
    <td width="62%" height="31">
    <div align="center"><%= balance %></div>
    </td>
         </tr>
    <%}
    catch(Exception ex)
         System.err.println("Caught an exception." );
    ex.printStackTrace();
    %>
    after deployed this JSP file and executed as
    http://localhost:8000/project/person/Show.jsp
    it displays error as follows
    unable to find AccountRemote,AccountHome,findByPrimaryKey
    How could deploy JSP along with EJB?.
    pls any one tells steps to be followed while Deploying EJB/JSP.
    with thanks
    vijay

    Hmmmm...
    ssniazi does nothing but ask for contact information or recommend Oracle products.
    Based on this I consider it likely that this person is some sort of sales representative either directly or indirectly associated with Oracle.
    I personally wouldn't provide any contact information to this person. Nor would I accept any advice until this person starts to actually provide some solutions or at least correctly reveals any financial interests that they might have.

  • Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.

              Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
              Acelet is the leader in J2EE tools area. If you google "j2ee tools",
              "j2ee logging", "j2ee scheduler" or alike, you will find Acelet
              is at the top of the result.
              Super 4.00 comes with:
              SuperEnvironment
              SuperLogging
              SuperPeekPoke
              SuperReport
              SuperScheduler
              SuperStress
              and SuperPatrol, as a schedule job.
              The evaluation edition can be anonymously downloaded from:
              http://www.ACElet.com.
              Super is a component based monitor and administration tool
              for EJB/J2ee. It provides built-in functionality as well as
              extensions, as SuperComponents. Users can install
              SuperComponents onto it, or uninstall them from it.
              Super has the following functions:
              * A J2EE monitor.
              * A gateway to J2EE/EJB servers from different vendors.
              * A framework holding user defined SuperComponents.
              * A full-featured J2EE logging and J2EE tracing tool for centralized,
              chronological logging.
              * An EJB tool for Peeking and Poking attributes from EJBs.
              * An EJB Stress test tool.
              * A J2EE global environment tool.
              * A J2EE report tool.
              * A J2EE Scheduler tool.
              * A J2EE Business patrol tool.
              It is written entirely in the Java(TM) programming language.
              The current version support:
              * JOnAS 2.4 and 2.6
              * SunONE 7.0
              * Universal servers.
              * Weblogic 6.1, 7.0 and 8.1
              * Websphere 4.0 and 5.0.2
              * jBoss 3.0 and 3.2
              ********** What is new:
              Version 4.00 November, 2003
              Enhancement:
              1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
              (with/without proxy) protocol mode for SuperEnvironment,
              SuperLogging, SuperReport and SuperScheduler.
              2. SuperLogging 4.00: tracing can work on both live database and retired database.
              3. SuperReport 3.00: works for both live database and retired database.
              4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
              Panel.
              Bug fix:
              1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
              Version 3.00 July, 2003
              Enhancement:
              1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
              scope,
              with enhancements and bug fixes.
              2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
              password.
              Add MenuTreePanel.
              3. Improved GUI and document.
              4. Add support to WebLogic 8.1.
              Bug fix:
              1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
              2. SuperScheduler 2.0: Startup should never be reported as missed.
              3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
              Version 2.20 Jan. 2003
              Enhancement:
              1. Add desktop and start menu shortcuts for MS-Windows.
              2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
              3. SuperLogging 2.40: Add new sendAlarmEmail() method.
              4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
              direct database is not practical; Allow user to choose
              favorite logging software; Add Last day as Monthly
              repeating attribute.
              Change:
              1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
              Bug fix:
              1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
              open Environment Manager.
              2. SuperLogging client 1.52: Annoying exception thrown when you use
              JDK 1.4 (the program runs okay).
              3. SuperPeekPoke 1.61: Fix bug where input object contains
              java.lang.Double and alike.
              4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
              PatrolAlarm for SuperPatrol; Composite task with members;
              Non-scheduled run on other host; Around edges of last
              days in Monthly with holiday policy.
              Version 2.10 July 2002
              Enhancement:
              1. SuperScheduler 1.3: Add Future View to check future schedule in
              both text and Gantt-chart mode.
              2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
              activities.
              3. SuperEnvironment 1.3: uses new graphic package adding print and
              preference facilities.
              4. SuperPeekPoke 1.6: uses new graphic package adding print and
              preference facilities.
              5. SuperStress 1.21: uses new graphic package.
              Bug fix:
              1. SuperStress 1.21: fixed graphic related bugs.
              Version 2.01 June 2002
              Enhancement:
              1. Add options for Look & Feel.
              2. Preference is persistent now.
              Bug fix:
              1. Installation for WebLogic 7.0: extEnv may not be installed on the
              right place, so SuperLibrar on the server side was not loaded and
              causes other problems.
              Version 2.00 June 2002
              Enhancement:
              1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
              when any Doer causes things to change.
              2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
              3. SuperReport 1.2: Support default HTML browser for reading HTML document.
              4. Support WebLogic 7.0.
              5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
              6. SuperEnvironment 1.21: New SuperEnvironment tour.
              Bug fix:
              1. WebSphere Envoy did not always list all JNDI names.
              Version 1.90 May 2002
              Enhancement:
              1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
              2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
              effective period. Add Patrol job type as SuperPatrol.
              3. Add support for both JOnAS and jBoss.
              4. Add more elements on Report criteria.
              Change:
              1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
              and descend.
              2. New log database.
              Bug fix:
              1. Alert email should be sent once in the interval, regarding number of servers
              in the clustering.
              2. Minor bug fixes to make errors handled better on SuperLogging.
              3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
              them.
              4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
              Version 1.80 March 2002
              Enhancement:
              1. Add new component: SuperScheduler
              Bug fix:
              1. SuperLogging: Verbose should ignore class registration.
              2. SuperLogging-tracing: an exception was thrown if the java class without package
              name.
              Version 1.70 January 2002
              Enhancement:
              1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
              weblogic 6.1, need download an application).
              2. Add alias names for log threshold as new Java suggests.
              3. New component: SuperReport.
              Change:
              1. SuperLogging: Log database parameters are specified in a properties file, instead
              of EJB's deployment descriptor. It is more convenient and it avoids some potential
              problems. No change for development, easier for administration.
              Bug fix:
              1. Add Source Path Panel now accepts both directory and jar file.
              2. Bug in SuperEnvironment example (for version 1.60 only).
              Version 1.60 December 2001
              Enhancement:
              1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
              2. Add timeout parameter to logging access.
              3. New installation program with A). Easy install. B). Remote command line install.
              4. Support EJB 2.0 for Weblogic 6.1.
              5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
              was supported since version 1.5).
              Change:
              1. Poke: argument list is set at define time, not invoke time.
              2. Default log database change to server mode from web server mode, booting performance
              to 10-20 times.
              Bug fix:
              1. If the returned object is null, Peek did not handle it correctly.
              2. If the value was too big, TimeSeries chart did not handle it correctly. Now
              it can handle up to 1.0E300.
              3. Help message was difficult to access in installation program.
              4. Source code panel now both highlights and marks the line in question (before
              it was only highlight using JDK 1.2, not JDK 1.3).
              5. Delete an item on PeekPoke and add a new one generated an error.
              Version 1.50 August, 2001
              Enhancement:
              1. Source code level tracing supports EJB, JSP, java helper and other
              programs which are written in native languages (as long as you
              write correct log messages in your application).
              2. Redress supports JSP now.
              3. New installation with full help document: hope it will be easier.
              4. Support WebSphere 4.0
              Version 1.40 June, 2001
              Enhancement:
              1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
              and PieView for GlobalProperties.
              GlobalProperties is an open source program from Acelet.
              2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
              Changes:
              1. The structure of log database changed. You need delete old installation and
              install everything new.
              2. The format of time stamp of SuperLogging changed. It is not locale dependent:
              better for report utilities.
              3. Time stamp of SuperLogging added machine name: better for clustering environment.
              Bug fix:
              1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
              Style Panel may not show up.
              Version 1.30 May, 2001
              Enhancement:
              1. Add ConnectionPlugin support.
              2. Add support for Borland AppServer.
              Version 1.20 April, 2001
              Enhancement:
              1. Redress with option to save a backup file
              2. More data validation on Dump Panel.
              3. Add uninstall for Super itself.
              4. Add Log Database Panel for changing the log database parameters.
              5. Register Class: you can type in name or browse on file system.
              6. New tour with new examples.
              Bug fix:
              1. Redress: save file may fail.
              2. Install Bean: some may fail due to missing manifest file. Now, it is treated
              as foreign beans.
              3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
              on the original file, do not need copy to a temporary directory anymore.
              4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
              Now it pick up all availble ones and give warning messages.
              5. Stress: Launch>Save>Cancel generated a null pointer exception.
              Changes:
              1. installLogDatabase has been changed from .zip file to .jar file.
              2. SuperLogging: If the log database is broken, the log methods will not try to
              access the log database. It is consistent with the document now.
              3. SuperLogging will not read system properties now. You can put log database
              parameters in SuperLoggingEJB's deployment descriptor.
              Version 1.10 Feb., 2001
              Enhancement:
              1. Re-written PeekPoke with Save/Restore functions.
              2. New SuperComponent: SuperStress for stress test.
              3. Set a mark at the highlighted line on<font size=+0> the Source Code
              Panel (as a work-a-round for JDK 1.3).</font>
              4. Add support for WebLogic 6.0
              Bug fix:
              1. Uninstall bean does physically delete the jar file now.
              2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
              Version 1.00 Oct., 2000
              Enhancement:
              1. Support Universal server (virtual all EJB servers).
              2. Add Lost and Found for JNDI names, in case you need it.
              3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
              for Envoys which do not support JNDI list).
              Version 0.90: Sept, 2000
              Enhancement:
              1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
              and alike) as input values.
              2. Reworked help documents.
              Bug fix:
              1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
              further time-out.
              2. MDI related bugs under JDK 1.3.
              Version 0.80: Aug, 2000
              Enhancement:
              1. With full-featured SuperLogging.
              Version 0.72: July, 2000
              Bug fix:
              1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
              Version 0.71: July, 2000
              Enhancement:
              1. Re-worked peek algorithm, doing better for concurent use.
              2. Add cacellable Wait dialog, showing Super is busy.
              3. Add Stop button on Peek Panel.
              4. Add undeploy example button.
              Bug fix:
              1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
              1.2 and 1.3
              Version 0.70: July, 2000
              Enhancement:
              1. PeekPoke EJBs without programming.
              Bug fix:
              1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
              Changes:
              1. All changes are backward compatible, but you may need to recompile monitor
              windows defined by you.
              Version 0.61: June, 2000
              Bug fix:
              1. First time if you choose BUFFER as logging device, message will not show.
              2. Fixed LoggingPanel related bugs.
              Version 0.60: May, 2000
              Enhancement:
              1. Add DATABASE as a logging device for persistent logging message.
              2. Made alertInterval configurable.
              3. Made pace for tracing configurable.
              Bug fix:
              1. Fixed many bugs.
              Version 0.51, 0.52 and 0.53: April, 2000
              Enhancement:
              1. Add support to Weblogic 5.1 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Context sensitive help is available for most of windows: press F1.
              2. Fix installation related problems.
              Version 0.50: April, 2000
              Enhancement:
              1. Use JavaHelp for help system.
              2. Add shutdown functionality for J2EE.
              3. Add support to Weblogic 4.5 (support for Logging/Tracing and
              user defined GUI window, not support for regular monitoring).
              Bug fix:
              1. Better exception handling for null Application.
              Version 0.40: March, 2000
              Enhancement:
              1.New installation program, solves installation related problems.
              2. Installation deploys AceletSuperApp application.
              3. Add deploy/undeploy facilities.
              4. Add EJB and application lists.
              Change:
              1.SimpleMonitorInterface: now more simple.
              Version 0.30: January, 2000
              Enhancement:
              1. Add realm support to J2EE
              2. Come with installation program: you just install what you want
              the first time you run Super.
              Version 0.20: January, 2000
              Enhancement:
              Add support to J2EE Sun-RI.
              Change:
              1. Replace logging device "file" with "buffer" to be
              compliant to EJB 1.1. Your code do not need to change.
              Version 0.10: December, 1999
              Enhancement:
              1. provide SimpleMonitorInterface, so GUI experience is
              not necessary for developing most monitoring applications.
              2. Sortable table for table based windows by mouse
              click (left or right).
              Version 0.01 November., 1999:
              1. Bug fix: An exception thrown when log file is large.
              2. Enhancement: Add tour section in Help information.
              Version 0.00: October, 1999
              Thanks.
              

Maybe you are looking for

  • Help required in identifying the admin groups for a IT Resource

    I would like to pick up the user details of the members in the admin groups of a particular IT resource. Can anyone help me in this regard..??? Thanks in advance

  • Join between Oracle and non-Oracle Database

    We are working at a project with the follow architecture: - 5 Databases (3 Oracle, 1 Sybase and 1 DB2); - Session Bean like Session Facade Pattern; - Entity Bean (BMP); - OC4J (Oracle Container for J2EE); The case is that we cannot make join between

  • Locking the Program

    Hello all, I am wondering what would be the best approach in Java to create a program that will lock users out after a certain amount of time. Thanks for your time.

  • How do I listen to my home iTunes library at work via the Internet?

    I know this question must have been asked before, and if so, I apologize; I did some digging and didn't find anything. I do know that if I could somehow find iTunes 4.0 to install on both my home and work Macs, that I could just access my home librar

  • It should have image hide option in Album Home XPERIA C

    All images are displayed in Home screen of album. so as per customer point of viewe there should be hide option available in album for which image/video we dont want to show to other user on single click. kindly procide update.