Using @EJB in main as an alternative to InitialContext Object

Hallo everyone,
I have successfully run my main Method which calls an EJB using InitialContext (jndi-lookup).
If I am not mistaken, it is also possible to call an EJB in main-method using @EJB Annotation? I have tried this by importing
Import javax.ejb.EJB;
public static void main(String args[]) {
@EJB
private static TheBeanRemote tbr;
But unfortunately, it gave me the error in the compile Phase:
the annotation @EJB is disallowed for this Location
My questions:
1. Is it generally allowed to call an EJB in the main method?
2. If yes, did I miss some configuration XML-file in order to call EJB with annotations?
Thank you for your help.
Regars, Ratna

No, the @EJB annotation will only work in an actual JEE container (server) and only in a class that is actually managed by said container. And that is properly documented basically anywhere that covers EJB technology, so that can only mean you're doing wild guess work here in stead of proper study. That won't work, this is difficult technology to apply.

Similar Messages

Using local session bean interface from web container using EJB 3.0

Hi,
How can you use a local session bean interface from Java (rather than data controls) in a web container using EJB 3.0?
I can use a remote interface by looking up InitialContext, but I can't find a local interface this way (even from another session EJB). I can use a local interface from an EJB using annotation "EJB", but as I understand, this is not available in the web container.
If I try to add an ejb-jar.xml file, these seems to mess up by project...
Hope you can help.
Roger

The portable way to retrieve an EJB reference in Java EE is to either inject it or look it up via the
component's private naming environment. The simplest way is :
@EJB
private DocumentManager dm;
The global JNDI name is only used as an implementation specific way to uniquely assign an
identifier to a specific Remote EJB. It's best for this not to appear directly in the source code.
There's more on global JNDI names in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
The alternative to annotations is to use an ejb-ref to declare the ejb dependency. The ejb-ref
is declared in the standard deployment descriptor corresponding to the component doing the
lookup. Each ejb-ref has an ejb-ref-name, e.g. <ejb-ref-name>DM_ref</ejb-ref-name>
The code looks up the ejb-ref-name relative to the java:comp/env namespace to retrieve the
EJB reference.
DocumentManager dm = (DocumentManager)
new InitialContext().lookup("java:comp/env/DM_ref");

Using EJBs in Web Dynpro

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Thanks for your reply and your suggestion. I have posted in the Web Dynpro Java forum... and suggest those wishing to participate in this thread to refer to the Web Dynpro Java forum.
As for your answer, I'm afraid it doesn't satisfy me.
Reuse is hardly an issue, since the CommandBean is specifically tailor-made for the Web Dynpro application that needs to use it. I could hardly imagine building another application that would just happen to have the exact same needs as far as data structure and processing is concerned...
As for the right Eclipse environment... the CommandBean is not an EJB artifact - it is an EJB client. The aforementioned tutorial in fact suggests creating it in the Java perspective.
But thanks anyway for your time and suggestion

Using EJBs in Web Dynpro Applications

I have recently started to develop Web applications using the Web Dynpro framework. Coming from a pure J2EE world, I must admit that Web Dynpro has a few innovative features that I find interesting for user interface development. The use of component & view contexts, for example, is not unlike the ActionForms that one may find in a Struts application, but pushed a bit further. No complaints here.
What I do have some problems with is the whole CommandBean paradigm that is put forth by SAP (refer to the document <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webdynpro/using%20ejbs%20in%20web%20dynpro%20applications.pdf">Using EJBs in Web Dynpro Applications</a>).
I do understand the usefulness of defining a model that will be used to generate and eventually bind to Context data structures. That's fine. What I do object to is the use of a so-called CommandBean to play that role. Again, coming from a J2EE world, I am familiar with the BusinessDelegate pattern - which would typically be used by a client application to invoke business logic on the server side. I would propose that a better, cleaner way of integrating EJBs with the Web Dynpro framework would be to use a BusinessDelegate for invoking business logic, and importing a separate and distinct ModelBean (instead of a CommandBean) to be used for defining and binding to Context data.
I have built one Web Dynpro application thus far. Instead of using a CommandBean, I created a ModelBean that extends my business object DTO (Data Transfer Object) (which is quite appropriate for that role, given that it implements all the get & set methods that are required for the business data that I need to model). My Web Dynpro application also makes use of an independant BusinessDelegate that is packaged with my EJB DC - this is a standard best practice on J2EE projects. I have been asked by the people working with me to modify this architecture to bring it more in line with the SAP way of doing things. I am open-minded and willing to learn and accept new ways of thinking and doing things. However, I fail to understand the usefulness of merging structure and behaviour by resorting to CommandBeans:
- It violates the MVC paradigm by having one object (the CommandBean) serve as both model AND controller as far as the Web Dynpro application is concerned. The CommandBean is obviously a model - since it is literally imported as such into the Web Dynpro application. It is ALSO a controller from the Web Dynpro's application perspective, since all calls to the back-end go thru the CommandBean via one or more of its execute_xxx methods. In contrast, the use of a business delegate by the Web Dynpro application clearly separates the model (the CommandBean... or rather, a more suitably named ModelBean) from the controller (BusinessDelegate).
- Doesn't carry its own weight. In other words, I haven't yet been provided with any valid justification for going thru the extra effort of coding the CommandBean's execute methods. It's been proposed to me that it somehow serves as an abstraction layer between the Web Dynpro application and the business logic. I would argue that it is the BusinessDelegate's role to abstract away the back-end logic from clients. If one does have a BusinessDelegate available, I would argue there's no need to code execute methods in a separate CommandBean. To prove my point, I would simply point out that all of the CommandBean examples that I have seen so far, either in How-To documents, or in production code, all follow the same pattern....
CommandBean.execute_doSomething() calls BusinessDelegate.doSomething()
Not a heck of an "abstraction" layer... I would in fact argue that it is worse than useless. If some major change occurs in the business logic that requires changing the doSomething() operation, we expect of course to modify the BusinessDelegate. The Web Dynpro client will also presumably need to be modified - that's to be expected, and unavoidable. But then, we'll also need to go about and change the CommandBean's execute_doSomething() method - again, extra work for no apparent benefit. Adding and removing business methods has the same implication. All this for an layer that simply adds the prefix execute_ in front of all business method calls... Is this "abstraction layer" worth the cost of creating and maintaining it ??
- Unnecessarily complicates error handling. I have been told that for technical reasons, it is recommended that all exceptions thrown by the CommandBean be of type WDException or WDRuntimException. But what if the client application needs to react differently to different failure scenarios ? When I create a business object, I might wish to provide the user with an error messages if connection is lost to the backend, and with a different error message if an object already exists in the database with the same attributes. In order to do that, I will have to catch the WDException, extract the cause, and continue processing from there... possible, yes, but clearly less standard and more labor intensive than the classical try/catch mechanism.
To say nothing about the fact that SAP's own API documentation clearly states that applications using Web Dynpro can reference and catch WDExceptions, but THEY MUST NOT THROW OR EXTEND IT !
- Produces unnecessary DCs. Page 6 of the aforementioned document presents an architectural view of a Web Dynpro project that uses a CommandBean. Why an extra DC for the CommandBean ?? I created my ModelBean class right inside the Web Dynpro project (in the Package view). That, to me, is where this class should reside, because it is created for no other reason that to be used by this particular Web Dynpro application. What is the benefit of placing it in its own independant DC ?
- Not a typical application of the Command pattern. The well-documented command pattern (Design Patterns - Gang of Four) has been devised mainly to enable encapsulation of request as objects, thereby making it possible to:
- specify, queue and execute requests at different times
- decouple execution of a command from its invoker
- support undo operations
- support logging changes so that they can be reapplied in case of system crash making it possible to assemble commands into composite commands (macros), thereby structuring a system around high-level operations built on primitive operations.
None of this applies to the way the SAP CommandBeans are being used. Not that much of an issue to people new to J2EE and/or OO development... but quite confusing for those already familiar with the classic Command pattern.
At this point, I fail to understand the advantage of merging structure (model) and behaviour (execute methods) through the use of a unique CommandBean object. Am I missing something ?

Hi Romeo,
You would be disappointed, this reply ain't anywhere nearby to what you are talking about...
I wanted to mail you, but you have not mentioned your email in your profile.
I am really impressed by your flair for writing. It would be far better had you written a blog on this topic. Believe me, it would really be better. There is a much wider audience waiting out there to read your views rather than on the forums. This is what I believe. To top it, you would be rewarded for writing something like this from SDN. On the blogs too, people can comment and all, difference being there you would be rewarded by SDN, here people who reply to you would be rewarded by you. Doesn't make much a difference.
Anyways the ball is still in your court
As far as I am concerned, it has still not been much time since I have started working on Web Dynpro. So can't really comment on the issue...
Bye
Ankur

Problem in invoking LiveCycle using EJB

Hi All,
I am trying to invoke LC using EJB protocol. I referred the code example from the link http://help.adobe.com/en_US/livecycle/9.0/programLC/help/index.htm?content=001001.html#154 8359
But I am facing the problem in the same code. Here is the stack trace for the same:
Error Occurred: Exception thrown is NOT a
DSCException : UnExpected From DSC
com.adobe.idp.um.api.UMException
| [com.adobe.livecycle.usermanager.client.AuthenticationManagerServiceClient] errorCode:16385 errorCodeHEX:0x4001 message:Exception thrown is NOT a DSCException : UnExpected From DSC chainedException:java.lang.IllegalStateExceptionchainedExceptionMessage:null chainedException trace:java.lang.IllegalStateException
at com.adobe.idp.dsc.clientsdk.ServiceClientFactory$1.handleThrowable(
ServiceClientFactory.java:69)at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(
ServiceClient.java:220)at com.adobe.livecycle.usermanager.client.AuthenticationManagerServiceClient.authenticate(
AuthenticationManagerServiceClient.java:109)at in.gov.ebiz.eforms.invocation.AuthenticateUsersTest.main(
AuthenticateUsersTest.java:47)Caused by: java.lang.NoClassDefFoundError:
javax/ejb/EJBException
at com.adobe.idp.dsc.clientsdk.ServiceClientFactory.evaluateMessageDispatcher(
ServiceClientFactory.java:587)at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(
ServiceClient.java:215)... 2 more
Caused by:
java.lang.ClassNotFoundException: javax.ejb.EJBException
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(
Native Method)at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
... 4 more
at com.adobe.livecycle.usermanager.client.ManagerServiceClient.throwNonUMExceptionAsUMExcept ion(
ManagerServiceClient.java:53)at com.adobe.livecycle.usermanager.client.ManagerServiceClient.handleException(
ManagerServiceClient.java:95)at com.adobe.livecycle.usermanager.client.AuthenticationManagerServiceClient.authenticate(
AuthenticationManagerServiceClient.java:113)at in.gov.ebiz.eforms.invocation.AuthenticateUsersTest.main(
AuthenticateUsersTest.java:47)
Please advice me. Am I missing some jar? or Do I need to configure some settings at the server end?
Regards,
Ambika

The .xml and code looks ok. Using java:comp/env is the right approach. How does getInitialContext() instantiate the InitialContext()? Make sure it's using the no-arg "new InitialContext" Also try running the $APS_HOME/bin/verifier on your .ear. Please also post the full stack trace. Thanks.
--ken

How to use EJB Remote with Netbeans7.0 ?

I try to create Session Bean in Netbeans 7.0 but when I select Remote then I have to select Java Application in Netbeans. It different from Netbeans 6.8 ,6.9 which in Netbeans6.8, 6.9 not have dropdown for select Java Application when we choose Remote. So I don't know how to use EJB Remote in Netbeans7.0 then I click finish. After that, I create Project is Enterprise Application Client. but in Main.java at this line
BLSessionRemote obj = (BLSessionRemote)ctx.lookup("TestBean");
It can't find BLSessionRemote in Session Beans. How to use EJB Remote with Netbeans7.0 ?

Why don't you ask this question in the Netbeans mailing lists, where it belongs. Come here when you have problems with code you wrote yourself.

Second application using EJB with CMP cannot see SQL Server Tables.

We are running Sun One Application Server 7 V2004Q2 . We are also running Microsoft SQL Server 2000 Driver for JDBC Service Pack 3 Version 2.2.0040 and SQL Server 2000 Standard Edition Version 8.00.818(SP3).
(The 2 applications described below run perfectly fine when run one at a time. The second one fails only when it is started after the first one and it does not matter which one is strarted first..)
Using the above, we run 2 applications that open SQL Server Connection Pools via EJB with CMP. The first application opens the connection pool correctly and successfullly obtains a connection from that connection pool and get table information from SQL Server.
The second application opens a second connection pool to a second database in the same SQL Server. However, when the second application requests data over a connection from the second connection pool, we get an error message that it cannot find the requested table.
In addition, the second application cannot ever see the SQL data until we restart the instance of the Sun One Application Server AND start that application by itself.

Yes, they are.
---------------------------Stack Trace -------------------------------
[04/Feb/2005:17:03:37] FINE ( 2260): for host 127.0.0.1 trying to POST /SmhsVisitingStudentWeb/visitingstudentdean, ntrans-j2ee reports: mapped uri "/visitingstudentdean" in context "/SmhsVisitingStudentWeb" to resource "visitingstudentdean"
[04/Feb/2005:17:03:37] FINE ( 2260): context = StandardEngine[null].StandardHost[server1].StandardContext[SmhsVisitingStudentWeb]
[04/Feb/2005:17:03:37] FINE ( 2260): contextPath = /SmhsVisitingStudentWeb
[04/Feb/2005:17:03:37] FINE ( 2260): wrapper = null
[04/Feb/2005:17:03:37] FINE ( 2260): servletPath = null
[04/Feb/2005:17:03:37] FINE ( 2260): pathInfo = null
[04/Feb/2005:17:03:37] FINE ( 2260): SingleSignOn[server1]: Process request for '/SmhsVisitingStudentWeb/visitingstudentdean'
[04/Feb/2005:17:03:37] FINE ( 2260): SingleSignOn[server1]: Checking for SSO cookie
[04/Feb/2005:17:03:37] FINE ( 2260): SingleSignOn[server1]: SSO cookie is not present
[04/Feb/2005:17:03:37] FINE ( 2260): WebModule[SmhsVisitingStudentWeb]: Mapping contextPath='/SmhsVisitingStudentWeb' with requestURI='/SmhsVisitingStudentWeb/visitingstudentdean' and relativeURI='/visitingstudentdean'
[04/Feb/2005:17:03:37] FINE ( 2260): WebModule[SmhsVisitingStudentWeb]: Decoded relativeURI='/visitingstudentdean'
[04/Feb/2005:17:03:37] FINE ( 2260): WebModule[SmhsVisitingStudentWeb]: Trying exact match
[04/Feb/2005:17:03:37] FINE ( 2260): WebModule[SmhsVisitingStudentWeb]: Mapped to servlet 'visitingstudentdean' with servlet path '/visitingstudentdean' and path info 'null' and update=true
[04/Feb/2005:17:03:37] FINE ( 2260): visitingstudentdean: init
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINEST ( 2260): In SimpleSFSBUUIDUtilImpl.createSessionKey() ++++++++ timeField = df664744 counterField = 1
[04/Feb/2005:17:03:37] FINEST ( 2260): ---SQLPersistenceManagerFactory.initialize().
[04/Feb/2005:17:03:37] FINEST ( 2260): :Thread[service-j2ee-2,5,main] -->SQLPersistenceManagerFactory.getPersistenceManager().
[04/Feb/2005:17:03:37] FINEST ( 2260): Thread[service-j2ee-2,5,main] <->SQLPersistenceManagerFactory.getPersistenceManager() FOUND javax.transaction.Transaction: com.sun.ejb.containers.PMTransactionImpl@4.
[04/Feb/2005:17:03:37] FINEST ( 2260): <--SQLPersistenceManagerFactory.getFromPool().
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::send_request()
[04/Feb/2005:17:03:37] FINE ( 2260): Security context is null (nothing to add to service context)
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): ++++ Entered SecClientRequestInterceptor::receive_reply
[04/Feb/2005:17:03:37] FINE ( 2260): No SAS context element found in service context list
[04/Feb/2005:17:03:37] FINE ( 2260): Status to be set : 0
[04/Feb/2005:17:03:37] FINE ( 2260): Invoked receivedReply()
[04/Feb/2005:17:03:37] FINE ( 2260): ---SQLPersistenceManagerFactory: dbname = Microsoft SQL Server.
[04/Feb/2005:17:03:37] FINE ( 2260): <-> DBVendorType(), vendorName = [ Microsoft SQL Server] propertyName: microsoft_sql_server short name: MSSQL.
[04/Feb/2005:17:03:37] FINE ( 2260): --> DBVendorType.initialize().
[04/Feb/2005:17:03:37] FINE ( 2260): ---SQLStoreManager: vendor type = MSSQL.
[04/Feb/2005:17:03:37] FINEST ( 2260): PersistenceManagerImpl cache properties: txCacheInitialCapacity=20, flushedCacheInitialCapacity=20, flushedCacheLoadFactor=0.75, weakCacheInitialCapacity=20, _weakCacheLoadFactor=0.75.
[04/Feb/2005:17:03:37] FINEST ( 2260): NullSemaphore constructor() for PersistenceManagerImpl.cacheLock.
[04/Feb/2005:17:03:37] FINEST ( 2260): NullSemaphore constructor() for PersistenceManagerImpl.fieldUpdateLock.
[04/Feb/2005:17:03:37] FINEST ( 2260): <--SQLPersistenceManagerFactory.getFromPool() PM: com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a for JTA com.sun.ejb.containers.PMTransactionImpl@4.
[04/Feb/2005:17:03:37] FINEST ( 2260): <->SQLPersistenceManagerFactory.getPersistenceManager() JDO Transaction: Transaction:
status = STATUS_NO_TRANSACTION
Transaction Object = Transaction@18859698
threads = 0
[04/Feb/2005:17:03:37] FINEST ( 2260): Thread[service-j2ee-2,5,main] Tran[ Transaction:
status = STATUS_NO_TRANSACTION
Transaction Object = Transaction@18859698
threads = 0
].begin:status = STATUS_NO_TRANSACTION ,txType: UNKNOWN for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:37] FINEST ( 2260): Thread[service-j2ee-2,5,main] Tran[ Transaction:
status = STATUS_NO_TRANSACTION
Transaction Object = Transaction@18859698
threads = 0
].setStatus: STATUS_NO_TRANSACTION => STATUS_ACTIVE for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:37] FINEST ( 2260): Thread[service-j2ee-2,5,main] <->SQLPersistenceManagerFactory.getPersistenceManager() : com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a for JTA: com.sun.ejb.containers.PMTransactionImpl@4.
[04/Feb/2005:17:03:37] FINEST ( 2260): ---PersistenceManagerImpl.getCurrentWrapper() > current: null.
[04/Feb/2005:17:03:37] FINEST ( 2260): ---PersistenceManagerImpl.pushCurrentWrapper() > current: null new: com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerWrapper@12dd1b8.
[04/Feb/2005:17:03:37] FINER ( 2260): QueryImpl create new query QueryImpl@19109112
[04/Feb/2005:17:03:37] FINER ( 2260): QueryImpl compile query QueryImpl(candidateClass: class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, parameters: java.lang.String jdoParam1, , variables: , filter: ((this.password == jdoParam1) & (this.active == true)), result: this, identity: QueryImpl@19109112)
[04/Feb/2005:17:03:37] FINEST ( 2260): JQLC dump tree (AST)
query [55, (0/0), null, RD:null]
classDef [56, (0/0), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
parameterDef [58, (0/0), null, RD:null]
. [91, (1/10), null, RD:null]
. [91, (1/5), null, RD:null]
java [52, (1/1), null, RD:null]
lang [52, (1/6), null, RD:null]
String [52, (1/11), null, RD:null]
_jdoParam1 [52, (1/18), null, RD:null]
resultDef [83, (0/0), null, RD:null]
this [5, (1/1), null, RD:null]
filterDef [61, (0/0), null, RD:null]
& [39, (1/32), null, RD:null]
== [23, (1/17), null, RD:null]
. [91, (1/7), null, RD:null]
this [5, (1/3), null, RD:null]
password [52, (1/8), null, RD:null]
_jdoParam1 [52, (1/20), null, RD:null]
== [23, (1/47), null, RD:null]
. [91, (1/39), null, RD:null]
this [5, (1/35), null, RD:null]
active [52, (1/40), null, RD:null]
true [18, (1/50), null, RD:null]
[04/Feb/2005:17:03:37] FINER ( 2260): JQLC start semantic analysis
[04/Feb/2005:17:03:37] FINEST ( 2260): JQLC dump tree (typed AST)
query [55, (0/0), null, RD:null]
classDef [56, (0/0), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
parameterDef [58, (0/0), null, RD:null]
java.lang.String [81, (1/10), java.lang.String, RD:null]
_jdoParam1 [52, (1/18), java.lang.String, RD:null]
resultDef [83, (0/0), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
this [5, (1/1), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
filterDef [61, (0/0), null, RD:null]
& [39, (1/32), boolean, RD:null]
== [23, (1/17), boolean, RD:null]
this.password [71, (1/7), java.lang.String, RD:null]
this [5, (1/3), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
password [52, (1/8), java.lang.String, RD:null]
_jdoParam1 [80, (1/20), java.lang.String, RD:null]
== [23, (1/47), boolean, RD:null]
this.active [71, (1/39), java.lang.Boolean, RD:null]
this [5, (1/35), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
active [52, (1/40), java.lang.Boolean, RD:null]
true [18, (1/50), boolean, RD:null]
[04/Feb/2005:17:03:37] FINER ( 2260): JQLC start optimizer
[04/Feb/2005:17:03:37] FINEST ( 2260): JQLC dump tree (optimized AST)
query [55, (0/0), null, RD:null]
classDef [56, (0/0), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
parameterDef [58, (0/0), null, RD:null]
java.lang.String [81, (1/10), java.lang.String, RD:null]
_jdoParam1 [52, (1/18), java.lang.String, RD:null]
resultDef [83, (0/0), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
this [5, (1/1), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
filterDef [61, (0/0), null, RD:null]
& [39, (1/32), boolean, RD:null]
== [23, (1/17), boolean, RD:null]
this.password [71, (1/7), java.lang.String, RD:null]
this [5, (1/3), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
password [52, (1/8), java.lang.String, RD:null]
_jdoParam1 [80, (1/20), java.lang.String, RD:null]
this.active [71, (1/39), java.lang.Boolean, RD:null]
this [5, (1/35), gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState, RD:null]
active [52, (1/40), java.lang.Boolean, RD:null]
true [82, (1/50), boolean, RD:null]
[04/Feb/2005:17:03:37] FINER ( 2260): JQLC start code generation
[04/Feb/2005:17:03:37] FINER ( 2260): SQLStoreManager.getPersistenceConfig(), classType = gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState.
[04/Feb/2005:17:03:38] SEVERE ( 2260): Validation error in class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState: com.sun.jdo.api.persistence.model.util.ModelValidationException: Warning: Cannot find the table Student for the class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState.
Verify that the schema file exists and that its contents are correct.
[04/Feb/2005:17:03:38] FINE ( 2260): Exception.
com.sun.jdo.api.persistence.support.JDOUserException: The mapping for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState is invalid. Compile the class in the IDE, correct any errors, and verify that all required files are packaged for execution.
 at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.getPersistenceConfig(SQLStoreManager.java:128)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.loadPersistenceConfig(PersistenceManagerImpl.java:2085)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.getRetrieveDesc(PersistenceManagerImpl.java:1009)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.createRetrieveDesc(CodeGeneration.java:707)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.checkRetrieveDesc(CodeGeneration.java:4665)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.prepareRetrieveDescs(CodeGeneration.java:4360)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.query(CodeGeneration.java:850)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.JQLC.codeGen(JQLC.java:332)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:626)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:552)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl.ejbFindActiveByPassword(StudentBean129315485_ConcreteImpl.java:3491)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl_LocalHomeImpl.findActiveByPassword(StudentBean129315485_ConcreteImpl_LocalHomeImpl.java:137)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean.ejbCreate(StudentDeanSessionBean.java:29)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean_LocalHomeImpl.create(StudentDeanSessionBean_LocalHomeImpl.java:27)
 at gwumc.edu.smhs.servlet.VisitingStudentDeanModel.<init>(VisitingStudentDeanModel.java:18)
 at gwumc.edu.smhs.servlet.VisitingStudentDean.doPost(VisitingStudentDean.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
 at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
 at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
 at com.iplanet.ias.web.WebContainer.service(WebContainer.java:850)
[04/Feb/2005:17:03:38] INFO ( 2260): Bean Student method ejbFindActiveByPassword: problems running JDOQL query with params [29]
com.sun.jdo.api.persistence.support.JDOFatalInternalException: Failed to load the configuration for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState.
NestedException: com.sun.jdo.api.persistence.support.JDOUserException: The mapping for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState is invalid. Compile the class in the IDE, correct any errors, and verify that all required files are packaged for execution.
 at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.getPersistenceConfig(SQLStoreManager.java:145)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.loadPersistenceConfig(PersistenceManagerImpl.java:2085)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.getRetrieveDesc(PersistenceManagerImpl.java:1009)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.createRetrieveDesc(CodeGeneration.java:707)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.checkRetrieveDesc(CodeGeneration.java:4665)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.prepareRetrieveDescs(CodeGeneration.java:4360)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.query(CodeGeneration.java:850)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.JQLC.codeGen(JQLC.java:332)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:626)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:552)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl.ejbFindActiveByPassword(StudentBean129315485_ConcreteImpl.java:3491)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl_LocalHomeImpl.findActiveByPassword(StudentBean129315485_ConcreteImpl_LocalHomeImpl.java:137)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean.ejbCreate(StudentDeanSessionBean.java:29)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean_LocalHomeImpl.create(StudentDeanSessionBean_LocalHomeImpl.java:27)
 at gwumc.edu.smhs.servlet.VisitingStudentDeanModel.<init>(VisitingStudentDeanModel.java:18)
 at gwumc.edu.smhs.servlet.VisitingStudentDean.doPost(VisitingStudentDean.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
 at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
 at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
 at com.iplanet.ias.we
[04/Feb/2005:17:03:38] INFO ( 2260): b.WebContainer.service(WebContainer.java:850)
NestedStackTrace:
com.sun.jdo.api.persistence.support.JDOUserException: The mapping for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState is invalid. Compile the class in the IDE, correct any errors, and verify that all required files are packaged for execution.
 at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.getPersistenceConfig(SQLStoreManager.java:128)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.loadPersistenceConfig(PersistenceManagerImpl.java:2085)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.getRetrieveDesc(PersistenceManagerImpl.java:1009)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.createRetrieveDesc(CodeGeneration.java:707)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.checkRetrieveDesc(CodeGeneration.java:4665)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.prepareRetrieveDescs(CodeGeneration.java:4360)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.query(CodeGeneration.java:850)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.JQLC.codeGen(JQLC.java:332)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.doExecute(QueryImpl.java:626)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.QueryImpl.executeWithArray(QueryImpl.java:552)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl.ejbFindActiveByPassword(StudentBean129315485_ConcreteImpl.java:3491)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl_LocalHomeImpl.findActiveByPassword(StudentBean129315485_ConcreteImpl_LocalHomeImpl.java:137)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean.ejbCreate(StudentDeanSessionBean.java:29)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean_LocalHomeImpl.create(StudentDeanSessionBean_LocalHomeImpl.java:27)
 at gwumc.edu.smhs.servlet.VisitingStudentDeanModel.<init>(VisitingStudentDeanModel.java:18)
 at gwumc.edu.smhs.servlet.VisitingStudentDean.doPost(VisitingStudentDean.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
 at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
 at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
 at com.iplanet.ias.web.WebContainer.service(WebContainer.java:850)
[04/Feb/2005:17:03:38] FINEST ( 2260): ---PersistenceManagerImpl.popCurrentWrapper() > current: com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerWrapper@12dd1b8 prev: null.
[04/Feb/2005:17:03:38] FINE ( 2260): Exception in forceDestroyBean()
java.lang.IllegalStateException: Primary key not available
 at com.sun.ejb.containers.EntityContextImpl.getPrimaryKey(EntityContextImpl.java:159)
 at com.sun.ejb.containers.EntityContainer.forceDestroyBean(EntityContainer.java:1314)
 at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:1827)
 at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:1642)
 at com.sun.ejb.containers.BaseContainer.postInvoke(BaseContainer.java:553)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_ConcreteImpl_LocalHomeImpl.findActiveByPassword(StudentBean129315485_ConcreteImpl_LocalHomeImpl.java:142)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean.ejbCreate(StudentDeanSessionBean.java:29)
 at gwumc.edu.ejb.smhs.visitingstudent.StudentDeanSessionBean_LocalHomeImpl.create(StudentDeanSessionBean_LocalHomeImpl.java:27)
 at gwumc.edu.smhs.servlet.VisitingStudentDeanModel.<init>(VisitingStudentDeanModel.java:18)
 at gwumc.edu.smhs.servlet.VisitingStudentDean.doPost(VisitingStudentDean.java:27)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at org.apache.catalina.core.StandardWrapperValve.invokeServletService(StandardWrapperValve.java:720)
 at org.apache.catalina.core.StandardWrapperValve.access$000(StandardWrapperValve.java:118)
 at org.apache.catalina.core.StandardWrapperValve$1.run(StandardWrapperValve.java:278)
 at java.security.AccessController.doPrivileged(Native Method)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:274)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:212)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:203)
 at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:505)
 at com.iplanet.ias.web.connector.nsapi.NSAPIProcessor.process(NSAPIProcessor.java:158)
 at com.iplanet.ias.web.WebContainer.service(WebContainer.java:850)
[04/Feb/2005:17:03:38] FINEST ( 2260): Thread.currentThread()Tran[ Transaction:
status = STATUS_ACTIVE
Transaction Object = Transaction@18859698
threads = 1
].afterCompletion: status = STATUS_ACTIVE, sync = null, STATUS_ROLLEDBACK for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:38] FINEST ( 2260): Thread[service-j2ee-2,5,main] Tran[ Transaction:
status = STATUS_ACTIVE
Transaction Object = Transaction@18859698
threads = 1
].setStatus: STATUS_ACTIVE => STATUS_ROLLING_BACK for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:38] FINEST ( 2260): Thread[service-j2ee-2,5,main] Tran[ Transaction:
status = STATUS_ROLLING_BACK
Transaction Object = Transaction@18859698
threads = 1
].internalRollback:status = STATUS_ROLLING_BACK ,txType: CMT for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:38] FINEST ( 2260): Thread[service-j2ee-2,5,main] Tran[ Transaction:
status = STATUS_ROLLING_BACK
Transaction Object = Transaction@18859698
threads = 1
].setStatus: STATUS_ROLLING_BACK => STATUS_ROLLEDBACK for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:38] FINEST ( 2260): ---PersistenceManagerImpl.afterCompletion() process: true.
[04/Feb/2005:17:03:38] FINEST ( 2260): Thread[service-j2ee-2,5,main] Tran[ Transaction:
status = STATUS_ROLLEDBACK
Transaction Object = Transaction@18859698
threads = 1
].forget:status = STATUS_ROLLEDBACK ,txType: CMT for com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a.
[04/Feb/2005:17:03:38] FINEST ( 2260): ---SQLPersistenceManagerFactory.releasePersistenceManager() PM:com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a for JTA Tx: com.sun.ejb.containers.PMTransactionImpl@4.
[04/Feb/2005:17:03:38] FINEST ( 2260): ---SQLPersistenceManagerFactory.releasePersistenceManager() PM:com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl@15670a for JTA Tx: null.
[04/Feb/2005:17:03:38] FINEST ( 2260): <--SQLPersistenceManagerFactory.returnToPool().
[04/Feb/2005:17:03:38] FINE ( 2260): EJB5018: Some unmapped exception occurred : [{0}]
javax.ejb.EJBException: nested exception is: com.sun.jdo.api.persistence.support.JDOFatalInternalException: Failed to load the configuration for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState.
NestedException: com.sun.jdo.api.persistence.support.JDOUserException: The mapping for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState is invalid. Compile the class in the IDE, correct any errors, and verify that all required files are packaged for execution.
com.sun.jdo.api.persistence.support.JDOFatalInternalException: Failed to load the configuration for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState.
NestedException: com.sun.jdo.api.persistence.support.JDOUserException: The mapping for class gwumc.edu.ejb.smhs.visitingstudent.StudentBean129315485_JDOState is invalid. Compile the class in the IDE, correct any errors, and verify that all required files are packaged for execution.
 at com.sun.jdo.spi.persistence.support.sqlstore.SQLStoreManager.getPersistenceConfig(SQLStoreManager.java:145)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.loadPersistenceConfig(PersistenceManagerImpl.java:2085)
 at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerImpl.getRetrieveDesc(PersistenceManagerImpl.java:1009)
 at com.sun.jdo.spi.persistence.support.sqlstore.query.jqlc.CodeGeneration.createRetrieveDesc(CodeGeneration.java:707)
 a

