Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] WTP M4 I Build: Publish and Server launch (order of APIs getting called)

Hi Usha,

1) Please see Elson's note on this mailing list for how to tell the framework to start the server before publishing. If you disable automatic publishing and don't manually publish, then yes, this is the expected behaviour.

2) We didn't expose this as API but did have the neccessary code on the server adapter extension point so that we could expose it at a later date... until another request from your company conflicted with this and it was removed last milestone. :) If you are serious about this then please open up a feature request and we'll take another look at supporting both requests.

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

"Usha Kuntamukkala" <ukuntamu@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

05/13/2005 06:45 PM

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

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
[wtp-dev] WTP M4 I Build: Publish and Server launch (order of APIs        getting called)

Hi Tim,


I’m not sure if these were discussed already.


1)       I’m finding that during “Run on Server”, publish APIs are getting called before the server launch (or start) API is called. Considering that our requirements for the publish activity are dependent on the server being up completely, I turned off the option of “Automatically publish before starting the server” in the preferences page. However, after this, the publish doesn’t get called at all, the server starts up and my test client comes up. Is this the intended behavior or am I missing something?


Is there a way I can make sure that during “Run on server” the order in which APIs are called are – server start, publish, and then test client launch. With the current behavior, the test client coming up without     publish happening is unintuitive for the user.


2)       Manual option for publish on a component is only exposed via the server (which potentially has multiple components attached). Would it make sense to have the publish option on an individual component in order to facilitate easier iterative deployment?



wtp-dev mailing list

Back to the top