[jbosstools-issues] [JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog

[Brian Fitzpatrick (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008150#comment-13008150 ] 

Brian Fitzpatrick commented on JBIDE-16066:
-------------------------------------------

Ok, so here's what we have diagnosed. There's a timing issue in the Web Service wizard that can be worked around with a pause while on the JBoss Web Service Code Generation Configuration page. When you get to that page in the wizard, take a breath or two, then click Next - rather than just quickly clicking Next when you get here. The delay may need to be different based on system configuration or hardware speed, but I can get through it by counting "one one thousand, two one thousand, three one thousand" and then clicking Next. 

if you don't, you get a warning in the server console during deployment that looks something like this:
{code}
08:14:23,002 WARN  [org.jboss.as.ee] (MSC service thread 1-1) JBAS011006: Not installing optional component org.example.newwsdlfile.impl.NewWSDLFileImpl due to an exception (enable DEBUG log level to see the cause)
{code}

If it doesn't deploy successfully like this, all you have to do is a "Full Publish" on the deployed project in the Servers view and it works fine.

If you do the pause, it deploys fine and you can test it as expected.

This is NOT A BLOCKER.

> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-16066
>                 URL: https://issues.jboss.org/browse/JBIDE-16066
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: webservices
>    Affects Versions: 4.1.1.CR1
>         Environment: JBDS 7.1.0 CR1, EAP-6.1
>            Reporter: Radoslav Rábara
>            Assignee: Brian Fitzpatrick
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)