A Tip for using EJB 3.0 with WebLogic Ant Tasks

I started out writing this up as a problem, but then I found the answer so I'm, posting a tip instead.
When I tried to write an EJB [stateless] using EJB 3.0 in my legacy Weblogic ear project I started getting this error:
<pre>
No EJBs found in the ejb-jar file 'test'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
</pre>
This is why: wlcompile will put the class files in the App-Inf/classes directory unless it finds an ejb-jar.xml file in the META-INF directory for the module it is working on. With EJB 3.0, I wasn't using an ejb-jar.xml file because it was unnecessary. Later, Appc runs and it complains because there are no classes module directory, they went into the shared ear folder instead.
Here's I how it working again: Use javac [not wlcompile] to compile the EJB 3.0 module and make sure that the class files go into the correct module directory. Then you can use wlappc to generate all the associated files for the EJB. I have sucessfully deployed an ear file that uses both EJB 2.x and EJB 3.0 with this approach.
I wish Weblogic's own ejb3.0 sample application used their split directory deployment.
Good Luck.
John Aronson

Hi John,
I am working on development an enterprise application using EJB 3.0 on Weblogic 10.
While developing, I am keeping all my classes (from ejb's as well as web) into APP-INF/classes directory. It is working fine for Web and ejb 2.0 packages, but ejb 3.0 packages, I get the following error when I keep my ejb 3.0 beans classes in APP-INF/classes directory.
No EJBs found in the ejb-jar file 'customer'. Please ensure the ejb-jar contains EJB declarations via an ejb-jar.xml deployment descriptor or at least one class annotated with the @Stateless, @Stateful or @MessageDriven EJB annotation.
One solution is to keep the classes under customer ejb directory, but I wan tto keep all the classes in APP-INF/classes directory so that when using Eclipse IDE I can output all compiled sources into APP-INF/classes directory.
Has anyone faced this situation? Any suggestions to fix this issue?

How can I use EJB component on Weblogic 8.1 server ?

hi,dear sir:
How can I use EJB component on Weblogic 8.1 server ?
It need client jar to invoke ejb,but what will I to do for this jar file? what does it contain? format ?
If my EJB module contain 100 session bean and 50 Entity bean,but I want invoke 20 session beans in my module, how can I to do?
thank you...

Hi,
This forum is exclusively for Creator. please post this on appropriate forum
regards
CreatorTeam

Apple has just deleted my alias - which I was using as my main email address. They deny me creating a new one for 7 days. How can I get in touch with Apple so that they repair what they have broken?

Has anyone had a problems with their alias today?
Apple has deleted mine today; causing me a major headache as they deleted the alias that I use as my main email address.
What happened exactly, is that the @icloud.com alias remained, but the @me.com disapeared. So that the John.Smith alias became valid only for [email protected], but [email protected] disapeared.
To try to restore the situation, I deleted the alias, with the hope of re-creating it: but bad luck, that option is not open to me as I have had 5 aliases active till today, and they now only give you 3, and even once I had deleted 2, they would not allow me to set-up a new one for 7 DAYS.
I can't be without email for 7DAYS, care of Apple. Calling AppleCare does not seem to help, and the line gets dropped once I have explained the problem.
Please help me raise someone at Apple to fix this.
Alain

See this discussion, https://discussions.apple.com/message/19779377#19779377

Saving parameters entered in a gui dialog to be used in the main panel

Hi,
I'm having a nightmare at the moment.
I've finished creating a program for my final year project, that is all comand line at the moment.
i'm required to design a GUI for this. i've started already and have a main panel that has a few buttons one of which is a setParameters button. which opens up a file dialog that allows the user to enter parameters that will be used by the main panel later on.
I'm having trouble imagining how these parameters will be accessed by the main Panel once they are saved.
At the moment, without the GUI i have get and set methods in my main program which works fine. Is this the kind of thing i'll be using for this?
my code for the parameters dialog
public class Parameters extends JDialog
 private GridLayout grid1, grid2, grid3;
 JButton ok, cancel;
 public Parameters()
 setTitle( "Parameters" );
 setSize( 400,500 );
 setDefaultCloseOperation( DISPOSE_ON_CLOSE );
 grid1 = new GridLayout(7,2);
 grid2 = new GridLayout(1,2);
 JPanel topPanel = new JPanel();
 topPanel.setLayout(grid1);
 JPanel buttonPanel = new JPanel();
 buttonPanel.setLayout(grid2);
 ok = new JButton("OK");
 ok.addActionListener(new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 //when pressed i want to save the parameters that the user has entered
 //and be able to access these in the RunPanel class
 cancel = new JButton("Cancel");
 cancel.addActionListener(new ActionListener() {
 public void actionPerformed(ActionEvent e) {
 //when pressed just want the Jdialog to close
 buttonPanel.add(ok);
 buttonPanel.add(cancel);
 JTextArea affinityThresholdScalar = new JTextArea();
 JTextArea clonalRate = new JTextArea();
 JTextArea stimulationValue = new JTextArea();
 JTextArea totalResources = new JTextArea();
 JLabel aTSLabel = new JLabel("affinityThresholdScalar");
 JLabel cRLabel = new JLabel("clonalRate");
 topPanel.add(aTSLabel);
 topPanel.add(affinityThresholdScalar);
 topPanel.add(cRLabel);
 topPanel.add(clonalRate);
 Container container = getContentPane();//.add( topPanel );
 container.add( topPanel, BorderLayout.CENTER );
 container.add( buttonPanel, BorderLayout.SOUTH );
 }the main panel class is:
public class RunPanel extends JPanel implements ActionListener
 JButton openButton, setParametersButton, saveButton;
 static private final String newline = "\n";
 JTextArea log;
 JFileChooser fc;
 Data d = new Data();
 Normalise rf = new Normalise();
 Parameters param = new Parameters();
 public RunPanel()
 super(new BorderLayout());
 log = new JTextArea(5,20);
 log.setMargin(new Insets(5,5,5,5));
 log.setEditable(false);
 JScrollPane logScrollPane = new JScrollPane(log);
 fc = new JFileChooser();
 openButton = new JButton("Open a File...")
 openButton.addActionListener(this);
 setParametersButton = new JButton("Set User Parameters");
 setParametersButton.addActionListener(this);
 saveButton = new JButton("save");
 saveButton.addActionListener(this);
 JPanel buttonPanel = new JPanel(); //use FlowLayout
 buttonPanel.add(openButton);
 buttonPanel.add(setParametersButton);
 JPanel savePanel = new JPanel();
 savePanel.add(saveButton);
 add(buttonPanel, BorderLayout.PAGE_START);
 add(logScrollPane, BorderLayout.CENTER);
 add(savePanel, BorderLayout.SOUTH);
 public void actionPerformed(ActionEvent e) {
 if (e.getSource() == openButton) {
 int returnVal = fc.showOpenDialog(RunPanel.this);
 if (returnVal == JFileChooser.APPROVE_OPTION) {
 File file = fc.getSelectedFile();
 log.append("Opening: " + file.getName() + "." + newline);
 Vector data = d.readFile(file);
 log.append("Reading file into Vector " +data+ "." + newline);
 Vector dataNormalised = rf.normalise(data);
 else {
 log.append("Open command cancelled by user." + newline);
 log.setCaretPosition(log.getDocument().getLength());
 else if (e.getSource() == saveButton) {
 int returnVal = fc.showSaveDialog(RunPanel.this);
 if (returnVal == JFileChooser.APPROVE_OPTION) {
 File file = fc.getSelectedFile();
 log.append("Saving: " + file.getName() + "." + newline);
 } else {
 log.append("Save command cancelled by user." + newline);
 log.setCaretPosition(log.getDocument().getLength());
 else
 if (e.getSource() == setParametersButton)
 log.append("loser." + newline);
 param.show();
 private static void createAndShowGUI() {
 JFrame.setDefaultLookAndFeelDecorated(true);
 JDialog.setDefaultLookAndFeelDecorated(true);
 JFrame frame = new JFrame("AIRS");
 frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
 JComponent newContentPane = new RunPanel();
 newContentPane.setOpaque(true);
 frame.setContentPane(newContentPane);
 frame.pack();
 frame.setVisible(true);
 public static void main(String[] args) {
 javax.swing.SwingUtilities.invokeLater(new Runnable() {
 public void run() {
 createAndShowGUI();
}Can anybody offer any suggestions?
Cheers

What you need is my ParamDialog. I think it could be perfect for this sort of thing. There are a few references in it to some of my other classes namely
StandardDialog. Which you can find by searching for other posts on this forum. But if you'd rather not find that you could just use JDialog instead
WindowUtils.visualize() this is just a helper method for getting things visualized on the screen. You can just use setBounds and setVisible and you'll be fine.
You are welcome to use and modify this code but please don't change the package or take credit for it as your own work.
If you need to bring up a filedialog or a color chooser you will need to make some modifications. If you do this, would you mind posting that when you are done so that myself and others can use it? :)
StandardDialog.java
================
package tjacobs.ui;
import java.awt.Dialog;
import java.awt.Frame;
import java.awt.GraphicsConfiguration;
import java.awt.HeadlessException;
import javax.swing.JFrame;
import javax.swing.JLabel;
import javax.swing.JPanel;
import javax.swing.JPasswordField;
import javax.swing.JTextField;
import java.awt.*;
import java.util.HashMap;
import java.util.Properties;
/** Usage:
* * ParamDialog pd = new ParamDialog(new String[] {"A", "B", "C"});
* pd.pack();
* pd.setVisible(true);
* Properties p = pd.getProperties();
public class ParamDialog extends StandardDialog {
 public static final String SECRET = "(SECRET)";
 String[] fields;
 HashMap<String, JTextField> mValues = new HashMap<String, JTextField>();
 public ParamDialog(String[] fields) throws HeadlessException {
 this(null, fields);
 public ParamDialog(JFrame owner, String[] fields) {
 super(owner);
 setModal(true);
 this.fields = fields;
 JPanel main = new JPanel();
 main.setLayout(new GridLayout(fields.length, 1));
 for (int i = 0; i < fields.length; i++) {
 JPanel con = new JPanel(new FlowLayout());
 main.add(con);
 JTextField tf;
 if (fields.endsWith(SECRET)) {
 con.add(new JLabel(fields[i].substring(0, fields[i].length() - SECRET.length())));
 tf = new JPasswordField();
 else {
 con.add(new JLabel(fields[i]));
 tf = new JTextField();
 tf.setColumns(12);
 con.add(tf);
 mValues.put(fields[i], tf);
 this.setMainContent(main);
 public boolean showApplyButton() {
 return false;
 public void apply() {
 private boolean mCancel = false;
 public void cancel() {
 mCancel = true;
 super.cancel();
 public Properties getProperties() {
 if (mCancel) return null;
 Properties p = new Properties();
 for (int i = 0; i < fields.length; i++) {
 p.put(fields[i], mValues.get(fields[i]).getText());
 return p;
 public static void main (String[] args) {
 ParamDialog pd = new ParamDialog(new String[] {"A", "B", "C"});
 WindowUtilities.visualize(pd);
 public static Properties getProperties(String[] fields) {
 ParamDialog pd = new ParamDialog(fields);
 WindowUtilities.visualize(pd);
 return pd.getProperties();

How can I develop a web application using EJB design pattern?

I have searched over the web and found quite a lot of tutorials on how to use the EJB design pattern.
I know that there will be a home interface, EJB object interface and a SessionBean.
But the tutorials often only cover a single class, this made me unable to get a complete picture of how EJB design pattern can be implemented into a whole system.
I am now required to devleop an online shopping web application using EJB and JSP page.
I think I will need to create a lot of classes: Member, ShoppingCart, Product...etc.
What I want to ask is that, do I need to create a home interface, EJB object interface and a SessionBean for each of these classes?
I really need some ideas on how to develop this system using EJB + JSP pages.
Many thanks to you all.

For every EJB that you want to create, you will need to code a home and remote interface and a bean class.
You could start getting your ideas here
http://www.theserverside.com/books/wiley/masteringEJB/
http://www.coreservlets.com

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.

How to Retrive data from db using EJB in WebDynpro

hi...
i m using EJB's for backend connection in WebDynpro .in which i m able to store data in sapdb .for this i followed one tutorial which i have mentioned bellow which works perfectly.Now in the same Tutorial i want to retrive the data from database and disply it in WebDynpro
i .e i want to disply bonus when i give ssn no and also i want to disply all data in db.
Please help me as i m totaly new to this environment and also first time i m working on EJB.its very urgent
Thanks and Regards
Sonal<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c</a>

hi...
i m using EJB's for backend connection in WebDynpro .in which i m able to store data in sapdb .for this i followed one tutorial which i have mentioned bellow which works perfectly.Now in the same Tutorial i want to retrive the data from database and disply it in WebDynpro
i .e i want to disply bonus when i give ssn no and also i want to disply all data in db.
Please help me as i m totaly new to this environment and also first time i m working on EJB.its very urgent
Thanks and Regards
Sonal<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1f5f3366-0401-0010-d6b0-e85a49e93a5c</a>

Could not lookup PortalManagerHome in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager

Hi
I am just a starter on WLPortal.
I have created a barebone Application from scratch. I have synchronized it properly
from EBCC to WLP. But When I am trying to access the home page of my application,
I am getting from stack trace -
<Nov 6, 2002 5:37:59 PM IST> <Error> <PortalAppflow> <Could not lookup PortalManagerHome
in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager.
javax.naming.NameNotFoundException: Unable to resolve comp/env/ejb/PortalManager
Resolved: 'comp/env' Unresolved:'ejb' ; remaining name 'PortalManager'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:802)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:173)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:181)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:181)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:323)
at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:36)
at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:124)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at com.bea.p13n.util.JndiHelper.lookupNarrow(JndiHelper.java:96)
at com.bea.portal.appflow.PortalAppflowHelper.<clinit>(PortalAppflowHelper.java:64)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.init(PortalWebflowServlet.java:78)
at javax.servlet.GenericServlet.init(GenericServlet.java:258)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:700)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:643)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:588)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:368)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:242)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:215)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2459)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Nov 6, 2002 5:37:59 PM IST> <Error> <HTTP> <[WebAppServletContext(19695286,FirstWebApp,/FirstWebApp)]
Servlet failed with Exception
java.lang.NullPointerException:
at com.bea.portal.appflow.PortalAppflowHelper.createPortalManager(PortalAppflowHelper.java:82)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.setupPortalRequest(PortalWebflowServlet.java:187)
at com.bea.portal.appflow.servlets.internal.PortalWebflowServlet.doGet(PortalWebflowServlet.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:215)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at jsp_servlet.__index._jspService(__index.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:304)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2459)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
When I decompiled the class PortalAppflowHelper, I found a static block in it,
which was as under-
static
debug = Debug.getInstance(com.bea.portal.appflow.PortalAppflowHelper.class);
try
if(debug.ON)
debug.out("Looking up PortalManagerHome using EJB reference java:comp/env/ejb/PortalManager");
portalManagerHome = (PortalManagerHome)JndiHelper.lookupNarrow("java:comp/env/ejb/PortalManager",
com.bea.portal.manager.ejb.PortalManagerHome.class);
if(debug.ON)
debug.out("Successfully retrieved PortalManagerHome " + portalManagerHome);
catch(Exception e)
PortalAppflowLogger.errorFindingPortalManagerHome("java:comp/env/ejb/PortalManager",
e);
I have checked the PortalManager's JNDI name on WLConsole. Its ${APPNAME}.BEA_portal.PortalManager.
Should I change it?
When I tried to change it, I started getting other weird errors.
Thanks
Neeraj Hans

Neeraj -
The Portal framework code (including PortalAppflowHelper) uses ejb
references to find the PortalManager (and other EJBs) from servlets and
taglibs; that is what is signified by the java:comp/env/... name.
Since you built your webapp from scratch (instead of using the portal
wizard), you will need to make sure the you have the appropriate
<ejb-ref> entries in your web.xml, and the corresponding
<ejb-reference-description> entries in your weblogic.xml. By default,
you will need at least mappings for:
- ejb/PortalManager
- ejb/UserManager
- ejb/GroupManager
- ejb/PipelineExecutor
- ejb/EventService
See either the resulting webapp from using the portal wizard or
BEA_HOME/weblogic700/samples/portal/sampleportalDomain/beaApps/sampleportal/sampleportal/WEB-INF
for example syntax.
Greg
Neeraj Hans wrote:
Hi
I am just a starter on WLPortal.
I have created a barebone Application from scratch. I have
synchronized it properly
from EBCC to WLP. But When I am trying to access the home page of my
application,
I am getting from stack trace -
<Nov 6, 2002 5:37:59 PM IST> <Error> <PortalAppflow> <Could not lookup
PortalManagerHome
in the JNDI tree using EJB reference java:comp/env/ejb/PortalManager.
javax.naming.NameNotFoundException: Unable to resolve
comp/env/ejb/PortalManager
Resolved: 'comp/env' Unresolved:'ejb' ; remaining name 'PortalManager'
at <stack trace lines snipped>
When I decompiled the class PortalAppflowHelper, I found a static
block in it,
which was as under-
static
debug =
Debug.getInstance(com.bea.portal.appflow.PortalAppflowHelper.class);
try
if(debug.ON)
debug.out("Looking up PortalManagerHome using EJB
reference java:comp/env/ejb/PortalManager");
portalManagerHome =
(PortalManagerHome)JndiHelper.lookupNarrow("java:comp/env/ejb/PortalManager",
com.bea.portal.manager.ejb.PortalManagerHome.class);
if(debug.ON)
debug.out("Successfully retrieved PortalManagerHome "
+ portalManagerHome);
catch(Exception e)
PortalAppflowLogger.errorFindingPortalManagerHome("java:comp/env/ejb/PortalManager",
e);
I have checked the PortalManager's JNDI name on WLConsole. Its
${APPNAME}.BEA_portal.PortalManager.
Should I change it?
When I tried to change it, I started getting other weird errors.
Thanks
Neeraj Hans

Using @EJB in main as an alternative to InitialContext Object

Similar Messages

Maybe you are looking for