cancel
Showing results for 
Search instead for 
Did you mean: 

Generating Java Proxies - Corrupt EJBs

Former Member
0 Kudos

Hi,

I have generated both a client and server Java proxies, and have imported the the following external libraries: aii_msg_runtime.jar,

aii_proxy_xirt.jar,

aii_utilxi_misc.jar &

guidgenerator.jar.

I have created a EJB Project myEJB with a Bean implementation <myInterface>_PortTypeImpl extending com.sap.aii.proxy.xiruntime.core.AbstractProxy and implementing the interface <myInterface>_PortType.

If I try to select in the J2EE explorer view one of the following generated beans I get error 'Corrupt ejb':

AbstractProxyBean,

AbstractProxyBean2,

AbstractProxyInboundBean,

AbstractProxyInboundBean2,

AbstractProxyInboundBean4,

<myInterface>_PortTypeBean.

So, I create a EJB Assembly Project myEJBAssembly and assisgn the myEJB to the assembly, I remove the references to the following

AbstractProxyBean,

AbstractProxyBean2,

AbstractProxyInboundBean,

AbstractProxyInboundBean2,

AbstractProxyInboundBean4,

in the ejb-jar.xml descriptor file. leaving <myInterfcace>_PortTypeBean which leaves me only the <myInterface>_PortTypeBean in my assembly.

I do not change any code in the bean and try to build JAR files from the context menu (root node on Assembly ) and I get an error: 'EnterpriseJavaBean <myInterface>_PortTypeBean is corrupt.

I need to be able to generate the Jar files prior to building my .ear file to deploy.

Please help.

Also,

Should I be able to see the bean infomation such as the Overview where I can naviate to the bean class, home interface too, as I cannot see this at all when I select one of the generated beans.

Thanks in advance.

Mark

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Try closing the ejb project and opening it again. (Righ-click on the project, in the context menu choose 'Close Project' and then choose 'Open Project' the same way) On a few occasions, I found this to work too.

Regards,

Suresh.

Former Member
0 Kudos

Thanks. This is not the problem, although my version of NWDS does require the open/close to eliminate a certain error.

For future information, I have solved the problem as its a problem with the O/S which NWDS is installed on. I am currently running on Windows 2000 when I encounter the issue with the Corrupt EJB, but trying the same version of NWDS on XP works fine.

Thanks for your help.

Mark

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Mark

Check the following thread,

cheers

Sameer