Web services interface

Hi all,

I’m working on a plugin for eclipse (www.eclipse.org) called Insectivore
(www.zclipse.org/projects/insectivore) that allows task sharing and
integration with the ide.

I’m very interested in hooking the Insect up to an external task service, is
there an ETA on the web service interface or maybe a WSDL doc? Also, do you
have a public demo I can hit to play around with?

Todd

BTW Jesse, I was the guy with Mike and Heather at the Diesel cafe in Davis
Square last w/e.

“He is a being, so brilliant yet so corrupt, which, like
a rotten mackerel by moonlight, stinks as it shines.”
- John Randolph, speaking of Henry Clay

Hi all,

I’m working on a plugin for eclipse (www.eclipse.org) called Insectivore
(www.zclipse.org/projects/insectivore) that allows task sharing and
integration with the ide.

I’m very interested in hooking the Insect up to an external task service, is
there an ETA on the web service interface or maybe a WSDL doc? Also, do you
have a public demo I can hit to play around with?

hmm… depending on requests i’ll start working on encapsulating RT
into SOAP (a python/gtk GUI using this SOAP interface may follow) so
that it is possible to access RT (at least partially) from webpages
written in PHP or Java or …

I’m very interested in hooking the Insect up to an external task service, is
there an ETA on the web service interface or maybe a WSDL doc? Also, do you
have a public demo I can hit to play around with?

hmm… depending on requests i’ll start working on encapsulating RT
into SOAP (a python/gtk GUI using this SOAP interface may follow) so
that it is possible to access RT (at least partially) from webpages
written in PHP or Java or …

The internal web-services API that we’re working on is going to be
REST-based. It’s based on simple GET/POST requests and squirts things
back to the client as RFC-822 formatted messages. It was designed to be
easy to implement and work with, even from simple shell scripts. We’re
expecting the initial version to be available within the next couple
weeks. That said, I’d be thrilled to see a prototype SOAP interface, with an eye
toward eventually providing it in core. Do you want to start with basic
ticket display/create/update?

Best,
Jesse

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

I’m very interested in hooking the Insect up to an external task service, is
there an ETA on the web service interface or maybe a WSDL doc? Also, do you
have a public demo I can hit to play around with?

hmm… depending on requests i’ll start working on encapsulating RT
into SOAP (a python/gtk GUI using this SOAP interface may follow) so
that it is possible to access RT (at least partially) from webpages
written in PHP or Java or …

The internal web-services API that we’re working on is going to be
REST-based. It’s based on simple GET/POST requests and squirts things
back to the client as RFC-822 formatted messages. It was designed to be
easy to implement and work with, even from simple shell scripts. We’re
expecting the initial version to be available within the next couple
weeks. That said, I’d be thrilled to see a prototype SOAP interface, with an eye
toward eventually providing it in core. Do you want to start with basic
ticket display/create/update?

that’s the plan.
first display, then create and then updating.

display is the most critical for me (using RT as a simple workflow
engine, interpreting custom fields as states and using the field values
to display the position of the ticket in the workflow). I’m no perl
hacker and i feel a lot more comfortable with other languages for GUI
programming. honestly, merging tickets and editing ticker relations
through the web interface is not very easy but i have no idea how it can
be done better through the web.

