gt;>> REST service artifact* through the Governance Center Publisher.
>>>
>>> Currently, there is no media type handler to handle manually added rest
>>> service artifacts through the publisher and these are handled by the
>>> default handler. That's
Hi Madawa,
IMO, we do not need a separate media type handler for this. Reason being a
media type handler for a REST call doesn't seem correct. Rather what we
need is a method to take the URL etc to utilize the methods in WADL and
swagger processor. WDYT??
Using existing swagger and WADL processor
-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Shazni Nazir;X-NUM-GUESTS=0:mailto:sha...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=Vijitha Kumara;X-NUM-GUESTS=0:mailto:viji...@wso2.com
ATTENDEE;CUTYPE=RESOURCE;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP
-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=Senaka Fernando;X-NUM-GUESTS=0:mailto:sen...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Shazni Nazir;X-NUM-GUESTS=0:mailto:sha...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION
=
TRUE;CN=Sameera Perera;X-NUM-GUESTS=0:mailto:samee...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
;CN=Shazni Nazir;X-NUM-GUESTS=0:mailto:sha...@wso2.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
TRUE;CN=Kishanthan
