Help me for EJB

Hi,
I'm trying to run a ejb example downloaded from http://java.sun.com/javaee/5/docs/tutorial/information/download.html this link. And when try to build the app its showing some error that javax.ejb doesnt exist.What would i do? I am a beginner please help me. Thanks in advance.
with regards from Som

You need that jar in your classpath when you compile the code. Setting the classpath and compiling from a command line is entry level Java, perhaps you should check it out before delving into J2EE:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/classpath.html
http://en.wikipedia.org/wiki/Classpath_(Java)
If you are not using the command line but an IDE then simply it add the jar to the build path. For example is eclipse: Project > Properties > Java Build Path
m

Similar Messages

Beginner Question - Help Needed for EJB QL Sample Application

I'm working with a group of student interns, like myself, and we've been given an assignment to work with Oracle. All of us have no training or experience with this, so we're just learning as we go.
I've been trying to run the EJB QL Sample Application (http://www.oracle.com/technology/sample_code/tech/java/ejb_corba/ejbql/Install.html), but I keep running into problems at step 3.
Now, we will deploy the sample application onto OC4J. Open another command prompt and go to the folder <OC4J_HOME>/j2ee/home and run the following commands one-by-one
> java -jar admin.jar ormi://<machine_name>:<admin_port> admin <admin_pwd> -deploy -file <SAMPLE_HOME>/build/ejbql.ear -deploymentName Ejbql
> java -jar admin.jar ormi://<machine_name>:<admin_port> admin <admin_pwd> -bindWebApp Ejbql ejbql-war http-web-site /ejbql
where,
<machine_name> Name of the machine where OC4J Server is running
<admin_port> Admin Port on which the OC4J server listens. This value by default is 23791 unless explicitly changed by the user
<admin_pwd> Adminstrator password to access OC4J. The default value is welcome
When I do this step I get this error:
Error: Unable to find java:comp/ServerAdministrator: Lookup error: javax.naming.
AuthenticationException: Invalid username/password for default (sds); nested exc
eption is:
javax.naming.AuthenticationException: Invalid username/password for defa
ult (sds)
com.evermind.client.orion.AdminCommandException: Unable to find java:comp/Server
Administrator: Lookup error: javax.naming.AuthenticationException: Invalid usern
ame/password for default (sds); nested exception is:
javax.naming.AuthenticationException: Invalid username/password for defa
ult (sds)
at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminCo
nsole.java:105)
at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java
:27)
javax.naming.NamingException: Lookup error: javax.naming.AuthenticationException
: Invalid username/password for default (sds); nested exception is:
javax.naming.AuthenticationException: Invalid username/password for defa
ult (sds) [Root exception is javax.naming.AuthenticationException: Invalid usern
ame/password for default (sds)]
at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:153)
at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminCo
nsole.java:102)
at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java
:27)
Caused by: javax.naming.AuthenticationException: Invalid username/password for d
efault (sds)
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2410
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2226
at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java:1692)
at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java:727)
at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:134)
... 2 more
---- Embedded exception
javax.naming.AuthenticationException: Invalid username/password for default (sds
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2410
at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2226
at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java:1692)
at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java:727)
at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:134)
at com.evermind.client.orion.Oc4jAdminConsole.executeCommand(Oc4jAdminCo
nsole.java:102)
at com.evermind.client.orion.Oc4jAdminConsole.main(Oc4jAdminConsole.java
:27)
Any suggestions to fix this error?
Thanks in advance for any help.

George,
The Readme.html file is available with the ejbqlsample.jar downloadable (Extract and find the doc in Ejbql\docs\Readme.html) which is printable.
Or,
If you are trying to print the file directly from OTN site, you need to set the Page-Setup Orientation to 'Landscape'.
Hope this helps.
Regards
Pushkala

I need a clarification : Can I use EJBs instead of helper classes for better performance and less network traffic?

My application was designed based on MVC Architecture. But I made some changes to HMV base on my requirements. Servlet invoke helper classes, helper class uses EJBs to communicate with the database. Jsps also uses EJBs to backtrack the results.
I have two EJBs(Stateless), one Servlet, nearly 70 helperclasses, and nearly 800 jsps. Servlet acts as Controler and all database transactions done through EJBs only. Helper classes are having business logic. Based on the request relevant helper classed is invoked by the Servlet, and all database transactions are done through EJBs. Session scope is 'Page' only.
Now I am planning to use EJBs(for business logic) instead on Helper Classes. But before going to do that I need some clarification regarding Network traffic and for better usage of Container resources.
Please suggest me which method (is Helper classes or Using EJBs) is perferable
1) to get better performance and.
2) for less network traffic
3) for better container resource utilization
I thought if I use EJBs, then the network traffic will increase. Because every time it make a remote call to EJBs.
Please give detailed explanation.
thank you,
sudheer

