axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert W. McKitrick Jr. (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2326) BeanMapping registers a type mapping for more than one encoding style.
Date Sun, 04 Dec 2005 14:33:31 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2326?page=comments#action_12359254 ] 

Robert W. McKitrick Jr. commented on AXIS-2326:
-----------------------------------------------

Sorry for the missing information - fat fingers.
Environment:
  MS Windows 2000 Pro
  WebLogic 8.1
  Sun JDK-1.4.2_09

Description: 

When using RPC /literal a beanMapping in the .wsdd file works fine. The documentation says
the beanMapping is an equivalent typeMapping for the encodingStyle "http://schemas.xmlsoap.org/soap/encoding/".
However, if I use the equivalent typeMapping instead, I get the infamous error: java.io.IOException:
No serializer found for class ... in registry org.apache.axis.encoding.TypeMappingDelegate@126f828.
It took me a while to realize I just needed to also register a type mapping for the encoding
style of "". NOTE that is an empty string. IMO the documentation should state this clearly.
I had to register both encodingStyles because I wanted the schema included in the wsdl and
that appears to only gets generated if there is a type mapping for the encoded style. 

NOTE: Since the last bug I reported I was told to use 'use="encoded"' I thought I should state
here that this is literal for interop purposes.



> BeanMapping registers a type mapping for more than one encoding style.
> ----------------------------------------------------------------------
>
>          Key: AXIS-2326
>          URL: http://issues.apache.org/jira/browse/AXIS-2326
>      Project: Apache Axis
>         Type: Bug
>   Components: Deployment / Registries, Documentation
>     Versions: 1.3
>  Environment: MS WIndows 2000 Pro
>     Reporter: Robert W. McKitrick Jr.
>     Priority: Minor

>


-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message