Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: for the plan.

Jump to: navigation, search


< Lyo


What is OSLC4J?

OSLC4J is a Java toolkit for building Open Services for Lifecycle Collaboration providers and consumers. It includes:

  • annotations to decorate Java objects with OSLC attributes
  • annotations to assist with resource preview UIs (compact rendering)
  • built-in support for service provider and resource shape documents
  • libraries to simplify service provider and consumer development
  • sample applications, including an OSLC Registry (catalog) application and a Change Management provider implementation
  • Tests for the sample applications to complement the Lyo OSLC Test Suite

Getting started with OSLC4J

  1. Setup the Eclipse environment for Lyo-based development
  2. Create an initial REST server application, ready for Lyo-based development
  3. Use Lyo Designer to model a single server or complete toolchain and generate an initial code base

JARs are no longer available for download since Lyo 2.1.0. All artefacts are available through Eclipse Maven repos linked above. Lyo Designer is available through an Eclipse download site.

Using in Maven

Be sure to add Eclipse Maven repositories in your POM file before adding OSLC4J dependencies:

        <name>Eclipse Lyo Releases</name>
        <name>Eclipse Lyo Snapshots</name>


  • OSLC4J - The core component providing OSLC annotation and model support (org.eclipse.lyo.oslc4j.core / oslc4j-core)
  • Apache Jena Provider - A library to assist with serialization/de-serialization of OSLC-annotated Java objects to/from RDF XML (org.eclipse.lyo.oslc4j.core / oslc4j-jena-provider).
  • Apache Wink Json4J Provider - A library to assist with serialization/de-serialization of OSLC-annotated Java objects to/from JSON (org.eclipse.lyo.oslc4j.core / oslc4j-json4j-provider).
  • Apache Wink JAX-RS Provider - Utility classes, including an OSLC REST Client, to facilitate development using the Apache Wink JAX-RS implementation.

The Apache Jena and Apache Wink components are the built-in providers for RDF, RDF XML, JSON and JAX-RS. Additional providers could be implemented using technologies such as OpenRDF and Jersey.

Sample code

Annotation sample

    //sample simple string attribute (dcterms:description, as in
    @OslcDescription("Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content.")
    @OslcPropertyDefinition(OslcConstants.DCTERMS_NAMESPACE + "description")
    public String getDescription()
        return description;
    //sample relationship attribute (oslc_cm:affectsTestResult, as in
    @OslcDescription("Associated QM resource that is affected by this Change Request.")
    @OslcPropertyDefinition(Constants.CHANGE_MANAGEMENT_NAMESPACE + "affectsTestResult")
    @OslcTitle("Affects Test Results")
    public URI[] getAffectsTestResults()
        return affectsTestResults.toArray(new URI[affectsTestResults.size()]);

JAX-RS method sample

This illustrates implementation of an OSLC-CM (REST) server/provider

    //support GET for a specific OSLC ChangeRequest
    @Produces({OslcMediaType.APPLICATION_RDF_XML, OslcMediaType.APPLICATION_XML, OslcMediaType.APPLICATION_JSON})
    public ChangeRequest getChangeRequest(@Context                      final HttpServletResponse httpServletResponse,
                                          @PathParam("changeRequestId") final String              changeRequestId)
        final ChangeRequest changeRequest = Persistence.getChangeRequest(changeRequestId);
        if (changeRequest != null)
            setETagHeader(getETagFromChangeRequest(changeRequest), httpServletResponse);
            return changeRequest;
        throw new WebApplicationException(Status.NOT_FOUND);
    //support POST to create a new ChangeRequest
    @Consumes({OslcMediaType.APPLICATION_RDF_XML, OslcMediaType.APPLICATION_XML, OslcMediaType.APPLICATION_JSON})
    @Produces({OslcMediaType.APPLICATION_RDF_XML, OslcMediaType.APPLICATION_XML, OslcMediaType.APPLICATION_JSON})
    public Response addChangeRequest(@Context final HttpServletRequest  httpServletRequest,
    		                         @Context final HttpServletResponse httpServletResponse,
                                              final ChangeRequest       changeRequest)
           throws URISyntaxException
        final long identifier = Persistence.getNextIdentifier();
        final URI about = new URI(httpServletRequest.getScheme(),
                                  httpServletRequest.getContextPath() + "/changeRequests/" + identifier,
        final Date date = new Date();
        setETagHeader(getETagFromChangeRequest(changeRequest), httpServletResponse);
        return Response.created(about).entity(changeRequest).build();

See also

Back to the top