4 Replies Latest reply on May 23, 2005 8:09 AM by Thomas Diesler

    JBossWS Tools: XML based configuration file

    Anil Saldanha Master

      http://jira.jboss.com/jira/browse/JBWS-110

      There are 4 tasks that can be done via jbossws, command line tool for JBossWS tools - JavaToWSDL, JavaToXSD, WSDLToJava and XSDToJava.

      I am thinking of the following structure for JavaToWSDL task in the configuration file. Similar elements can be created for the other tasks.

      <!--This is the config file used by jbossws-->
      <configuration>
       <javatowsdl>
       <service name="SomeService"
       interface="org.jboss.myinterfaces.mySEI"
       packagename="org.jboss.test"
       wsdlstyle="rpc"
       wsdldest="output/resources/tools/config"/>
       <namespaces targetns="http://org.jboss/types"
       typens="http://org.jboss/types" />
       <mapping directory="output/resources/tools/config"
       filename="jaxrpc-mapping.xml" />
       </javatowsdl>
      </configuration>
      


      Please provide feedback.

      One thing I have decided is that there will be no command line options passed to jbossws. Everything that is needed is via this xml file.

      Do you think creating a Schema file for the configuration file is necessary?

      No surprise! A single xml configuration file can have multiple elements from the 4 tasks I mentioned above AND jbossws will generate the artifacts.



        • 1. Re: JBossWS Tools: XML based configuration file
          Anil Saldanha Master

          There will be additional attributes/elements within each of the 4 major elements - JavaToWSDL, JavaToXSD,..... I do not need feedback about those. :-)

          I am interested in knowing whether you think the above block is intuitive to users, when backed with good documentation in the JBossWS Tools document??

          • 2. Re: JBossWS Tools: XML based configuration file
            Thomas Diesler Master

            There are really just two modes for the tool:

            1: client side working from wsdl
            2. server side working from java

            Some of the options (i.e. targetNamespace) apply accross the fine grained tasks. The tasks java2wsdl and java2xsd should both be run for server side for example. There is also the webservices.xml artifact for the server side.

            You may want to have common options for server/client side plus individual options for the fine grained tasks.

            Yes, we need a schema for the config file once it is reasonably stable. The test build should have a generation step that builds the artifacts that are currently generated by wscompile.

            • 3. Re: JBossWS Tools: XML based configuration file
              Ole Matzura Novice

              Hi all!

              Hope I'm not out of line here :-) We are building a fairly large SOA with JBoss where we start from WSDLs on both server and client side.. so a third mode

              3. server side working from wsdl

              will definetly be required for us

              on a personal note, I think that generating WSDL's from java is like generating interfaces from classes (interfaces/WSDLs are abstract definitions, java-web-services/classes are implementations), which I find a bit "backwards" from a design point of view and fairly unusual in the java community (generating interfaces from classes ;-) maybe i'm wrong here.. !?

              regards!

              /Ole

              • 4. Re: JBossWS Tools: XML based configuration file
                Thomas Diesler Master

                In my desription of the modes I was perhaps to restrictive. It should be possible to generate the server side artifacts from wsdl.

                Generating the client side from SEI is probably indeed nonsense.

                Ole, from an accademic point of view you're probably right. However, the vast majority of people start of with the SEI when providing a service endpoint.