With JAX-WS, the point you have about java2wsdl is only true on our container ;) All other containers require you to generate additional source code that has to be bundled with the deployment. We generate the bytecode dynamically at deploy time. -Jason ________________________________ From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Burr Sutter Sent: Thursday, November 09, 2006 9:22 AM To: Thomas Diesler; Heiko Braun Cc: jbossws-dev(a)lists.jboss.org Subject: RE: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not? I'm not sure if you want my 2 cents but option #1 makes for the best demo though many audience members would like to see the wsdl2java (contract first) method as well. I normally don't show this but I do need to add it. Java2wsdl from the command is only for those folks wishing to integrate the WS development into their automated build scripts/unit testing. ________________________________ From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev-bounces@lists.jboss.org] On Behalf Of Thomas Diesler Sent: Thursday, November 09, 2006 10:10 AM To: Heiko Braun Cc: jbossws-dev(a)lists.jboss.org Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not? ok, lets do #1 Heiko Braun wrote: People wont realize it, since I start with an JSR181-EJB3 first and the pickup the WSDL from there. /Heiko ________________________________ From: Thomas Diesler [mailto:thomas.diesler@redhat.com] Sent: Thursday, November 09, 2006 3:59 PM To: Jason T. Greene Cc: Heiko Braun; jbossws-dev(a)lists.jboss.org Subject: Re: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not? This shows how badly broken the integration is. If we can do it in container, why can this not be done offline? So what should the message be for java2wsdl? #1 deploy to server, pickup the wsdl from the browser #2 use wsgen I'd opt for #1 otherwise we have people generating conflicting contracts. cheers -thomas Jason T. Greene wrote: We don't yet have an offline tool for java2wsdl. http://jira.jboss.com/jira/browse/JBWS-1043 Last we discussed this task was delayed until the following were completed: - CTS compliance - Backporting to jbossws-1.0 -Jason -----Original Message----- From: jbossws-dev-bounces(a)lists.jboss.org [mailto:jbossws-dev- bounces(a)lists.jboss.org] On Behalf Of Thomas Diesler Sent: Thursday, November 09, 2006 8:35 AM To: Heiko Braun Cc: jbossws-dev(a)lists.jboss.org Subject: [jbossws-dev] Re: jax-ws client artifacts: wsimport or not? For java2wsdl use our tools. For wsdl2java use wsimport and monitor http://jira.jboss.org/jira/browse/JBWS-1042 -thomas Heiko Braun wrote: What's the (communication) strategy for jax-ws tools? Are we going to point people to the RI tools until we are ready? What should be communicated at JBW? I am currently hacking the demo and don't know if I should hide the RI or not... /Heiko -- Heiko Braun JBoss, a division of Red Hat T: +49 89 52350383 M: +49 178 1496854 -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ jbossws-dev mailing list jbossws-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbossws-dev -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.0/524 - Release Date: 11/8/2006