Owen,
thank a lot for the answer. It was what I needed.
R.
----- Original Message -----
From: "Owen D Burroughs" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 28, 2003 11:11 AM
Subject: Re: WSIFDynamicTypeMap
>
> Roberto,
>
> WSIFDynamicTypeMap is used as a provider (binding) independent way of
> storing a mapping between an xml type name (QName) and a Java class. The
> information can be used by the various WSIF providers in whatever way they
> see fit. For example, the Apache Axis provider will use the information to
> help register type mappings on the Axis Call object, whereas the Java and
> EJB providers do not use the information, instead relying on what is
> provided in the format binding.
>
> The job of "translating" WSDL type names to Java class names is either
> carried out by the user through calls to mapType and mapPackage on
> WSIFService, or can be left to the new automatic mapping functionality
> which has recently been added (see my post from 26th Feb). The actual
> generation of the class files themselves is not in the scope of WSIF.
Tools
> such as WSDL2Java in Axis can be used for this.
>
> Hope this helps.
>
> Owen
>
>
>
> |---------+---------------------------->
> | | "Roberto |
> | | Podesta'" |
> | | <[EMAIL PROTECTED]|
> | | t.unige.it> |
> | | |
> | | 26/02/2003 15:24 |
> | | Please respond to|
> | | wsif-dev |
> | | |
> |---------+---------------------------->
>
>---------------------------------------------------------------------------
-----------------------------------------------------------------------|
> |
|
> | To: <[EMAIL PROTECTED]>
|
> | cc:
|
> | Subject: WSIFDynamicTypeMap
|
> |
|
> |
|
>
>---------------------------------------------------------------------------
-----------------------------------------------------------------------|
>
>
>
> Hi,
> I have understood that WSIFDynamicTypeMap has the role of mapping the
> abstract schema in the WSDL messages for the operation in the PortType to
> java types them corresponding, so its scope is "translate" WSDL types to
> java type for the client routine and does nothing for the binding issue,
is
> it correct?
> tx
> Roberto
>
>
