| problem with content assistant [message #250250] |
Mon, 17 December 2007 23:04  |
Eclipse User |
|
|
|
Hi, all:
here's a problem with content assistant when we developing our own IDE
by extending JDT.
Our IDE is similar withe EclipeME.
We have a new container by extending
org.eclipse.jdt.core.classpathContainerInitializer, and every thing works
fine: compile, run/debug etc.
But when edit the .java source file, the content assistant does not work
correctly, e.g. suppose that I want to type String.ValueOf(...)
typing "Stri", content assistant works ok
typing "String.", content assistant can not find any static members
typing "String.va", content assistant list all static members that
start with "va"
why content assist failed when I type "String." (note the dot "." here)
What does the magic?
Can any body help?
Thanks for advanced.
Nick
|
|
|
| Re: problem with content assistant [message #250254 is a reply to message #250250] |
Tue, 18 December 2007 03:07  |
| Eclipse User |
|
|
|
nick.tan wrote:
> Hi, all:
> here's a problem with content assistant when we developing our own
> IDE by extending JDT.
> Our IDE is similar withe EclipeME.
> We have a new container by extending
> org.eclipse.jdt.core.classpathContainerInitializer, and every thing
> works fine: compile, run/debug etc.
> But when edit the .java source file, the content assistant does not
> work correctly, e.g. suppose that I want to type String.ValueOf(...)
> typing "Stri", content assistant works ok
> typing "String.", content assistant can not find any static members
> typing "String.va", content assistant list all static members that
> start with "va"
> why content assist failed when I type "String." (note the dot "." here)
> What does the magic?
> Can any body help?
Anything in .log? Did you also extend content assist? If not, I suggest
to file a bug with steps to reproduce / test case against JDT Core.
Dani
>
> Thanks for advanced.
>
> Nick
>
|
|
|
| Re: problem with content assistant [message #250282 is a reply to message #250254] |
Tue, 18 December 2007 22:04 |
| Eclipse User |
|
|
|
Daniel Megert wrote:
> Anything in .log? Did you also extend content assist? If not, I suggest
> to file a bug with steps to reproduce / test case against JDT Core.
Finally I find out that the evil is in my own rt.jar
I created it by according to the GP STIP Spec
(http://www.globalplatform.org):
The core Java API selected by STIP technology is a strict subset of the
core API defined by the CLDC configurations of Sun's J2ME. It contains
only the two packages java.lang and java.util. The package java.io is here
present only to contain one exception needed for the class
java.lang.String. blah blah blah...
I copy part of .class files from cldcapi11.jar and package a new rt.jar.
So I guess that it failed when JDT trying to parse .class into AST because
it can not find e.g. com.sun.midp.io.SystemOutputStream in my new rt.jar.
|
|
|
Powered by
FUDForum. Page generated in 0.02919 seconds
Home