axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-axis/java TODO.txt
Date Wed, 16 Jan 2002 20:53:31 GMT
butek       02/01/16 12:53:31

  Modified:    java     TODO.txt
  Some more WSDL2Java to-do's.
  Revision  Changes    Path
  1.9       +14 -1     xml-axis/java/TODO.txt
  Index: TODO.txt
  RCS file: /home/cvs/xml-axis/java/TODO.txt,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- TODO.txt	15 Jan 2002 17:57:02 -0000	1.8
  +++ TODO.txt	16 Jan 2002 20:53:31 -0000	1.9
  @@ -43,6 +43,8 @@
   ! <> Mapping of XML names.  We do some, not all, of what JAX-RPC specifies.
   ! <> Faults - What do we handle now?  What needs to be enhanced?  JAX-RPC needs improving,
first, we think.
   ! <> Derived type support.
  +! <> Object[] doesn't work.  If we have method(Object[] array) and we pass in an
Object[], we get NullPointerExceptions.  If, however, we pass in a String[] or a Phone[] then
it works.  Object[] becomes xsd:anyType[].  Since anyType doesn't work, I don't expect anyType[]
to work.
  +! <> do we want xsd:anyType to work?
   * <Russell> (ongoing) Need to pull everything writer-specific out of the framework(Emitter/SymbolTable/etc).
 Signatures are still in there.  So are Wsdl2java options that only the writers care about.
  @@ -52,7 +54,18 @@
   ! <> Automatically creating a package name from a namespace is very limited at the
  -! <Tom> Literal soap:body support.  (I'm not sure how far Tom's gotten on this.)
  +! <Tom> Literal soap:body support.  There is a large list of issues and things to
  +  - Need a test case, preferably one against a .NET web service.
  +  - The message type files are still emitted and they should not be.
  +  - We do not even try to emit faults differently if they have literal use
  +  - The operation parameter generation needs to be moved out of
  +    populatePortTypes in the symbol table and moved to JavaWriter (RJB - I
  +    don't know whether I agree with this, but it's a problem where it is).
  +  - If we discover a portType has multiple bindings, we abort.
  +    Since interfaces are generated from portTypes, and the literal/encoded
  +    switch is in the binding, we must have the binding todecide what the
  +    interface will look like.
  +  - We do not emit SOAPElement arguments per JAX-RPC yet.
   ! <Russell/Rich> If a reference to a type is encountered before the definition, a
RefdType is created and added to the symbol table.  Once the type is defined, this RefdType
is replaced by a real type.  Other objects may have referred to the RefdType.  Their references
also need to be replaced.  This doesn't affect any of our existing tests.

View raw message