Return-Path: Mailing-List: contact axis-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list axis-user@xml.apache.org Delivered-To: moderator for axis-user@xml.apache.org Received: (qmail 51716 invoked from network); 9 Jul 2002 18:31:56 -0000 Received: from cobia.net (66.155.53.17) by daedalus.apache.org with SMTP; 9 Jul 2002 18:31:56 -0000 Received: from GLENLIVET [63.79.204.2] by cobia.net with ESMTP (SMTPD32-6.06) id AC64157014E; Tue, 09 Jul 2002 14:33:08 -0400 Reply-To: From: "Chris Haddad" To: Subject: RE: WSDL-Service Payload encoding/decoding to/from different "XML"-Formats Date: Tue, 9 Jul 2002 14:24:33 -0400 Organization: Cobia Communications Message-ID: <004301c22775$e433c490$9865fea9@GLENLIVET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0044_01C22754.5D222490" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <003801c22756$57dbf9a0$133f07d5@mycomputer> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Status: O X-Status: X-Keywords: X-UID: 243 This is a multi-part message in MIME format. ------=_NextPart_000_0044_01C22754.5D222490 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Wolfgang - Can you communicate the exact use case and maybe provide an example? I've become a bit familiar with the serialization subsystem, but I'm not clear on your exact requirements. For example, do you desire to: Retain the default QName->object type mappings? Override the default QName->object type mappings? Extend the type map with new QName->object mappings? Translate default QNames into alternative QNamess? Are the above scenarios based on a specific service endpoint, or used across the entire server? There are already a fair amount of switches inside Axis to register alternative Type mappings and serialization techniques, so from first glance, it seems like you could build on top of the framework. /Chris -----Original Message----- From: wolfgang.mueller-bln@web.de [mailto:wolfgang.mueller-bln@web.de] Sent: Tuesday, July 09, 2002 10:39 AM To: axis-user@xml.apache.org Subject: WSDL-Service Payload encoding/decoding to/from different "XML"-Formats Hello, In a project I have to transform the communication between an AXIS-Client and a SOAP-Service directly to another XML-Format or Object Model. For that I need, similar to that what is already realised in AXIS, a Type Mapping between the Service Type (RPC-Parameter-Types) and the "local"-Types (Object Model). Where is the best point to integrate such a mapping? One option would be, directly to use the Stubs, as produced by WSDL2Java, generating from these informations the transformators for type mapping. Looking at this option, I have the feeling to reimplent a lot of things already implemented in the AXIS-Encoding-Subsystem. Therefore comes up the other option, to integrate this type-mapping directly in the Encoding-Subsystem with special extended factory classes and serializers/deserializers. Would this be the preferable solution? Are there some papers around, giving a more global view on the AXIS-Encoding Subsystem? Thanks for your comments. Regards, Wolfgang ------=_NextPart_000_0044_01C22754.5D222490 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Wolfgang –   =

 

Can you communicate the exact use = case and maybe provide an example?  I’ve become a bit familiar with the serialization = subsystem, but I’m not clear on your exact requirements. 

 

For example, do you desire = to:

 

Retain the default QName->object type mappings?

Override the default QName->object type mappings?

Extend the type map with new QName->object = mappings?

Translate default QNames into alternative QNamess?

 

Are the above scenarios based on a specific service endpoint, or used across the entire = server?

 

There are already a fair amount of switches inside Axis to register alternative Type mappings and = serialization techniques, so from first glance, it seems like you could build on top = of the framework.

 

/Chris

 

-----Original = Message-----
From: = wolfgang.mueller-bln@web.de [mailto:wolfgang.mueller-bln@web.de]
Sent: Tuesday, July 09, = 2002 10:39 AM
To: = axis-user@xml.apache.org
Subject: WSDL-Service = Payload encoding/decoding to/from different = "XML"-Formats

 

Hello,

 

In a project I have to = transform the communication between an AXIS-Client and a = SOAP-Service

directly to another = XML-Format or Object Model. For that I need, similar to that what is = already

realised in AXIS, a Type Mapping between the Service Type (RPC-Parameter-Types) and = the

"local"-Types = (Object Model).

 

Where is the best point to = integrate such a mapping?

 

One option would be, = directly to use the Stubs, as produced by WSDL2Java, generating =

from these informations the transformators for type mapping.  

 

Looking at this option, I = have the feeling to reimplent a lot of things already = implemented

in the = AXIS-Encoding-Subsystem.

 

Therefore comes up the = other option, to integrate this type-mapping directly in the =

Encoding-Subsystem with = special extended factory classes and

serializers/deserializers.

 

Would this be the = preferable solution?

 

Are there some papers = around, giving a more global view on the

AXIS-Encoding = Subsystem?

 

Thanks for your = comments.

 

Regards,<= /o:p>

Wolfgang<= /o:p>

 

------=_NextPart_000_0044_01C22754.5D222490--