Hi,

yes, i understand. In that case we have to integrate wink in to carbon
platform at the code level. I did a POC around this sometime back.
There we registered the wink servlet using HTTPService. The deployment
should be done programatically.

If the component is the deployment model, we can deploy the service
classes to the wink engine, using a similar approach we use in axis2
service deployment. (by looking at a manifest header to identify the
service).

Even that, I can't figure out how we can provide basicauth,etc stuff.

SCIM standalone version used the above approach, AFAIK.

--Pradeep
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to