| out of the blue [message #3366] |
Fri, 13 June 2003 09:55 |
Eclipse User |
|
|
|
Originally posted by: glongman.intelligentworks.nospam.com
I build/maintain the Spindle plugin (http://spindle.sourceforge.net) which
adds Eclipse support for web developers using Tapestry
(http://jakarta.apache.org/tapestry).
Here's something that's been a thorn in my side for a while. I'd like to see
more first class support for non java elements in Java Projects. Its a pain
that things like java files and packages are represented by objects in
jdt.core but non java elements are not.
i.e. If I have an IPackageFragment and I call get children, non java
resources are not included in the results(I have to call another method to
get 'em)Which makes sense as they are not represented in the JavaModel. I
think they should be.
Plus, there should be better support for all non java resources found in jar
files. Right now my plugin does everything with IStorages rather than
IResources as sometimes I don't know if my non java resources come from a
jar file or not. Plus finding the package fragment for a non java resource
in a jar file is a pain as there is no way to relate a JarEntry file to an
IJavaElement except by looking at the result of JarEntryFile.toString().
That gives you the system file path of the zip/jar and from there you can
find the package fragment root. Much better would be to have an interface in
the jdt model like INonJavaResource which I can call getParent() on.
Seems to me that supporting web apps requires manipluating non java
resources like web.xml, jsp files, as well as Tapestry spec files. So better
support for non java resources would benefit all users developing plugins
that use results of the eclipse web tools project.
thanks for listening to my rant.
Geoff
Geoff Longman
Intelligent Works Inc.
|
|
|
Powered by
FUDForum. Page generated in 0.05397 seconds
Home