© 2005 by ibm; made available under the epl v1.0 | may 19, 2005 tim deboer [email protected] wtp...

© 2005 by IBM; made available under the EPL v1.0 | May 19, 2005

Tim [email protected]

WTP Server Tools Open HouseWTP Server Tools Open House

2 WTP | Server Tools Open House | © 2005 by IBM; made available under the EPL v1.0

Agenda

Plugins Contributors API Status Quality Current work items


WST Server Plugins

Server Tools Framework org.eclipse.wst.server.core* org.eclipse.wst.server.ui* org.eclipse.wst.server.util

Adds notion of a “server” to Eclipse Starting/stopping servers, publishing, targeting projects, adding &

removing modules Framework for adding new server types Servers view, wizards, editor framework, etc. Ability to choose resource and Run on Server

Depends only on Eclipse

* Contains API


WST Internet Plugins

TCP/IP Monitor org.eclipse.wst.internet.monitor.core**

org.eclipse.wst.internet.monitor.ui**

Monitor for Web pages, Web services Shows request from client and the server’s response

Useful for understanding applications, debugging, etc.

Supports TCP/IP and HTTP

View bytes, images, or XML

** Contains provisional API



Web Browser utilities org.eclipse.wst.internet.webbrowser

The internal Web browser and support for launching external browsers moved into Eclipse in 3.1M6

Utilities for the Eclipse browser plugin Easily switch between browsers, toolbar button to open internal

browser



Proxy Settings org.eclipse.wst.internet.proxy

Manage internet proxy configuration and JRE properties Preference page

HTTP proxy servers and firewalls

Authenticating proxy servers

SOCKS

Likely to move to Eclipse 3.2



Internet Cache org.eclipse.wst.internet.cache

Caches documents requested from the internet Currently only used by the XML resolver


JST Server Plugins

J2EE server utilities org.eclipse.jst.server.core*

org.eclipse.jst.server.ui

Generic Server support org.eclipse.jst.server.generic.core*

org.eclipse.jst.server.generic.serverdefinition

org.eclipse.jst.server.generic.ui

Adds support for J2EE servers to be defined using plain XML files No code required, add support for a new server in minutes

.serverdefinition plugin contains adapters for WebLogic, JONaS, and JBoss


JST Server Plugins

Apache Tomcat Server support org.eclipse.jst.server.tomcat.core

org.eclipse.jst.server.tomcat.ui

Apache Geronimo Server support org.eclipse.jst.server.geronimo.core

org.eclipse.jst.server.geronimo.ui


Server Tools Contributors

Gorkem Ercan Generic server support and adapters for JONaS, WebLogic, JBoss

Larry Isaacs (SAS) Tomcat support

Tim deBoer (IBM) Server Tools framework, TCP/IP monitor, Tomcat support

Elson Yuen (IBM) Server Tools framework

Ted Bashor, Thomas Yip, Konstantin Komissarchik (BEA) Server Tools API

Tim Francis (IBM) Geronimo support


API Status

Done! … almost

API is basically ready to go. Based on past experience we’re reasonably comfortable with the current content

Reasonable validation through several servers and API users in WTP

BEA and IBM are both in the process of validating the API internally

Provisional APIs: TCP/IP Monitor

Parts of server tools relating to features


Quality

Initial code contribution was shipped in previous products. Although it has undergone lots of cleanup and refactoring since then, much of the code is still stable

We’ve been fixing bugs continuously to keep the code relatively stable throughout

Bugs have been slowing growing – 30 currently on queue

Still some work to do to get ship-ready


Current Work Items - Assembly

Each server type has it’s own requirements on assembly Does it happen on build or on publish?

Do utility projects get jarred up? Does complete EAR file get created?

The current .deployables directory is server specific and should not be in the workspace

Working with J2EE team and BEA to define an assembly mechanism

Provide support to assemble modules in .metadata

Assembly can be done via a builder or as part of a publish

Everything is under the server’s control


Current Work Items - Features

Proposal from BEA to enable/disable fine grained features on a module/component

Allows better control over classpath, UI, and which servers support a module that has extensions

Recently deferred to 1.1

Marking affected classes as provisional API

Still investigating to keep options open and migration low


For more information

Component overviews Overviews exist for all three components (wst.internet, wst.server,

jst.server) on the WTP website

Some documentation about specific function:

Run on Server Generic servers

EclipseCon presentation

API – javadoc in code or in online help

Bugzilla Feel free to open enhancement requests for unclear javadoc, further

documentation you’d like to see, etc.


Help Needed

We’re not done yet! If you are planning on using or building on WTP, we can use your

help with: API review

Bug fixes

Testing

JUnit tests

Feedback


Thank you

Questions&

Comments

© 2005 by ibm; made available under the epl v1.0 | may 19, 2005 tim deboer [email protected] wtp...

Documents