Hello all, I did what C�dric told me and it finally works!
So I guess even if you only have a local EJB, you still need to set the "remoteInterfaceName" parameter in the WSDD file. Anyway, thanks for your help C�dric. Vinu. --- C�dric_Chabanois <[EMAIL PROTECTED]> wrote: > EJBProvider does probably not work with local ejbs. > > However, getEJBMetaData() is called only if it does > not find > "remoteInterfaceName" in the wsdd. > Try to set remoteInterfaceName (!) to your local > interface name in wsdd. > > Please tell us if it worked. > > I think that local EJB support is very important. > In fact, they are faster but more importantly they > can take parameters that > are not serializable. > Out parameters are not serializable (StringHolder > ...) and they should not > be used with remote EJB. > > > C�dric > > > Hello all, > > > > I have deployed a local EJB (it doesn't have a > remote > > interface) to JBoss 3.0.4 and I am trying to > expose > > its public methods as web services by using the > > java:ejb provider. However, when I try to access > its > > ?WSDL file, it is returning an AxisFault: > > > > Fault - org.apache.axis.ConfigurationException: > > java.lang.NoSuchMethodException: > > DepositLocalHome.getEJBMetaData() > > > > The "getEJBMetaData()" method only applies to > REMOTE > > EJBs. So I don't know why it is trying to call it > on > > this local EJB. Is there an option in the WSDD > file to > > tell Axis that it is indeed an LOCAL EJB and not a > > remote one? > > > > Here is my Deploy.wsdd file: > > > > <?xml version="1.0" encoding="UTF-8"?> > > <deployment > xmlns="http://xml.apache.org/axis/wsdd/"; > > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java";> > > <service name="DepositService" > provider="java:EJB"> > > <parameter name="beanJndiName" > > value="local/Deposit"/> > > <parameter name="homeInterfaceName" > > value="DepositLocalHome"/> > > <parameter name="allowedMethods" value="*"/> > > <parameter name="jndiURL" > > value="jnp://localhost:1099"/> > > <parameter name="jndiContextClass" > > value="org.jnp.interfaces.NamingContextFactory"/> > > </service> > > </deployment> > > > > --- > > If only Axis had better documentation, then it > would > > be so much easier. Unfortunately, this is not the > > case. Can anyone please help me with this problem? > > > > Thanks in advance, > > Vinu. > > > > > > __________________________________________________ > > Do you Yahoo!? > > U2 on LAUNCH - Exclusive greatest hits videos > > http://launch.yahoo.com/u2 > > __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos http://launch.yahoo.com/u2
