facebook

confluence search api – not supported (closed)

  1. MyEclipse Archived
  2.  > 
  3. Web Services
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #257638 Reply

    Dianne Silva
    Member

    Hi, we have a Confluence web service that we want to access from MyEclipse in a simple java client.

    Any idea what code we need from the XFire layer to instantiate a remote web service correctly?

    The remote web service is this: http://confluence.atlassian.com/rpc/soap-axis/confluenceservice-v1?wsdl

    thanks,
    Bruce

    #257678 Reply

    Brian Fernandes
    Moderator

    Bruce,

    Have you tried our top down Web Service wizard? You can invoke this wizard from the Eclipse toolbar and then choose the Top-down scenario. Point it to the wsdl url above to generate web service classes and a sample test client.

    Hope this helps,
    Brian.

    #257712 Reply

    Dianne Silva
    Member

    Hi Brian, we’ll try that next. Dan Diephouse wrote back from xfire, he says the issue is with confluence’s wsdl so nothing wrong with xfire regarding this issue.

    thanks,
    Bruce
    ===========================================

    Dan, thanks for the clarification. I didn’t realize confluence’s wsdl was the problem. We’ll just avoid the dynamic client with their current web service.

    thanks,
    Bruce

    On 8/27/06, Dan Diephouse (JIRA) <jira@codehaus.org> wrote:

    [ http://jira.codehaus.org/browse/XFIRE-599?page=all ]

    Dan Diephouse closed XFIRE-599.
    ——————————-

    Resolution: Won’t Fix

    There are two problems with the confluence wsdl which make it non-basic profile conformant (see http://www.ws-i.org for more information about the Basic Profile – it is basically a standard which tells you how to build correct web services).
    1. It uses RPC-Encoding which is deprecated
    2. It has multiple operations with the same name, which isn’t allowed in the basic profile.

    We may support these in the future, but I believe there are already issues for these.

    > exception in dynamic client when wsdl contains method named “search”
    > ——————————————————————–
    >
    > Key: XFIRE-599
    > URL: http://jira.codehaus.org/browse/XFIRE-599
    > Project: XFire
    > Issue Type: Bug
    > Components: Core
    > Affects Versions: 1.1.2
    > Environment: winxp sp2
    > Reporter: Bruce Krasnof
    > Assigned To: Dan Diephouse
    >
    > Trying to do a dynamic client with confluence’s remote soap api, but a soap “search” method is causing a conflict I think.
    > This line raises an exception:
    > Client client = new Client(new URL(“http://confluence.atlassian.com/rpc/soap-axis/confluenceservice-v1?wsdl&#8221;));
    > exception: An operation with name [search] already exists in this service
    > thanks,
    > Bruce


    This message is automatically generated by JIRA.

    If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa

    For more information on JIRA, see: http://www.atlassian.com/software/jira

Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: confluence search api – not supported (closed)

You must be logged in to post in the forum log in