[ http://jira.codehaus.org/browse/XFIRE-634?page=comments#action_80867 ] Jakub Mendys commented on XFIRE-634: ------------------------------------
1.2.2 release has not fixed this problem > WSDL contains multiple copies of schema declaration when using xmlbean > binding > ------------------------------------------------------------------------------- > > Key: XFIRE-634 > URL: http://jira.codehaus.org/browse/XFIRE-634 > Project: XFire > Issue Type: Bug > Affects Versions: 1.0, 1.1.2 > Environment: xmlbean 2.2 java 1.4 > Reporter: Jakub Mendys > Assigned To: Dan Diephouse > Fix For: 1.2.2 > > Attachments: test.zip > > > I started my development with XML schema. Using XMLBeans I have generated > java representations of schema elements. > At the end I have incorporated this into xFire WebService using xmlbean > bindings. > After I have deployed the application I've tried to examin WSDL. The first > request results in valid XML document but all subsequest request result in > WSDL being bigger and bigger. After investigation I've found that new copy of > schema is added on each WSDL request. > This does not stop webservice from working. > The proplem does not apply when default (AEGIS) bidning are used. > See test case: > =========================== > Under link http://jmendys.com/test.zip you will find a test case to reproduce > this problem. > The zip contains folder 'test' which is an exploded war ready to deploy. After > deployment is exposes 2 services: > * XFireTestService1 (without xmlbean bidings) > * XFireTestService2 (with xmlbean bindings) > When you request for WSDL for the second service you will notice that on each > request the response is bigger and bigger. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
