WSDL DOM -> JAXME conversion

[Srinath Perera <he...@vijayaba.cse.mrt.ac.lk>]

Hi All,

using JAXME We can't find (I belive there does not exists) get the any
attributes that are not part of the Schema spec but in the complex type

e.g.

     <xsd:complexType name="hobbyArray">
 *       <xsd:complexContent>
 *         <xsd:restriction base="soapenc:Array">
 *           <xsd:attribute ref="soapenc:arrayType"
			wsdl:arrayType="xsd:string[]"/>
 *         </xsd:restriction>
 *       </xsd:complexContent>
 *     </xsd:complexType>

the wsdl:arrayType is not schma defined and I can't find any way to get 
it with jaxme. (same prob occurs trying to extract value attributes from
element at attchment )

q1) Am I Overlooking something, Can Anybody show how to extract that
attrib if there is a way. (I drop mail to JAXME list as well)
q2) If we are to do a fix on jaxme should we do the fix overselves, or
will they do it for us. (If we are to do it would be time consuming
busniss ... only if no option)

we continuing without helping these case for time been, 

We are going to remove SchemaUtils,remove node from TypeEntry correct
all referances and  make TypeEntry handle logic itself, Will be LOT of
changes inside  symbolTable.

Srinath

Re: WSDL DOM -> JAXME conversion

[Steve Loughran <st...@iseran.com>]

Glen Daniels wrote:
> -1.  Until such time as another way of transmitting serialized object graphs
> becomes a (de-facto or de-jure) standard, SOAP encoding is the way to do it.
> I am strongly against the idea of removing encoding support from Axis.

I too am -1 here, simply because I dont want to break my existing app.

That said, it would be nice to structure the code so you could do a 
build of a client JAR without either rpc/enc or doc/lit support.

Re: WSDL DOM -> JAXME conversion

[Glen Daniels <gl...@thoughtcraft.com>]

-1.  Until such time as another way of transmitting serialized object graphs
becomes a (de-facto or de-jure) standard, SOAP encoding is the way to do it.
I am strongly against the idea of removing encoding support from Axis.

The HTTP binding is in the adjuncts section too, and we plan to keep
implementing that, right? :)

--Glen

----- Original Message ----- 
From: "Sanjiva Weerawarana" <sa...@watson.ibm.com>
To: <ax...@ws.apache.org>
Sent: Monday, October 13, 2003 11:38 AM
Subject: Re: WSDL DOM -> JAXME conversion


> "Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk> writes:
> >      <xsd:complexType name="hobbyArray">
> >  *       <xsd:complexContent>
> >  *         <xsd:restriction base="soapenc:Array">
> >  *           <xsd:attribute ref="soapenc:arrayType"
> > wsdl:arrayType="xsd:string[]"/>
> >  *         </xsd:restriction>
> >  *       </xsd:complexContent>
> >  *     </xsd:complexType>
> >
> > the wsdl:arrayType is not schma defined and I can't find any way to get
> > it with jaxme. (same prob occurs trying to extract value attributes from
> > element at attchment )
>
> Isn't it time to stop supporting the old soapenc stuff?? WSDL 1.2
> won't have this stuff in it and even SOAP 1.2 has all but deprecated
> it by moving this stuff to the adjucts section.
>
> I think its time to move on.
>
> Sanjiva.
>
>

Re: WSDL DOM -> JAXME conversion

[Sanjiva Weerawarana <sa...@watson.ibm.com>]

"Srinath Perera" <he...@vijayaba.cse.mrt.ac.lk> writes:
>      <xsd:complexType name="hobbyArray">
>  *       <xsd:complexContent>
>  *         <xsd:restriction base="soapenc:Array">
>  *           <xsd:attribute ref="soapenc:arrayType"
> wsdl:arrayType="xsd:string[]"/>
>  *         </xsd:restriction>
>  *       </xsd:complexContent>
>  *     </xsd:complexType>
> 
> the wsdl:arrayType is not schma defined and I can't find any way to get 
> it with jaxme. (same prob occurs trying to extract value attributes from
> element at attchment )

Isn't it time to stop supporting the old soapenc stuff?? WSDL 1.2
won't have this stuff in it and even SOAP 1.2 has all but deprecated
it by moving this stuff to the adjucts section. 

I think its time to move on.

Sanjiva.