I am playing with j2ee 1.4 webservice on JBoss 4.0 and I've noticed that  
ServiceDescription only configures WSDl<->Java mapping for types directly referenced 
as operation input/output parameters. I wonder what is the reason behind this 
implementation? Should JBoss map all complex types mentioned in the WSDL or in the 
jaxrpc mapping file? This would eliminate need to use  ws4ee-deployment.xml for many 
wsdl/mapping files generated by wscompile from jwsdp.

I think I'll be able to provide a patch if there are no compelling reasons to keep the 
current behaviour.

Regards,
Igor

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3848986#3848986

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3848986


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to