Hi Danny, hi William,
you can't use circular dependencies in a xsd schema with
document/literal style webservices. See
http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/
XFire is all about document/literal there are no efforts to support
legacy (from our perspective) RPC style services.
It's sad to say this, but if you have to use a service which is not
following the ws-i (www.ws-i.org) rules, you have to use Axis.
If you are about creating a webservice (William's case) you probably
need to create a webservice object model. Which is a good idea anyway,
because it decouples your exposed interface from your application. Once
you have a couple of users, every change in your application will be
really hard if you can't continue supporting the past versions of your
service, so you will be happy about the decision to create a different
model for the interfae in the future.
A framework we use to map between our appliaction model and our
interface model is dozer (dozer.sourceforge.net)
Cheers, Mika
Danny Trieu schrieb:
Dan,
Generating the client proxies code giving the wsdl that has import to
wsdl and xsd that have circular dependency. Is there anyway to get
around this when you have no control of the targeted webservice.
Thanks Dan,
--danny
--
cyber:con gmbh
Mika Göckel
Rathausallee 10
53757 Sankt Augustin
tel (+49)2241 / 9350 0
fax (+49)2241 / 9350 99
mob (+49) 172 / 279 2771
skype mika.goeckel
email [EMAIL PROTECTED]
