Admin service WSDL fix the contract between the actual service
implementation and the client.
If you take ServiceProviderRegistration service in IS - then the
Service Provider Registration UI is one client - and also App Manager
is another client. There can be many clients as well.
Right now we
Hi Prabath,
Great idea,
This will loosen the dependency between the admin service and the admin
service clients. So the admin services can evolve easily, as new features
come under a different version tag and existing functionalities are not
effected.
But we have to have some policies to
Hi Fathima,
Regarding project names, I can see below options based on your document.
1. If the project name is already taken, let user to come up with another
project name.
2. Treat applications as jira project components.
3. Append the tenant domain to the project name.
If we need to multi
AFAIK the $subject is not working today.
Can we please get that fixed...? This would lead us to many more
useful integration patterns...
--
Thanks Regards,
Prabath
Twitter : @prabath
LinkedIn : http://www.linkedin.com/in/prabathsiriwardena
Mobile : +1 650 625 7950
Hi Pulasthi,
you mentioned only BPS/BPEL-engine. What about the
BPS/BPMN-activiti-engine? Should it not a prefered way to define workflows?
best regards
Manfred
2015-04-04 14:40 GMT+02:00 Pulasthi Mahawithana pulast...@wso2.com:
Hi Frank,
I sent a separate mail[1] with the architecture. Our
