On Jan 22, 2007, at 6:46 AM, Aman Nanner/MxI Technologies wrote:
This GBean apparently takes a magic attribute "kernel" of type
"String"
(according to the source code definition, although the
documentation I've
seen says it should be of type Kernel).
Its the actual kernel instance that geronimo is running in. Where is
the documentation that says its a String?
I can't find any examples on how a
GBean that takes magic attributes is declared within an application
module,
and I keep getting a constructor initialization error. Is the magic
attribute supposed to be specified at all in the XML GBean
declaration?
You don't specify anything about the magic attributes in xml, they
are added (by magic :-) for you by the gbean infrastructure when the
gbean instance is created. Another magic attribute that is often
useful is the classLoader of the module the gbean is deployed in.
What is the error you are getting?
thanks
david jencks
David Jencks
<[EMAIL PROTECTED]
oo.com> To
[email protected]
01-18-2007
08:24 cc
PM
Subject
Re: Accessing EJB via JNDI
from a
Please respond to web application
[EMAIL PROTECTED]
che.org
On Jan 18, 2007, at 3:02 PM, Aman Nanner/MxI Technologies wrote:
Hi,
I'm running into an issue using the Geronimo 1.2 beta release.
I'm running a web application from which an EJB is being looked up
via its
JNDI name as declared in the openejb-jar.xml descriptor that
resides in the
EJB module. In my web.xml for the web application, I have the EJB
declared
as a reference.
The problem is that I get a NameNotFoundException by looking up the
EJB via
the JNDI name. However, if I look up the EJB via it's EJB
reference, as
defined in the ejb-jar.xml, then the lookup succeeds. I know that
I should
be using the EJB reference to look up the EJB anways, but I've got
a legacy
app that I'm trying to port to Geronimo that is littered with EJB
lookups
using direct JNDI names.
Before I dive into the Geronimo source code, perhaps somebody knows
for
sure that EJB JNDI lookups are supposed to fail from within a server
context (i.e. it will fail by design) and let me know?
You have to do a bit of work to enable this -- we didn't end up
including all the pieces in geronimo.
If you check out https://svn.apache.org/repos/asf/geronimo/sandbox/
plugins/global-jndi you'll find a class EjbBindings. I don't think
this made it into geronimo itself. If you build this little project
and deploy an instance of this ejbBindings gbean in your ejb app it
should result in each ejb getting bound in the global java:context
under the names you specified in the openejb-jar plan.
I think the gbean config would look something like
<gbean name="EjbBindings"
class="org.apache.geronimo.gjndi.binding.EJBBindings">
<attribute name="homeContext">remote</attribute>
<attribute name="localHomeContext">local</attribute>
</gbean>
Then a typical remote home would be bound at java:remote/foo.
Hope this helps and sorry for not making it easier.
thanks
david jencks
Thanks,
Aman
_____________________________________________________________________
_
____________
* This message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that
is privileged, confidential and exempt from disclosure under
applicable law. Unless you are the addressee (or authorized to
receive for the addressee), you may not use, copy or disclose the
message or any information contained in the message. If you have
received this message in error, please advise the sender by reply e-
mail , and delete the message, or call (collect) 001 613 747 4698. *
______________________________________________________________________
____________
* This message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that
is privileged, confidential and exempt from disclosure under
applicable law. Unless you are the addressee (or authorized to
receive for the addressee), you may not use, copy or disclose the
message or any information contained in the message. If you have
received this message in error, please advise the sender by reply e-
mail , and delete the message, or call (collect) 001 613 747 4698. *
