When I said the WSDL is "generated", I meant that the WSDL binding / service informations are generated and added to the WSDL PortType retrieved from the target endpoint. The component just looks for the target WSDL, extract the needed information (PortType, Messages, schemas, etc...), add the binding / service informations and expose it as the WSDL for the endpoint.
If you specify the wsdl on the http endpoint, it will use this one instead of loading the wsdl from the target endpoint. On 4/18/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
On 4/18/07, Owen Thomas <[EMAIL PROTECTED]> wrote: > > Hi Bruce. Thanks for getting back to me. > > > > I believe you still need to define the wsdlResource attribute as > > noted in the servicemix-http documentation to point to the WSDL > > file. Then you can visit the URL defined in the locationURI > > attribute like so: > > > http://0.0.0.0:8192/example/?wsdl > > > This will forward the request to > > http://0.0.0.0:8192/example/main.wsdl and should display the WSDL > > for the service. > > Hmmm... I still have to put in a WSDL even though I've elected an xbean > deployment? It says that wsdlResource is optional... Am I incorrect in > assuming that one is generated when the SU is deployed? It is generated when possible. Additionally, since my earlier message, I believe I have gotten the > server to produce something - always good to know I'm being heard. I > type 'http://sydserv05:8192' (I don't think that's telling too much), I > get a 404 - Not Found error, but am suggested another service via the > link: > > http://sydserv05:8192/example/ > > I follow this and get another 404 error. The page says that it was > unable to find the requested resource: 'requestURI=/example/main.wsdl'. Yeah, this means the generation has failed. You should be able to have more informations if you increase the log level to DEBUG. The most common cause is that the target endpoint does not have any wsdl description or is not activated yet. Owen. > -- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
