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)


In the server type extension point, you set a "startBeforePublish"
attribute to true.  This will make sure the server is started before the
publish happens.


Elson Yuen
WebSphere Tools (AST)
IBM Toronto Lab
Tel: (905) 413-2689, T/L: 969-2689

             <ukuntamu@xxxxxxx                                          To
             >                         "General discussion of project-wide
             Sent by:                  or architectural issues."       
             wtp-dev-bounces@e         <wtp-dev@xxxxxxxxxxx>           
             05/13/2005 06:45          [wtp-dev] WTP M4 I Build: Publish
             PM                        and Server launch (order of APIs
                                       getting called)                 
             Please respond to                                         
               discussion of                                           
              project-wide or                                          

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