Access bean(wrapper) for EJB

How can I develop access bean(wrapper) for EJB in JDeveloper?

Search the Internet for a product called JACOB
JAva COm Bridge

Similar Messages

Using local interfaces for EJB (session bean)

Hi,
I�ve a question regarding when to use the Local interfaces(EJBLocal and EJBLocalHome) of a enterprise bean. I understand that calls to enterprise bean can be made locally if the client which is invoking is in the same JVM as that of EJB. I�ve written a web client (servlet) which is packaged in a EAR and this servlet is trying to invoke a session bean which is in a �different� EAR using local interfaces. Both the EARs have been deployed in a single server (websphere 6.0 server). It didn�t work for me this way�..If I package the servlet in the same EAR of session bean then it works fine.
So is this to say that both EARs are not running on the same JVM? Or should it work even if the client and the session bean are in different EARs but in same server?
Can anyone explain me the fundamentals behind this.
Thanks in advance

Local access is only portable within the same .ear. For example, the Java EE SDK and SUN's
application servers have never supported local EJB access from a web/EJB component in a different
.ear. One issue is that local access requires that both the caller and target EJB have the same
classloader. By definition, different Java EE applications have distinct classloaders. In addition,
in Java EE 5 persistence context propagation does not span applications, so it wouldn't work in the
local case.
--ken

Excessive cxs socket connections created for ejb access

We are seeing a large number of TCP connections being created to the cxs engine for ejb access in our application.
We are running iPlanet application server 6.0, sp3 on Solaris 8. We have a web application that accesses a singleton component running in a kjs engine. That singleton accesses cmp entity beans and stateless session beans for serving client requests over the RMI/IIOP bridge. When three clients are connected and making requests, the number of TCP connections to the IIOP port (9010) starts to increase until everything freezes. I believe the "freezing" of the client apps is due to the open socket limit of 1024 being exceeded. According to the developer doc we can increase rlim_fd_max to 8192 to fix that problem.
However, my question is why are there an increasing number of socket connections? We are caching the ejb instances in the singleton so we should not be creating a large pool of EJBs. I have verfied the large number of sockets using netstat and also using RMI runtime logging in the kjs engine.
Does anyone have any ideas what could be happening here?
Thanks,
Mark

I noticed that most of the TCP connections are made to port 32787. Can anyone from iPlanet tell me what is listening on this port? The large number of socket connections is really tying up server resources.
Thanks,
Mark

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.

Multiple inheritance in remote interfaces for EJB 3.0 session beans on Webl

Hi All,
We started migration from EJB 2.1(WLS 8.1) to EJB 3.0(WLS 10.3.2) and identified few serious problems. One of them is related with multiple business interfaces inheritance. I wrote simple example that presents point of the problem.
we have session bean AImpl:
+@Stateless(name="A")+
+@Remote({A.class})+
+@TransactionAttribute(TransactionAttributeType.REQUIRED)+
+public class AImpl implements A {+
+@Override+
+public void writeA() {+
System.out.println("A");
+}+
+@Override+
+public void writeB() {+
System.out.println("B");
+}+
+@Override+
+public void writeC() {+
System.out.println("C");
+}+
+}+
with remote interface A:
+@Remote+
+@JNDIName(A.JNDI_NAME)+
+public interface A extends B, C {+
public static String JNDI_NAME = "A_JNDI_NAME";
void writeA();
+}+
As you can see A extends B, and C. Definition of both interfaces is very simple:
+public interface B {+
void writeB();
+}+
+public interface C {+
void writeC();
+}+
Everything looks nice until we want to invoke some method on AImpl bean. For above implementation code:
A a = ctx.lookup(A. JNDI_NAME);
a.writeA();
a.writeB();
a.writeC();
writes down ”A \n B” and throws exception:
caused by: java.lang.NoSuchMethodException: pl.gov.arimr.zszik.bazowe.slowniki.ejb.A_vt0zts_AImpl_1032_WLStub.*writeC()*
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:165)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:57)
so.. in stub generated by WLS there is no method from interface C ! What more interesting after small change in interface A rely on change in interface implementation order from B, C to C, B (+public interface A extends C, B {+) server writes down only A and I have stack like below:
Caused by: java.lang.NoSuchMethodException: pl.gov.arimr.zszik.bazowe.slowniki.ejb.A_vt0zts_AImpl_1032_WLStub.*writeB()*
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:165)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:57)
After this experience I came up with suspicion that Weblogic 10.3 does not support inheritance from multiple interfaces in one “generation”. Instead of that it takes only the first interface from the list.
Does anybody have some experience with such a situation? maybe someone have an idea how to work around this problem?