Please suggest me which method (is Helper classes or Using EJBs) is perferable :
1) to get better performance
EJB's have quite a lot of overhead associated with them to support transactions and remoteability. A non-EJB helper class will almost always outperform an EJB. Often considerably. If you plan on making your 70 helper classes EJB's you should expect to see a dramatic decrease in maximum throughput.
2) for less network traffic
There should be no difference. Both architectures will probably make the exact same JDBC calls from the RDBMS's perspective. And since the EJB's and JSP's are co-located there won't be any other additional overhead there either. (You are co-locating your JSP's and EJB's, aren't you?)
3) for better container resource utilization
Again, the EJB version will consume a lot more container resources.

Help for EJB

Hi,
after I added a busness method in EJB Bean class, I cannot add the method in remote interface.
can anybody help me?
zhou

Yes, you should have an application server for EJB container. Try JBoss; it's free.

A free ebook for EJB 3.0 with the latest version of Netbean

Hi,
I am a trainee although with a good background in java.
I'm urgently in need of a free ebook for EJB 3.0 with the latest version of Netbean. Pls, help me with one if you have. my email is [email protected]
Again, is container managed bean good for a big project?
Thanks.
Emeka

emekaco wrote:
Hi,
I am a trainee although with a good background in java.
I'm urgently in need of a free ebook for EJB 3.0 with the latest version of Netbean. Pls, help me with one if you have. my email is [email protected]
http://www.theserverside.com/tt/books/wiley/masteringEJB3/index.tss
Here's a good free e-book but without Netbean. It covers everything you would need to know about EJBs.
>
Again, is container managed bean good for a big project?
The question is too vague to be answered. It's a design decision that needs more details.

Writing a Standalone Client for EJB 3.0 Bean For Weblogic 10

