apache jaxrpc issues

[ru...@us.ibm.com]

FYI.

Note to JCP@apache.org.  After this note, I do not plan to copy jcp@apache.
org for "routine" communications, merely "significant" ones.  Any Apache
member that is interested in more closely following this is welcome to join
the axis-tck mailing list.

- Sam Ruby

---------------------- Forwarded by Sam Ruby/Raleigh/IBM on 06/26/2002 03:
01 PM ---------------------------

Lance Andersen <La...@sun.com> on 06/26/2002 02:56:17 PM

To:    Sam Ruby/Raleigh/IBM@IBMUS
cc:
Subject:    apache jaxrpc issues



Hi Sam,

Here is the list of issues that I am aware of and our response. Please be
aware that you appear to have a drop of the jaxrpc TCK prior to the final
release.

I have also attached a template that I would appreciate if you use going
forward for submitting issues.  Please let me know if you have any
questions.

Regards,
Lance



1. Problem: The echoMix method used by the parameterModeTest has the wrong
parameter order!  This is causing the TCK to fail for Axis, because Axis
is using the correct parameter order.


This issue was addressed in the final version of the jaxrpc tck

2. Boolean Value Issue

The TCK expects a bean that has a boolean property foo to have a getter
named "getFoo()".  This conflicts with the Java Bean Specification.  Axis
generates the appropriate "isFoo()" getter.


We have logged  bug 4708351.  If you could please forward which tests
are failing, that would help us make sure we have addressed all of the
issues.


3. XML to Java mapping problems

One example is the get<wsdl-port-name> method generated in the Service
interface.  If the wsdl port name is "foo", the TCK is expecting "getfoo".
  Not only does this violate JSR 101 chapter 20, but it is also not
conventional java.  Axis generates "getFoo".


We do not have enough information to work through this particular issue.
 If you could please provide us with the tests in question and walk us
through the problem you encountered with the test that would be most
helpful.


4. Service.getPorts issue

com.sun.ts.tests.jaxrpc.api.javax_xml_rpc.Service.Client.GetPortsPosTest2
expects an empty Iterator from service.getPorts().  We throw a
ServiceException because, according to the JAX-RPC javadoc, "Throws:
ServiceException - If this Service class does not have access to the
required WSDL metadata".  We believe the TCK should accept a
ServiceException.

We concur that this is an issue and it is being addressed via bug 4709354.



5. Roundtrip issues
There are at least 2 roundtrip issues with com.sun.ts.tests.jaxrpc.ee.j2w.
marshalltest which is a Java-to-WSDL test.

We have logged bug 4708425.

6. wrapped doc/lit

We believe the tests are valid.  Please see the example in section 6.4.3 of
the jaxrpc specification.



7. Full bean constructor issue
The TCK, in various places, assumes the generated beans have full
constructors.  While full constructors on beans are certainly reasonable,
they are not mandated by any spec, so we believe the TCK should not


We agree with your assessment and have logged bug 4708365


8. Stub/Call get/setProperty issue

This has been logged as bug 4708407



--
Lance Andersen                       email: Lance.Andersen@sun.com
Sun Microsystems Inc.                phone: (781) 442-2037
1 Network Drive, UBUR02-301          fax  : (781) 442-1610
Burlington, MA 01803


 1. Licensee Name:

 2. TCK and version:

 3. SDK version:

 4. Priority (low, medium, high, ):

 5. Specification Reference:
       - Spec Name:
       - Spec version
       - Spec date:
       - Page/Section to reference:

 6. Test Name(s):
 7. Problem Description: