That will generate static WSDL, correct? I had hoped that ServiceMix would
automatically create this WSDL dynamically on deployment. Is that possible?
A couple of days ago I did successfully invert the wsdl-first example (to
create a code-first variant.) To do this, I copied all of the Java files
from the wsdl-first example (mostly generated by Maven, except for
Person.java.) I made a new project with these files. I then used Ant, with
Axis' java2wsdl task to generate a WSDL. Then I zipped up my SU and my SA
(along with unmodified wsdl-first-http-su-3.2.1.zip) using the unmodified
xbean.xml and jbi.xml. This SA deployed and performed exactly as the
wsdl-first demo had. I then deleted the WSDL generation step from my Ant
script so that it instead just compiles and zips. This new, WSDL-less SA
also deployed and performed exactly as the wsdl-first demo had. This is why
I wanted to try to create a POJO-based service without any pre-built WSDL.
It appears that ServiceMix can in at least some circumstance deal without
it.
bsnyder wrote:
>
> 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/
>
>
--
View this message in context:
http://www.nabble.com/Where%27s-my-WSDL--tp15460599s12049p15470475.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
