February 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by thomas.diesler＠jboss.com

Hey, Jason this is excellent work - well done. anonymous wrote : | The custom provider can be specified using the "org.jboss.ws.tools.jaxws.webServiceImporterProvider" system property, or the static field on WebServiceImporter.class. | Please have a look at javax.xml.soap.FactoryLoader | /** | * Load a factory using this ordered lookup procedure | * | * 1. Use the system property | * 2. Use the properties file "lib/jaxm.properties" in the JRE directory | * 3. Use the Services API (as detailed in the JAR specification), if available, to determine the classname | * 4. Use the default factory implementation class | * | * @return the factory impl, or null | */ | public static Object loadFactory(String propertyName, String defaultFactory) | This is the lookup we use thrughout the jaxws impl. And most importantly, now that we have wsgen + wsimport functionality we should make it available in jbossws-1.2.0. This would give us the much needed community QA before 2.0.0 Could you please merge your work to branches/jbossws-1.2.0 For sake of clarity I suggest we do not refer to wsgen + wsimport when we talk about our tool set. How about: wswsdl, wsjava? cheers View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009942#4009942 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009942

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: javax classes in jbossws-client.jar

by thomas.diesler＠jboss.com

Yes, this should change in 1.2.0 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009935#4009935 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009935

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by jason.greene＠jboss.com

"omatzura" wrote : | to make my life easier, integrated tools in soapui are launced by spawning a seperate process and running the command-line versions.. maybe not the best from a resource-perspective, but it keeps the code clean from "linking"/class-loaders/etc.. I'll try to go with this strategy for these 2 as well (unless there is some reason to do otherwise..) | OK, however you like to do it. One thing I was thinking of doing to help integrators concerned with dependencies is to provide a tiny jar (with no dependencies) that contains just the JAX-WS tools API and SPI. An integrator could then include this tiny jar in their classpath. The code would something like: | WebServiceGenerator generator = WebServiceGenerator.newInstance(new URLClassLoader(impljars)); | generator.setGenerateSource(true); | generator.setGenerateWsdl(true); | generator.setOutputDirectory(new File("output")); | generator.setMessageStream(stream); | generator.generate(TestMe.class); | anonymous wrote : | Do I "just" need the latest jbossws 2.0 sources to build/run these? | The least amount of steps would be to checkout and build jbossas/trunk. The wsgen.sh and wsimport.sh scripts are in the bin directory, you can extract the needed jars from those scripte. anonymous wrote : | Also, have there been any changes to the wstools command-line options/config since 1.0.3 that I should support in our dialogs? (just point me to the docs and I can look at the details myself..) | Just a small change: http://fisheye.jboss.com/browse/JBossWS/trunk/jbossws-core/src/main/resou... -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009805#4009805 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009805

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by omatzura

Thanks Jason! I missed that one.. Obviously we should integrate with WSGenerate as well.. to make my life easier, integrated tools in soapui are launced by spawning a seperate process and running the command-line versions.. maybe not the best from a resource-perspective, but it keeps the code clean from "linking"/class-loaders/etc.. I'll try to go with this strategy for these 2 as well (unless there is some reason to do otherwise..) Do I "just" need the latest jbossws 2.0 sources to build/run these? Also, have there been any changes to the wstools command-line options/config since 1.0.3 that I should support in our dialogs? (just point me to the docs and I can look at the details myself..) regards! /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009751#4009751 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009751

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - javax classes in jbossws-client.jar

by jason.greene＠jboss.com

I noticed that javax classes are in jbossws-client.jar. Is this intentional? They should only be in the corresponding api jars. -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009722#4009722 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009722

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by jason.greene＠jboss.com

Excellent Ole! Die you see the thread I posted about WebServiceGenerate?: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=100066 If you want to start integrating with this API, I would like to get your feedback, so we can make any necessary changes (although I expect none) before 2.0.0 release. After that point, this should be a stable backwords compatble API that you and other integrators can rely on. Since your project integrates with other WS stacks, I made sure the design can accomidate various classloading strategies. So for example, you might want to create a classloader just for interfacing with jbossws, and then pass this loader to the API, and it won't pollute your main soapui loader. In the case of importing there is also an setAdditionalCompilerClasspath that you would need to use if the jbossws jars are not on the starting classpath. Also the API offers you the ability to hook in a printstream so that you can render output into a dialog. Let me know if you run into any issues or have any questions. Thanks, -Jason View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009553#4009553 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009553

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RI tools dependency

by heiko.braun＠jboss.com

Cool, that's excellent! View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009515#4009515 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009515

19 years, 2 months

1
0
0 / 0

What JIRA issues are backed up by tests?

by Thomas Diesler

FYI, I updated this page to reflect the current test coverage What JIRA issues are backed up by tests? http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQJIRATests -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: wsimport API, SPI, command line tool, and ant task

by omatzura

Great! We are just preparing soapui 1.7 and related plugins, I can add support for this tool right away.. ok? regards! /Ole eviware.com View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009221#4009221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009221

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: RI tools dependency

by jason.greene＠jboss.com

I forgot to mention, because of this you no longer need to define the path to the RI in your ant.properties in trunk. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009204#4009204 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009204

19 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev February 2007