User engine apparently breaking wsdl generation


#1

(X-posting to the rails 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


#2

Keith L. wrote:

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

The problem is fixed if :wsdl is removed from the following line in
authorized_system.rb.

hide_action :action_method_names, :wsdl, :deepcopy

Not sure why this causes a problem only in the dispatch or layered case.

Keith