After some more digging, I found out the bug in which you removed the
xsd:any from the default WSDL generation and since it was in 1.1
final, I decided it was probably safe for me to update my code to
that. Seems to be working. :) And again, thanks for being so active
and helpful on the list Dan!
Mark
On Dec 17, 2006, at 12:46 AM, Mark Slater wrote:
Hi Dan,
I hate to nitpick, because your messages here have been far more
helpful than I've come to expect from open source mailing lists,
but you didn't actually answer the question. :)
Its great for me to know that the current version of XFire won't do
that, but I'm not currently in a position to upgrade, and in my
case, the xsd:any is causing the built-in Ruby client to give me
the following message "error occurred: nil not allowed: any". I'm
using the 1.1-beta-1 (yeah, I know its pretty old), and I'll be
able to upgrade to the latest version in a few weeks or so, but
until then, I need to shut that thing off.
So how do we turn it off? Or if anyone knows how to get around that
error in Ruby, I'd be happy with that too!
Thanks,
Mark
On Dec 5, 2006, at 8:02 PM, Dan Diephouse wrote:
I *thought* xsd:any generation was off by default now. You aren't
using an old version of xfire are you?
- Dan
On 12/5/06, Adli < [EMAIL PROTECTED]> wrote:
Hi,
Part of my generated wsdl is:
<xsd:complexType name="EventKey">
<xsd:sequence>
<xsd:element minOccurs="0" name="Entity" type="xsd:string"/>
<xsd:element minOccurs="0" name="EntityId" type="xsd:string"/>
<xsd:element minOccurs="0" name="EventId" type="xsd:string"/>
<xsd:any maxOccurs="unbounded" minOccurs="0"/>
</xsd:sequence>
<xsd:anyAttribute/>
</xsd:complexType>
is from class EventKey using Java5 annotations:
@XmlType(name="EventKey")
class EventKey{
@XmlElement(name="Entity")
public String getEntity();
@XmlElement(name="EntityId")
public String getEntityId();
@XmlElement(name="EventId")
public String getEventId();
.......
}
How can I not generate the extra xsd:any from my complexType?
Thanks,
Adli
--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog
