Fwd: WADL Parser

[Alex O'Ree <sp...@gmail.com>]

Some related info for WADL2UDDI integration

---------- Forwarded message ----------
From: Reihaneh Rabbany <ra...@cs.ualberta.ca>
Date: Wed, May 22, 2013 at 2:41 PM
Subject: Re: WADL Parser
To: Alex O'Ree <sp...@gmail.com>


Dear Alex,

Thanks for your email. I will actually be very happy if my code be
included in an Apache project.

This is a code I implemented for one of my graduate course projects
about three years ago.
And there is no updated version or active development on it (the only
update is our published paper which is based on results from that
project).
In fact the project was coded very hastily, in 3 days or so, therefore
use it with caution.
It also does not include any automatic build like maven but all
required libraries are included in the dependencies/.

Let me know if you have any other questions,

Cheers,
--
Reihaneh Rabbany
Graduate Research Assistant and PhD student,
Department of Computing Science,
University of Alberta,
Edmonton, AB,
Phone: +1 (780) 710 - 3943
http://cs.ualberta.ca/~rabbanyk/


On Wed, May 22, 2013 at 5:26 AM, Alex O'Ree <sp...@gmail.com> wrote:
>
> Reihaneh Rabbany,
>
> I found your website via a google search for "WADL Parser". I'm
> currently work on the Apache Software Foundation project called jUDDI
> (http://juddi.apache.org). It's an open source web service registry
> based on the OASIS standard from circa 2005. Long story short, I'm
> considering using your code to help facilitate the automated
> registration of REST based services into the registry. I do have a few
> questions.
> 1) Are you ok with using your code in an Apache project?  It looks
> like its BSD licensed so there's no licensing issue.
> 2) Is the latest version published in the website or is it in version
> control elsewhere? For reference, I found it here
> http://webdocs.cs.ualberta.ca/~rabbanyk/research/WS/
> 3) I don't see any build specific files, such as a pom or build.xml.
> This leads me to believe that there's no maven artifacts published
> anywhere. Is that correct?
> 4) What is the current status of the parser? (active development,
> stable, testing, etc)
>
> Thanks for your time
>
> Alex
>