You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Andreas Bobek <an...@uni-rostock.de> on 2006/03/24 17:49:39 UTC
[Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in
WSDL
Hi,
I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
Code generation works well.
Deploying with bindings to SOAP 1.1 works well, too.
But when bind to SOAP 1.2 I get follow exception:
org.apache.wsdl.impl.WSDLProcessingException: no port with soap binding
found
at
org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
lder.java:219)
at
org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
lder.java:127)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(Ar
chiveReader.java:267)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(Archi
veReader.java:333)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:
383)
..
which I think means WSDL-SOAP 1.2 is not known.
Debugging inside AxisServiceBuilder:
javax.wsdl.extensions.UnknownExtensibilityElement
UnknownExtensibilityElement
({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
Is this a limitation in Axis up to now?
Thank you, Andreas Bobek.
WG: Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2
in WSDL
Posted by Andreas Bobek <an...@uni-rostock.de>.
Hi Anne,
thank you for the specification.
I'm very interested in WSDL 1.1 to SOAP 1.2 binding. I need it to work
with the Devices Profile (it's a MUST there).
I use axis-wsdl4j-1.2.jar (inside Axis2 libs). Does anybody know
whether this is supporting 1.2 binding or 1.1 binding only?
Will 1.2 binding be supported in the final Axis2 release?
Thank you, Andreas.
----- Originalnachricht -----
Von: Anne Thomas Manes <at...@gmail.com>
Datum: Samstag, März 25, 2006 5:11 pm
Betreff: Re: [Axis2-0.94] service deploy fails when ports bound to SOAP
1.2 in WSDL
An: axis-user@ws.apache.org
> Axis supports SOAP 1.2, but perhaps the version of wsdl4j that
> you're using
> doesn't.
>
> FYI: Just found this new specification from IBM, Microsoft,
> Oracle, and SAP:
> a formal definition of a SOAP 1.2 binding for WSDL 1.1:
>
> http://www.oracle.com/technology/tech/webservices/pdf/WSDL11SOAP12.pdf
>
> And also, a SOAP 1.1 binding for MTOM:
>
> http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-
> soapbinding/ws-soap11.pdf
>
> Anne
>
>
> On 3/24/06, Andreas Bobek <an...@uni-rostock.de> wrote:
> >
> > Hi,
> >
> > I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> >
> > xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
> > xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
> >
> > Code generation works well.
> > Deploying with bindings to SOAP 1.1 works well, too.
> >
> > But when bind to SOAP 1.2 I get follow exception:
> >
> > org.apache.wsdl.impl.WSDLProcessingException: no port with soap
> binding> found
> > at
> > org.apache.axis2.deployment.AxisServiceBuilder.getAxisService
> > (AxisServiceBui
> > lder.java:219)
> > at
> > org.apache.axis2.deployment.AxisServiceBuilder.getAxisService
> > (AxisServiceBui
> > lder.java:127)
> > at
> >
>
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFil
e> (Ar
> > chiveReader.java:267)
> > at
> >
>
org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs>
(Archi
> > veReader.java:333)
> > at
> > org.apache.axis2.deployment.DeploymentEngine.doDeploy(
> > DeploymentEngine.java:
> > 383)
> > ..
> >
> > which I think means WSDL-SOAP 1.2 is not known.
> >
> > Debugging inside AxisServiceBuilder:
> > javax.wsdl.extensions.UnknownExtensibilityElement
> > UnknownExtensibilityElement
> > ({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> >
> > Is this a limitation in Axis up to now?
> >
> > Thank you, Andreas Bobek.
> >
> >
>
Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL
Posted by Anne Thomas Manes <at...@gmail.com>.
Axis supports SOAP 1.2, but perhaps the version of wsdl4j that you're using
doesn't.
FYI: Just found this new specification from IBM, Microsoft, Oracle, and SAP:
a formal definition of a SOAP 1.2 binding for WSDL 1.1:
http://www.oracle.com/technology/tech/webservices/pdf/WSDL11SOAP12.pdf
And also, a SOAP 1.1 binding for MTOM:
http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-soapbinding/ws-soap11.pdf
Anne
On 3/24/06, Andreas Bobek <an...@uni-rostock.de> wrote:
>
> Hi,
>
> I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
>
> xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
> xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
>
> Code generation works well.
> Deploying with bindings to SOAP 1.1 works well, too.
>
> But when bind to SOAP 1.2 I get follow exception:
>
> org.apache.wsdl.impl.WSDLProcessingException: no port with soap binding
> found
> at
> org.apache.axis2.deployment.AxisServiceBuilder.getAxisService
> (AxisServiceBui
> lder.java:219)
> at
> org.apache.axis2.deployment.AxisServiceBuilder.getAxisService
> (AxisServiceBui
> lder.java:127)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile
> (Ar
> chiveReader.java:267)
> at
> org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs
> (Archi
> veReader.java:333)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(
> DeploymentEngine.java:
> 383)
> ..
>
> which I think means WSDL-SOAP 1.2 is not known.
>
> Debugging inside AxisServiceBuilder:
> javax.wsdl.extensions.UnknownExtensibilityElement
> UnknownExtensibilityElement
> ({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
>
> Is this a limitation in Axis up to now?
>
> Thank you, Andreas Bobek.
>
>
RE: [Axis2-0.95] How to free objects ?
Posted by "Inoguchi, Kinichiro" <Ki...@hp.com>.
I created new issue as 528.
https://issues.apache.org/jira/browse/AXIS2-528
Thanks,
kinichiro
-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]
Sent: Monday, March 27, 2006 10:55 PM
To: axis-user@ws.apache.org
Subject: Re: [Axis2-0.95] How to free objects ?
Can u please open a JIRA bug report?
thanks,
dims
On 3/27/06, Inoguchi, Kinichiro <Ki...@hp.com> wrote:
> Hi,
>
> At client-side, how to free objects after receiving response message ?
>
> I tested getVersion sample with stub modules generated by WSDL2Java.
> This test class 'testVersion' calls getVersion service 10,000 times.
>
> While running this test class, memory size of client-side-jvm keeps
> incleasing.
>
> Has anyone know ?
>
> Thanks,
> kinichiro
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2-0.95] How to free objects ?
Posted by Davanum Srinivas <da...@gmail.com>.
Can u please open a JIRA bug report?
thanks,
dims
On 3/27/06, Inoguchi, Kinichiro <Ki...@hp.com> wrote:
> Hi,
>
> At client-side, how to free objects after receiving response message ?
>
> I tested getVersion sample with stub modules generated by WSDL2Java.
> This test class 'testVersion' calls getVersion service 10,000 times.
>
> While running this test class, memory size of client-side-jvm keeps
> incleasing.
>
> Has anyone know ?
>
> Thanks,
> kinichiro
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL
Posted by Davanum Srinivas <da...@gmail.com>.
This has been fixed in latest SVN :)
-- dims
On 4/5/06, Andreas Bobek <an...@uni-rostock.de> wrote:
>
> Both, code generation and deploying of WSDL 1.1 / SOAP 1.2 services is now
> working in 0.95 :-)
>
> BUT,
>
> if I use AxisService.printWSDL(OutputStream out, String requestIP)
> I get a WSDL with SOAP 1.1 binding!
> Furthermore, if there is no SOAP 1.1 namespace declared in the original WSDL
> file, I get an exception
>
> WSDLException: faultCode=OTHER_ERROR: Can't find prefix for
> 'http://schemas.xmlsoap.org/wsdl/soap/'. Namespace prefixes must be set on
> the Definition object using the addNamespace(...) method.:
> at
> org.apache.axis2.description.AxisService.printUsingWSDLDefinition(AxisServic
> e.java:497)
> at
> org.apache.axis2.description.AxisService.printWSDL(AxisService.java:427)
> ...
>
>
> I suppose this a limitation of WSDL4J ?
>
> Just for info,
> Andreas Bobek.
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Deepal Jayasinghe [mailto:deepal@opensource.lk]
> > Gesendet: Dienstag, 28. März 2006 06:16
> > An: axis-user@ws.apache.org
> > Betreff: Re: [Axis2-0.94] service deploy fails when ports
> > bound to SOAP 1.2 in WSDL
> >
> > oh I didnt know that :(
> >
> > Davanum Srinivas wrote:
> >
> > >Deepal,
> > >
> > >Already fixed :) see http://tinyurl.com/jy8mz fix should be in 0.95.
> > >
> > >-- dims
> > >
> > >On 3/26/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
> > >
> > >
> > >>yes , thats a bug in Axis2 and we will fix that before 1.0.
> > >>
> > >>Andreas Bobek wrote:
> > >>
> > >>
> > >>
> > >>>Hi,
> > >>>
> > >>>I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> > >>>
> > >>>xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
> > >>>xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
> > >>>
> > >>>Code generation works well.
> > >>>Deploying with bindings to SOAP 1.1 works well, too.
> > >>>
> > >>>But when bind to SOAP 1.2 I get follow exception:
> > >>>
> > >>>org.apache.wsdl.impl.WSDLProcessingException: no port with soap
> > >>>binding found
> > >>> at
> > >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> > ce(AxisSer
> > >>>viceBui
> > >>>lder.java:219)
> > >>> at
> > >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> > ce(AxisSer
> > >>>viceBui
> > >>>lder.java:127)
> > >>> at
> > >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> > rocessWSDL
> > >>>File(Ar
> > >>>chiveReader.java:267)
> > >>> at
> > >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> > rocessWSDL
> > >>>s(Archi
> > >>>veReader.java:333)
> > >>> at
> > >>>org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deplo
> > ymentEngine.java:
> > >>>383)
> > >>>..
> > >>>
> > >>>which I think means WSDL-SOAP 1.2 is not known.
> > >>>
> > >>>Debugging inside AxisServiceBuilder:
> > >>>javax.wsdl.extensions.UnknownExtensibilityElement
> > >>>UnknownExtensibilityElement
> > >>>({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> > >>>
> > >>>Is this a limitation in Axis up to now?
> > >>>
> > >>>Thank you, Andreas Bobek.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>--
> > >>Thanks,
> > >>Deepal
> > >>................................................................
> > >>~Future is Open~
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> > >--
> > >Davanum Srinivas : http://wso2.com/blogs/
> > >
> > >
> > >
> > >
> >
> > --
> > Thanks,
> > Deepal
> > ...............................................................
> > ~Future is Open~
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
AW: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in
WSDL
Posted by Andreas Bobek <an...@uni-rostock.de>.
Both, code generation and deploying of WSDL 1.1 / SOAP 1.2 services is now
working in 0.95 :-)
BUT,
if I use AxisService.printWSDL(OutputStream out, String requestIP)
I get a WSDL with SOAP 1.1 binding!
Furthermore, if there is no SOAP 1.1 namespace declared in the original WSDL
file, I get an exception
WSDLException: faultCode=OTHER_ERROR: Can't find prefix for
'http://schemas.xmlsoap.org/wsdl/soap/'. Namespace prefixes must be set on
the Definition object using the addNamespace(...) method.:
at
org.apache.axis2.description.AxisService.printUsingWSDLDefinition(AxisServic
e.java:497)
at
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:427)
...
I suppose this a limitation of WSDL4J ?
Just for info,
Andreas Bobek.
> -----Ursprüngliche Nachricht-----
> Von: Deepal Jayasinghe [mailto:deepal@opensource.lk]
> Gesendet: Dienstag, 28. März 2006 06:16
> An: axis-user@ws.apache.org
> Betreff: Re: [Axis2-0.94] service deploy fails when ports
> bound to SOAP 1.2 in WSDL
>
> oh I didnt know that :(
>
> Davanum Srinivas wrote:
>
> >Deepal,
> >
> >Already fixed :) see http://tinyurl.com/jy8mz fix should be in 0.95.
> >
> >-- dims
> >
> >On 3/26/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
> >
> >
> >>yes , thats a bug in Axis2 and we will fix that before 1.0.
> >>
> >>Andreas Bobek wrote:
> >>
> >>
> >>
> >>>Hi,
> >>>
> >>>I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> >>>
> >>>xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
> >>>xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
> >>>
> >>>Code generation works well.
> >>>Deploying with bindings to SOAP 1.1 works well, too.
> >>>
> >>>But when bind to SOAP 1.2 I get follow exception:
> >>>
> >>>org.apache.wsdl.impl.WSDLProcessingException: no port with soap
> >>>binding found
> >>> at
> >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> ce(AxisSer
> >>>viceBui
> >>>lder.java:219)
> >>> at
> >>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisServi
> ce(AxisSer
> >>>viceBui
> >>>lder.java:127)
> >>> at
> >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> rocessWSDL
> >>>File(Ar
> >>>chiveReader.java:267)
> >>> at
> >>>org.apache.axis2.deployment.repository.util.ArchiveReader.p
> rocessWSDL
> >>>s(Archi
> >>>veReader.java:333)
> >>> at
> >>>org.apache.axis2.deployment.DeploymentEngine.doDeploy(Deplo
> ymentEngine.java:
> >>>383)
> >>>..
> >>>
> >>>which I think means WSDL-SOAP 1.2 is not known.
> >>>
> >>>Debugging inside AxisServiceBuilder:
> >>>javax.wsdl.extensions.UnknownExtensibilityElement
> >>>UnknownExtensibilityElement
> >>>({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> >>>
> >>>Is this a limitation in Axis up to now?
> >>>
> >>>Thank you, Andreas Bobek.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>--
> >>Thanks,
> >>Deepal
> >>................................................................
> >>~Future is Open~
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
> >--
> >Davanum Srinivas : http://wso2.com/blogs/
> >
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ...............................................................
> ~Future is Open~
>
>
Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2
in WSDL
Posted by Deepal Jayasinghe <de...@opensource.lk>.
oh I didnt know that :(
Davanum Srinivas wrote:
>Deepal,
>
>Already fixed :) see http://tinyurl.com/jy8mz fix should be in 0.95.
>
>-- dims
>
>On 3/26/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
>
>>yes , thats a bug in Axis2 and we will fix that before 1.0.
>>
>>Andreas Bobek wrote:
>>
>>
>>
>>>Hi,
>>>
>>>I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
>>>
>>>xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
>>>xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
>>>
>>>Code generation works well.
>>>Deploying with bindings to SOAP 1.1 works well, too.
>>>
>>>But when bind to SOAP 1.2 I get follow exception:
>>>
>>>org.apache.wsdl.impl.WSDLProcessingException: no port with soap binding
>>>found
>>> at
>>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
>>>lder.java:219)
>>> at
>>>org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
>>>lder.java:127)
>>> at
>>>org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(Ar
>>>chiveReader.java:267)
>>> at
>>>org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(Archi
>>>veReader.java:333)
>>> at
>>>org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:
>>>383)
>>>..
>>>
>>>which I think means WSDL-SOAP 1.2 is not known.
>>>
>>>Debugging inside AxisServiceBuilder:
>>>javax.wsdl.extensions.UnknownExtensibilityElement
>>>UnknownExtensibilityElement
>>>({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
>>>
>>>Is this a limitation in Axis up to now?
>>>
>>>Thank you, Andreas Bobek.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>--
>>Thanks,
>>Deepal
>>................................................................
>>~Future is Open~
>>
>>
>>
>>
>>
>>
>
>
>--
>Davanum Srinivas : http://wso2.com/blogs/
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2 in WSDL
Posted by Davanum Srinivas <da...@gmail.com>.
Deepal,
Already fixed :) see http://tinyurl.com/jy8mz fix should be in 0.95.
-- dims
On 3/26/06, Deepal Jayasinghe <de...@opensource.lk> wrote:
> yes , thats a bug in Axis2 and we will fix that before 1.0.
>
> Andreas Bobek wrote:
>
> >Hi,
> >
> >I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
> >
> >xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
> >xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
> >
> >Code generation works well.
> >Deploying with bindings to SOAP 1.1 works well, too.
> >
> >But when bind to SOAP 1.2 I get follow exception:
> >
> >org.apache.wsdl.impl.WSDLProcessingException: no port with soap binding
> >found
> > at
> >org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
> >lder.java:219)
> > at
> >org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
> >lder.java:127)
> > at
> >org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(Ar
> >chiveReader.java:267)
> > at
> >org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(Archi
> >veReader.java:333)
> > at
> >org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:
> >383)
> >..
> >
> >which I think means WSDL-SOAP 1.2 is not known.
> >
> >Debugging inside AxisServiceBuilder:
> >javax.wsdl.extensions.UnknownExtensibilityElement
> >UnknownExtensibilityElement
> >({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
> >
> >Is this a limitation in Axis up to now?
> >
> >Thank you, Andreas Bobek.
> >
> >
> >
> >
> >
>
> --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
>
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
[Axis2-0.95] How to free objects ?
Posted by "Inoguchi, Kinichiro" <Ki...@hp.com>.
Hi,
At client-side, how to free objects after receiving response message ?
I tested getVersion sample with stub modules generated by WSDL2Java.
This test class 'testVersion' calls getVersion service 10,000 times.
While running this test class, memory size of client-side-jvm keeps
incleasing.
Has anyone know ?
Thanks,
kinichiro
Re: [Axis2-0.94] service deploy fails when ports bound to SOAP 1.2
in WSDL
Posted by Deepal Jayasinghe <de...@opensource.lk>.
yes , thats a bug in Axis2 and we will fix that before 1.0.
Andreas Bobek wrote:
>Hi,
>
>I have a WSDL file with a binding to SOAP 1.2 only, e.g. I use
>
>xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" instead of
>xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/"
>
>Code generation works well.
>Deploying with bindings to SOAP 1.1 works well, too.
>
>But when bind to SOAP 1.2 I get follow exception:
>
>org.apache.wsdl.impl.WSDLProcessingException: no port with soap binding
>found
> at
>org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
>lder.java:219)
> at
>org.apache.axis2.deployment.AxisServiceBuilder.getAxisService(AxisServiceBui
>lder.java:127)
> at
>org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLFile(Ar
>chiveReader.java:267)
> at
>org.apache.axis2.deployment.repository.util.ArchiveReader.processWSDLs(Archi
>veReader.java:333)
> at
>org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:
>383)
>..
>
>which I think means WSDL-SOAP 1.2 is not known.
>
>Debugging inside AxisServiceBuilder:
>javax.wsdl.extensions.UnknownExtensibilityElement
>UnknownExtensibilityElement
>({http://schemas.xmlsoap.org/wsdl/soap12/}binding)
>
>Is this a limitation in Axis up to now?
>
>Thank you, Andreas Bobek.
>
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~