[Sean Dynan]

Hi all

I autogenerated the helloWorld.jsp as per the instructions and added the <% out.println(“Hello World”); xxx%>.

When I saved the file the JSP compiler reported the following unexpected error at Line 1:

de cannot be resolved or is not a valid superclass

I notice that there is a buildCommand entry in the .project file referencing de.bb.bje.eclipse.IncrementalJspBuilder. Do I need to add something to this project’s class path?

Here are the bits you asked for:
What operating system and version are you running?
Windows XP Pro SP1

What Eclipse version and build id are you using?
Version: 2.1.2, Build id: 200311030802 (installed in c:\dev-tool\ide-editor\eclipse)

Was Eclipse freshly installed for MyEclipse?
Yes. MyEclipse 2.6.4 (installed in c:\dev-tool\ide-editor\MyEclipse)

Are any other external plugins installed?
If you mean like MyEclipse, no. But quite a few internal ones.

How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*?
Seven:

pde.build_2.1.0
pde.core_2.1.2
pde.doc.user_2.1.0
pde.runtime_2.1.0
pde.source_2.1.2
pde.ui_2.1.2
pde_2.1.0

What MyEclipse version are you using? (Help > About Eclipse Platform > Features)
MyEclipse 2.6.4

What JDK version are you using to run Eclipse?
1.4.2_02-b03

What JDK version are you using to launch your application server?
The same: 1.4.2_02-b03

What steps did you take that resulted in the issue?
See description at the top of this post.

What application server are you using?
JBoss 3.2.2 (but not running for this error)

Are there any errors in the Eclipse log? (<workspace>/.metadata/.log)
Only a java.lang.VerifyError stack trace from org.eclipse.ant.core during Eclipse shutdown.

Thanks
—
Sean

[support-michael]

Hi Sean,

I just ran through the example with a very similar environment to your’s and replicated the problem. In my case the “de” error marker shows up after I close and then reopen the file. The “de” marker disappears once all syntax errors are resolved. I deployed and debugged the file so you should be able to continue without incident other than the annoying marker.

This issue is related to a JSP validation bug that has since been resolved and will be released as part of the MyEclipse 2.7RC-1 next week. Sorry for the delay in responding but I first wanted to run through this case on a couple of environments.

Michael
MyEclipse Support

[Sean Dynan]

Thanks Michael

Out of interest, can you tell me why this only shows up on my config? I presume it didn’t on older configs (e.g. the one used when the tutorial was written)?

—
Sean

[support-michael]

Sure! The facts are there was a showstopper issue and we have been refactoring the JSP editor internals as we move towards JSP2.0 support. Addressing the showstopper issue was an immediate priority that resulted in a tradeoff of introducing a lesser bug that the refactoring effort enables to be addressed much more simply than on the older architecture. It was a pure tradeoff decision of lesser evils prevailing with the knowledge that we would have a much better product in less than 30 days from the 2.6.4 release.

Michael
MyEclipse Support

[Sean Dynan]

Lookin’ forward to the next release then!
—
Sean

[Author]

Posts