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

For the interceptors and decorators something like the aspectj eclipse plugin would help.

[]s On Mon, Nov 3, 2008 at 10:51 PM, Gavin King <gavin(a)hibernate.org&gt; wrote: > 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&gt; 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 > _______________________________________________ > webbeans-dev mailing list > webbeans-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/webbeans-dev >

> > > Third "find clients", "find implementations" for injection points, > "find observers" for event types. > FWIW: Of the features mentioned, I imagine this would be the most useful to me. It'd be nice if the validator also offered quick-fix suggestions. Maybe this is part of validation you've already planned, but it'd be good to check the serializability of beans injected into passivating-scoped beans.

wrote:

It'd be nice if the validator also offered quick-fix suggestions. >> > If you could attach examples of code issues and what quick fix you want for that would be great.

https://jira.jboss.org/jira/browse/JBIDE-3126

> 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." Ok, it is in https://jira.jboss.org/jira/browse/JBIDE-3120 > Second, "new binding type", "new interceptor binding type", "new > deployment type" wizards. https://jira.jboss.org/jira/browse/JBIDE-3121 https://jira.jboss.org/jira/browse/JBIDE-3122 https://jira.jboss.org/jira/browse/JBIDE-3123 > Third "find clients", "find implementations" for injection points, > "find observers" for event types. https://jira.jboss.org/jira/browse/JBIDE-3124 https://jira.jboss.org/jira/browse/JBIDE-3125 /max

> 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." Ok, it is in https://jira.jboss.org/jira/browse/JBIDE-3120 > Second, "new binding type", "new interceptor binding type", "new > deployment type" wizards. https://jira.jboss.org/jira/browse/JBIDE-3121 https://jira.jboss.org/jira/browse/JBIDE-3122 https://jira.jboss.org/jira/browse/JBIDE-3123 > Third "find clients", "find implementations" for injection points, > "find observers" for event types. https://jira.jboss.org/jira/browse/JBIDE-3124 https://jira.jboss.org/jira/browse/JBIDE-3125 /max _______________________________________________ webbeans-dev mailing list webbeans-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/webbeans-dev

Mmmm ... I dunno. Usually a decorator is going to be for a specific interface, not for a specific web bean.

Seriously, I'm not sure how much extra value there is to this that is not already covered by eclipse's ability to generate a class from an interface....