First, see here:
http://docs.jboss.org/webbeans/reference/1.0/en-US/html/xml.html
"The advantage of this approach is that you can write an XML schema
that prevents spelling errors in your XML document. It's even possible
for a tool to generate the XML schema automatically from the compiled
Java code. Or, an integrated development environment could perform the
same validation without the need for the explicit intermediate
generation step."
Second, "new binding type", "new interceptor binding type", "new
deployment type" wizards.
Third "find clients", "find implementations" for injection points,
"find observers" for event types.
Not sure if there is additional value in "find interceptors", "find
intercepted web beans" and "find "decorators", "find decorated
web
beans", etc.
On Mon, Nov 3, 2008 at 2:40 PM, Max Rydahl Andersen
<max.andersen(a)redhat.com> wrote:
Hi,
In case you have a minute or five, it would be good to start hearing what
kind of tooling we should consider adding for webbeans in the next rev of
tooling...
Pete and I already did a few suggestions while we were in Copenhagen you can
see here:
https://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&&am...
If you got some concrete ones add them to jira directly or put the
suggestions on this list for dicsussion.
--
/max
_______________________________________________
webbeans-dev mailing list
webbeans-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/webbeans-dev
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org