[OSLC] Generating language bindings for the OSLC interfaces

Arthur Ryman ryman at ca.ibm.com
Wed Feb 3 09:35:56 EST 2010


Andy,

For approach b) yu need to describe the REST API in a machine processible 
format. There are two formats I know of - WADL and WSDL 2.0.

There is a community around WADL, largely at java.net.

 I worked on the WSDL 2.0 spec at W3C and advocated for features that 
allowed it to describe REST APIs, not just SOAP. The Apache Axis 2.0 
project supports WSDL 2.0 and can generate Java bindings. However, I don't 
know if anyone is using it for REST. I worked with Lawrence Mandel on the 
Apache Woden project which created a WSDL 2.0 reference implementation 
which was picked up by Apache Axis 2.0. Lawrence wrote up an article 
describing how to describe REST services using WSDL 2.0. [1] There are 
also examples at the W3C WSDL 2.0 site.

If someone wanted to explore this approach it could be done independantly 
of OSLC, i.e. someone could write the WADL or WSDL 2.0 description and try 
to generate code.

[1] http://www.ibm.com/developerworks/webservices/library/ws-restwsdl/

Arthur Ryman, IBM DE
Chief Architect, Rational Project and Portfolio Management
Office: 905-413-3077, Cell: 416-939-5063
Assistant: Nancy Barnes, 905-413-4182 



From:
Andrew J Berner <ajberner at us.ibm.com>
To:
community at open-services.net
Date:
02/03/2010 07:00 AM
Subject:
[OSLC] Generating language bindings for the OSLC interfaces
Sent by:
community-bounces at open-services.net




To use the OSLC interfaces effectively, client programmers need an easy 
way
to get 3GL language bindings to program against the interface.  In
practice, most ALM tools, which are the prime candidates to use the
interfaces, would benefit from either a Java or C# binding.  I can imagine
two ways of getting these bindings:

a) For each interface, someone in the community, or a group of members,
produce the binding by hand and maintain it as the interface evolves

b) Clients use a set of commonly available tools to generate bindings

Can someone from each workgroup comment, please, on how this can be
addressed for the interface under development?  Which language bindings 
are
of interest (testing my hypothesis that Java and C# will suffice for most
of the community)?

Andy Berner
Lead Architect, ISV Technical Enablement and Strategy
IBM Rational Business Development
972 561-6599
ajberner at us.ibm.com

Ready for IBM Rational software partner program -
http://www.ibm.com/isv/rational/readyfor.html


_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20100203/22191c72/attachment.html>


More information about the Community mailing list