Hey guys,
Testing 1.5 RC0 has proved that the issue specified defect isn't
actually resolved - I still only get one endpoint for the SOAP/HTTP
service when I request ?wsdl - so is this something that is not
possible, or doesn't quite fit into the roadmap for Tuscany?
That being said, 2900 is not as high priority for me anymore - thanks
to contrib2wsdl. Could we get some documentation around this tool as
part of 1.5?
I've attached my maven configuration that I've got to work with this
tool if it's any use?
Cheers,
Dave.
On Thu, May 21, 2009 at 6:14 AM, ant elder (JIRA)
<[email protected]> wrote:
>
> [
> https://issues.apache.org/jira/browse/TUSCANY-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> ant elder closed TUSCANY-2900.
> ------------------------------
>
> Resolution: Fixed
>
>> WSDL Generation does not respect all binding.ws entries
>> -------------------------------------------------------
>>
>> Key: TUSCANY-2900
>> URL: https://issues.apache.org/jira/browse/TUSCANY-2900
>> Project: Tuscany
>> Issue Type: Bug
>> Components: Java SCA Axis Binding Extension
>> Affects Versions: Java-SCA-1.4
>> Environment: Linux x86_64 Weblogic 9.2.3 JDK 1.5.0_12
>> Reporter: Dave Sowerby
>> Assignee: Simon Laws
>> Fix For: Java-SCA-1.5
>>
>>
>> If I modify the the helloworld-ws-reference-jms's helloworldwsjms.composite
>> file so that the service entry is as follows:
>> <service name="HelloWorldService">
>> <interface.java interface="helloworld.HelloWorldService" />
>> <binding.ws
>> uri="jms:/queue.sample?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61619"/>
>> <binding.ws />
>> </service>
>> I find that the generated ?wsdl does not include the binding for the JMS
>> SOAP Endpoint - only the new <binding.ws />
>> Also, there is no obvious way for accessing the original
>> helloworld-ws-reference-jms service's generated WSDL.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<phase>install</phase>
<configuration>
<tasks>
<mkdir dir="${project.build.directory}/generated-sources/wsdl" />
<java classname="org.apache.tuscany.tools.contrib2wsdl.Contrib2WSDL">
<arg line="-c ${project.build.directory}/${artifactId} -o ${project.build.directory}/generated-sources/wsdl" />
<sysproperty key="javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom"; value="org.apache.xpath.jaxp.XPathFactoryImpl" />
<classpath refid="maven.plugin.classpath" />
</java>
</tasks>
</configuration>
<goals>
<goal>run</goal>
</goals>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>org.apache.tuscany.sca</groupId>
<artifactId>tuscany-contrib2wsdl</artifactId>
<version>1.5</version>
</dependency>
<dependency>
<groupId>xalan</groupId>
<artifactId>xalan</artifactId>
<version>2.7.0</version>
</dependency>
</dependencies>
</plugin>