Steps for Writing a Standalone Client
Client Code
package com.client;
import java.util.Properties;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.rmi.PortableRemoteObject;
import com.StatelessService;
public class StatelessClient {
     public static void main(String [] args){
          Context ctx = null;
          try {
               ctx = getInitialContext("t3://localhost:7001/protossbservice","weblogic","weblogic");
               Object ref = ctx.lookup("StatelessService#"+StatelessService.class.getName());
               StatelessService service = (StatelessService)PortableRemoteObject.narrow(ref,StatelessService.class);
               System.out.println("StatelessClient.getMessage() ++");
               String message = service.getMessage();
               System.out.println("StatelessClient.getMessage --");
                    System.out.println("Message from Bean "+message);
     } catch (NamingException e) {
               e.printStackTrace();
     private static Context getInitialContext(String url, String user, String password) throws NamingException {
        Properties h = new Properties();
        h.put(Context.INITIAL_CONTEXT_FACTORY,
                "weblogic.jndi.WLInitialContextFactory");
        h.put(Context.PROVIDER_URL, url);
        h.put(Context.SECURITY_PRINCIPAL, user);
        h.put(Context.SECURITY_CREDENTIALS, password);
        return new InitialContext(h);
Business Interface
package com;
public interface StatelessService {
     public String getMessage();
Stateless Session Bean
package com;
import javax.annotation.PostConstruct;
import javax.ejb.Remote;
import javax.ejb.Stateless;
* Test Stateless Session Bean
@Stateless(mappedName="StatelessService")
@Remote(StatelessService.class)
public class StatelessServiceBean implements StatelessService {
     public String getMessage(){
          return "I am invoked";

emekaco wrote:
Hi,
I am a trainee although with a good background in java.
I'm urgently in need of a free ebook for EJB 3.0 with the latest version of Netbean. Pls, help me with one if you have. my email is [email protected]
http://www.theserverside.com/tt/books/wiley/masteringEJB3/index.tss
Here's a good free e-book but without Netbean. It covers everything you would need to know about EJBs.
>
Again, is container managed bean good for a big project?
The question is too vague to be answered. It's a design decision that needs more details.

JNDI Lookup in JSP fails for EJB 3.0

I am new to Java technology. I read the EJB FAQ, NetBeans docs and may forum discussions and I am still confused with the error I am having.
Background:
I have developed a persistance bean and related sessions beans (similar to the customer-cmp-ear application in the Java App Server samples). Now I am trying to access this bean using a JSP. After deploying the war file in the App Server and try to access the page, I get the following error.
javax.naming.NameNotFoundException: No object bound to name java:comp/env/ConsumerSessionLocal
After reading many articles, I understood that I dont have to prepare any descriptors, or JAR files for EJB 3.0.
Environment Details:
Java App Server Ver 9.0
NetBeans 5.5
I normally build the war files using NetBeans.
I use App Server Admin console to deploy the web applications using the above war file.
EJB details:
Persistance EJB : person.java
Session Objects
Consumer.java (this implements ConsumerSessionLocal, ConsumerSessionRemote). This Stateless bean accesses the methods in person.java.
ConsumerSessionLocal.java - local interface
ConsumerSessionRemote.java - remote interface
SearchConsumer.jsp
This JSP page is calling the ConsumerSessionLocal using the JNDI lookup through InitialContext.
Here is the Code snippet:
try {
InitialContext ic = new InitialContext();
Object o = ic.lookup("java:comp/env/ConsumerSessionLocal");
ConsumerSessionLocal consSession = (ConsumerSessionLocal) o;
I am able to see the jsp page in the browser, however, after a submit action, I get the Java Naming Exception error.
javax.naming.NameNotFoundException: No object bound for java:comp/env/ConsumerSessionLocal
I would appreciate your help/any of your thoughts.
Thanks in advance.
-Ram

I did not really solve it. Instead I used some of the tutorials that used JNDI lookup and modified those as my way forward. I did not really find out exactly what I was doing wrong.
/Anders

Can't create a JAXB binding for ejb-jar.xml using xjc

Hi all,
I have been trying to build a JAXB binding for EJB deployment descriptors, mainly because I have to update a hand-cranked ejb-jar.xml file on the fly with some additions that have come from a code generator.
I have tried to use
xjc ejb-jar_2_1.xsd j2ee_1_4.xsd ejb-jar_2_1.xsd
xjc on the schema definitions I found at http://java.sun.com/xml/ns/j2ee/ but I can't get it to work. It produces reams of errors, see below for a short extract.
Of course, someone could put me out of my misery and tell me where to find a binding that someone else has done. I can't be the first chimp on the planet that has wanted to do this!
Any help much appreciated.
errors:
[WARNING] warning: "blockDefault" attribute of <schema> is not supported
line 3 of xml.xsd
[WARNING] warning: "finalDefault" attribute of <schema> is not supported
line 3 of xml.xsd
[WARNING] warning: <key> identity constraint will be ignored by JAXB validation
line 117 of j2ee_web_services_client_1_1.xsd
[WARNING] warning: <key> identity constraint will be ignored by JAXB validation
line 115 of ejb-jar_2_1.xsd
[WARNING] warning: <keyref> identity constraint will be ignored by JAXB validation
line 129 of ejb-jar_2_1.xsd
[WARNING] warning: <key> identity constraint will be ignored by JAXB validation
line 145 of ejb-jar_2_1.xsd
[WARNING] warning: <keyref> identity constraint will be ignored by JAXB validation
line 159 of ejb-jar_2_1.xsd

Exception initializing 'oracle.dbtools.raptor.MonitorJDBCAddin' in extension 'Oracle SQL Developer': oracle.classloader.
util.AnnotatedNoClassDefFoundError:
Missing class: oracle.jdbc.OracleDriverThe Oracle driver is not on the classpath.

Difference between narrow() method usage and simple class cast for EJB

Hi,
I have a very simple question:
what is the difference between PortableRemoteObject.narrow(fromObj,
toClass) method usage and simple class cast for EJB.
For example,
1)
EJBObject ejbObj;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)PortableRemoteObject.narrow(ejbObj,ABean.class);
OR
2)
EJBObject bean;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)ejbObj;
Which one is better?
P.S. I'm working with WL 6.1 sp2
Any help would be appreciated.
Thanks in advance,
Orly

[email protected] (Orly) writes:
Hi,
I have a very simple question:
what is the difference between PortableRemoteObject.narrow(fromObj,
toClass) method usage and simple class cast for EJB.
For example,
1)
EJBObject ejbObj;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)PortableRemoteObject.narrow(ejbObj,ABean.class);
OR
2)
EJBObject bean;
// somewhere in the code the home.create() called for bean ...
ABean a = (ABean)ejbObj;
Which one is better?(1) is mandated by the spec. It is required because CORBA systems may
not have sufficient type information available to do a simple case.
P.S. I'm working with WL 6.1 sp2 You should always use PRO.narrow()
andy

IDE for EJB's

Hi there
I'm looking for IDE's for EJB development.
Best would be if it support UML notation or any other modeling language
if you know any, please let me now
thanks
Thomas

There are quite a few available, you can try Oracle's JDeveloper, you can
download it from oracle for free (evaluation), you can also try ArgoUML,
that you can get from www.sourceforge.net or www.freshmeat.com . It's an
opensource utility written in java that resamlbes Rational Rose. Hope that
helps.
-alex
Thomas Egeter wrote:
Hi there
I'm looking for IDE's for EJB development.
Best would be if it support UML notation or any other modeling language
if you know any, please let me now
thanks
Thomas

JAVA client JNDI lookup for EJB session in cluster in WLS 5.1

The documentation says :
 to obtain a Context for JNDI lookup do the following :
 Hashtable ht = new Hashtable();
 ht.put(Context.INITIAL_CONTEXT_FACTORY,
 "weblogic.jndi.WLInitialContextFactory");
 ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
 try {
 Context ctx = new InitialContext(ht);
 // Do the client's work
 catch (NamingException ne) {
 // A failure occurred
 finally {
 try {ctx.close();}
 catch (Exception e) {
 // a failure occurred
 where "mycluster" is the DNS name of my cluster. My DNS server (Windows 200
 DNS server) use round robin
 to call alernatively all the wls server node in "mycluster" and it's OK. The
 two servers of my cluster
 are called alternatively for my EJB session stateless.
 Now I unplug one of the two nodes of my cluster and the remaining server is
 called only 2 times
 and not after.
 Questions :
 -is the load balancing between the nodes of mycluster only rely on DNS or
 is there an internal
 mecanism in EJB sub to try one server then an other ?
 - do I need to obtain a new reference on JNDI Context for each call ?
 Thank's a lot.
 Farid Bellameche.


 I too have the same problem. My scenario is :
 I have the web tier architecture away from cluster. All ejbs are in cluster
 running in two seperate machines. We have a factory class running in
 webtier(we use servlet in this tier) which obtains home interface only once
 and stores it for future reference. When ever we need the remoteobject stub,
 we ask the factory class and which in turn uses the stored home interface to
 get the same.
 In the webtier, I list all the servers in the cluster as a part of url as
 mentioned by you.
 I started the web tier as well as Object tier cluster. I could see the
 request coming in both the machines in the cluster for the ejb. But When I
 bring one the server in the cluster,
 1. Web tier throws an exception saying that it could not connect
 to server using t3.
 2. The other machine which is running the server, also says
 'failed to create socket to : -32323234324 sever name
 using protocol t3.
 It looks like I am able to get load balance. But I am not able to get the
 fail over to be working.
 In the weblogic-ejb-jar.xml, I added the following.
 <clustering-descriptor>
 <home-is-clusterable>true</home-is-clusterable>
 <home-load-algorithm>round-robin</home-load-algorithm>
 </clustering-descriptor>
 I compiled and added the .jar file. So the jar file now has replica aware
 stubs.
 Could any one of you help me for why the fail over is not working?
 Suersh
 "Giri Alwar" <[email protected]> wrote in message
 news:[email protected]...
 > Farid,
 > (1) Yes, the stub has the logic to perform load-balancing and
 fail-over.
 > (2) In almost all cases, no. You can get the context once, store it
 and
 > use it thereafter. Please refer to
 > http://www.weblogic.com/docs51/cluster/concepts.html#1025061 for more
 info.
 >
 > A couple of notes on your situation. From what you are describing, your
 > Windows DNS server is setup to serve only one IP from the cluster (using
 > round-robin) as opposed to a list of all IP's in the cluster. Hence, the
 > initial context you obtain is tied to a single server in the cluster (the
 > one returned by the DNS). The weblogic implementation on the client side
 has
 > no idea of the existence of the other servers in the cluster. This is not
 a
 > cluster aware context. To obtain a cluster aware context, either list all
 > the IP's in the URL like t3://server1,server2,server3:7001 or have
 > "mycluster" return a list of all servers in the cluster.
 >
 > Giri
 >
 >
 > "Farid Bellameche" <[email protected]> wrote in message
 > news:[email protected]...
 > > The documentation says :
 > >
 > > to obtain a Context for JNDI lookup do the following :
 > > Hashtable ht = new Hashtable();
 > > ht.put(Context.INITIAL_CONTEXT_FACTORY,
 > > "weblogic.jndi.WLInitialContextFactory");
 > > ht.put(Context.PROVIDER_URL, "t3://mycluster:7001");
 > > try {
 > > Context ctx = new InitialContext(ht);
 > > // Do the client's work
 > > }
 > > catch (NamingException ne) {
 > > // A failure occurred
 > > }
 > > finally {
 > > try {ctx.close();}
 > > catch (Exception e) {
 > > // a failure occurred
 > > }
 > > }
 > >
 > > where "mycluster" is the DNS name of my cluster. My DNS server (Windows
 > 200
 > > DNS server) use round robin
 > > to call alernatively all the wls server node in "mycluster" and it's OK.
 > The
 > > two servers of my cluster
 > > are called alternatively for my EJB session stateless.
 > > Now I unplug one of the two nodes of my cluster and the remaining server
 > is
 > > called only 2 times
 > > and not after.
 > >
 > > Questions :
 > > -is the load balancing between the nodes of mycluster only rely on DNS
 > or
 > > is there an internal
 > > mecanism in EJB sub to try one server then an other ?
 > >
 > > - do I need to obtain a new reference on JNDI Context for each call ?
 > >
 > >
 > > Thank's a lot.
 > >
 > > Farid Bellameche.
 > >
 > >
 > >
 > >
 >
 >

Does mapping to JNDI for ejb-refs have a performance impact?

Does mapping to JNDI names for ejb-refs have a performance impact for
WLS6.1?
In the ejb-jar.xml deployment descriptor, you can define an ejb reference as
follows:
<ejb-ref>
<ejb-ref-name>ejb/AccountHomeRemote</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<home>com.package structure.AccountHomeRemote</home>
<remote>com.package structure.AccountRemote</remote>

</ejb-ref>
Now, optionally, you can use the ejb-link element - or - you can, in the
weblogic DD, specify a JNDI name that the ejb-ref maps to.
Using a JNDI name buys you some flexibility. If, for some reason, the jar is
divided, you dont have to convert ejb-link's to JNDI names. The question is:
Is there a performance cost in doing this?
Cheers

Hi Aashish,
Thanks for your quick reply. it was helpful, but i am not using RFC's. Correct me if i am wrong, but i have explained the scenarios in detail below.
Scenario 1. Synchronous
1) PI Picks file from a common folder.
2) PI does a data mapping and sends the data to ECC.
3) ECC contains an inbound interface which receives the data and in which abap proxy code is written.
4) The abap proxy code executes a function module and sends the response as an internal table back to PI.
5) PI receives the response and places it in a text/csv file and places it back to another folder.
I assume that the above would be possible only using BPM. What i understand is that in order for an interface to receive and send data, abstract mappings are to be used, and for this BPM is required. We do not have any conversions etc. its just a simple matter of receiving an internal table from ECC and creating a file to place in the folder.
I also understand that BPM could have bottlenecks due to queue and cache issues, messages might be pending, or lost etc.
Scenario 2. Asynchronous
1) PI Picks file from a common folder.
2) PI does a data mapping and sends the data to ECC.
3) ECC contains an inbound interface which receives the data and in which abap proxy code is written.
4) ABAP Proxy code executes the same function module and calls a seperate outbound interface and passes the values to it. This would be used in sending the response back.
5) PI receives the response from the second interface and places it in a text/csv file and places it back to another folder.
I would like to know which would be the better approach. Documentation/references to support your claims would be much appreciated.
Cheers,
Mz

NameAlreadyBoundException for EJB server.

I got NameAlreadyBoundException for EJB server when I tried to start PNS in VAJave Websphere test Enviornment.
Any help is appreciated.

Hi,
I think you need to stop the Application Server before you start the WebSphere Test Environment.
If the problem still persist then try changing the port number in PNS.
Hope this helps.

Links for ejb 3

Hi All,
I just cleared SCJP and am looking for SCBCD as my next step.
It would be helpful if someone can provide links for EJB 3.0 version

EJB 3.0 Specs:
http://jcp.org/aboutJava/communityprocess/final/jsr220/index.html
EJB 3.0 Simplified API Quiz:
http://java.sun.com/developer/Quizzes/ejb/ejb3.0_simplified_api.html
JavaEE Tutorial:
http://java.sun.com/javaee/5/docs/tutorial/doc/
-cheng

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 the Source Code
Panel (as a work-a-round for JDK 1.3).
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.

Help me for EJB

Similar Messages

Maybe you are looking for