axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Reopened: (AXIS-1120) DefaultTypeMappingImpl is not compliant with JAX-RPC 1.1
Date Wed, 16 Jun 2004 03:25:10 GMT
Message:

   The following issue has been reopened.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1120

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1120
    Summary: DefaultTypeMappingImpl is not compliant with JAX-RPC 1.1
       Type: Bug

     Status: Reopened

    Project: Axis
 Components: 
             Deployment / Registries
   Versions:
             current (nightly)

   Assignee: Davanum Srinivas
   Reporter: Ias

    Created: Sat, 8 Nov 2003 8:13 AM
    Updated: Tue, 15 Jun 2004 8:23 PM
Environment: Operating System: All
Platform: All

Description:
The current DefaultTypeMappingImpl's XML to Java type mapping is not along 
with that of JAX RPC 1.1 spec. 
I heard from Jongjin that someone suggested following it up, but some 
compatibility issues have remained so that such change hasn't been made yet.

I'd like to propose the following steps toward the upcoming future:

1. Providing SUPPORT_JAX_RPC_1_1 option to switch the feature on build time

The attached patch is designed for the purpose. Now the option is turned off 
and works fine with all-tests. It's no doubt that some of the tests fail in 
case of "turn-on", but it must be helpful to those who want to try the exact 
JAX-RPC 1.1 type mapping.

2. Adopting by default

I think this feature may be considered experimental until sufficient 
discussion and consensus are achieved. I expect the next version of axis (e.g. 
1.2) can choose it and encourage users and developers to keep up with it.

Finally, I found that the patch on DefaultTypeMappingImpl from
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24382
was potentially problematic because of "the order game". I changed the order 
of registering of xsd:anySimpleType in front of xsd:string for right Java to 
XML mapping. I'm willing to make a small patch only for this problem when 
necessary.

Thanks for your feedback in advance,

Ias


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message