Is there any way to FORCE xfire to add a type to the generated WSDL using 
XmlBeans?  Occationally, I'll have a simple type that is used through 
inheritance that might be included from a separate Schema and it won't show up. 
 Its maddening.  I found in the forum a reference to the overrideTypesList 
property.. Here is a snippet from my services.xml file:

<bean name="addressCleanerWS"
                class="org.codehaus.xfire.spring.ServiceBean">
                <property name="namespace"
                        value="http://ns.choicepoint.net/address"; />
                <property name="serviceBean" ref="addressCleaner" />
                <property name="serviceFactory" 
ref="xmlbeansServiceFactory"></property>
                <property name="serviceClass"
                        value="com.choicepoint.address.ws.IAddressCleanerWS" />
                <property name="properties">
                        <map>
                                <entry key="writeXsiType"><value 
type="java.lang.Boolean">true</value></entry>
                                <!--entry key="writeXsiType" value="true"/-->
                                <entry key="overrideTypesList">
                                        <list>
                                                
<value>com.choicepoint.service.Request</value>
                                        </list>
                                </entry>
                        </map>
                </property>
        </bean>


com.choicepoint.service.Request is the base class that isn't showing up.  Can 
anyone give me any assistance?  I would greatly appreciate it.

Paul

-----------------------------------------
The information contained in this e-mail message is intended only
for the personal and confidential use of the recipient(s) named
above. This message may be an attorney-client communication and/or
work product and as such is privileged and confidential. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and
that any review, dissemination, distribution, or copying of this
message is strictly prohibited. If you have received this
communication in error, please notify us immediately by e-mail, and
delete the original message.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to