|
| Re: WTP vs/or MyEclipse [message #166352 is a reply to message #166287] |
Mon, 10 April 2006 14:37   |
 Werner Punz
Messages: 52
Registered: July 2009 |
Member |
|
|
Jimisola Laursen schrieb:
> Hi!
>
> WTP vs/or MyEclipse?
>
> This might not be the right question to ask since MyEclipse uses some WTP
> functionality.
> However, MyEclipse has not come to be what I thought it would be - a tool
> for J2EE.
> Now they seem to add more and more functionality outside of this scope
> (Matisse, Bugzilla and so on).
>
> My question is rather: if I want a tool for developing J2EE application (web
> applications) with xhtml/css/javascript, jsp/servlets/..., deployment,
> debugging etc - is WTP sufficient or do I need a tool that builds on top of
> it?
>
Just a short analysis on MyEclipse. MyEclipse is 90% a mixture of
already existing OSS plugins.
It is based on an old version of the WTP (they are currently moving to 1.0)
their db stuff spring stuff etc... all existing plugins with extra
functionality added by them, the same goes for the javascript stuff.
As for the direction of myeclipse. You just have to check out their road
map, they still are moving strongly along the J2EE road, it just was
that one of the hugest requests for years have been a decent UI builder
for client side apps.
Their next release will be centered around WTP1.0 integration, better
JSF support and Matisse from what I could gather (usually the road maps
are pretty correct)
As for your needs.
So you can get around 80-90% of the functionality without it.
As for your needs, from what I saw from the 1.0.x wtp and web standards
tools, it should be sufficient.
|
|
|
| Re: WTP vs/or MyEclipse [message #166394 is a reply to message #166352] |
Tue, 11 April 2006 00:15 |
Tim Wagner
Messages: 22
Registered: July 2009 |
Junior Member |
|
|
And of course you can use WTP directly - version 1.0.2 is nearly final
and is slated for release later this month.
Another option is to use commercial tools that focus on J2EE and Web
Application development. The Eclipse Awards
( http://www.eclipse.org/org/foundation/eclipseawards/winners. php)
include several offerings in this area, including the Best Commercial
Developer Tool winner, BEA Workshop Studio 3.0.
Werner Punz wrote:
> Jimisola Laursen schrieb:
>
>>Hi!
>>
>>WTP vs/or MyEclipse?
>>
>>This might not be the right question to ask since MyEclipse uses some WTP
>>functionality.
>>However, MyEclipse has not come to be what I thought it would be - a tool
>>for J2EE.
>>Now they seem to add more and more functionality outside of this scope
>>(Matisse, Bugzilla and so on).
>>
>>My question is rather: if I want a tool for developing J2EE application (web
>>applications) with xhtml/css/javascript, jsp/servlets/..., deployment,
>>debugging etc - is WTP sufficient or do I need a tool that builds on top of
>>it?
>>
>
> Just a short analysis on MyEclipse. MyEclipse is 90% a mixture of
> already existing OSS plugins.
> It is based on an old version of the WTP (they are currently moving to 1.0)
> their db stuff spring stuff etc... all existing plugins with extra
> functionality added by them, the same goes for the javascript stuff.
> As for the direction of myeclipse. You just have to check out their road
> map, they still are moving strongly along the J2EE road, it just was
> that one of the hugest requests for years have been a decent UI builder
> for client side apps.
> Their next release will be centered around WTP1.0 integration, better
> JSF support and Matisse from what I could gather (usually the road maps
> are pretty correct)
>
> As for your needs.
> So you can get around 80-90% of the functionality without it.
> As for your needs, from what I saw from the 1.0.x wtp and web standards
> tools, it should be sufficient.
|
|
|
Powered by
FUDForum. Page generated in 0.02518 seconds
] 
Search
Help
Register
Login
Home
