Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <20277599.1190737910614.JavaMail.jira@brutus>
Date: Tue, 25 Sep 2007 09:31:50 -0700 (PDT)
From: "Colm O hEigeartaigh (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Created: (CXF-1062) Bug in EndpointImpl#stop()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Bug in EndpointImpl#stop()
--------------------------

                 Key: CXF-1062
                 URL: https://issues.apache.org/jira/browse/CXF-1062
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
            Reporter: Colm O hEigeartaigh
            Priority: Minor
         Attachments: cxf_jaxws.patch

I've run into a problem with the following bit of code:

Endpoint endpoint = Endpoint.create(...);
endpoint.publish(...);
endpoint.stop();
System.out.println(endpoint.isPublished());

The println returns "true" even though the endpoint has been stopped. This is because in EndpointImpl we have:

public void stop() {
        if (null != server) {
            server.stop();
        }
}  

public boolean isPublished() {
        return server != null;
}

So as "server" isn't null, just "stopped", isPublished() returns true. This is contrary to the functionality of the method:

"Returns true if the endpoint is in the published state.".

http://java.sun.com/javaee/5/docs/api/javax/xml/ws/Endpoint.html#isPublished()

In the attached patch, I've fixed this problem by setting the Server implementation to null when EndpoingImp#stop() is called. This makes sense as stop()ed Endpoints can't be re-published (according to the JAX-WS spec). A unit test is also included in the patch.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.