[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [wtp-dev] WTP 1.0 project facets
- From: Naci Dai <naci.dai@xxxxxxxxxxxxx>
- Date: Sat, 05 Nov 2005 11:23:57 +0200
- Delivered-to: email@example.com
- Organization: Eteration
- User-agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
I would to keep the number of standard facets to a minimal, easy to
understand set. I am concerned about the potential abuse of the facet
concept every time we think we have something a little different. For
example, I could not understand all the ejb.modes they either need more
explanation for me to understand what they mean or a clearer design;
What is a development mode (jst.ejb.default, ejb.dev.mode)? I am
assuming it is not a mode to distinguish runtime/development but
xdoclet/vs another method for ejbs (i.e. beehive). It also seems the
facets are one-dimensional (i.e. xdoclet for web/ejb will require two
facets is this correct).
Along that line of thought, why should jstl need an additional facet,
should it be default capability with jst.web facet with proper version.
Struts on the other hand can have a facet (as it is not a standard
technology), but as Arthur pointed out, it is outside our scope.
Finally, the concept of a facet is not much different than eclipse base
project natures (now that we do not have multiple modules/project). Like
the natures and from a usability point-of-view, they should not be
something that is exposed to users freely in all tools. Facets are too
abstract for a user (compared to a server or an html file). Most users
will not care what facets are for as long as the tools do the work for
them. If this is what we mean by presets, I am all for it. Maybe, facet
pages of the wizards should be optional .
I guess what I am suggesting is facets should be an API level concept
(as opposed to User tool level). We should take extra care when we add
new ones, and expose them to the users when there is no need to do so.
First draft of a document describing the project facets that will be
in WTP 1.0 is available at
Â the ejb-related facets are just a proposal at this point
Â the Runtime Components list is incomplete, id strings may change
Â Presets will probably be added
Â no web service-related facets in there yet
Â should WTP 1.0 include facet ids for Struts, JSTL, â ?
Also note that this is not a developerâs guide (e.g. no implement X
interface instructions). Needs to be written...
wtp-dev mailing list
Inonu cad. Sumer sok. Zitas D1-15
Kozyatagi, Istanbul 34742
+90 (533) 580 2393 (cell)
+90 (216) 361 5434 (phone)
+90 (216) 361 2034 (fax)