[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Libor Zoubek commented on JBIDE-6106: ------------------------------------- For example https://jira.jboss.org/jira/browse/JBIDE-5870 it is fixed from the point of view of running and deploying web service. But we still can't get rid of that message "Selection must be WSDL" -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Feng Qian updated JBIDE-6106: ----------------------------- Component/s: Webservices -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6106: ------------------------------------------ The EAR/WAR issue is definitely one we need to look into, and I totally agree that it's a pain that it forces us to deploy EARs. We definitely have some issues with the WTP Web Services wizards. And I have some ideas on how to create a more simplified wizard that handles a similar set of tasks more straightforwardly. I just haven't had a chance to write anything down yet. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6106: ------------------------------------- Attachment: NewJBWSWizard_041510.jpg This image represents the possibility of a new, slimmed down version of the WTP Web Service wizard that's currently in the tooling. The idea here is to streamline to a few basic things so that developers can create their service and get on with their lives. The general flow here will be... 1) Select New->Other, Selects "Web Service (JBoss)" to bring up the new wizard. 2) Select whether you're starting from a WSDL file (URL or file-based) or an annotated Java class. (User can Browse to provide either method.) 3) Specify the server/runtime combination and which project to put the new web service in. The three links open two different dialogs, similar to the WTP wizard today - one for Server/runtime and one for Project configuration. In the Project dialog, the user can type a new project name and at "Finish" the new Dynamic Web Project will be created with that name, otherwise it will use the project selected. 4) Specify whether or not to create a test client for the web service. This will add a second page to the wizard where they would specify the project/package/class name for the test class. 5) Specify whether or not to publish the web service right away. If not, the service is simply created in the project specified and the user can drag/drop on the server in the tooling or select Add/Remove on the server to deploy. This isn't flashy. It's pretty straightforward. We'll reuse what we can from WTP to handle as much as possible, but cut out all the extraneous stuff that confuses users. My question is this... What other functionality do we need in this wizard? I'm hoping not much else would go in here. This is just a start of this discussion, there's not much code behind this wizard so far, but we have to start somewhere. :) Thaks for any and all input. --Fitz -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6106: ------------------------------------- Attachment: UseCase2 - JAX-WS bottom up.pdf A second case... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-6106: ------------------------------------- Attachment: UseCase3 - JAX-WS bottom up no annotations.pdf Third case... -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Lukas Jungmann commented on JBIDE-6106: --------------------------------------- I really like the way the wizard is being simplified. Some comments: 1) all use-cases are expecting some existing file somewhere (be it WSDL orJava file) but what if all I want to do is to start developing a service from scratch? here is possible 5th use-case to consider: Create a new Web Service from scratch. 1. In Eclipse, select File->New->Other... or press Ctrl+N. 2. Select the Web Services category and look for Web Service (JBoss) to launch the wizard. Once the wizard appears... 3. Specify non-existing Java class name... 4. Specify the target server and runtime... 5. Specify the target project to put the generated code in... 6. Click Finish. the wizard could then generate ie empty class (bellow) or a class with some empty (commented out?) @WebMethod: package sample; @javax.jws.WebService() public class SampleWS { } 2) I'd prefer to get rid of the "Generate Test Client" option (... in the long term) and would prefer to replace it with something more sophisticated, for example with some web service sensitive action, say Test Service, which would open up some UI where I would be able to set up parameters and send them to the running service (would be also nice to be able to send raw SOAP message through the UI) - opinions? 3) Publish the web service - when I looked at this option for the first time it wasn't clear to me what does that option mean - can the label be changed a bit to be more descriptive (ie add 'to UDDI registry' there) ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Libor Zoubek commented on JBIDE-6106: ------------------------------------- I like use cases and screenshots very much too. This is what I'd change/add: 1. Have an option to generate WS client and run it into non-web project. (This is possible now, but generated code works only when it runs on server, it relies on few jars, which are on server) 2. Have an option to generate client stubs without having server runtime. This makes sense, when one develops web service client only. Can this be accomplished? 3. Do we need to support runtimes other then JbossWS? I thought our wizards are not intended to replace current WTP wizards, but create web services our better way.This could be confusing for developers of Axis WS. Which wizard to use? And if Axis runtime implementation is buggy, we need to handle this and our wizards won't work anyway. Truth is, that such wizards wouldn't be such open and extensible, but on the other hand they would be stable and working. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-6106?page=com.atlassian.jira.plu... ] Brian Fitzpatrick commented on JBIDE-6106: ------------------------------------------ Lukas - 1) If we rewrite the Web Service wizard with the ability to create a Hello World class, we don't need the other one so it would probably go away. Question becomes how long do we need to keep it around if it's a matter of support. 2) I'm good with splitting out the WS Client bits into a separate wizard. 4) Why would we need to split up JAX-WS & JAX-RS into separate wizards? From a user standpoint, the flow is the same through the wizard - only the output changes slightly. I don't see the point in separating them. 5) We could certainly have a Preference page that captures the defaults for the page, but I kind of like the one page config concept for 90% of what we need. 6) Hmmm... Again, I like the page serving as both a summary and a one page config, so I'd rather not split the WSDL config out if we can avoid it. Libor - 1) Ok, so if we split out the WS Client into its own wizard, we should be able to put it into any Java-type project then? 2) I don't know that we can pull this off in this release, but it's something to look at in the future. 3) For now, we're going to probably have to have both the existing WTP wizard and this new wizard anyway. Are you suggesting that this wizard only support JBossWS? -- 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