[Wtp-wst-dev] Project granularity

["Dave Carlson" <dcarlson@xxxxxxxxxxxxxxx>]

Has there been any discussion about project granularity in WTP?  I can
understand the rationale for most of the plug-in divisions in the original
IBM contribution, which has ~150 plug-ins, but wonder if this is
necessary/desirable?

For example, there are 13 plug-ins for document validation, whereas the
entire JDT consists of only 6 plug-ins (ignoring documentation).  Separate
plug-ins are provided for xml, dtd, xsd, mof, html, wsdl, ear, and ejb doc
types.  This small granularity would enable updating specific doc types
(e.g. HTML) separate from others (e.g. DTD or XML).  But updating small
modules is rare in practice.

I recall an earlier comment/question about possibly absorbing the tabbed
property view (used in the XSD editor and others) into the Eclipse core.
This will likely be used outside of WTP.  For now, I merged
com.ibm.xtools.common.ui.properties into org.eclipse.wtp.ui plug-in, but if
it may be added to Eclipse core in 3.1, but we should keep it separate.

I've successfully migrated the XSD editor into the new package structure in
CVS.  The consensus is to wait for IBM's refresh before committing anything
to CVS, but is anyone else interested in an XSD editor that works with M1?
There is still no validation (of XSD docs or XML against an XSD).  If the
code refresh is still a few weeks away, I'll probably migrate the validation
plug-ins to the new WTP packages also.

Regards,
  Dave Carlson
  http://www.XMLmodeling.com