On Feb 13, 2008 3:38 PM, nate roe <[EMAIL PROTECTED]> wrote:
>
>
> I see.
>
> This WSDL was generated automatically by ServiceMix, somehow. I noticed
> with the "WSDL first" example that the WSDL didn't necessarily need to be
> included in the service assembly; that ServiceMix somehow generates a WSDL
> for it. I assume this is because the web service's SU's xbean.xml uses the
> jsr181:endpoint tag to specify a POJO class. I then created this "hello
> world" project based on what I learned from that sample, hoping to use
> POJOs to create Web Services.
>
> So when I deploy my SA, ServiceMix generates the WSDL below and writes it to
> stdout.
OK, well you're going to need to configure the pom.xml in the JSR181
SU to use the xfire-maven-plugin to generate the WSDL from the Java
class. Then you'll get a complete WSDL that can be used. If you've
looked at the wsdl-first example, then you should have already seen
the person.wsdl file the JSR181 SU. This was generated by the
xfire-maven-plugin. Take a look at the pom.xml for the JSR181 SU
project to see an example of how to use the xfire-maven-plugin to
generate WSDL. Your configuration will be slightly different, however,
because you're generating WSDL from a Java class; this is a paradigm
called code-first instead of WSDL-first.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
