Yes, the service shows on the axis welcome page. I have verified that before
deployment i have just the AdminService and Version services, and after
deployment i see my service WSInvestigation. When i navigate to the URL
/services/WSInvestigation it says that there is a service there. But when i
try to invoke one of the methods with
services/WSInvestigation?method=listUsers i get an exception about no
response message. It says that for any method i try to call, whether it
exists in the bean or not.
When i deploy, the server-config.wsdd is located in
$JBOSS_DIR/server/default/deploy/$EAR_FILE/$WAR_FILE/WEB-INF. I am deploying
an ear so these files are in the exploded directory in default/tmp/deploy.
I tried using both remote and local but neither of them showed any methods.
The ear layout is :
EAR_FILE
META-INF
application.xml
wsinvEJB.jar
WAR_FILE
META-INF
WEB-INF
classes (currently empty)
lib
<axis jars>
wsinvEJB_client.jar
web.xml
The web.xml contains the parts needed to expose the AxisServlet and
AdminServlet servlets.
I will try generating the wsdl and adding that to my deploy.wsdd and seeing
if it can call the method then. I thought there would be some magic on the
inside that looked up the interface from the EJB provides, and then generated
the wsdl based on that interface. Looking at the source code (but not too in
depth) it does look like the ability is there because the EJBProvides extends
the RPCProvider which extends the JavaProvider which has the generateWSDL
method. I haven't had much luck turning on debug statements in the axis
servlet so i can't see where the code is going. And i haven't tried stepping
through with a debugger yet.
edward
On Tue, 7 Sep 2004 18:33:32 +0600
Mahen Perera <[EMAIL PROTECTED]> wrote:
> Hi edward,
>
> Is the service shown in the Deployed Services section in the Welcome page?
>
> i havene tried the scenario ur saying ,,, (that is to view the WSDL)
>
> As far as I know Axis has a Java2WSDL, but not a EJB2WSDL I guess,,
> there fore not sure whether it will work
>
> Another point : - did u try using *remote* instead of *local*
> interfaces as parameter names.
>
> Where is ur server-config.wsdd file located?
>
> Mahen
>
>
> On Tue, 7 Sep 2004 07:35:52 -0400, edward winston <[EMAIL PROTECTED]> wrote:
> > I am using the first method, trying to get the Axis servlet to talk
> > directly to the EJB provider.
> >
> > edward
> >
> > On Tue, 7 Sep 2004 09:30:21 +0600
> >
> >
> > Mahen Perera <[EMAIL PROTECTED]> wrote:
> >
> > > Hi edward,
> > >
> > > Need some more info as to how u have set up the ear.
> > >
> > > Are u using the EJB provider to call ur Session Bean directly. In
> > > other words , does the flow goes like the following
> > >
> > >
> > > Client --> Axis servlet --> EJB Provider --> ur Session Bean
> > >
> > > OR
> > >
> > > r u using the Java provider as in
> > >
> > > Client --> Axis Servlet --> Java Provider --> Ur Java Class which
> > > wraps the Session Bean --> Session Bean
> > >
> > >
> > > Mahen
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Mon, 6 Sep 2004 13:03:13 -0400, edward winston <[EMAIL PROTECTED]>
> > > wrote:
> > > > I am having problems deploying a web service that will front a
> > > > stateless session bean. I have the session bean created and have
> > > > tested that it works and am deploying that in the ear.
> > > >
> > > > Then i added a web component to the ear, included the axis jar in the
> > > > WEB-INF/lib directory and redeployed the ear. The beans are loaded
> > > > just fine and my test client still works, and i can get to axis via
> > > > the web.
> > > >
> > > > Axis is working because i see the default services of AdminService
> > > > and Version and i can get the wsdl for both of those services. When
> > > > i deploy the service that fronts the session bean, the service shows
> > > > up, but there are no methods exposed. If i try to get the wsdl it
> > > > says that it could not generate the wsdl. It confirms that there is
> > > > a service but maybe it is mis configured.
> > > >
> > > > Here is my deploy.wsdd file :
> > > >
> > > > <deployment xmlns="http://xml.apache.org/axis/wsdd/";
> > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > > > xsi:schemaLocation="http://xml.apache.org/axis/wsdd/
> > > > ../../../../../schema/axis-wsdd.xsd ">
> > > > <service name="WSInvestigation" provider="java:EJB">
> > > > <parameter name="beanJndiName" value="local/AccessCounterSB" />
> > > > <parameter name="localHomeInterfaceName" value="AccessCounterSBLHif"
> > > > /><parameter name="localInterfaceName" value="AccessCounterSBLif" />
> > > > <parameter name="jndiURL" value="jnp://saturn:1099" />
> > > > <parameter name="jndiContextClass"
> > > > value="org.jnp.interfaces.NamingContextFactory"/>
> > > > <parameter name="allowedMethods" value="listUsers" />
> > > > </service>
> > > > </deployment>
> > > >
> > > > I have tried using '*' as the value of 'allowedMethods' but that
> > > > didn't work either.
> > > >
> > > > Any clues as to what I am doing wrong here?
> > > >
> > > > edward
> > > >
> >
