After looking at the responses on this
subject, from the validation component side I suggest a splitting of plugins
here as needed rather than moving the validation plugins with JDT dependency
from WST to JST. We can have 2 flavor's where one flavor of the plugin
is with JDT dependency and one without. The one with JDT dependency lives
in JST and the one without lives in WST.
<dcarlson@xxxxxxxxxxxxxxx> Sent by: wtp-dev-admin@xxxxxxxxxxx
11/12/2004 01:33 PM
Please respond to wtp-dev
RE: [wtp-dev] should WST have references
We need to be more specific than
"no JDT requred by WST". I am very interested in mapping
XML/XSD/WSDL to/from Java and expect that JDT will be very useful here.
But it's important (to my use cases) that these features be available
in an optional feature. It should be possible to package up a set
of features/plugins that provide XML/XSD editing and validation that runs
on the core Eclipse platform, without JDT.
From: wtp-dev-admin@xxxxxxxxxxx [mailto:wtp-dev-admin@xxxxxxxxxxx]
On Behalf Of Arthur Ryman
Sent: Friday, November 12, 2004 11:01 AM
Cc: wtp-dev@xxxxxxxxxxx; wtp-dev-admin@xxxxxxxxxxx
Subject: Re: [wtp-dev] should WST have references to JDT?
I agree in principal. Any generic function should be moved into the platform.
However, some tools may be generating Java, even in WST. Not all Java related
function is in J2EE. For example, what about XSD to Java generators? They
are not necessarliy in J2EE so they should be in WST. Or the reverse, generation
of XML from Java. You might want to access a Java model or some function
that is in JDT.