I’d be happy to take a crack at it, but my Perl skills are infantile–I
program almost entirely in Java :(. I could probably work on the web
services layer, though, and somebody would just have to cook up the Perl
service from the .wsdl.

ToddFrom: “Jesse Vincent” jesse@bestpractical.com
To: “Michael Lausch” mla+ml.rt-devel@lausch.at
Cc: “Todd Chambery” chambery@suppressingfire.org;
rt-devel@lists.fsck.com
Sent: Monday, March 10, 2003 5:15 PM
Subject: Re: [rt-devel] web services interface

I’m very interested in hooking the Insect up to an external task
service, is

there an ETA on the web service interface or maybe a WSDL doc? Also,
do you

have a public demo I can hit to play around with?

hmm… depending on requests i’ll start working on encapsulating RT
into SOAP (a python/gtk GUI using this SOAP interface may follow) so
that it is possible to access RT (at least partially) from webpages
written in PHP or Java or …

The internal web-services API that we’re working on is going to be
REST-based. It’s based on simple GET/POST requests and squirts things
back to the client as RFC-822 formatted messages. It was designed to be
easy to implement and work with, even from simple shell scripts. We’re
expecting the initial version to be available within the next couple
weeks. That said, I’d be thrilled to see a prototype SOAP interface, with
an eye
toward eventually providing it in core. Do you want to start with basic
ticket display/create/update?

Best,
Jesse


http://www.bestpractical.com/rt – Trouble Ticketing. Free.


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel

I’d be thrilled to see a decent WDSL spec for RT, since that’s the side
I’m really weak on. What’s out there right now for bug tracking/trouble
ticketing SOAP APIs? I expect that RT would end up supporting some
"standard" API, as well as a richer RT API.

-jOn Mon, Mar 10, 2003 at 05:59:53PM -0500, Todd Chambery wrote:

I’d be happy to take a crack at it, but my Perl skills are infantile–I
program almost entirely in Java :(. I could probably work on the web
services layer, though, and somebody would just have to cook up the Perl
service from the .wsdl.

Todd

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Keep me posted on your progress and let me know what you’d like me to do…

ToddFrom: “Michael Lausch” mla@lausch.at
To: “Jesse Vincent” jesse@bestpractical.com
Cc: “Todd Chambery” chambery@suppressingfire.org;
rt-devel@lists.fsck.com; zclipse-devel@lists.sourceforge.net
Sent: Tuesday, March 11, 2003 10:00 AM
Subject: [Zclipse-devel] Re: [rt-devel] web services interface

I’d be thrilled to see a decent WDSL spec for RT, since that’s the side
I’m really weak on. What’s out there right now for bug tracking/trouble
ticketing SOAP APIs? I expect that RT would end up supporting some
"standard" API, as well as a richer RT API.

I found a OSS Java Specification for Trouble Ticketing. It contains the
XSD files for the datatypes and an API spec for Java classes.
I’ll try to make up some simple WSDL files for this (and try to
understand the SOAP::Lite module :wink:

-j

I’d be happy to take a crack at it, but my Perl skills are
infantile–I

program almost entirely in Java :(. I could probably work on the web
services layer, though, and somebody would just have to cook up the
Perl

service from the .wsdl.

Todd


http://www.bestpractical.com/rt – Trouble Ticketing. Free.


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


Michael Lausch
See my web page http://www.lausch.at/ or query PGP key server for PGP
key.
“Reality is that which, when you stop believing in it, doesn’t go away”.
– Philip K. Dick


This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en


Zclipse-devel mailing list
Zclipse-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/zclipse-devel

Keep me posted on your progress and let me know what you’d like me to do…

It would be great to know when rt3.fsck.com has a SOAP interface, or at
least figure out what we need to do to get it to that point.

mike

Todd

----- Original Message -----
From: “Michael Lausch” mla@lausch.at
To: “Jesse Vincent” jesse@bestpractical.com
Cc: “Todd Chambery” chambery@suppressingfire.org;
rt-devel@lists.fsck.com; zclipse-devel@lists.sourceforge.net
Sent: Tuesday, March 11, 2003 10:00 AM
Subject: [Zclipse-devel] Re: [rt-devel] web services interface

I’d be thrilled to see a decent WDSL spec for RT, since that’s the side
I’m really weak on. What’s out there right now for bug tracking/trouble
ticketing SOAP APIs? I expect that RT would end up supporting some
"standard" API, as well as a richer RT API.

I found a OSS Java Specification for Trouble Ticketing. It contains the
XSD files for the datatypes and an API spec for Java classes.
I’ll try to make up some simple WSDL files for this (and try to
understand the SOAP::Lite module :wink:

-j

I’d be happy to take a crack at it, but my Perl skills are
infantile–I

program almost entirely in Java :(. I could probably work on the web
services layer, though, and somebody would just have to cook up the
Perl

service from the .wsdl.

Todd


http://www.bestpractical.com/rt – Trouble Ticketing. Free.


rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel


Michael Lausch
See my web page http://www.lausch.at/ or query PGP key server for PGP
key.
“Reality is that which, when you stop believing in it, doesn’t go away”.
– Philip K. Dick

Michael R. Head burner@zclipse.org
ZClipse.org: Building quality opensource plugins for Eclipse