Shutdown class; unable to access EJBs/JDBC

Question

I have a fundamental question here, and for which I have not found any documentation
on BEA's own documentation center.
Can I, or can I not invoke operations on EJBs/JDBC/JNDI etc from my implementation
of weblogic.common.T3ShutdownDef??
Startup classes can in general access all resources, and they can also invoke
services on EJBs if LoadBeforeAppDeployments is false (the default) in config.xml.
However, the same does not seem to be true for shutdown classes. I am unable to
access services from a shutdown class.
As soon as I invoke weblogic.Admin with SHUTDOWN as the command, the server transitions
to STANDBY state and then the shutdown class is invoked.
The session bean is found and available, but when a transaction is sought to be
created to execute a finder on an EntityBean within the SessionBean, I get an
exception that transactions cannot be created in the Standby state of the server.
To get around this, I thought I will get a reference to the DataSource from JNDI
and execute a query on the JDBC connection, and that failed as well, saying that
JDBC connections are also not available.
Am I doing something wrong here? Or is this a bug.
I am developing on WLS 7.0.
Thanks!
Vivek.

Answer 1

quote:
Please help me understand why. I have the easeToLoc setup to
received input variables:
The syntax of ActionScript dictates that you refer to the
callback function in the way that I pointed out. The only argument
that is passed to that listener function is an event object. This
is what it expects, nothing more. Take a look at the
docs
for more info, specifically the categories under Programming
ActionScript 3.0 -> Handling Events.
Looking at navPanelClose() and navPanelOpen(), the values
you're trying to pass seem more like constants to me, not
variables. So why not declare them as constants within this class
and refer to them as such within easeToLoc()? If you truly want to
use variables, perhaps creating a separate utility class to handle
this logic will work better.
When trying to access a method within one class from another
...let's say you want to access myMethod() within class MyAClass
from class MyBClass. You could:
1. Declare myMethod() as static and then refer to it from
anywhere after importing MyAClass. So you can call
MyAClass.myMethod() without having to instantiate MyAClass. This is
what you're trying to do here, I think.
2. Have class MyBClass extend MyAClass where myMethod() is
public or protected and MyBClass is in the same package as MyAClass
when it's declared as protected. For this to work you'd have to
instantiate MyBClass.
TS