[
https://jira.jboss.org/jira/browse/JBESB-2285?page=com.atlassian.jira.plu...
]
Kevin Conner commented on JBESB-2285:
-------------------------------------
Daniel, we want all the feedback we can get but JIRA is not the correct place to discuss
it.
JIRA drives our workload and needs to be specific with respect to what is required so that
we can understand and deal with it.
If you have a specific request or bug report to file then please do so. If it is a
general comment then the forums will allow us to discuss the issues further and provide
visibility for others who may be interested.
I am not trying to dissuade you from providing feedback.
Kev
Service Repository support not Servicen Registry cause it is provide
by JUDDI
-----------------------------------------------------------------------------
Key: JBESB-2285
URL:
https://jira.jboss.org/jira/browse/JBESB-2285
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.4
Environment: JBoss ESB 4.4 or SOA Platform 4.3
Reporter: Daniel F?rberg
Fix For: 4.x
Attachments: techneutralsynchbus.jpg
Actually i was at the partner talk about JBoss ESB at Devoxx 08 in Antwerp. And some
questions
about the support the ws-stack and Service Repositories which provides an Api that can
fullfill
som of our customers needs regarding implementation of SOA. I spoke to an representative
in
Exibition hall from France and got some information. It ended up here raising JIRA, as a
feature
request. The software Mark Little recomended was SOA Software which is a comercial
product.
We do only work with open source at the company i work for, so it's not an option.
Mark mention
little about the DNA project. I have been i contact with a local represnative here in
Sweden at
Redhat also. It ended up that i sucessfully created an overview architecture with WSO2
instead.
But were a little bit late, they already started the dev with Mule. I wanted to continue
with, as
long as they are not satisfied with Mule. We can meet up, cause we have the trust.
Anyhow back to require this customer have:
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)
WS-Policy or correspondant support for implicit autentication and authorization of
systems or services
Scheduled publising/unpublishing of wenbservices without need for restart
Adjust opening hours for services(service activation)
and i provide a sketch of the suggested solution:
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira