Nick,

Looking over the Axis-codebase, I have come to the conclusion that this is a
"feature" of the Java2WSDL package and the
Axis EJBProvider which we have subclassed. The EJBProvider gives the EJB
interface class to the emmitter which then
does the getDeclaredMethods() reflection call instead of getMethods().

This is indeed not nice and makes me think of handing the emitter our own
meta-model (org.apache.axis.description) 
for EJBeans ...

CGJ 

-----Urspr�ngliche Nachricht-----
Von: Nicholas Wilcox [mailto:[EMAIL PROTECTED]] 
Gesendet: Mittwoch, 9. Oktober 2002 07:23
An: [EMAIL PROTECTED]
Betreff: [JBoss-user] Problem in Jboss.net with WSDL


I have a stateless session bean whose remote interface extends another
interface.

    
public interface UserManagerRemote extends IUserManager, EJBObject
    {
        // All 
business methods defined in IUserManager
    }

When I expose this EJB as a webservice 
through jboss.net none of the methods show up in the dynamically generated
WSDL file 
(http://localhost:8080/axis/services/LdapUserManager?wsdl).

If I add the 
methods in UserManagerRemote than they do appear in the WSDL.

Is this a bug or do I need to 
do something different?

Please cc me when replying because I'm not on the list.

-- 

Nick Wilcox.





-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf _______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
###########################################

This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to