[ http://issues.apache.org/jira/browse/AXIS2-647?page=comments#action_12377589 ]
Ajith Harshana Ranabahu commented on AXIS2-647: ----------------------------------------------- Hi Thilo, I did deploy the service and ran the generated client against the it. But seems to be working for me! What I've attached is the working service archive and the client source. These are made with no change to generated code what so ever except for the implementation of the skeleton > "Unbound namespace URI" when generating code for ADB and using chained schema > imports > ------------------------------------------------------------------------------------- > > Key: AXIS2-647 > URL: http://issues.apache.org/jira/browse/AXIS2-647 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Environment: Axis2 1.0 RC4 > Reporter: Thilo Frotscher > Attachments: Restaurant.xsd, RestaurantMessages.xsd, RestaurantService.aar, > RestaurantService.wsdl, restaurant-client-src.zip, restaurant-src.zip > > My scenario is as follows: > - I defined the datatypes for my sample application in file Restaurant.xsd > and namespace R1 > - I defined the messages for communication with the RestaurantService in file > RestaurantMessages.xsd and namespace R2 > - RestaurantMessages.xsd imports Restaurant.xsd, since the messages make use > of the basic datatypes. > - My WSDL imports RestaurantMessages.xsd > - WS-I test tools show that this WSDL complies to BP > - This scenario worked nicely with Axis 1.3 > I generated service and client code for this WSDL with WSDL2Java and ADB > option. When I send a message to the service using the generated proxy, I get > an "Unbound namespace URI" error for namespace R1( ! ) on the server side. > That is interesting, because the messages that are sent back and forth are > all in namespace R2 and my request message does not contain any reference to > R1 whatsoever. However, the response message (R2) is supposed to contain > types defined in Restaurant.xsd. > > If I move all the datatype definitions from file Restaurant.xsd into > RestaurantMessages.xsd and thus from R1 to R2, everything works fine. > Apparently Axis2 / ADB has issues with chained imports, perhaps only if not > all of the imports belong to the same namespace. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
