The problem you are having is that you are not running WSM at all, you
are just running Axis.
First problem is that you have jwsClasses but the classes that that are
compiled in the jwsClasses are never used.
FYI...You don't need to compile the Web Service files in a separate
directory. Your build target should look like:
<!-- ========================================= -->
<!-- build - build all binaries -->
<!-- ========================================= -->
<target name="build" depends="dirs">
<deploy-wsm webappDir="${webapp.dir}"/>
<javac srcdir="${src.dir}" destdir="${classes.dir}"
classpathref="build.classpath"/>
<build-webservices srcdir="${ws-src.dir}"
destdir="${classes.dir}"
tempdir="${gen.dir}"
classpathref="build.classpath"/>
<jar jarfile="${webservice.jar}">
<fileset dir="${classes.dir}" />
</jar>
</target>
And not:
<target name="build" depends="dirs">
<deploy-wsm webappDir="${webapp.dir}"/>
<javac srcdir="${src.dir}" destdir="${classes.dir}"
classpathref="build.classpath"/>
<build-webservices srcdir="${ws-src.dir}"
destdir="${jwsclasses.dir}" ERROR!
tempdir="${gen.dir}"
classpathref="build.classpath"/>
<jar jarfile="${webservice.jar}">
<fileset dir="${classes.dir}" />
</jar>
</target>
In your case, the Jar file that you build doesn't include the classes in
the jwsClasses directory. FYI...We do require the source to be in its
own directory, but the classes should all be in the same directory.
The next thing to notice is that the WSDL that is generated for your
service is RPC encoded even though it should be document. The problem
is this:
You have zero length .jws files (e.g. AxisLMSServerStub.jws) in your
application's base directory. Furhter more your don't have the
server-config.wsdd so all you see is standard Axis and no WSM.
What happens is this:
When the URL comes to Axis, Axis notices that there is .jws (the zero
length files in the base dir) file and does the "drop in deployment"
where a .jws is assumed to be the source code for the web service.
During this process your real .jws gets compiled by Axis (since it has
no package) this becomes your web service. So the WSDL you see is
actually coming from the drop in deployment handler, which is why it is
RPC encoded.
Question: I don't know why you are not using server-config.wsdd? Why is
this file not part of your project. You should be using the one that
comes in the wsm-blank sample. Without this file we would never run.
Question: Why do you have the zero length .jws files?
To fix the problem you would need to get the server-config.wsdd, fix the
build.xml and remove the zero length .jws files.
Hope this helps
daryoush
> -----Original Message-----
> From: James Black (JIRA) [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 22, 2005 2:00 PM
> To: beehive-dev@incubator.apache.org
> Subject: [jira] Commented: (BEEHIVE-849) A method that doesn't have a
> @WebMethod annotation appears in my webservice
>
> [ http://issues.apache.org/jira/browse/BEEHIVE-
> 849?page=comments#action_12316517 ]
>
> James Black commented on BEEHIVE-849:
> -------------------------------------
>
> Sorry, this file won't build the clients, but the file in JIRA-848
will,
> and it demonstrates this problem.
>
> > A method that doesn't have a @WebMethod annotation appears in my
> webservice
> >
------------------------------------------------------------------------
> ---
> >
> > Key: BEEHIVE-849
> > URL: http://issues.apache.org/jira/browse/BEEHIVE-849
> > Project: Beehive
> > Type: Bug
> > Components: Web Services (181)
> > Environment: Solaris 8, JDK1.5, Tomcat 5.5.9, June nightly build of
> beehive
> > Reporter: James Black
> > Assignee: daryoush mehrtash
> > Attachments: JAMES_BLACK_PROBLEM2.jar, jamesblack2.wsdl,
> jamesblackproblem.jar, jamesblackproblem.jar, ws_test.tar.gz
> >
> > My .jws file extends a class that has checkEmail, checkNetid,
> checkNumber as methods. These methods appear in the wsdl file, even
> though they don't have an annotation of '@WebMethod'.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the
administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
> http://www.atlassian.com/software/jira
>
