Thats for mapping List<String> types, so you probably have a method that returns or receives a List<String>, this is handle a bit different in the current snapshot. But this way works fine in 2.0 don't worry about it.

On Jul 30, 2007, at 6:48 PM, gdprao wrote:


Thanks Julio. It worked and has eliminated the setter method from the WSDL after adding this annotation. However, I see extra type (stringArray) in WSDL schema section is getting added up automatically which is not present
in my service:

<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns="http://jaxb.dev.java.net/array"; attributeFormDefault="unqualified"
elementFormDefault="unqualified"
targetNamespace="http://jaxb.dev.java.net/array";>
<xs:complexType final="#all" name="stringArray">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="item" nillable="true"
type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:schema>


Thanks,
Durga


Julio Arias wrote:

Hi -

This problem is fix in the latest SNAPSHOT, I you don't want to
update yet add @WebMethod(exclude = true) annotation to any method in
your Impl that you don't want to expose in your WSDL.

On Jul 30, 2007, at 3:45 PM, gdprao wrote:


I have developed a service in CXF and my service implementation
class which
defines a setter injection method for Delegate which actually
performs the
business logic.
After deploying the service, in the WSDL generated by CXF I see the
schema
with elements for setServiceDelegate and
setServiceDelegateResponse. Is there a way can I annotate and make
certain
methods in my service implementation class transient so that I
don't want to
have their type information published in the WSDL.
Please see the following code snippets of implementation class and
spring
configuration. I am using CXF2.0.


public class FooServiceImpl implements FooService {

        private FooServiceDelegateIntf serviceDelegate=null;
        
        public void setServiceDelegate(FooServiceDelegateIntf delegate) {
                this.serviceDelegate = delegate;
        }

//... Web Service methods..

}


<beans xmlns="http://www.springframework.org/schema/beans";
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
        xmlns:jaxws="http://cxf.apache.org/jaxws";
        xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd
http://cxf.apache.org/jaxws http://cxf.apache.org/schemas/ jaxws.xsd">

        <import resource="classpath:META-INF/cxf/cxf.xml" />
        <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml" />
        <import resource="classpath:META-INF/cxf/cxf-servlet.xml" />
        
        <bean id="fooWebService"
                class="com.mydomain.FooServiceImpl">
                <property name="serviceDelegate" ref="fooServiceDelegate"></
property>
        </bean>
        
        <jaxws:endpoint id="fooService" implementor="#fooWebService"
                address="/FooService"/>
                
</beans>

--
View this message in context: http://www.nabble.com/CXF-adding-
types-for-setter-injection-methods-tf4179440.html#a11884764
Sent from the cxf-user mailing list archive at Nabble.com.





Julio Arias
Java Developer
Roundbox Global : enterprise : technology : genius
---------------------------------------------------------------------
Avenida 11 y Calle 7-9, Barrio Amón, San Jose, Costa Rica
tel: 404.567.5000 ext. 2001 | cell: 11.506.849.5981
email: [EMAIL PROTECTED] | www.rbxglobal.com
---------------------------------------------------------------------




--
View this message in context: http://www.nabble.com/CXF-adding- types-for-setter-injection-methods-tf4179440.html#a11888262
Sent from the cxf-user mailing list archive at Nabble.com.





Julio Arias
Java Developer
Roundbox Global : enterprise : technology : genius
---------------------------------------------------------------------
Avenida 11 y Calle 7-9, Barrio Amón, San Jose, Costa Rica
tel: 404.567.5000 ext. 2001 | cell: 11.506.849.5981
email: [EMAIL PROTECTED] | www.rbxglobal.com
---------------------------------------------------------------------

Reply via email to