- This topic has 6 replies, 3 voices, and was last updated 20 years, 12 months ago by
.
-
Posts
-
– System Setup ——————————-
Operating System and version:
Eclipse version: Eclipse 3M6
Eclipse build id: 200312182000
Fresh Eclipse install (y/n): Y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.7
Eclipse JDK version: 1.4.2
Application Server JDK version: 1.4.2
Are there any exceptions in the Eclipse log file? No– Message Body ——————————-
Hi there Guys
Your paying registered community has just gone up by one ! Again i say : WOW. Capitol W.. O .. W. This has got to be the best / most radical development to have hit the community since java crawled out of the primeval soup. It still amazes me how you can produce a product of such high quality and still have possibly the best customer support i’ve ever experienced. I presume a high degree of inter-stellular multi-tasking is going on somewhere in the core. :). Baa humbug to all those overpriced ides i say !
On that note: Any ideas on an xdoclet issue i’ve got?
1. I’ve noticed that the auto completion of tags don’t seem to work in all contexts. ie: auto complete for a @struts tag only works in an Action. Trying to add the tag to a normal java class doesn’t work. This sounds almost too good to be true – correct behaviour (CB) i hope.However on that note, i can’t seem to get some of the tags working… where i’m pretty sure they should work. For example, your xdoclet tutorial – when you create the Tag class and extend TagSupport. I can’t get any of the @jsp tags to work. Surely in this instance they should work in the class.?
…
* @jsp.variable name-given=”atEnd”
* class=”java.lang.Integer”
* scope=”AT_END”
* declare=”true”
*
*/
public class BasicTag extends TagSupport {
…The @jsp doesn’t autocomplete in any of the above.
I’ve tried updating the xdoc jars in
‘org.jboss.ide.eclipse.xdoclet.core_3.6.200’ to include the latest stage release of 1.2.. no joy (and breaks ide… so i’ll wait for the stable 3.7 version)Could it be a mis-configuration (MC), ?
Or am i just being a bleeding idyot (BI) ?
Kind Regards
GilesGiles, I’ve fired your question to the commander and chief of XDoclet-MyEclipse support and see what he has to say. Thank you for such a detailed report, it helps us track down the culprits right away.
Giles,
Thank you for the kudos on the product. When 2.7/3.7 go GA they’ll have over 80 enhancements / fixes over RC2 so I think everyone will enjoy them.
Now to your question. Yes, the XDoclet assist is somewhat intelligent as to what classes it will offer support for and we will have version 1.2 integrated into the GA builds. However, I don’t know why you’re not getting assistance on the @jsp tag. It could be a “known limitation” or a bug in the XDoclet implementation, but in any case I’ve referenced this thread to some current enhancement work we’re planning for 2.8 to make sure it gets sorted out. I wish I had more information, but I don’t other than I couldn’t get it to work either. Development will be doing a good bit with XDoclet for 2.8, so you’re actually rather timely in raising the issue from a product perspective, but unfortunately that doesn’t help you in the short term and for that I apologize. Thanks for your patience while we continue to build and enhance. 🙂
