Topic
3 replies Latest Post - ‏2013-01-31T15:36:00Z by CarlD
saikiran
saikiran
20 Posts
ACCEPTED ANSWER

Pinned topic Web Experience Factory JAXB generated web services problem

‏2013-01-17T12:11:40Z |
Hi

I am using WEF (8.0) to consume the JAXB generated web services. The response object contains the return keyword as the element name.

<xs:complexType name="getEmployeeResponse">
<xs:sequence><xs:element minOccurs="0" name="return" type="tns:employee"/></xs:sequence>
</xs:complexType>

Because of that The Data page never identifies the return ... I have to change it to return1. Because of this I am facing the No data display problem in the Data page.

If I use the Data Page like this then the data is getting displayed:

DataServices/clientInquiry_sc/getEmployee/results/getEmployeeResponse
If I use the Data Page like this then the data is not getting displayed:

DataServices/clientInquiry_sc/getEmployee/results/getEmployeeResponse/return1
Any body faced similar problems? Is there any bettter solution to avoid these kind of problem?
Updated on 2013-01-31T15:36:00Z at 2013-01-31T15:36:00Z by CarlD
  • mburati
    mburati
    2551 Posts
    ACCEPTED ANSWER

    Re: Web Experience Factory JAXB generated web services problem

    ‏2013-01-18T14:47:42Z  in response to saikiran
    It sounds like one of the options you tried worked, so is there a reason you can't use that option?

    For situations where the data coming back from any back end in any provider model isnt' suitable for automatically generating the page data, WEF provides Transform builders to transform the data (structure too not just names) to something more suitable for use in consumer models. There's also a more limited set of transform mapping that you can do directly in the Service layer builders.

    I hope that info helps,
    ..Mike Burati
    http://www-10.lotus.com/ldd/pfwiki.nsf/
    The postings on this site are my own and do not necessarily represent the positions, strategies, or opinions of IBM.
    • saikiran
      saikiran
      20 Posts
      ACCEPTED ANSWER

      Re: Web Experience Factory JAXB generated web services problem

      ‏2013-01-24T23:53:01Z  in response to mburati
      Hi

      By the way I found the way to avoid return while services generated using JAXB.

      We can use @WebResult annotation to avoid the return keyword.

      http://jax-ws.java.net/jax-ws-ea3/docs/annotations.html
      • CarlD
        CarlD
        46 Posts
        ACCEPTED ANSWER

        Re: Web Experience Factory JAXB generated web services problem

        ‏2013-01-31T15:36:00Z  in response to saikiran
        I stumbled on your post and just wanted to mention that we've been using custom java web services on our project for a while with minimal annotations (no JAXB annotations required). I even blogged about it a few years ago here:

        http://dsixe-wpf.blogspot.com/2010/11/creating-web-services-for-portlet.html

        I'm not sure if this is similar to what your project is using, but it works great for us.

        Just FYI. Carl.

        IBM Certified Solution Developer - WebSphere Portlet Factory 7.0
        My blog http://dsixe-wpf.blogspot.com