Issue Details (XML | Word | Printable)

Key: XFIRE-634
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Dan Diephouse
Reporter: Jakub Mendys
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
XFire

WSDL contains multiple copies of schema declaration when using xmlbean binding

Created: 08/Sep/06 02:51 AM   Updated: 23/Nov/06 02:22 AM   Resolved: 01/Oct/06 10:57 PM
Component/s: None
Affects Version/s: 1.0, 1.1.2
Fix Version/s: 1.2.2

Time Tracking:
Not Specified

File Attachments: 1. Zip Archive test.zip (6 kB)

Environment: xmlbean 2.2 java 1.4

Testcase included: yes


 Description  « Hide

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.



Dan Diephouse added a comment - 11/Sep/06 05:00 PM

Scheduling for 1.2.2


Jakub Mendys added a comment - 19/Sep/06 07:40 AM

test case (maven build)


Jakub Mendys added a comment - 19/Sep/06 07:41 AM

original test case has been replaced by maven project attached


Dan Diephouse added a comment - 19/Sep/06 10:41 AM

OK, thanks for the test case. Will try to check this out later today.



Jakub Mendys added a comment - 23/Nov/06 02:22 AM

1.2.2 release has not fixed this problem