Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Why Do I Need to Explicitly Publish for Tomcat To Pick Up Edited JSPs?

Hi Rob,

Sorry for the delay in replying. There were several issues here that existed in 0.7 but weren't exposed until .deployables was removed and the servers had to handle their own publishing and delta calculations. I've fixed a number of bugs in this area for RC2, including 112363 (see comments in the bug). There is still one known blocking issue that we're investigating (119769 - modification changes not detected for non-Java resources in Java output) but we've done a lot of testing, and initial feedback on a couple of the fixes has been good. I'm sorry to hear that you've started using MyEclipse, and I'd apprecaite it if you can still provide feedback on RC2 or 1.0 and give us another chance.

Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)

Rob Sanheim <rsanheim@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

12/02/2005 02:25 PM

Please respond to
"General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Re: [wtp-dev] Why Do I Need to Explicitly Publish for Tomcat To Pick        Up Edited JSPs?

On 12/2/05, Arthur Ryman <ryman@xxxxxxxxxx> wrote:
> 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

I've been complaining about this one awhile, and its actually forced
me off WTP onto MyEclipse.  Tim told me it would be looked at for 1.0,
but its getting pretty late in the game now...

You can set up some auto-publish behavior in the tomcat server config
window, but it never really worked right in builds I tried it in.

Here's the bug:

- Rob Sanheim
wtp-dev mailing list

Back to the top