RE: Migrating XFire/Aegis inheritance to CXF

2008-02-11 Thread InJeNiErO 
=xsd:string/
 /xsd:sequence
 /xsd:complexType
 /xsd:schema
 xsd:schema xmlns:ns0=http://model.testapplication;
 attributeFormDefault=unqualified elementFormDefault=qualified
 targetNamespace=http://ws.testapplication/;
 xsd:element name=doService type=tns:doService/
 xsd:complexType name=doService
 xsd:sequence
 xsd:element minOccurs=0 name=arg0 type=xsd:string/
 /xsd:sequence
 /xsd:complexType
 xsd:element name=doServiceResponse type=tns:doServiceResponse/
 xsd:complexType name=doServiceResponse
 xsd:sequence
 xsd:element minOccurs=0 name=return type=ns0:Dummy/
 /xsd:sequence
 /xsd:complexType
 /xsd:schema
   /wsdl:types
   wsdl:message name=doService
 wsdl:part element=tns:doService name=parameters
 /wsdl:part
   /wsdl:message
   wsdl:message name=doServiceResponse
 wsdl:part element=tns:doServiceResponse name=parameters
 /wsdl:part
   /wsdl:message
   wsdl:portType name=GetDummyWSPortType
 wsdl:operation name=doService
   wsdl:input message=tns:doService name=doService
 /wsdl:input
   wsdl:output message=tns:doServiceResponse
 name=doServiceResponse
 /wsdl:output
 /wsdl:operation
   /wsdl:portType
   wsdl:binding name=GetDummyWSSoapBinding
 type=tns:GetDummyWSPortType
 soap:binding style=document
 transport=http://schemas.xmlsoap.org/soap/http/
 wsdl:operation name=doService
   soap:operation soapAction= style=document/
   wsdl:input name=doService
 soap:body use=literal/
   /wsdl:input
   wsdl:output name=doServiceResponse
 soap:body use=literal/
   /wsdl:output
 /wsdl:operation
   /wsdl:binding
   wsdl:service name=GetDummyWS
 wsdl:port binding=tns:GetDummyWSSoapBinding name=GetDummyWSPort
   soap:address location=http://localhost:8080/services/GetDummy/
 /wsdl:port
   /wsdl:service
 /wsdl:definitions
 
 InJeNiErO.
 
