Long promised wsdl file

RT Developers
1

Hey all,

I’ve got some rudimentary external task integration working with
Insectivore, and the result of my web services experimentation may be
found in the attached wsdl file.

Basically, it advertises two methods,

Task[]  getAllTasksForUser(String)
Task    getTaskForId(String)

The Task complex type is holder class that contains all the information
Insectivore uses to populate it’s own IDE tasks. RT has a much richer
task definition, but this the ideal packet of info for us. For clarity,
a Task is:

Task
   int     assignedTo
   String  description
   int     id
   Link[]  links
   String  module
   Note[]  notes
   int     severity
   int     state
   User    submitter
   User[]  subscribers
   String  summary

Link
   String name
   String url
   String description

User
   String name
   String email

Note
   User   author
   Date   date
   String text

I cooked up a dummy mysql backend–if you’d like the create/populate
scripts, I can send those too.

The URLs will all have to be changed to the web service URL for RT, ex.

     <wsdlsoap:address

location=“http://localhost:8080/axis/services/RTAccess”/>

Let me know what you think.

Todd

PS please cross-post to zclipse-devel@lists.sourceforge.netOn Wed, Mar 19, 2003 at 12:26:00PM -0500, Michael R Head wrote:

On Wed, 2003-03-19 at 01:03, Jesse Vincent wrote:

Is now out. I think this finally resolves the perf issues folks were
seeing with rc1 and rc2.

Is RT3.0 intending to have a SOAP/web svcs interface? Alternatively,
what extension points does RT3 have that are network accessible? I
checked in the docs and the RT/FM, but didn’t find anything obvious.

As previously discussed on rt-devel (And I thought cced to
zclipse-devel), we’re working on a REST-based API for RT 3.0.x, but it’s
not making it into 3.0.0, as the developer’s rather late in delivering.
I’d thought that one of the zclipse folks was going to work on putting
together a WDSL spec for a SOAP api that we could then look at
implementing.

    Best,
    Jesse

rtaccess.wsdl (5.74 KB)

2

So you know, this hasn’t been ignored. I’ve actually got an RT SOAP
server sending out tickets and searches in response to queries. I’m
currently attempting to build up a proper WSDL file for the xml we’ll be
sending and recieving (sadly, perl’s SOAP::Lite implementation only has
the absolute minimum of contact with WSDL, so I basically have to define
everything twice :confused:

-jOn Sat, Apr 05, 2003 at 12:14:54PM -0500, Todd Chambery wrote:

Hey all,

I’ve got some rudimentary external task integration working with
Insectivore, and the result of my web services experimentation may be
found in the attached wsdl file.

Basically, it advertises two methods,

Task getAllTasksForUser(String)
Task getTaskForId(String)

The Task complex type is holder class that contains all the information
Insectivore uses to populate it’s own IDE tasks. RT has a much richer
task definition, but this the ideal packet of info for us. For clarity,
a Task is:

Task
int assignedTo
String description
int id
Link links
String module
Note notes
int severity
int state
User submitter
User subscribers
String summary

Link
String name
String url
String description

User
String name
String email

Note
User author
Date date
String text

I cooked up a dummy mysql backend–if you’d like the create/populate
scripts, I can send those too.

The URLs will all have to be changed to the web service URL for RT, ex.

    <wsdlsoap:address

location=“http://localhost:8080/axis/services/RTAccess”/>

Let me know what you think.

Todd

PS please cross-post to zclipse-devel@lists.sourceforge.net

On Wed, Mar 19, 2003 at 12:26:00PM -0500, Michael R Head wrote:

On Wed, 2003-03-19 at 01:03, Jesse Vincent wrote:

Is now out. I think this finally resolves the perf issues folks were
seeing with rc1 and rc2.

Is RT3.0 intending to have a SOAP/web svcs interface? Alternatively,
what extension points does RT3 have that are network accessible? I
checked in the docs and the RT/FM, but didn’t find anything obvious.

As previously discussed on rt-devel (And I thought cced to
zclipse-devel), we’re working on a REST-based API for RT 3.0.x, but it’s
not making it into 3.0.0, as the developer’s rather late in delivering.
I’d thought that one of the zclipse folks was going to work on putting
together a WDSL spec for a SOAP api that we could then look at
implementing.

   Best,
   Jesse

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.