Announcement Announcement Module
Collapse
No announcement yet.
Re-deployment of FormTags service does not restart war Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Re-deployment of FormTags service does not restart war

    I have been testing the Form tags demo (shared services) by making a change in the source of one of the files in the service and saving it in eclipse. Eclipse re-deploy's the service to the SpringSource AP and stops the war service without restarting it.

    Is this the way it should work? How can you debug a service if it stops the war without restarting it every time you make a change to a bundle? I am using beta9 and the latest SpringSource Tool Suite.

    I'm very excited about the new appServer and am hoping I am doing something wrong.

    Frank

    P.S., sorry for posting this first on the announcement category. You might want to change the default drop-down list to general from announcements so that unobservant guys like me do not make that mistake ;-)

  • #2
    Re-deployment of FormTags service does not restart war

    Any chance of getting a response to this post?

    Frank

    Comment


    • #3
      Re-deployment of FormTags service does not restart war

      Hi Frank,

      I'll try to reproduce the error you're encountering and get back to you.

      Regards,

      Sam

      Comment


      • #4
        Re-deployment of FormTags service does not restart war

        Frank,

        I was able to reproduce this. You should here back from us shortly.

        Christian

        Comment


        • #5
          Re-deployment of FormTags service does not restart war

          Thanks. Looking forward to your response. Let me know if there is anything I can do.

          Frank

          Comment


          • #6
            Re-deployment of FormTags service does not restart war

            This problem just made it to my inbox and, unfortunately, I am tied up this morning which means any fix won't make it into the next milestone release. However, the behaviour does sound wrong, so I raised a JIRA issue to track it and will look into it in the couple of days.

            See: https://issuetracker.springsource.com/browse/PLATFORM-145

            Comment

            Working...
            X