Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] Integration of Service Creation with Policy Editor planned for Ganymede release
1. How we will manage policy files in service project (JAX-WS) and how policies will mapped to service? 
   a) as separate files with .policy extension
In this case it is necessary to map policy files to wsdl (or individual operations/bindings in wsdl). Simple scenario could be just save policy files into service project and suppose that all of them will be automatically attached to service. 

I think we should be flexible about from where we discover
policies, so we could have .policy files, or we could introspect
WSDL files that have policy attachments for example.

Also, we shouldn't assume that there will be only one 'service' in an
eclipse project - this would only be one way to approach the development. 

The important thing is to be able to see the policies and discover
what entities they apply to. I think it would be very useful if we
could have some kind of extension to the project explorer that would
show the policies in a virtual folder or some such, or even better,
perhaps the things-that-can-support-policies can have their own
virtual representation in the project explorer, and the policies
can be shown as being contained by them.

I think I am leading up to some kind of common project model here :)

If we take the model of your SOA development from STP-IM, and then
create a way to visualize that model in the project explorer, that
could give us a lot of freedom in terms of coupling the entities
like services, policies, processes, to code - even allowing us to
create introspectors that will populate the SOA project model from
existing projects.


2. Will we support Policy Repository for Ganymede?
   a) File System based implementation;
   b) DB based implementation;
c) no Policy Repository, just policy files saved in service project (JAX-WS). 

For Ganymede my guess would be to design an extension point to allow
different implementations, and produce a policy repository view that
will permit browsing and selection of policies. We should probably
just commit to a file based implementation as an example - or an
EFS implementation, or even just the local project :)


4. What kind of policy validation we will implement for Ganymede?
   a) simple schema validation;
   b) rule-based validation;
   c) validation framework based solution.
I suggest to keep the first iteration as simple as possible: manage policy files in service project only; provide schema based validation; store custom assertion XML schemas in service project; do not support Policy Repository. When we will have first integrated solution, it could be extended by additional features and functionality. 
What is your opinion?


Simple is good - at this point we should be looking at providing and
refining extension points for these storage and validation options.
Once those are in place we can provide the simplest of exemplars,
and we will have created a platform to which others may add should
they wish to do so.

I still like the unified project model, though, any thoughts?

  best regards
   Oisin

----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland

Back to the top