Forum: Ruby on Rails User engine apparently breaks wsdl in some cases

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
D4e51fd9554030ab55c379fdc1a34826?d=identicon&s=25 Keith Lancaster (klancaster)
on 2006-03-19 01:26
(X-posting to the engine group as well)

Wsdl calls fail under certain circumstances when the user engine is in
use. After much experimentation, this is what I found.

* I have an application that uses the login and user engines for
permissions and security. The configuration works correctly.
* I created a web service for the application. If I use direct dispatch
(the default), I can both invoke the service and call service.wsdl and
get the expected results.
* If I modify the web service to use layered or delegated dispatching, I
can still invoke the service, but the service.wsdl call fails with
"method not found"
* If I then comment out the line "include UserEngine" in the
application.rb, the wsdl call works again.

It *seems* to me that something in the user engine is overriding the
wsdl call or masking it in some way. I am going to continue to
investigate this, but any help would be greatly appreciated.

Keith
This topic is locked and can not be replied to.