[nvembar]

I’m having trouble with an EJB deployment to the Sun Application Server.

My setup is as follows: we have one source tree where the code resides, and a number of projects linked to that tree with Exclude filters set appropriately for each project.

Because of that single source tree, we had to do a little work get XDoclet to write out the ejb-jar.xml and sun-ejb-jar.xml to the correct locations, but we have that working. We get deployable jar files through the IDE. I’m using J2EE 1.4, by the way.

However, the issue is when we try to use the resulting EJBs — the PortableRemoteObject.narrow() method returns null. I’m using the CNCtxFactory for my initial context, if that’s of any interest. I’ve done some research and tracked down the issue to a lack of RMI stubs in the EJB jar file.

So, my question is, how do I get the RMI stubs to get created via MyEclipse? Is there an XDoclet setting I’m missing or a setting somewhere in the interface?

Thanks in advance and I can certainly provide more detail if that will help,
Navin

[Riyad Kalla]

Navin,
Good question, each application server generates different stubs. Typically when you “deploy” or “install” a enterprise app or EJB into a J2EE server using the administrative console, part of that deployment step is the actual generation of the stubs. I believe you may be skipping that step that is necessary.

For example, when you deploy an EAR to WebSphere, you deploy the EAR file itself from within MyEclipse to the server. Then you need to flip over to the administrative console for WebSphere and install the application. From there it is exploded and all the stubs generated. I imagine the same holds true for Sun App server.

[Author]

Posts