[jbosstools-issues] [JBoss JIRA] Updated: (JBIDE-5934) Web service client wizard bad behaviour

Max Rydahl Andersen (JIRA) jira-events at lists.jboss.org
Thu Feb 25 08:57:10 EST 2010


     [ https://jira.jboss.org/jira/browse/JBIDE-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Rydahl Andersen updated JBIDE-5934:
---------------------------------------

      Component/s: Webservices
    Fix Version/s: 3.1.1
         Assignee: Brian Fitzpatrick


Which Wizard is this ? The WTP provided one or our own Sample Webservice ?

> Web service client wizard bad behaviour
> ---------------------------------------
>
>                 Key: JBIDE-5934
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5934
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Webservices
>    Affects Versions: 3.1.0.CR2
>            Reporter: Libor Zoubek
>            Assignee: Brian Fitzpatrick
>             Fix For: 3.1.1
>
>
> 1. On the 2nd page of WSClient wizard (type of JBossWS) is allowed to enter invalid package name. We should perform validation. One can then get invalid generated sources (which wizard says) or NullPointerException (when package name contains @ )
> 2. Wizard should warn user when it is possible to overwrite some source files. Consider case when user creates web service (for example uses  our 'Sample web service wizard'). He decides to generate client. Opens New web Service Client Wizard, enters service's WSDL and clicks Finish. Because of the fact, that package name is by default derived from namespaces found in WSDL, generated proxies overwrite service implementation without warning. Wizard should just check, if filled 'Package Name' exists or not and warn about possible risks.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list