Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Lyo/TRSWorkshop"

< Lyo
m
m (Introduction)
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
'''* DRAFT IN PROGRESS *'''
+
= Tracked Resource Set Provider for Bugzilla Workshop  =
 
+
= Tracked Resource Set(TRS) Provider for Bugzilla Workshop  =
+
  
 
== Setup  ==
 
== Setup  ==
Line 14: Line 12:
 
== Introduction  ==
 
== Introduction  ==
  
This workshop will focus on the implementation of Tracked Resource Set provider. It is intended to provide a foundation in the skills required for developing Tracked Resource Set Provider implementations.
+
This workshop will focus on the implementation of Tracked Resource Set (TRS) provider. It is intended to provide a foundation in the skills required for developing Tracked Resource Set Provider implementations.  
  
As the TRS is based on OSLC, this workshop is designed as the supplement for the workshop [[Lyo/OSLCWorkshop|WKSP-1875 OSLC Enable Your Tool in a Day]] and depends on its OSLC provider/consumer functions.
+
As the TRS is based on OSLC, this workshop is designed as the supplement for the workshop [[Lyo/OSLCWorkshop|OSLC Workshop]] and depends on its OSLC provider/consumer functions.
 +
 
 +
'''NOTE: ''' There are two versions of the TRS workshop. One is based on a draft version of the OSLC Tracked Resource Set specification (see [[Lyo/TRSSDKPreview|Tracked Resource Set Technical Preview]]) and another is based on the latest specification. Please refer to [[Lyo/BuildTRS4JBugzilla|Building and running the TRS Adapter for Bugzilla sample]]
  
 
== Learning Objectives  ==
 
== Learning Objectives  ==
Line 22: Line 22:
 
This workshop leads you to go through steps to enable Bugzilla as Tracked Resource Set Provider, which is an already-working implementation. This will make Bugzilla capable of sending Change Logs.  
 
This workshop leads you to go through steps to enable Bugzilla as Tracked Resource Set Provider, which is an already-working implementation. This will make Bugzilla capable of sending Change Logs.  
  
It is built on top of [[Lyo/BuildOSLC4JBugzilla|OSLC-CM compatible adapter]] which implements OSLC Change Management(CM) provider, it is recommended to try [[Lyo/OSLCWorkshop|WKSP-1875 OSLC Enable Your Tool in a Day]] first. The basic understanding of CM provider is also required for this workshop.  
+
It is built on top of [[Lyo/BuildOSLC4JBugzilla|OSLC-CM compatible adapter]] which implements OSLC Change Management(CM) provider, it is recommended to try [[Lyo/OSLCWorkshop|OSLC Workshop]] first. The basic understanding of CM provider is also required for this workshop.  
  
 
Once you will complete this workshop, you will have the fundamental skill of&nbsp;:  
 
Once you will complete this workshop, you will have the fundamental skill of&nbsp;:  
Line 29: Line 29:
 
*The extension of OAuth implementation  
 
*The extension of OAuth implementation  
 
*OSLC resources definition for TRS
 
*OSLC resources definition for TRS
 +
 +
== Questions ?  ==
 +
* Open a new [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Lyo Lyo Bugzilla ticket] if you will find bugs or have enhancement requests.
 +
* For the discussion, you can join [https://dev.eclipse.org/mailman/listinfo/lyo-dev Lyo mailing lists] or [http://www.eclipse.org/forums/index.php/f/228/ Eclipse Community Forums for Lyo].

Latest revision as of 22:15, 24 February 2014

Tracked Resource Set Provider for Bugzilla Workshop

Setup

Please refer to Building and running the TRS Adapter for Bugzilla sample

Prerequisite

  • Java, JavaScript, Java Servlet, Java Server Pages (JSP), HTML and JAX-RS Web Services programming experience
  • Basic understanding of Resource Description Framework (RDF), Open Services for Lifecycle Collaboration (OSLC http://open-services.net/) and OAuth (http://oauth.net/core/1.0/)

Introduction

This workshop will focus on the implementation of Tracked Resource Set (TRS) provider. It is intended to provide a foundation in the skills required for developing Tracked Resource Set Provider implementations.

As the TRS is based on OSLC, this workshop is designed as the supplement for the workshop OSLC Workshop and depends on its OSLC provider/consumer functions.

NOTE: There are two versions of the TRS workshop. One is based on a draft version of the OSLC Tracked Resource Set specification (see Tracked Resource Set Technical Preview) and another is based on the latest specification. Please refer to Building and running the TRS Adapter for Bugzilla sample

Learning Objectives

This workshop leads you to go through steps to enable Bugzilla as Tracked Resource Set Provider, which is an already-working implementation. This will make Bugzilla capable of sending Change Logs.

It is built on top of OSLC-CM compatible adapter which implements OSLC Change Management(CM) provider, it is recommended to try OSLC Workshop first. The basic understanding of CM provider is also required for this workshop.

Once you will complete this workshop, you will have the fundamental skill of :

  • TRS service REST API implementation
  • The extension of OAuth implementation
  • OSLC resources definition for TRS

Questions ?

Back to the top