Home » Language IDEs » ServerTools (WTP) » Webtools lomboz and others
| Webtools lomboz and others [message #2585] |
Thu, 12 June 2003 06:03  |
Eclipse User |
|
|
|
Well, JavaONE is more than a skip and a jump away and it is not in my list
of places to go this year so let me start it here.
I am happy to see this project, even if it is here to gather ideas at this
time. That being the case, let me ramble and share some of the experiences
from the Lomboz project, because I believe it will provide some insight to
"webtools".....
-If webtools project is managed, structured and developed with the right
vision, and with the help of quality contributions, this project will become
another strong point for the whole eclipse project.
- What is webtools? Is it J2EE specific? Does JavaScript editors count as
webtools? What about EJB tools, they are not necessarily related to web.
The list is long. This is not surprising. Most of Java development is
geared towards things that has something to do with the web. Therefore is
JDT itself a web tool?
-Web has an incredible amount of developer. Not all of them come from the
same culture. Web page developers have a totally different understanding of
coding/testing/design than, say traditional java developers. Who will be
the target audience for this project: Web designer, java/j2ee developer, ...
Before getting too philosophical - I would start by organizing the tools in
the following groups:
1) Web-side technologies
- Editors for JSP, HTML, XML, JavaScript, web.xml, application.xml,
ejb-jar.xml ... with all the goodies-syntax highlighting, code-assist, help
etc.
-Wizards - Servlet/Jsp/Web Application-War/Ear etc.
2) Components
- EJB Wizards, OR Mapping wizards
-Web Services wizards
4) Infrastructure support
-Launching/Debugging/Stopping/Configuring application servers
-Deploying/Undeploying applications and components
5) Developer tools
-Profiling/Testing/Performance monitors that work with application
servers
-Another hard point is J2EE development. J2EE is an overwhelming pile of
standards. It tells you to do things a certain way. Developers do not like
tight shoes, even if they have to wear one. Best tools let you wear that
shoe without really being aware of it. There are many tools out there, not
all of them are good. There has to be some philosophy to what tools fit
this project as well.
-I would like to see some discussions and development of structure in terms
of these issues. We would like to donate the Lomboz source if this project
is a fit. However, I would hate to do it in the expense of killing a good
tool if this project fails to fulfill its promise.
-One final question - Who is/will be the lead for this project?
Naci Dai /
|
|
|
| Re: Webtools lomboz and others [message #3433 is a reply to message #2585] |
Fri, 13 June 2003 15:46  |
| Eclipse User |
|
|
|
Originally posted by: jlinuxcn.yahoo.com.cn
I think some other groups need to be included in Web tools.
1.some good framework for building web applications. for example: struts .
2. some j2ee design model
3.generate some codes automated , for example DAO classes and
ValueObject class
Naci Dai wrote:
> Well, JavaONE is more than a skip and a jump away and it is not in my list
> of places to go this year so let me start it here.
>
>
>
> I am happy to see this project, even if it is here to gather ideas at this
> time. That being the case, let me ramble and share some of the experiences
> from the Lomboz project, because I believe it will provide some insight to
> "webtools".....
>
>
>
> -If webtools project is managed, structured and developed with the right
> vision, and with the help of quality contributions, this project will become
> another strong point for the whole eclipse project.
>
>
>
> - What is webtools? Is it J2EE specific? Does JavaScript editors count as
> webtools? What about EJB tools, they are not necessarily related to web.
> The list is long. This is not surprising. Most of Java development is
> geared towards things that has something to do with the web. Therefore is
> JDT itself a web tool?
>
>
>
> -Web has an incredible amount of developer. Not all of them come from the
> same culture. Web page developers have a totally different understanding of
> coding/testing/design than, say traditional java developers. Who will be
> the target audience for this project: Web designer, java/j2ee developer, ...
>
>
>
> Before getting too philosophical - I would start by organizing the tools in
> the following groups:
>
>
>
> 1) Web-side technologies
>
> - Editors for JSP, HTML, XML, JavaScript, web.xml, application.xml,
> ejb-jar.xml ... with all the goodies-syntax highlighting, code-assist, help
> etc.
>
> -Wizards - Servlet/Jsp/Web Application-War/Ear etc.
>
>
>
> 2) Components
>
> - EJB Wizards, OR Mapping wizards
>
> -Web Services wizards
>
>
>
> 4) Infrastructure support
>
> -Launching/Debugging/Stopping/Configuring application servers
>
> -Deploying/Undeploying applications and components
>
>
>
> 5) Developer tools
>
> -Profiling/Testing/Performance monitors that work with application
> servers
>
>
>
>
>
> -Another hard point is J2EE development. J2EE is an overwhelming pile of
> standards. It tells you to do things a certain way. Developers do not like
> tight shoes, even if they have to wear one. Best tools let you wear that
> shoe without really being aware of it. There are many tools out there, not
> all of them are good. There has to be some philosophy to what tools fit
> this project as well.
>
>
>
>
>
> -I would like to see some discussions and development of structure in terms
> of these issues. We would like to donate the Lomboz source if this project
> is a fit. However, I would hate to do it in the expense of killing a good
> tool if this project fails to fulfill its promise.
>
>
>
> -One final question - Who is/will be the lead for this project?
>
>
>
>
>
> Naci Dai /
>
>
|
|
|
Goto Forum:
Current Time: Wed May 07 17:04:22 EDT 2025
Powered by FUDForum. Page generated in 0.04426 seconds |
Home