Ticket #682 (closed issue: fixed)

Opened 14 years ago

Last modified 14 years ago

[M] Vocabserver API

Reported by: lawrence Owned by: rkl
Priority: desirable Milestone: PROD
Component: vocab Version:
Keywords: Cc:


The Vocabserver api is not very intuitive: the method parameters do not have meaningful names, e.g:

<oxy:searchVocab xmlns:oxy="urn:VocabServerAPI"

Can we consider a future version with meaningful names? It's pretty difficult to use wsdl analyser tools with it as it stands ...

Change History

comment:1 Changed 14 years ago by rkl

  • Status changed from new to assigned

Do you mean replace in0 by listKey, in1 by searchTerm, and in2 by termType, (the names I know the 3 parameters of searchVocab by)?

comment:2 Changed 14 years ago by lawrence

exactly so.

comment:3 Changed 14 years ago by rkl

Talked to Geoff about this and he reckoned that the WSDL would need manually editing to do this, which strikes me as far from ideal. Has Matt managed this automatically using Axis WSDL generation and if so, how?

comment:4 Changed 14 years ago by mpritcha

On the contrary (IMHO), what I've done with the DiscoveryService? is to *start* with the WSDL (...and the schema, in fact), write it manually and thereby define the interface, leaving me free to develop the actual backend as I see fit. So I write the WSDL, and generate the code from the WSDL using Axis2's WSDL2Java tool (and XMLBeans as the data binding). Happy to demonstrate this at some stage...

comment:5 Changed 14 years ago by rkl

  • Status changed from assigned to closed
  • Resolution set to fixed

I'm familiar with WSDL2Java for building client stubs. What we did is to set up the method calls as a java skeleton then use Java2WSDL (as demonstrated by Jon Blower on his Web Services course). Talking to Geoff, manual tidying of the WSDL shouldn't be an issue and we'll do it for V2. So, I'm closing this ticket.

Note: See TracTickets for help on using tickets.