[ploskikl]

Hi,

I’ve installed Eclipse 3.0M8 and the MyEclipseIDE plug paired with M8.

When I select Window > Preferences > MyEclipse > J2EE > Library Sets, I’m able to select J2EE 1.3.

WHen I select J2EE 1.2, the dialog window that appears contains this notice: “J2EE 1.2 library set support is not available at this time. A future release will support J2EE 1.2 – 1.4 libraries.”

I looked at the Roadmap that appears on your web site but could not see an indication of when support for J2EE 1.4 libraries is planned.

My question is: do you when support for J2EE 1.4 libraries will be implemented in the MyEclipseIDE plug in planned for use once Eclipse 3.0 is released?

Thank you!
– Karen

[Riyad Kalla]

Hi Karen,
We are starting our J2EE 1.4 support in MyEclipse 2.8/3.8 with initial support for JSP 2.0. We will continue to add functionality addressing the 1.4 spec and hopefully be where we need to be by MyEclipse 2.9/3.9.

If you JUST need the 1.4 libs, its easy with M8 to create a new library set and add it to your project. Or just add the JARs to your build path and remove the 1.3 Library set that we automatically add.

If you were asking more related to wizards and automation of 1.4 support, then see my first answer.

[nat101]

Can you please explain the definition of MyEclipse’s support of 1.4. If I can use the 1.4 libs myself now, as described here, what functionality am I missing until MyEclipse ‘supports’ j2ee 1.4 out of the box?[/b][/code]

[Riyad Kalla]

nat101,
While you are more than welcome to develop with 1.4 now, what we mean by ‘official’ is support for things like JSP 2.0 and the Expression Language in the JSP editor and other J2EE 1.4 oddities (schema support in the XML editor for the 2.4 Servlet spec, etc.)

[Dave Haas]

Hi Riyad.

I don’t agree that disabling the J2EE 1.3 Container is simple. If I create a new web project and right click on the J2EE 1.3 Container in the Package Explorer, the delete option is disabled. I have to go into the project properties dialog and delete it under the Libraries tab. Also, there seems to be no way to add a new library set to the MyEclipse preferences in the preferences dialog under the J2EE option. I have to manually create a new library set using the User Libraries tab under the Java->Build Path->User Libraries preferences page.

Just some thoughts.

Dave

[Riyad Kalla]

I don’t agree that disabling the J2EE 1.3 Container is simple.

Its a matter of perspective.

I have to go into the project properties dialog and delete it under the Libraries tab.

Yes, this is what I meant. You need to remove the Library Set that we automatically add, from your build path.

Also, there seems to be no way to add a new library set to the MyEclipse preferences in the preferences dialog under the J2EE option.

Correct, there is not. The previous Library Set functionality that was provided by MyEclipse was not fully functional and only meant for the purpose of deploying sets of files together. Eclipse 3.0M8 release provided ‘official’ support for Library Sets and this is why I said it would be easy, because its provided by the base Eclipse install, not use (I should have clarified this, I’m sorry).

I have to manually create a new library set using the User Libraries tab under the Java->Build Path->User Libraries preferences page.

Right, see that wasn’t so bad. Infact, some might say it was simple 😀

Please note that now our primary development platform is focused on Eclipse 3, after 3.8 GA, our 3.9 release will work hard to really integrate these Eclipse solutions so we shouldn’t run into confusion like this in the future. I agree that the problems you ran into shouldn’t have been there and we hope to smooth things out in the near future.

[nat101]

Will 3.9 also have wizards to build web services (and related, soap etc) that has become part of the 1.4 spec?
Will the wizards reflect new features in current technologies, like ejb 2.1?
Thanks;
-nat

[Riyad Kalla]

Nat,
Our roadmap is always kept up to day on the site, and you’ll notice for the 3.9 release is still blank. We usually don’t establish our roadmap for the next release until we’ve hit a GA release with the current development version. This is because we don’t know yet what will be stable enough to make the 2.8/3.8 cut and what will need to be pushed back to 3.9 and also the biggest deciding factor is that we don’t know yet what people will “have to have” after 2.8/3.8 goes out the door. I know web services is important to us, so we certainly have plans to support it eventually.

[Author]

Posts