I pessimistically think that you've found a bug. Could you please drop
this into JIRA?
 
 -Original Message-
 From: Segal, Jeffrey [mailto:[EMAIL PROTECTED]
 Sent: Thursday, November 01, 2007 4:31 PM
 To: cxf-user@incubator.apache.org
 Subject: Migrating XFire/Aegis inheritance to CXF
 
 I'd like to bump the question posed a few weeks ago by Nalyd (see
 http://www.nabble.com/Aegis-inheritance-tf4668138.html#a13335122).
 
 I am attempting to ensure that some additional classes which are not
 present in my service interfaces get bound along with the others, a
 common problem given a service such as:
 
 public void queue(Job job);
 
 where there exists the following classes:
 
 public class BigJob extends Job { ... }
 public class SmallJob extends Job {...}
 
 In this case, Job will be bound to XML elements, but BigJob and
 SmallJob
 will not.  XFire does support this, documented at
 http://xfire.codehaus.org/Aegis+Inheritance.  However, I cannot find a
 similar piece of documentation on porting this solution to CXF.  It
 seems as if the support is all still there but not necessarily exposed
 (see http://cwiki.apache.org/CXF20DOC/aegis-theory-of-operation.html).
 
 I have played around with a few things in my Spring configuration,
 such
 as adding something like this to my ServiceFactoryBean:
 
 bean id='jaxws-and-aegis-service-factory'
 class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean
 ...
 property name=properties
 map
 entry key=writeXsiType
 value type=java.lang.Booleantrue/value
 /entry
 entry key=overrideTypesList
 list
 valuecom.foo.bar.BigJob/value
 valuecom.foo.bar.SmallJob/value
 /list
 /entry
 /map
 /property
 ...
 /bean
 
 This deploys without error, but my WSDL and corresponding stubs do not
 include the overridden types.  Any ideas?
 
 Thanks!
 Jeff
 
 



-- 
View this message in context: 
http://www.nabble.com/Migrating-XFire-Aegis-inheritance-to-CXF-tp13536859p15413115.html
Sent from the cxf-user mailing list archive at Nabble.com.

RE: Migrating XFire/Aegis inheritance to CXF

2008-02-11 Thread InJeNiErO 
  /wsdl:message
  wsdl:portType name=GetDummyWSPortType
wsdl:operation name=doService
  wsdl:input message=tns:doService name=doService
/wsdl:input
  wsdl:output message=tns:doServiceResponse name=doServiceResponse
/wsdl:output
/wsdl:operation
  /wsdl:portType
  wsdl:binding name=GetDummyWSSoapBinding type=tns:GetDummyWSPortType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=doService
  soap:operation soapAction= style=document/
  wsdl:input name=doService
soap:body use=literal/
  /wsdl:input
  wsdl:output name=doServiceResponse
soap:body use=literal/
  /wsdl:output
/wsdl:operation
  /wsdl:binding
  wsdl:service name=GetDummyWS
wsdl:port binding=tns:GetDummyWSSoapBinding name=GetDummyWSPort
  soap:address location=http://localhost:8080/services/GetDummy/
/wsdl:port
  /wsdl:service
/wsdl:definitions

InJeNiErO.

I pessimistically think that you've found a bug. Could you please drop
this into JIRA?

 -Original Message-
 From: Segal, Jeffrey [mailto:[EMAIL PROTECTED]
 Sent: Thursday, November 01, 2007 4:31 PM
 To: cxf-user@incubator.apache.org
 Subject: Migrating XFire/Aegis inheritance to CXF
 
 I'd like to bump the question posed a few weeks ago by Nalyd (see
 http://www.nabble.com/Aegis-inheritance-tf4668138.html#a13335122).
 
 I am attempting to ensure that some additional classes which are not
 present in my service interfaces get bound along with the others, a
 common problem given a service such as:
 
 public void queue(Job job);
 
 where there exists the following classes:
 
 public class BigJob extends Job { ... }
 public class SmallJob extends Job {...}
 
 In this case, Job will be bound to XML elements, but BigJob and
SmallJob
 will not.  XFire does support this, documented at
 http://xfire.codehaus.org/Aegis+Inheritance.  However, I cannot find a
 similar piece of documentation on porting this solution to CXF.  It
 seems as if the support is all still there but not necessarily exposed
 (see http://cwiki.apache.org/CXF20DOC/aegis-theory-of-operation.html).
 
 I have played around with a few things in my Spring configuration,
such
 as adding something like this to my ServiceFactoryBean:
 
 bean id='jaxws-and-aegis-service-factory'
 class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean
 ...
 property name=properties
 map
 entry key=writeXsiType
 value type=java.lang.Booleantrue/value
 /entry
 entry key=overrideTypesList
 list
 valuecom.foo.bar.BigJob/value
 valuecom.foo.bar.SmallJob/value
 /list
 /entry
 /map
 /property
 ...
 /bean
 
 This deploys without error, but my WSDL and corresponding stubs do not
 include the overridden types.  Any ideas?
 
 Thanks!
 Jeff



-- 
View this message in context: 
http://www.nabble.com/Migrating-XFire-Aegis-inheritance-to-CXF-tp13536859p15412041.html
Sent from the cxf-user mailing list archive at Nabble.com.

Migrating XFire/Aegis inheritance to CXF

2007-11-01 Thread Segal, Jeffrey 
I'd like to bump the question posed a few weeks ago by Nalyd (see
http://www.nabble.com/Aegis-inheritance-tf4668138.html#a13335122).
 
I am attempting to ensure that some additional classes which are not
present in my service interfaces get bound along with the others, a
common problem given a service such as:
 
public void queue(Job job);
 
where there exists the following classes:
 
public class BigJob extends Job { ... }
public class SmallJob extends Job {...}
 
In this case, Job will be bound to XML elements, but BigJob and SmallJob
will not.  XFire does support this, documented at
http://xfire.codehaus.org/Aegis+Inheritance.  However, I cannot find a
similar piece of documentation on porting this solution to CXF.  It
seems as if the support is all still there but not necessarily exposed
(see http://cwiki.apache.org/CXF20DOC/aegis-theory-of-operation.html).  
 
I have played around with a few things in my Spring configuration, such
as adding something like this to my ServiceFactoryBean:
 
bean id='jaxws-and-aegis-service-factory'
class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean
...
property name=properties
map
entry key=writeXsiType
value type=java.lang.Booleantrue/value
/entry
entry key=overrideTypesList
list
valuecom.foo.bar.BigJob/value
valuecom.foo.bar.SmallJob/value
/list
/entry
/map
/property
...
/bean
 
This deploys without error, but my WSDL and corresponding stubs do not
include the overridden types.  Any ideas?
 
Thanks!
Jeff

RE: Migrating XFire/Aegis inheritance to CXF

2007-11-01 Thread Benson Margulies 
I pessimistically think that you've found a bug. Could you please drop
this into JIRA?

 -Original Message-
 From: Segal, Jeffrey [mailto:[EMAIL PROTECTED]
 Sent: Thursday, November 01, 2007 4:31 PM
 To: cxf-user@incubator.apache.org
 Subject: Migrating XFire/Aegis inheritance to CXF
 
 I'd like to bump the question posed a few weeks ago by Nalyd (see
 http://www.nabble.com/Aegis-inheritance-tf4668138.html#a13335122).
 
 I am attempting to ensure that some additional classes which are not
 present in my service interfaces get bound along with the others, a
 common problem given a service such as:
 
 public void queue(Job job);
 
 where there exists the following classes:
 
 public class BigJob extends Job { ... }
 public class SmallJob extends Job {...}
 
 In this case, Job will be bound to XML elements, but BigJob and
SmallJob
 will not.  XFire does support this, documented at
 http://xfire.codehaus.org/Aegis+Inheritance.  However, I cannot find a
 similar piece of documentation on porting this solution to CXF.  It
 seems as if the support is all still there but not necessarily exposed
 (see http://cwiki.apache.org/CXF20DOC/aegis-theory-of-operation.html).
 
 I have played around with a few things in my Spring configuration,
such
 as adding something like this to my ServiceFactoryBean:
 
 bean id='jaxws-and-aegis-service-factory'
 class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean
 ...
 property name=properties
 map
 entry key=writeXsiType
 value type=java.lang.Booleantrue/value
 /entry
 entry key=overrideTypesList
 list
 valuecom.foo.bar.BigJob/value
 valuecom.foo.bar.SmallJob/value
 /list
 /entry
 /map
 /property
 ...
 /bean
 
 This deploys without error, but my WSDL and corresponding stubs do not
 include the overridden types.  Any ideas?
 
 Thanks!
 Jeff