On Tue February 24 2009 3:39:21 pm relphie wrote:
> I don't think it is actually the result of the type mapper, since all
> methods, even those with simple arguments and default-mapped-types are
> failing.
>
> I think it is simple enough to see realize that if the generated wsdls are
> different, i.e. missing/different schema definitions, then different
> versions will not work.
Well, if schema definitions are missing, that means something isn't detecting
a type that 2.0 did. Remember, 2.1/2.2 use JAXB 2.1 instead of 2.0 so there
are more ways to detect types and mappers and such. Example: the
XmlJavaTypeAdapter annotations can live on the SEI methods themselves where
that wasn't allowed in 2.0.
> It really appears that passivity is not being given a high enough priority
> with 2.1 and 2.2 branches. Are there test run to determine whether 2.0
> clients/services work with 2.1/2.2 clients/services? My tests are hit and
> miss, but most do not work.
It would be REALLY helpful if you could create a JIRA and attach a testcase
that works with 2.0 and doesn't with 2.1/2.2. That would be the biggest
help in determining why. In theory, 2.0 services SHOULD work fine with
2.1/2.2 and your the first to really report a lot of issues with it. (except
for issues mentioned in the migration guide) Thus, having a testcase from you
would be great.
Dan
>
> dkulp wrote:
> > On Tue February 24 2009 1:30:13 pm relphie wrote:
> >> I have tried the same thing with another of my simpler services -
> >> connecting a 2.0.x client to a 2.2 server - and it seems to be working
> >> fine. I think the problems appear with my more complicated service
> >> where I
> >> had define a custom type mapper for one of my interfaces. I use the
> >> interface as a map key, and it appears that the schema for that return
> >> value is not being properly generated. Here is my interface:
> >
> > How is the type mapper registered? It may be that that isn't being
> > picked
> > up.
> >
> > With 2.1/2.2, you can add @XmlJavaTypeAdapter annotations onto the actual
> > methods as well to get things mapped for the Maps.
> >
> > Dan
> >
> >> <code>
> >> @WebService
> >> public interface OrganizationService
> >> {
> >> public Collection<Organization> retrieveByAlias(OrganizationAlias
> >> alias);
> >>
> >> public Map<OrganizationAlias, Collection<Organization>>
> >> retrieveByAliases(Collection<OrganizationAlias> aliases);
> >>
> >> public Map<String, Organization> retrieveByIds(Collection<String>
> >> organizationIds);
> >> }
> >> </code>
> >>
> >> And I will attach the generated 2.0 and 2.2 wsdls:
> >>
> >> http://www.nabble.com/file/p22187629/OrganizationService.wsdl
> >> OrganizationService.wsdl
> >> http://www.nabble.com/file/p22187629/OrganizationService22.wsdl
> >> OrganizationService22.wsdl
> >>
> >> Any ideas?
> >>
> >> relphie wrote:
> >> > Hello,
> >> >
> >> > I am attempting to upgrade my 2.0.9 cxf service to 2.2-SNAPSHOT.
> >> > However, with my 2.0.9 client, I am unable to pass my tests connection
> >>
> >> to
> >>
> >> > a 2.2-SNAPSHOT server. Also, the server side WSDL that is generated
> >> > is different between the 2.0.9 version and the 2.2 version. Is this
> >> > to be expected? Is 2.0.9 and 2.2-SNAPSHOT compatible?
> >> >
> >> > Thanks,
> >> > Brian
> >
> > --
> > Daniel Kulp
> > [email protected]
> > http://www.dankulp.com/blog
--
Daniel Kulp
[email protected]
http://www.dankulp.com/blog
