[
http://jira.codehaus.org/browse/XFIRE-774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89892
]
Stephane Dupertuys commented on XFIRE-774:
------------------------------------------
I agree with Jakub, this bug is still present on 1.2.4. It appears when
- a non xmlbean bean object like DataHandler is include as parameter of method
- XmlbeanWSDLBuilder and XmlbeanTypeRegistry are used :
xfire spring configuration:
{code:xml}
<!-- ============================================ -->
<!-- FACTORIES -->
<!-- ============================================ -->
<bean id="xmlBeansAnnotationServiceFactory"
class="org.codehaus.xfire.annotations.AnnotationServiceFactory"
singleton="true">
<constructor-arg index="0" ref="webAnnotations" /><!--
WebAnnotations -->
<constructor-arg index="1" ref="xfire.transportManager" /><!--
TransportManager -->
<constructor-arg index="2" ref="xmlbeans.aegisBindingProvider"
/><!-- BindingProvider -->
<property name="wsdlBuilderFactory"
ref="xfire.xmlbeansWSDLBuilderFactory"/>
</bean>
<!-- ============================================ -->
<!-- WSDL BUILDER -->
<!-- ============================================ -->
<bean id="xfire.xmlbeansWSDLBuilderFactory"
class="org.codehaus.xfire.xmlbeans.XmlBeansWSDLBuilderFactory">
</bean>
<!-- ============================================ -->
<!-- REGISTRIES + PROVIDERS -->
<!-- ============================================ -->
<bean id="xmlbeansTypeRegistry"
class="org.codehaus.xfire.xmlbeans.XmlBeansTypeRegistry" />
<bean id="xmlbeans.aegisBindingProvider"
class="org.codehaus.xfire.aegis.AegisBindingProvider">
<constructor-arg index="0" ref="xmlbeansTypeRegistry" />
</bean>
<!-- ============================================ -->
<!-- ANNOTATION FACADES -->
<!-- ============================================ -->
<bean id="webAnnotations"
class="org.codehaus.xfire.annotations.jsr181.Jsr181WebAnnotations" />
{code}
webservice:
{code:java}
@WebService
public interface RepositoryWebService {
/**
*
* @param context
* @param subject
* @param teleprocedure
* @param document
* @return
*/
@WebMethod
public RepositoryWSResultDocument addDocument(
@WebParam(header=true)ContextDocument context,
@WebParam(header=true)ServiceVersionDocument version,
SubjectDocument subject,
TeleprocedureDocument teleprocedure,
@WebParam(name="data")DataHandler document);
}
{code}
> WSDL contains multiple copies of schema declaration when using xmlbean binding
> ------------------------------------------------------------------------------
>
> Key: XFIRE-774
> URL: http://jira.codehaus.org/browse/XFIRE-774
> Project: XFire
> Issue Type: Bug
> Affects Versions: 1.2.2
> Environment: BEA Weblogic 8.1 SP2
> Reporter: Jakub Mendys
> Assigned To: Dan Diephouse
> Priority: Minor
> Attachments: xFireTest.zip
>
>
> 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 examine WSDL. The first
> request results in valid XML document but all subsequent 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 problem does not apply when default (AEGIS) binding are used.
> See test case:
> ===========================
> The zip contains folder 'test' which is an exploded war ready to deploy. After
> deployment is exposes 2 services:
> * XFireTestService1 (without xmlbean bindings)
> * 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.
> This is a copy of closed bug XFIRE-634
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
