# User engine apparently breaking wsdl generation

**URL:** <https://www.ruby-forum.com/t/user-engine-apparently-breaking-wsdl-generation/83762>\
**Category:** Engines\
**Created:** [March 19, 2006, 1:27am UTC](https://www.ruby-forum.com/t/user-engine-apparently-breaking-wsdl-generation/83762 "2006-03-19T01:27:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [March 19, 2006, 1:27am UTC](https://www.ruby-forum.com/t/user-engine-apparently-breaking-wsdl-generation/83762/1 "2006-03-19T01:27:54Z")

</div>

(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

---

<div class="post-metadata">

**Author:** ![klancaster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/f1d935/32.png) [@klancaster](https://www.ruby-forum.com/u/klancaster)\
**Post date:** [March 20, 2006, 2:26am UTC](https://www.ruby-forum.com/t/user-engine-apparently-breaking-wsdl-generation/83762/2 "2006-03-20T02:26:27Z")

</div>

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