John,
I had to revert the 1.6 because of problem in wsdl2java for
axis2\modules\samples\wsdl\perf.wsdl.
In this wsdl, see the snippet below.
<wsdl:portType name="PerfPortType">
<wsdl:operation name="handleStringArray" parameterOrder="input">
<wsdl:input name="handleStringArrayRequest"
message="impl:handleStringArrayRequest"/>
<wsdl:output name="handleStringArrayResponse"
message="impl:handleStringArrayResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="PerformanceSoapBinding" type="impl:PerfPortType">
<wsdlsoap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="handleStringArray">
<wsdlsoap:operation soapAction="handleStringArray"/>
<wsdl:input>
<wsdlsoap:body use="literal"/>
</wsdl:input>
<wsdl:output>
<wsdlsoap:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
in WSDLReaderImpl.java, line 1037, you try to look up the operation using
portType.getOperation(name, inputName, outputName);
unfortunately in the lines just before that you set the inputName and
outputName to ":none" (Constants.NONE) in WSDL4J 1.6
These 2 variables are set to null in WSDL 1.5.3, so the lookup
succeeds, whereas in 1.6 it fails (as it tries to look for inputName =
":none")
Sorry, i won't recommend moving Axis2 1.1 to WSDL4J 1.6 because of this problem.
thanks,
dims
On 9/22/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
I see other failures :( let's see if i can fix it quickly.
-- dims
On 9/22/06, John Kaputin (gmail) <[EMAIL PROTECTED]> wrote:
> Dims,
> I just noticed the Axis2 build breaks due to WSDLLocator.close() and
> DOM2Writer.nodeToString in WSDL4J 1.6, but see you've now fixed them. Thanks
> for getting v1.6 into Axis2.
>
> John Kaputin.
>
>
> On 9/22/06, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
> >
> > Done.
> >
> > thanks,
> > dims
> >
> > On 9/22/06, John Kaputin (gmail) <[EMAIL PROTECTED]> wrote:
> > > Folks,
> > > I notice an update to properties.xml from Sept 16th that replaces
> WSDL4J
> > > 1.5.2 with v1.5.3, released last week to roll up a few fixes. Can you
> use
> > > WSDL4J v1.6 in the Axis2 1.1 release instead?
> > >
> > > WSDL4J 1.6 was also released last week. This includes not only the
> fixes in
> > > 1.5.3 but also some of the outstanding Issue Trackers requesting new
> > > function that involved additions to the API (delivered as a maintenance
> > > release of JSR110). Note, these are "additions" to the API, hence v1.6
> is
> > > backward compatible with 1.5.x.
> > >
> > > Some of those Issue Trackers were raised by the Axis community
> including
> > > the use of /META-INF/services property file to specify the factory class
> and
> > > a close() method on WSDLLocator interface. Other changes include
> relaxing
> > > the WSDL extensibility rules to permit every WSDL element to have
> extension
> > > elements and attributes (per WS-I BP 1.1, in support of JAXWS) and SOAP
> 1.2
> > > binding extensions.
> > >
> > > You can see the 1.6 release at sourceforge.net/projects/wsdl4j for full
> > > details (see file JSR110-maint-rel-1_2- changelog.pdf).
> > >
> > > regards,
> > > John Kaputin.
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
