Bob,

Your challenge is that the element contains an <xsd:any>. That's a
wildcard. ADB has no way of knowing what it might contain, therefore
it gives you an OMElement. It can't map it to a more defined object
because it doesn't know what kind of object it is. You must process it
as an OMElement.

How does the viewFields type relate to the request/response messages?
Can you provide more of the schema?

Anne

On 4/30/07, no spam <[EMAIL PROTECTED]> wrote:

thank you and I did read that, but it gives me no idea at all how to get the
ADBBean from the OMElement (or whatever).  ADB javadocs, which I've also
looked at, seem completely disconnected from everything else.

Bob

----- Original Message ----
From: Davanum Srinivas <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, April 30, 2007 1:26:28 PM
Subject: Re: newbie help - how to build up an ADBBean?

see the OM tutorial -
http://ws.apache.org/commons/axiom/OMTutorial.html


On 4/30/07, no spam <[EMAIL PROTECTED]> wrote:
>
>
> I've generated some ADB code from Microsoft SharePoint WSDL, using the ADB
> bindings.  Can someone give me some basic orientation?  Here are relevant
> details:
>
> a schema fragment (useless, imho) from the wsdl is is:
>
>       <s:element name="GetListItemsResponse">
>         <s:complexType>
>           <s:sequence>
>             <s:element minOccurs="0" maxOccurs="1"
> name="GetListItemsResult">
>               <s:complexType mixed="true">
>                 <s:sequence>
>                   <s:any />
>                 </s:sequence>
>               </s:complexType>
>             </s:element>
>           </s:sequence>
>         </s:complexType>
>       </s:element>
>
> there is a setViewFields() call which I'd like to make.  It takes a
> ViewFields_type14, which also tells me nothing:
>
>         public static class ViewFields_type14
>         implements org.apache.axis2.databinding.ADBBean{
>         /* This type was generated from the piece of schema that had
>                 name = viewFields_type14
>                 Namespace URI =
> http://schemas.microsoft.com/sharepoint/soap/
>                 Namespace Prefix = ns1
>                 */
>                         /**
>                         * field for ExtraElement
>                         */
>                         protected org.apache.axiom.om.OMElement
> localExtraElement ;
>                            /**
>                            * Auto generated getter method
>                            * @return org.apache.axiom.om.OMElement
>                            */
>                            public
org.apache.axiom.om.OMElement
> getExtraElement(){
>                                return localExtraElement;
>                            }
>                             /**
>                                * Auto generated setter
method
>                                * @param param
ExtraElement
>                                */
>                                public void
> setExtraElement(org.apache.axiom.om.OMElement param){
>
> this.localExtraElement=param;
>                                }
>
>
> the ADBBean interface also has nothing in it but a getPullParser() method.
> So how can I build up a ViewFields_type14 such that the Java compiler will
> be happy?  I've spent at least an hour poring over the ADB documentation
and
> so far extracted nothing actionable.  How about a code sample?
>
> Bob
>
>
>  ________________________________
> Ahhh...imagining that irresistible "new car" smell?
>  Check out new cars at Yahoo! Autos.
>  ________________________________
> Ahhh...imagining that irresistible "new car" smell?
>  Check out new cars at Yahoo! Autos.


--
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



 ________________________________
Ahhh...imagining that irresistible "new car" smell?
 Check out new cars at Yahoo! Autos.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to