For me, at least, I think I'd need to ask you to post up enough Java code to demonstrate the effect. Some of the others might be more energetic. I'll see if I can construct a test case that repros your problem, however.
> -----Original Message----- > From: Tawfik [mailto:[EMAIL PROTECTED] > Sent: Monday, September 10, 2007 4:41 PM > To: [email protected] > Subject: RE: Aegis mappings not reflecting in wsdl method parameters > > > Please see the JIRA I posted about a couple of weeks ago: > > https://issues.apache.org/jira/browse/CXF-962 > > From the tests I did, it seems to be a general issue that can easilly > duplicated. With any service method, the parameters are always named arg0, > arg1, ... and the minoccurs is set to 0. The aegis mapping files are > being > read from what I see in the log files. > If there is a way to get the minoccurs be 1 (may be by having it be the > default as in xfire) then I could switch to annotation to have the > arguments > named correctly. > > If you need any more details please don't hesitate to ask and I'll respond > ASAP. > > Thank you! > > > bmargulies wrote: > > > > Could you post a JIRA with an entire test case, by some chance? If so, > > I'll look for the fix. > > > >> -----Original Message----- > >> From: Tawfik [mailto:[EMAIL PROTECTED] > >> Sent: Monday, September 10, 2007 4:22 PM > >> To: [email protected] > >> Subject: Re: Aegis mappings not reflecting in wsdl method parameters > >> > >> > >> Has anyone see anything relating to this issue? We are trying to > > migrate > >> from xfire to cxf but will not be able to unless we find a way to get > > this > >> working. Our main concern is the minoccurs for method parameters, we > >> cannot > >> have is set to 0 in the wsdl. Did the default change from 1 in xfire > > to 0 > >> in cxf? > >> > >> I would appreciate ANY help to move forward. > >> > >> Thanks > >> > >> > >> Tawfik wrote: > >> > > >> > > >> > > >> > Tawfik wrote: > >> >> > >> >> I am trying to migrate from xfire to cxf but need to re-use the > > aegis > >> >> mapping files we already have. I have tried using both the simple > >> >> frontend and the jax-ws front end but I get the same problem. Here > > is > >> my > >> >> config: > >> >> > >> >> <beans xmlns="http://www.springframework.org/schema/beans"; > >> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > >> >> xmlns:simple="http://cxf.apache.org/simple"; > >> >> xsi:schemaLocation="http://www.springframework.org/schema/beans > >> >> http://www.springframework.org/schema/beans/spring-beans.xsd > >> >> http://cxf.apache.org/simple > > http://cxf.apache.org/schemas/simple.xsd";> > >> >> > >> >> <import resource="classpath:services_definition.xml" /> > >> >> <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" /> > >> >> > >> >> <simple:server id="spatialQuery" serviceClass="ISpatialQuery" > >> >> address="/SpatialQuery"> > >> >> <simple:dataBinding> > >> >> <bean > >> class="org.apache.cxf.aegis.databinding.AegisDatabinding" > >> >> /> > >> >> </simple:dataBinding> > >> >> <simple:serviceBean> > >> >> <ref bean="spatialqueryService" /><!-- defined in > >> >> services_definition.xml --> > >> >> </simple:serviceBean> > >> >> <!-- did not help... > >> >> <simple:serviceFactory> > >> >> <ref bean="serviceFactory"/> > >> >> </simple:serviceFactory> > >> >> --> > >> >> </simple:server> > >> >> </bens> > >> >> > >> >> The aegis mapping files are taking effect for the object model and > > the > >> >> schema for all objects look as they should. The problem is limited > > to > >> >> method parameters. What I get in the wsdl for one of the methods > > looks > >> >> like this: > >> >> > >> >> <complexType name="findFeaturesByExtent"> > >> >> <sequence> > >> >> <element minOccurs="0" name="arg0" type="ns0:Envelope" /> > >> >> <element minOccurs="0" name="arg1" type="ns0:SpatialQueryOptions" > > /> > >> >> <element minOccurs="0" name="arg2" type="string" /> > >> >> </sequence> > >> >> </complexType> > >> >> > >> >> but it should be (based on the aegis mapping files and the wsdl > > from > >> >> xfire with those same mapping files): > >> >> > >> >> <xsd:element name="findFeaturesByExtent"> > >> >> <xsd:complexType> > >> >> <xsd:sequence> > >> >> <xsd:element maxOccurs="1" minOccurs="1" name="extent" > >> nillable="true" > >> >> type="tns:Envelope" /> > >> >> <xsd:element maxOccurs="1" minOccurs="1" > > name="spatialQueryOptions" > >> >> nillable="true" type="tns:SpatialQueryOptions" /> > >> >> <xsd:element maxOccurs="1" minOccurs="1" name="token" > > nillable="true" > >> >> type="xsd:string" /> > >> >> </xsd:sequence> > >> >> </xsd:complexType> > >> >> > >> >> Note that I do see that the mapping file for the service is being > > read > >> >> but it is just not reflecting on the wsdl: > >> >> [01 Sep 07 09:35:25][main XMLTypeCreator DEBUG][getDocument:112] > > Found > >> >> mapping file : /ISpatialQuery.aegis.xml > >> >> > >> >> Any help is appriciated > >> >> > >> >> Thanks > >> >> > >> >> > >> > > >> > > >> > >> -- > >> View this message in context: > > http://www.nabble.com/Aegis-mappings-not- > >> reflecting-in-wsdl-method-parameters-tf4388442.html#a12602039 > >> Sent from the cxf-user mailing list archive at Nabble.com. > > > > > > > > -- > View this message in context: http://www.nabble.com/Aegis-mappings-not- > reflecting-in-wsdl-method-parameters-tf4388442.html#a12602415 > Sent from the cxf-user mailing list archive at Nabble.com.
