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.