This is Not Supported in WebLogic that the Remote Interface extends other Interfaces. Because Annotation Processor just looks up inside the implemented interface methods. The actual interface which is Implemented by the Bean Class. So the Methods declared inside the Interface B and Interface C will be ignored and will not be available as part of the generated Stubs. Thats why u are getting NoSuchMethodError.
You can even contact Oracle Support on this...there are 3-4 Cases on it. And the Solution is Work As Designed.
Workaround is : edit your interface A as following
Declare all the Business Methods only in the Remote Interface and not inside it's Super Interfaces.
Example:
@Stateless(name="A")
@Remote({A.class})
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class AImpl implements A {
@Override
public void writeA() {
System.out.println("A");
@Override
public void writeB() {
System.out.println("B");
@Override
public void writeC() {
System.out.println("C");
@Remote
@JNDIName(A.JNDI_NAME)
public interface A extends B, C {
public static String JNDI_NAME = "A_JNDI_NAME";
void writeA();
void writeB();
void writeC();
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

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

Javabean Clients for EJBs in OC4J

Is there anyone who has written a Javabean that accesses a EJB
deployed in OC4J, doesnt have to be a structural EJB, could be
any class that does it and is then used by a JSP. If so, could
you please help me out. I cant seem to do that, i cant
understand what will be the directory structure. I use the ANT
tool for creating the ear file.

Hi nil,
This may help you:
http://kb.atlassian.com/content/tutorials/jollem/orion-cmp-
primer/
It shows how to access a CMP entity EJB from a JSP. The java code
is embedded in the JSP file(s) but I think you can easily move
the code to a java bean and call the java bean methods from the
JSP.
Hope this helps you.
Good Luck,
Avi.

CMP Entity Beans Wrapper Classes Source Code

Is there any way to have JDev or OC4J 9.0.4 save the .java source file that creates the wrapper cmr ejb classes? It would be helpful when debugging in JDev for it to have the source to debug with. Or even to just see the generated java file from the abstract cmp beans.
Any one know?
Tkx,
Jim

Hi Jim,
If you haven't already seen it, perhaps this where to find the temperary files created during deployment (from this forum's archives) will help.
Good Luck,
Avi.

Clustering read-only bean-managed entity ejbs

 I'm designing a data caching approach that relies on using read-only entity ejbs with bean-managed persistence. My design is based on the fact that WebLogic blocks on entity bean access by concurrent users for a given bean instance (unique primary key). I would like to keep only one entity bean instance active(timeoutSetting=0) for eacy primary key for all users to share. That way I only have to hit the database one time to initially populate data in the entity bean. I'm worried about this approach in a WebLogic clustered environment. From reading notes in this newsgroup and other doc, it appears that WebLogic might not use one instance of the entity bean (based upon unique primary key) in a clustered environment. Is that true (that being multiple users could get their own instance of the entity bean with the same primary key)?
 Thanks,
 Bryan


Typically, the read-write EJBs are on each WL server instance, so there is
 no remote invocation -- it is all done by reference.
 Cameron Purdy
 Tangosol, Inc.
 http://www.tangosol.com
 +1.617.623.5782
 WebLogic Consulting Available
 "Bryan Dixon" <[email protected]> wrote in message
 news:[email protected]...
 >
 > I guess I'm confused about read-write (not read-only) entity beans being
 pinned or not. This is from WebLogic 5.1 EJB doc:
 > "read-write entity EJBs do not use a clustered EJBObject stub; a client's
 method calls to a particular EJB always go to a single WebLogic Server
 instance. If the server that a client is using fails, the client must
 re-find the entity EJB using the cluster-aware home stub."
 >
 > Doesn't that mean the entity bean instance for a primary key is pinned to
 a single WebLogic Server instance? Maybe I'm just misunderstanding
 terminology about what a "particular EJB" is - I was thinking it is an
 entity bean instance for a unique primary key.
 >
 > Thanks,
 > Bryan
 >
 >
 > "Cameron Purdy" <[email protected]> wrote:
 > >>I was thinking that read-write entity beans were pinned.
 > >
 > >Not unless you pin them. Basically, that means that the JAR/XML that
 > >contains/specifies the EJB only is on one server.
 > >
 > >> So if two separate weblogic instances in a cluster did a find on an
 entity
 > >ejb with the same primary key and then performed some business method on
 > >that entity ejb, would there really be two separate bean instances in
 each
 > >weblogic instance for the same primary key?
 > >
 > >If it is not pinned, yes.
 > >
 > >--
 > >Cameron Purdy
 > >Tangosol, Inc.
 > >http://www.tangosol.com
 > >+1.617.623.5782
 > >WebLogic Consulting Available
 > >
 > >
 > >"Bryan Dixon" <[email protected]> wrote in message
 > >news:[email protected]...
 > >>
 > >> Toa, thanks again.
 > >>
 > >> There are a couple of things I'm not clear about though. One is that I
 > >want one instance of an entity bean per primary key, not a singleton of
 the
 > >entity bean itself. How would JNDI in a clustered environment help me
 > >there?
 > >>
 > >> The other question I have is about having multiple instances of an
 entity
 > >bean for the same primary key in the cluster. I was thinking that
 > >read-write entity beans were pinned. So if two separate weblogic
 instances
 > >in a cluster did a find on an entity ejb with the same primary key and
 then
 > >performed some business method on that entity ejb, would there really be
 two
 > >separate bean instances in each weblogic instance for the same primary
 key?
 > >>
 > >> Thanks again,
 > >> Bryan
 > >>
 > >> "Tao Zhang" <[email protected]> wrote:
 > >> >
 > >> >"Bryan Dixon" <[email protected]> wrote:
 > >> >>
 > >> >>The reason I was wanting one instance per primary key is that I want
 to
 > >use this entity bean to cache some data from database tables. This data
 > >doesn't change frequently, so we were wanting to get it from this entity
 > >bean's memory instead of constantly hitting the database. This data is
 > >global to all users, so we don't want to store it in stateful session
 beans.
 > >> >>
 > >> >>After reading more about the read-only cache-strategy it doesn't
 appear
 > >that any sycnhronization will occur if the entity bean for a given
 primary
 > >key is updated (state data is updated) in one weblogic instance, that
 change
 > >will not get synced up with other weblogic instances for that same
 primary
 > >key. Is that correct?
 > >> >>
 > >> >It's correct. If you do want to have exact one copy in the cluster.
 You
 > >can read Using JNDI in cluster environment.
 > >> >
 > >> >>If I deploy this entity bean with read-write cache-strategy the
 WebLogic
 > >doc reads as if I will get one instance per primary key that is pinned to
 > >one WebLogic instance and I won't get any fail-over or load-balancing on
 the
 > >ejbObject (the entity bean instance). Did I read this correctly? If
 that
 > >is the case, what is the advantage of setting up read-write entity beans
 to
 > >be clusterable - just the Home objects? I definitely could be
 > >misunderstanding something in the doc since I'm very new to clustering.
 > >> "Tao
 > >> >Zhang"
 > >> ><[email protected]> wrote:
 > >> >>>
 > >> >
 > >> >It's not only instance in the cluster. Probably many instances.
 > >> >
 > >> >If you use 2 tier clustering, failover will not happen because of
 > >co-location. But if you use 3 tier cluster, you can write the special
 code
 > >in the client side to do failover and load-balance.
 > >> >
 > >> >In a 2 tier cluster, actually the ejb load balancing and failover is
 > >almost useless.
 > >> >
 > >> >But in 3 tier, you can use it.
 > >> >
 > >> >Hope this help.
 > >> >
 > >> >
 > >> >
 > >> >>>"Bryan Dixon" <[email protected]> wrote:
 > >> >>>>
 > >> >>>>Thanks Tao.
 > >> >>>>
 > >> >>>>A couple more questions...
 > >> >>>>I was planning deploying this entity bean with the read-only
 > >cache-strategy which means our transaction attribute would be
 > >TXN_NOT_SUPPORTED. Also, our db isolation is TRANSACTION_READ_COMMITTED.
 > >> >>>>
 > >> >>>>Based upon how I was planning on deploying this entity bean, would
 > >WebLogic create an instance of the bean for each primary key in each
 > >cluster? I'm just trying to figure out how many duplicate bean instances
 > >for the primary key I could have across all clusters. I was really just
 > >wanting one instance that is shared among all clients and was hoping that
 > >the clustering would provide me with fail-over if that one cluster went
 > >down.
 > >> >>>>
 > >> >>>If you use 3 tier cluster structure, it's impossible to know how
 many
 > >instances of ejb with the same primary key. Probably one instance for
 each
 > >wls instance.
 > >> >>>In wls5.1, it's impossible to host only read only entity bean
 instance
 > >in the 3-tier cluster. Because read only entity bean are clusterable in
 both
 > >home and remote interface.
 > >> >>>
 > >> >>>>Regarding making the bean a pinned service, which it sounds like I
 > >might have to do to get the results I want, how do I do that? Is that a
 > >deployment descriptor setting? Also, if I make it a pinned service, do I
 > >get any fail-over suport by clustering the bean?
 > >> >>>>
 > >> >>>For the pinned service, you can just deployed on one or several
 server
 > >instances. The per-server properties file is a good place to put the
 > >weblogic.ejb.deploy property. If only one pinned service in the cluster,
 you
 > >can't get fail over. If the that server instance fails, the home stub
 will
 > >be removed from the jndi in other server instances.
 > >> >>>
 > >> >>>Why do you must need only one instance in the cluster? Do you want
 > >exact-only-copy? You can read Using JNDI doc about its in cluster
 > >environment.
 > >> >>>
 > >> >>>
 > >> >>>
 > >> >>>
 > >> >>>>Thanks again,
 > >> >>>>Bryan
 > >> >>>>
 > >> >>>>
 > >> >>>>
 > >> >>>>"Tao Zhang" <[email protected]> wrote:
 > >> >>>>>
 > >> >>>>>
 > >> >>>>>Bryan Dixon <[email protected]> wrote in message
 > >> >>>>>news:[email protected]...
 > >> >>>>>>
 > >> >>>>>> I'm designing a data caching approach that relies on using
 > >read-only
 > >> >>>>>entity ejbs with bean-managed persistence. My design is based on
 the
 > >fact
 > >> >>>>>that WebLogic blocks on entity bean access by concurrent users for
 a
 > >given
 > >> >>>>>bean instance (unique primary key). I would like to keep only one
 > >entity
 > >> >>>>>bean instance active(timeoutSetting=0) for eacy primary key for
 all
 > >users to
 > >> >>>>>share. That way I only have to hit the database one time to
 > >initially
 > >> >>>>>populate data in the entity bean. I'm worried about this approach
 in
 > >a
 > >> >>>>>WebLogic clustered environment. From reading notes in this
 newsgroup
 > >and
 > >> >>>>>other doc, it appears that WebLogic might not use one instance of
 the
 > >entity
 > >> >>>>>bean (based upon unique primary key) in a clustered environment.
 Is
 > >that
 > >> >>>>>true (that being multiple users could get their own instance of
 the
 > >entity
 > >> >>>>>bean with the same primary key)?
 > >> >>>>>>
 > >> >>>>>
 > >> >>>>>
 > >> >>>>>It's true. In a cluster environment, each wls instance can have
 their
 > >ejb
 > >> >>>>>instance. The block of concurrent access to the ejb data is up to
 > >your
 > >> >>>>>transaction attribute and isolation level and your database.
 > >> >>>>>
 > >> >>>>>If you only want to keep one instance active, you can make the
 > >read-only
 > >> >>>>>entity bean a pinned service, to be deployed in one instance. But
 the
 > >> >>>>>network overhead is worse.
 > >> >>>>>
 > >> >>>>>
 > >> >>>>>> Thanks,
 > >> >>>>>> Bryan
 > >> >>>>>
 > >> >>>>>
 > >> >>>>
 > >> >>>
 > >> >>
 > >> >
 > >>
 > >
 > >
 >

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.

How create EJB 2.1 Stateful Session Bean in a EJB 3.0 Session Bean

Hi All,
We have been developing on EJB 2.1. We are now adding a module on EJB 3.0.
How can we "create" a stateful session bean with create method signature similar to create(String id)?
We have tried
// this is the remote interface
@EJB AddressBean abean;
But not working
Any help will be appreciated.

There is no explicit create() call for EJB 3.0 session beans. It doesn't really matter though
since you can accomplish the same thing by defining your own business method to act
as an initializer for whatever state you'd like. E.g.
@Remote
public interface FooInterface {
public void initialize(String id);
// ... other business methods
@EJB FooInterface fooRef;
fooRef.initialize("foo");
--ken

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.

Portal runtime error: Cannot access bean property

Dear all,
Does anybody have a clue what problem might couse the Portal Runtime Error described below?
It does seem to occur when a second user wants to access the Component.
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.xxxxx.luminaires/com.xxxx.iviews/Quotations/EasyQuote
Component Name : EasyQuoteDemo.EasyQuoteComponent
Tag tableView attribute model: Cannot access bean property quotationHeader.CurrentTableModel in page context.
Exception id: 04:50_21/09/04_0070
See the details for the exception ID in the log file
Thxs in advance
Joost

Hi Dominik,
Having a closer look at the problem, we found it is not the number of users.
It seems our JAVA components keeps the conenctions with SAP open and reopens a new one every time we start the component.
If we finished solving the problem, I will publish the solution.
Greetings,
Joost

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

Best practice for @EJB injection in junit test (out-of-container) ?

Hi all,
I'd like to run a JUnit test for a Stateless bean A which has another bean B injected via the @EJB annotation. Both beans are pure EJB 3 POJOs.
The JUnit test should run out-of-container and is not meant to be an EJB client, either.
What is the easiest/suggested way of getting this injection happening without explicitely having to instantiate the bean B in my test setup ?

you can deal with EntityBeans without having the Container managed senario , you can obtain instance of EntityManager using the "EntityManagerFactory" and providing the "persistence.xml" file and provide the "provider" (toplink,hibernate ,...), then you can use entities as plain un managed classes

Access bean(wrapper) for EJB

Similar Messages

Maybe you are looking for