[wtp-dev] Why Do I Need to Explicitly Publish for Tomcat To Pick Up Edit

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[wtp-dev] Why Do I Need to Explicitly Publish for Tomcat To Pick Up Edited JSPs?

From: Arthur Ryman <ryman@xxxxxxxxxx>
Date: Fri, 2 Dec 2005 13:47:48 -0500
Delivered-to: wtp-dev@xxxxxxxxxxx
List-archive: <http://eclipse.org/pipermail/wtp-dev>
List-help: <mailto:wtp-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/wtp-dev>, <mailto:wtp-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/wtp-dev>, <mailto:wtp-dev-request@eclipse.org?subject=unsubscribe>

I assume that the removal of .deployables has changed the behavior of server adapters. Back in 0.7, could edit a JSP and the refresh my browser to see the change. Now I need to click Publish first. This is more awkward. Why the change? Is there a way to set up an "auto publish" behavior?

Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

Follow-Ups:
- Re: [wtp-dev] Why Do I Need to Explicitly Publish for Tomcat To Pick Up Edited JSPs?
  - From: Rob Sanheim

Prev by Date: [wtp-dev] Towards RC2
Next by Date: [wtp-dev] API scan for 1.0RC1 is available
Previous by thread: [wtp-dev] Towards RC2
Next by thread: Re: [wtp-dev] Why Do I Need to Explicitly Publish for Tomcat To Pick Up Edited JSPs?
Index(es):
- Date
- Thread

Breadcrumbs