Interface with Jazz with REST or with the Java APIs ?

Adil Chahid (455●2●41●18) | asked Mar 26 '09, 5:50 p.m.

Hi all,
In the company I work for, we're trying to interface a ticketing system with RTC.

We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.

It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?

For instance, it doesn't seem that it supports attachements:

https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems




Create an attachment &#91;not released yet&#93;



JAZZ=projectareas/_vC_OAGt4Ed2yGaLMUWzhyA

curl -D - -k -b $COOKIES -F projectArea=$JAZZ -F content=@$1 $BASE/attachments

We have to transfer attachements from our current ticketing system to RTC.

Which of the two ways should we follow to interface RTC for version 2.0 ?

We thank you in advance for your time.

3 answers

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Susan Wu (471●21●16) | answered Mar 27 '09, 1:11 p.m.

Hi all,
In the company I work for, we're trying to interface a ticketing system with RTC.

We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.

It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?

For instance, it doesn't seem that it supports attachements:

https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems
Create an attachment &#91;not released yet&#93;



JAZZ=projectareas/_vC_OAGt4Ed2yGaLMUWzhyA

curl -D - -k -b $COOKIES -F projectArea=$JAZZ -F content=@$1 $BASE/attachments
We have to transfer attachements from our current ticketing system to RTC.

Which of the two ways should we follow to interface RTC for version 2.0 ?

We thank you in advance for your time.

Hi Adil,

We are trying to collect answer for your above concern. Please stay tuned.

Susan

permanent link

Todd Lainhart (406●1●1) | answered Mar 27 '09, 1:16 p.m.
FORUM MODERATOR / JAZZ DEVELOPER

I assume that your integration is client code that's communicating with the Jazz server, as opposed to a Jazz server extension.

The Java APIs in RTC 1.0 are stable and will continue to be supported in future releases. The REST APIs in RTC 1.0 are not stable, and are expected to change.

-- Todd

Todd Lainhart
Jazz Foundation

Hi all,
In the company I work for, we're trying to interface a ticketing system with RTC.

We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.

It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?

For instance, it doesn't seem that it supports attachements:

https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems
Create an attachment &#91;not released yet&#93;



JAZZ=projectareas/_vC_OAGt4Ed2yGaLMUWzhyA

curl -D - -k -b $COOKIES -F projectArea=$JAZZ -F content=@$1 $BASE/attachments
We have to transfer attachements from our current ticketing system to RTC.

Which of the two ways should we follow to interface RTC for version 2.0 ?

We thank you in advance for your time.

permanent link

Andre Weinand (481●1) | answered Mar 30 '09, 9:24 a.m.

I suggest to use the Java APIs since they already provide the necessary functionality.
The REST API will evolve for 2.0 to support the OSLC specification for Change Management, but this does not yet include attachment support.

--andre weinand
Jazz Work Items Team Lead

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

It's all about the answers!

Related questions

Interface with Jazz with REST or with the Java APIs ?

3 answers

Your answer