Mine have type="s:string" as well. I also have a field called totalresults that is at the same level as the items which is an integer and seems to be fine. I am able to reference that using lastResult.totalresults. The strings for category and categoryid are the ones I am having problems with. --- In [email protected], "Kelly Birr" <[EMAIL PROTECTED]> wrote: > > The only difference I can see between your WSDL and mine is that mine has > type="s:string" in the simple string elements. I've looked through my > services and have found type="tns:whatever" in some places and flex does > interpret those as more complex types. > > I can only assume this is what's happening to you. If you have control over > your WSDL you may try type="s:string". I had to do something similar in my > .NET web services to get the WSDL to read type="s:string" instead of > type="s:dateTime" for date/time values so Flex would leave them as strings > and not convert them to Date objects and mess up the time zone. > > - Kelly > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of someguy7_7 > Sent: Tuesday, July 04, 2006 10:32 PM > To: [email protected] > Subject: [flexcoders] Re: Beta 3 WebService Result > > Our webservices are written in J2EE 1.5 with Axis. I can get the specific > version of Axis if you think it matters. > > Here is part of wsdl that pertains to the question. Sorry about the > formatting. > > <complexType name="SearchResponse"> > <sequence> > <element maxOccurs="1" minOccurs="0" name="items" nillable="true"> > <complexType> > <sequence> > <element maxOccurs="1" minOccurs="0" name="totalresults" > type="tns1:int"/> > <element maxOccurs="unbounded" minOccurs="0" name="item" > nillable="true"> > <complexType> > <sequence> > <element maxOccurs="1" minOccurs="0" name="category" > type="tns1:string"/> > <element maxOccurs="1" minOccurs="0" > name="categoryid" > type="tns1:string"/> > </sequence> > </complexType> > </element> > </sequence> > </complexType> > </element> > </sequence> > </complexType> > > > Thanks > --- In [email protected], "Kelly Birr" <kelly.fx@> wrote: > > > > Yes, most likely. What does your WSDL element look like for these > strings? > > What technology are you using for your web services (.NET, J2EE, CF)? > > > > - Kelly > > > > -----Original Message----- > > From: [email protected] [mailto:[EMAIL PROTECTED] > > On Behalf Of someguy7_7 > > Sent: Tuesday, July 04, 2006 9:11 AM > > To: [email protected] > > Subject: [flexcoders] Re: Beta 3 WebService Result > > > > I assume you mean set the resultFormat in the <operation>. I have > set that > > as well as makeObjectsBindable="false" in the <webservice> and > <operation> > > but I still comes back as an array of complex strings. If I look at > the last > > result in the debugger it looks like this. > > > > item=Array(@12345) > > [0]=mx.rpc.xml.ComplexString(@23423) > > [1]=mx.rpc.xml.ComplexString(@745545) > > > > I am expecting something like > > item=Object(@12345) > > [0]=category(@23423) > > [1]=categoryid(@745545) > > > > Then I will be able to reference it by lastResult.items.item.category > > instead of lastResult.items.item[0]. > > > > Any ideas on why I am getting complex strings? Is this something to > do with > > how my wsdl is structured? > > > > Thanks > > --- In [email protected], "Kelly Birr" <kelly.fx@> wrote: > > > > > > If you set makeObjectsBindable="false" and resultFormat="object" in > > > the webservice tag you should get arrays of objects. > > > > > > <mx:WebService id="ws" resultFormat="object" > > makeObjectsBindale="false" /> > > > > > > - Kelly > > > > > > -----Original Message----- > > > From: [email protected] [mailto:[EMAIL PROTECTED] > > > On Behalf Of someguy7_7 > > > Sent: Monday, July 03, 2006 2:37 PM > > > To: [email protected] > > > Subject: [flexcoders] Re: Beta 3 WebService Result > > > > > > I am finally getting back to this issue. I have since moved to Flex > > > 2.0 released version. Is there no way for me to use > > resultFormat="object" if the > > > resulting data contains Object Arrays? Or in flex 2.0 are we > > required to use > > > e4x? > > > > > > --- In [email protected], "Tim Hoff" <TimHoff@> wrote: > > > > > > > > Either way, > > > > > > > > Change the resultFormat: > > > > > > > > <mx:WebService id="ws" resultFormat="e4x"/> > > > > > > > > Or, cast lastResult to an XML var. > > > > > > > > -TH > > > > > > > > --- In [email protected], "someguy7_7" <bmcpheeters@> > > > > wrote: > > > > > > > > > > Do you mean change the operation.resultFormat to "xml"? Or > somehow > > > > > cast the lastResult of the operation to a variable typed to "XML"? > > > > > > > > > > Brian > > > > > --- In [email protected], "Tim Hoff" <TimHoff@> wrote: > > > > > > > > > > > > The default return type from a web service call is object(). > > > > > > If > > > > you > > > > > > cast this to XML, you should be able to get the same > > > > funtionality. > > > > > > > > > > > > -TH > > > > > > > > > > > > --- In [email protected], "Brian McPheeters" > > > > > > <bmcpheeters@> wrote: > > > > > > > > > > > > > > We are porting an application from 1.5 to 2.0 Beta 3. The > > > > > > > app > > > > > > connects > > > > > > > to a couple different web services to populate a ListView. > > > > > > > In > > > > the > > > > > > 1.5 > > > > > > > version the result from the web service is an object that I > > > > can > > > > > > pull > > > > > > > data for the list view from using the result xml element > > > > names. > > > > > > > > > > > > > > Ex: currentitem.category, currentitem.categoryid > > > > > > > > > > > > > > But in 2.0 Beta 3 the result is interpreted by flex as an > > > > Array. > > > > > > > currentitem = Array (@38cceb21). This causes me to index > > > > > > > into > > > > the > > > > > > array > > > > > > > to get the values. > > > > > > > > > > > > > > Ex: currentitem[0],currentitem[1] > > > > > > > > > > > > > > Both apps are using the exact same webservices. Do I need to > > > > > > somehow > > > > > > > cast the result from the webservice to an object? Any ideas > > > > > > > on > > > > > > what is > > > > > > > causing this and how to get it so I can reference by element > > > > name > > > > > > in 2.0 > > > > > > > Beta 3? > > > > > > > > > > > > > > Thanks > > > > > > > Brian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > Flexcoders Mailing List > > > FAQ: > > > http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor > --------------------~--> See > > what's inside the new Yahoo! Groups email. > > http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/nhFolB/TM > > --------------------------------------------------------------------~- > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > > ------------------------ Yahoo! Groups Sponsor --------------------~--> See > what's inside the new Yahoo! Groups email. > http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/nhFolB/TM > --------------------------------------------------------------------~-> > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links >
------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/nhFolB/TM --------------------------------------------------------------------~-> -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
