On 7/26/07, Michael Bell <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> the problem is that the actual code generation blocks the use of the
> generated packages with common types by different web services because
> the generated ExtensionMappers are not identical if the web services do
> not share all XML/WSDL types.
>
> So it is not possible for me to write some common classes because the
> import of the common packages fails (except that I import all web
> services).


yes that is correct .

Amila Suriarachchi schrieb:
>
> > On 7/23/07, Michael Bell <[EMAIL PROTECTED]> wrote:
>
> > this extension mapper is used  in extensions(to support
> polymorphysum).  if
> > the input xml stream contains an
> > xsi:type element then we find the corresponding class from using this.
> >
> > Keeping one extension mapper would make the code generation easy sine we
> > have to find the class only in one place. other wise have to see in all
> the
> > places. you can not say classes in one package has only extended from
> the
> > class in the same package.
>
> I only see calls to the ExtensionMapper from classes which were
> generated for XML types. So it looks easy for me to modify the extension
> mapper in the correct way and place (this is what I do with my script).


I am talking about the  Classes which calls to the Extension mapper.

> if you split the extension mapper class then you have to change the places
> > it refer as well. some times if you only extends classes from the same
> > package this may work. but not a genearalized approach.
>
> The ExtensionMapper is used in the generated type classes. These classes
> can be very easily fixed. My script looks into the classes and modify
> the package of the extension mapper.
>
> I don't understand which external code uses the extension mapper. Can
> you point me to an example please?


this is what  I am saying.
lets say we have two packages p1, p2 and those contain classes c1 and c2 and
extension mappers are
em1 and em2.

And say em1 only refers to classes in p1 package and em2 only refers to p2
package classes.

if p2 pacakge classes extens for p1 package class,

then when refering from p1, (say c1) it won't be able to find the correct
class since em1 contain only the p1 package classes.

Anyway if you tool address this problem please send a patch.
better if you can make it like wsdl2java where user can run from the bin
directory by giving the
source folder (out put folder to wsdl2java).

I'll commit it as a tool.

thanks,
Amila.


Thanks Michael
> --
> _______________________________________________________________
>
> Michael Bell                    Humboldt-Universitaet zu Berlin
>
> Tel.: +49 (0)30-2093 2482       ZE Computer- und Medienservice
> Fax:  +49 (0)30-2093 2704       Unter den Linden 6
> [EMAIL PROTECTED]   D-10099 Berlin
> _______________________________________________________________
>
> X.509 CA Certificates / Wurzelzertifikate
>
> http://ra.pki.hu-berlin.de
>
>


-- 
Amila Suriarachchi,
WSO2 Inc.

Reply via email to