Re: [stp-dev] Look and feel proposal for integration of XEF and WTP-base

[Andrei Shakirin <andrei.shakirin@xxxxxxxxx>]

Hi David,

Absolutely agree! 
I also would like to avoid direct dependencies between WTP and XEF editors.
Just another name suggestion: "org.eclipse.stp.policy.common", because this stuff relates not only to XEF editor, but to STP policy framework as whole.

Our detail editor interfaces and schema provider classes could be located in different packages of this plugin module.

Regards,
Andrei.

----- Original Message -----
From: "David Bosschaert" <davidb@xxxxxxxx>
To: "STP Dev list" <stp-dev@xxxxxxxxxxx>
Sent: Dienstag, 15. Januar 2008 17.44 Uhr (GMT+0100) Europe/Berlin
Subject: Re: [stp-dev] Look and feel proposal for integration of XEF and	WTP-based policy editors

Hi Andrei,
> 2) I put ISchemaProvider interface also in the same package now.
>    For the future I suggest to create separate plugin module containing schemas provider and policy repository stuff (ISchemaProvider, ISchemaProviderExt, URLSchemaProvider, etc). It helps to avoid circular dependencies between editors and allows to use the stuff from other modules (not only our editors).
>   
This makes sense to me. Esp since there are people who use the XEF 
editor on its own already and I don't think they should be forced to 
depend on the WTP policy editor plugins if they don't use that piece.
I would be happy to create an interfaces-only plugin for the ones used 
by the XEF editor. It could be called
  org.eclipse.stp.xef.common
This would allow to have the dependencies only go one way. Would that 
work for you?

Cheers,

David

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