[Riyad Kalla]

Summary:
When completing the name and property attributes to the taglibs in a webpage (in my particular case, struts) IS (I’m asking) it possible to provide autocomplete on previously defined beans? It works currently when inside of a scriplet, (completes for the defined beans) but I’m wondering if it would complete when I’m doing something like:

<bean:define id="person" name="sessionPerson" scope="session" type="com.test.Person"/>
<logic:notEmpty name="|

and be able to offer “person” as a completion? Of course, the next step is to offer property completions as well since the IDE would be aware of the type of the bean.

This is just something to be added to the “it would be nice IF” list, not priority by any means.

[No Operation]

thinkin this is not possible, since you cannot guess what the attribute

name

expects, or the editor must know all available taglibs which seems impossible

NOP

[Riyad Kalla]

NOP this is why I mentioned it only provides completions from <bean:define> or <jsp:useBean> declarations in the same file… BUT I can see a problem with this… people might think these are the ONLY possible completions, even though any valid application, session or page context names would be valid as well…

Scott go ahead and close this request, as I just realized that this would probably cause more confusion then help…

[Sjoerd van Leent]

There is another reason why it is impossible, however nop did already try to explain this. The taglibs using the beans defined or used cannot give away they need beans. It is not possible to know whether a tag attribute needs a bean or not.

[Riyad Kalla]

Yes, now that I look at it, it was a bad request. 🙁

[Author]

Posts