This content has been marked as final. Show 1 reply
Very interesting idea. Below are quoted from the original place:
Lockup support of servicecontracts both in design- and runtime
Adminstarte service registry/repository containing servicecontract and
other metadata of interest including user acess control and authorization(WS-policy based, XACML)
This is definitely what SOA Repository is aiming to provide
WS-Policy or correspondant support for implicit autentication and authorization of systems or services
This is part of "runtime" supports that SOA Repository is going to provide: i.e., runtime policy enforcement etc.
Scheduled publising/unpublishing of wenbservices without need for restart
Adjust opening hours for services(service activation)
Firstly, JBOSS ESB has to support starting/stoping services without redeployment. As far as I know, this feature is not in place yet. Secondly, to avoid overlap with JON, SOA Repository may need to do the service scheduling through JON. But of course, we need to discuss where to store service scheduling information (like when to start the service, how long to run the service etc). Shall we store this info as metadata in SOA Repository or in JON.