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 Sa...@3com.com on 2007/03/14 23:09:43 UTC
Axis2: Interop with .NET
Hi..
We're trying to write a .NET client for our Axis2 Web Service. We have
Java clients that work just fine using our WSDL, but the .NET wsdl.exe
tool seems to choke on certain elements in our WSDL.
Case in point:
1. The element name below has a whitespace in it. This is no problem for
Axis1 or Axis2 WSDL2JAVA - but for .NET, I have to replace the white space
with an underscore.
<element name="ConnectionFailureFault">
<complexType>
<sequence>
<element name="Connection Failure" type="xsd:string"/>
</sequence>
</complexType>
</element>
I need to change the name as below:
<element name="Connection_Failure" type="xsd:string"/>
2. Having trouble with namespaces too.
<xsd:complexType name="SecurityType">
<xsd:sequence>
<xsd:element name="UsernameToken" type="wsns:UsernameTokenType"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
will only work with the WSDL.exe tool if the "wsns" is stripped from the
type.
My question to the group is:
- Has anyone encountered this before using .NET wsdl.exe?
- Is it possible we're not adhering to the rules of creating truly
interoperable design contracts, even though AXIS2 WSDL2JAVA let our WSDL
fly?
Thanks
\Sarwar
Re: Axis2: Interop with .NET
Posted by Amit Andhale <am...@gmail.com>.
Hi,
This may be the interoperability issue.
Please make sure that "namespace" specified in WSDL for complex type is same
as that of generated in WSDD file for the specified complex type. i.e.
"targetNamespace" tag value in WSDL should be same as "typeMapping"
namespace value.
Amit
On 3/15/07, Sarwar_Raza@3com.com <Sa...@3com.com> wrote:
>
>
> Hi..
> We're trying to write a .NET client for our Axis2 Web Service. We have
> Java clients that work just fine using our WSDL, but the .NET wsdl.exetool seems to choke on certain elements in our WSDL.
>
> Case in point:
> 1. The element name below has a whitespace in it. This is no problem for
> Axis1 or Axis2 WSDL2JAVA - but for .NET, I have to replace the white space
> with an underscore.
>
> <element name="ConnectionFailureFault">
> <complexType>
> <sequence>
> * <element name="Connection Failure" type="xsd:string"/>*
> </sequence>
> </complexType>
> </element>
>
>
> I need to change the name as below:
> * <element name="Connection_Failure" type="xsd:string"/>*
>
>
> 2. Having trouble with namespaces too.
> <xsd:complexType name="SecurityType">
> <xsd:sequence>
> * <xsd:element name="UsernameToken" type="wsns:UsernameTokenType"/>*
> </xsd:sequence>
> <xsd:anyAttribute namespace="##other" processContents="lax"/>
> </xsd:complexType>
>
> will only work with the WSDL.exe tool if the "wsns" is stripped from the
> type.
>
> My question to the group is:
> - Has anyone encountered this before using .NET wsdl.exe?
> - Is it possible we're not adhering to the rules of creating truly
> interoperable design contracts, even though AXIS2 WSDL2JAVA let our WSDL
> fly?
>
> Thanks
> \Sarwar
RE: WSDL URL for AXIS2 codegenerator
Posted by "Sampige, Srinivas" <SS...@DIRECTV.com>.
Hi Amila
I tried to generate a client for
http://soap.amazon.com/schemas2/AmazonWebServices.wsdl. This also
failed. I tried this since the other URL which I am actually using is
for a webservice available internal to our org. Since you requested for
the URL I tried the amazon URL. Please see the error below.
1) Snippet of ant file -
<property name="wsdl.location.scheduleRecevieService"
value="http://soap.amazon.com/schemas2/AmazonWebServices.wsdl" />
<target name="clientFromWSDL" depends="clean,prepare">
<echo message="Generating java client for
${wsdl.location.scheduleRecevieService}" />
<delete dir="${generatedOutput}" />
<java classname="org.apache.axis2.wsdl.WSDL2Java"
fork="true">
<classpath refid="axis.libraries.classpath"/>
<!-- location of the WSDL, currently this is a
local file URI -->
<!-- relative to the base dir of the ANT
project. -->
<!-- Following up with Apache to see if we can
give a absolute-->
<!-- URL to a remote webservice
-->
<arg value="-uri"/>
<arg
file="${wsdl.location.scheduleRecevieService}"/>
<!-- output location of the generated files -->
<arg value="-o"/>
<arg file="${generatedOutput}"/>
<!-- default package to be used -->
<arg value="-p"/>
<arg value="com.directv.dtss.itx.client"/>
<!-- generate code for synchronous calls only
-->
<arg value="-s"/>
<!-- use xmlbeans databinding method -->
<arg value="-d"/>
<arg value="xmlbeans"/>
<!-- namespace to package mapping -->
<arg value="-ns2p"/>
<arg
value="http://tempuri.org/=com.directv.dtss.itx.client"/>
<!-- generate service -->
<arg value ="-ss"/>
<arg value ="-g"/>
</java>
2) Error :
prepare:
[mkdir] Created dir: C:\workspace\TestAXIS2\build\classes
[mkdir] Created dir: C:\workspace\TestAXIS2\generatedOutput
clientFromWSDL:
[echo] Generating java client for
http://soap.amazon.com/schemas2/AmazonWebServices.wsdl
[delete] Deleting directory C:\workspace\TestAXIS2\generatedOutput
[java] Exception in thread "main"
org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing
WSDL
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGeneration
Engine.java:114)
[java] at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:32)
[java] at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21)
[java] Caused by: javax.wsdl.WSDLException: WSDLException:
faultCode=INVALID_WSDL: IO Error: java.io.FileNotFoundException:
C:\workspace\TestAXIS2\http:\soap.amazon.com\schemas2\AmazonWebServices.
wsdl (The filename, directory name, or volume label syntax is incorrect)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.readInTheWSDLFile(Cod
eGenerationEngine.java:273)
[java] at
org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGeneration
Engine.java:97)
[java] ... 2 more
[java] Caused by: java.io.FileNotFoundException:
C:\workspace\TestAXIS2\http:\soap.amazon.com\schemas2\AmazonWebServices.
wsdl (The filename, directory name, or volume label syntax is incorrect)
[java] at java.io.FileInputStream.open(Native Method)
[java] at java.io.FileInputStream.<init>(Unknown Source)
[java] at java.io.FileInputStream.<init>(Unknown Source)
[java] at
sun.net.www.protocol.file.FileURLConnection.connect(Unknown Source)
[java] at
sun.net.www.protocol.file.FileURLConnection.getInputStream(Unknown
Source)
[java] at
org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown
Source)
[java] at
org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown
Source)
[java] at
org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
________________________________
From: Lahiru Sandakith [mailto:sandakith@gmail.com]
Sent: Monday, March 19, 2007 8:15 PM
To: axis-user@ws.apache.org
Subject: Re: WSDL URL for AXIS2 codegenerator
Hi Srinivas,
Eclipse plugin does support the remote URL when do wsal2Java.
What went wrong in your invocation? can you post which remote wsdl that
you tried.
Thanks
Lahiru
On 3/19/07, Amila Suriarachchi <am...@gmail.com> wrote:
I have not tried with both. but it should be. I have tried with
wsdl2java tool and it works fine.
On 3/17/07, Sampige, Srinivas < SSampige@directv.com
<ma...@directv.com> > wrote:
Is it possible to provide a WSDL URL to the AXIS2 code generator? I
would like to generate a client (only) for a remote webservice. I have
tried it unsuccessfully both in the Eclipse plugin version as well as
the ANT version and I get "unexpected error occurred". Not sure if I
missed some configuration step. It works from a local file though.
-Srinivas
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
--
Amila Suriarachchi,
WSO2 Inc.
--
Regards
Lahiru Sandakith
Re: WSDL URL for AXIS2 codegenerator
Posted by Lahiru Sandakith <sa...@gmail.com>.
Hi Srinivas,
Eclipse plugin does support the remote URL when do wsal2Java.
What went wrong in your invocation? can you post which remote wsdl that you
tried.
Thanks
Lahiru
On 3/19/07, Amila Suriarachchi <am...@gmail.com> wrote:
>
> I have not tried with both. but it should be. I have tried with wsdl2java
> tool and it works fine.
>
> On 3/17/07, Sampige, Srinivas < SSampige@directv.com> wrote:
> >
> > Is it possible to provide a WSDL URL to the AXIS2 code generator? I
> > would like to generate a client (only) for a remote webservice. I have
> > tried it unsuccessfully both in the Eclipse plugin version as well as
> > the ANT version and I get "unexpected error occurred". Not sure if I
> > missed some configuration step. It works from a local file though.
> >
> > -Srinivas
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
--
Regards
Lahiru Sandakith
Re: WSDL URL for AXIS2 codegenerator
Posted by Vishal Mehra <vi...@gmail.com>.
It will good to add proxy setting information for invoking remote
webservice from CLI WSDL2Java -- it comes handy when remote service is
really remote (outside the organization)... Any plans of enhancing
WSDL2Java utility to accept proxy settings...
Thanks,
VM
On 3/19/07, Amila Suriarachchi <am...@gmail.com> wrote:
> I have not tried with both. but it should be. I have tried with wsdl2java
> tool and it works fine.
>
>
> On 3/17/07, Sampige, Srinivas < SSampige@directv.com> wrote:
> > Is it possible to provide a WSDL URL to the AXIS2 code generator? I
> > would like to generate a client (only) for a remote webservice. I have
> > tried it unsuccessfully both in the Eclipse plugin version as well as
> > the ANT version and I get "unexpected error occurred". Not sure if I
> > missed some configuration step. It works from a local file though.
> >
> > -Srinivas
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >
>
>
>
> --
> Amila Suriarachchi,
> WSO2 Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: WSDL URL for AXIS2 codegenerator
Posted by Amila Suriarachchi <am...@gmail.com>.
I have not tried with both. but it should be. I have tried with wsdl2java
tool and it works fine.
On 3/17/07, Sampige, Srinivas <SS...@directv.com> wrote:
>
> Is it possible to provide a WSDL URL to the AXIS2 code generator? I
> would like to generate a client (only) for a remote webservice. I have
> tried it unsuccessfully both in the Eclipse plugin version as well as
> the ANT version and I get "unexpected error occurred". Not sure if I
> missed some configuration step. It works from a local file though.
>
> -Srinivas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Amila Suriarachchi,
WSO2 Inc.
WSDL URL for AXIS2 codegenerator
Posted by "Sampige, Srinivas" <SS...@DIRECTV.com>.
Is it possible to provide a WSDL URL to the AXIS2 code generator? I
would like to generate a client (only) for a remote webservice. I have
tried it unsuccessfully both in the Eclipse plugin version as well as
the ANT version and I get "unexpected error occurred". Not sure if I
missed some configuration step. It works from a local file though.
-Srinivas
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: rampart-1.0.mar and Axis2
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi,
Seems like you are using axis2-1.1
Please use Rampart-1.1 with Axis2-1.1.
You have used wss4j axis-1.x type configuration and rampart
configuration is different from that. Have a look at the samples of
Rampart on sample configuration.
Also there are some articles available on different configs of Rampart :
http://www.wso2.org/library/240
http://www.wso2.org/library/255
Thanks,
Ruchith
p.s. Please post rampart related questions to rampart-dev@ws.apache.org
On 3/16/07, klasyk99@poczta.onet.pl <kl...@poczta.onet.pl> wrote:
> rampart-1.0.mar and Axis2
>
> I've added a rampart-1.0.mar module, also some lines have added to
> service.xml:
> <requestFlow>
> <handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
> <parameter name="passwordCallbackClass"
> value="sample.PWcallback.PWCallback"/>
> <parameter name="action" value="UsernameToken" />
> <parameter name="user" value="wss4j"/>
> <parameter name="passwordType" value="PasswordText" />
> </handler>
> </requestFlow>
>
> into my <service> ... </service>
>
>
> but it completely doesn't work.
> First of all, it's returned (to be honest I've no idea how can I fix
> it?]:
>
>
> 09:25:40,328 INFO [TomcatDeployer] deploy, ctxPath=/axis2,
> warUrl=.../deploy/axis2.war/
> 09:25:41,140 INFO [DeploymentEngine] Deploying module : addressing-1.1
> 09:25:41,765 ERROR [DeploymentEngine] Invalid module : rampart-1.0.mar
> caused org.apache.axis2.description.HandlerDescription.<init>(Ljavax/
> xml/namespace/QName;)V
> java.lang.NoSuchMethodError:
> org.apache.axis2.description.HandlerDescription.<init>(Ljavax/xml/namespace/QName;)V
> at
> org.apache.axis2.security.handler.WSDoAllHandler.<clinit>(WSDoAllHandler.java:38)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at
> java.lang.reflect.Constructor.newInstance(Constructor.java:494)
> at java.lang.Class.newInstance0(Class.java:350)
> at java.lang.Class.newInstance(Class.java:303)
> at
> org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:69)
> at
> org.apache.axis2.deployment.DeploymentEngine.addNewModule(DeploymentEngine.java:326)
> at
> org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:598)
> at
> org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:184)
> at
> org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:54)
> at
> org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:104)
> at
> org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:199)
> at
> org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61)
> at
> org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373)
> at
> org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317)
> at
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
> at
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925)
> at
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3857)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4118)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.apache.catalina.core.StandardContext.init(StandardContext.java:5005)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
> at
> org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:280)
> at
> org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:88)
> at
> org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
> at org.jboss.web.WebModule.startModule(WebModule.java:68)
> at org.jboss.web.WebModule.startService(WebModule.java:46)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.system.ServiceController
> $ServiceProxy.invoke(ServiceController.java:943)
> at $Proxy0.start(Unknown Source)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:428)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy27.start(Unknown Source)
> at
> org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:400)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
> at
> org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy28.start(Unknown Source)
> at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
> at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy9.deploy(Unknown Source)
> at
> org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
> at
> org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
> at org.jboss.deployment.scanner.AbstractDeploymentScanner
> $ScannerThread.doScan(AbstractDeploymentScanner.java:192)
> at
> org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:265)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
> at
> org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
> at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at org.jboss.system.ServiceController
> $ServiceProxy.invoke(ServiceController.java:943)
> at $Proxy0.start(Unknown Source)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:428)
> at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy4.start(Unknown Source)
> at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
> at
> org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
> at
> org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at
> org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
> at
> org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at
> org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
> at
> org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
> at
> org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
> at
> org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
> at $Proxy5.deploy(Unknown Source)
> at
> org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
> at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
> at org.jboss.Main.boot(Main.java:187)
> at org.jboss.Main$1.run(Main.java:438)
> at java.lang.Thread.run(Thread.java:595)
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
www.ruchith.org
www.wso2.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
rampart-1.0.mar and Axis2
Posted by "klasyk99@poczta.onet.pl" <kl...@poczta.onet.pl>.
rampart-1.0.mar and Axis2
I've added a rampart-1.0.mar module, also some lines have added to
service.xml:
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
<parameter name="passwordCallbackClass"
value="sample.PWcallback.PWCallback"/>
<parameter name="action" value="UsernameToken" />
<parameter name="user" value="wss4j"/>
<parameter name="passwordType" value="PasswordText" />
</handler>
</requestFlow>
into my <service> ... </service>
but it completely doesn't work.
First of all, it's returned (to be honest I've no idea how can I fix
it?]:
09:25:40,328 INFO [TomcatDeployer] deploy, ctxPath=/axis2,
warUrl=.../deploy/axis2.war/
09:25:41,140 INFO [DeploymentEngine] Deploying module : addressing-1.1
09:25:41,765 ERROR [DeploymentEngine] Invalid module : rampart-1.0.mar
caused org.apache.axis2.description.HandlerDescription.<init>(Ljavax/
xml/namespace/QName;)V
java.lang.NoSuchMethodError:
org.apache.axis2.description.HandlerDescription.<init>(Ljavax/xml/namespace/QName;)V
at
org.apache.axis2.security.handler.WSDoAllHandler.<clinit>(WSDoAllHandler.java:38)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at java.lang.Class.newInstance0(Class.java:350)
at java.lang.Class.newInstance(Class.java:303)
at
org.apache.axis2.deployment.util.Utils.addFlowHandlers(Utils.java:69)
at
org.apache.axis2.deployment.DeploymentEngine.addNewModule(DeploymentEngine.java:326)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:598)
at
org.apache.axis2.deployment.RepositoryListener.init(RepositoryListener.java:184)
at
org.apache.axis2.deployment.RepositoryListener.<init>(RepositoryListener.java:54)
at
org.apache.axis2.deployment.DeploymentEngine.loadRepository(DeploymentEngine.java:104)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.getAxisConfiguration(WarBasedAxisConfigurator.java:199)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:61)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:373)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:317)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:925)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3857)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4118)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.apache.catalina.core.StandardContext.init(StandardContext.java:5005)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503)
at
org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:150)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:280)
at
org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:88)
at
org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:357)
at org.jboss.web.WebModule.startModule(WebModule.java:68)
at org.jboss.web.WebModule.startService(WebModule.java:46)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController
$ServiceProxy.invoke(ServiceController.java:943)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:428)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy27.start(Unknown Source)
at
org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:400)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at
org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy28.start(Unknown Source)
at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy9.deploy(Unknown Source)
at
org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:319)
at
org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:507)
at org.jboss.deployment.scanner.AbstractDeploymentScanner
$ScannerThread.doScan(AbstractDeploymentScanner.java:192)
at
org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:265)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:274)
at
org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:230)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at org.jboss.system.ServiceController
$ServiceProxy.invoke(ServiceController.java:943)
at $Proxy0.start(Unknown Source)
at
org.jboss.system.ServiceController.start(ServiceController.java:428)
at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
at
org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
at
org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
at
org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:118)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:127)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
at
org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:245)
at
org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
at
org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at
org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
at org.jboss.Main.boot(Main.java:187)
at org.jboss.Main$1.run(Main.java:438)
at java.lang.Thread.run(Thread.java:595)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2: Interop with .NET
Posted by Paul Fremantle <pz...@gmail.com>.
The Eclipse WebTools project is a large download, but it does include
a WSDL validator that is pretty good in my opinion.
http://www.eclipse.org/webtools/main.php
Paul
On 3/15/07, Anne Thomas Manes <at...@gmail.com> wrote:
> Whitespace is not a valid character in an XML local name. I suggest
> you submit a JIRA to fix Axis and Axis2 to disallow use of whitespace
> in an XML local name.
>
> As for the namespace reference, have you declared the "wsns" namespace
> and have you imported it into the schema?
>
> I also suggest that you validate the WSDL/schema before attempting to
> generate clients from it.
>
> Anne
>
> On 3/14/07, Sarwar_Raza@3com.com <Sa...@3com.com> wrote:
> >
> > Hi..
> > We're trying to write a .NET client for our Axis2 Web Service. We have Java
> > clients that work just fine using our WSDL, but the .NET wsdl.exe tool seems
> > to choke on certain elements in our WSDL.
> >
> > Case in point:
> > 1. The element name below has a whitespace in it. This is no problem for
> > Axis1 or Axis2 WSDL2JAVA - but for .NET, I have to replace the white space
> > with an underscore.
> >
> > <element name="ConnectionFailureFault">
> > <complexType>
> > <sequence>
> > <element name="Connection Failure" type="xsd:string"/>
> > </sequence>
> > </complexType>
> > </element>
> >
> >
> > I need to change the name as below:
> > <element name="Connection_Failure" type="xsd:string"/>
> >
> >
> > 2. Having trouble with namespaces too.
> > <xsd:complexType name="SecurityType">
> > <xsd:sequence>
> > <xsd:element name="UsernameToken" type="wsns:UsernameTokenType"/>
> > </xsd:sequence>
> > <xsd:anyAttribute namespace="##other" processContents="lax"/>
> > </xsd:complexType>
> >
> > will only work with the WSDL.exe tool if the "wsns" is stripped from the
> > type.
> >
> > My question to the group is:
> > - Has anyone encountered this before using .NET wsdl.exe?
> > - Is it possible we're not adhering to the rules of creating truly
> > interoperable design contracts, even though AXIS2 WSDL2JAVA let our WSDL
> > fly?
> >
> > Thanks
> > \Sarwar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2: Interop with .NET
Posted by Anne Thomas Manes <at...@gmail.com>.
Whitespace is not a valid character in an XML local name. I suggest
you submit a JIRA to fix Axis and Axis2 to disallow use of whitespace
in an XML local name.
As for the namespace reference, have you declared the "wsns" namespace
and have you imported it into the schema?
I also suggest that you validate the WSDL/schema before attempting to
generate clients from it.
Anne
On 3/14/07, Sarwar_Raza@3com.com <Sa...@3com.com> wrote:
>
> Hi..
> We're trying to write a .NET client for our Axis2 Web Service. We have Java
> clients that work just fine using our WSDL, but the .NET wsdl.exe tool seems
> to choke on certain elements in our WSDL.
>
> Case in point:
> 1. The element name below has a whitespace in it. This is no problem for
> Axis1 or Axis2 WSDL2JAVA - but for .NET, I have to replace the white space
> with an underscore.
>
> <element name="ConnectionFailureFault">
> <complexType>
> <sequence>
> <element name="Connection Failure" type="xsd:string"/>
> </sequence>
> </complexType>
> </element>
>
>
> I need to change the name as below:
> <element name="Connection_Failure" type="xsd:string"/>
>
>
> 2. Having trouble with namespaces too.
> <xsd:complexType name="SecurityType">
> <xsd:sequence>
> <xsd:element name="UsernameToken" type="wsns:UsernameTokenType"/>
> </xsd:sequence>
> <xsd:anyAttribute namespace="##other" processContents="lax"/>
> </xsd:complexType>
>
> will only work with the WSDL.exe tool if the "wsns" is stripped from the
> type.
>
> My question to the group is:
> - Has anyone encountered this before using .NET wsdl.exe?
> - Is it possible we're not adhering to the rules of creating truly
> interoperable design contracts, even though AXIS2 WSDL2JAVA let our WSDL
> fly?
>
> Thanks
> \Sarwar
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: Axis2: Interop with .NET
Posted by Martin Gainty <mg...@hotmail.com>.
If you are using the Web Services Resource Transfer specification
you'll need to specify the specific namespace declaration
http://schemas.xmlsoap.org/ws/2006/08/resourceTransfer/wsrt.xsd
If you're using the Wireless Sensor Network System then you will need to locate the xsd (or write one yourself)
Of course your best bet is to find the person that created the WSDL and ask him for the specific locations of the XSD's
Heres a PhD that started on that road last year
http://mailman.doc.ic.ac.uk/pipermail/ukubinet-announce/2006-July/000235.html
then again if you have the wsdl you can always grep for the string which follows 'xlmns:wsns'
This WSNS is being called in almost every application I've seen
Keep me apprised,
Martin--
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited.
---------------------------------------------------------------------------
Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire.
----- Original Message -----
From: Sarwar_Raza@3com.com
To: axis-user@ws.apache.org
Sent: Wednesday, March 14, 2007 6:09 PM
Subject: Axis2: Interop with .NET
Hi..
We're trying to write a .NET client for our Axis2 Web Service. We have Java clients that work just fine using our WSDL, but the .NET wsdl.exe tool seems to choke on certain elements in our WSDL.
Case in point:
1. The element name below has a whitespace in it. This is no problem for Axis1 or Axis2 WSDL2JAVA - but for .NET, I have to replace the white space with an underscore.
<element name="ConnectionFailureFault">
<complexType>
<sequence>
<element name="Connection Failure" type="xsd:string"/>
</sequence>
</complexType>
</element>
I need to change the name as below:
<element name="Connection_Failure" type="xsd:string"/>
2. Having trouble with namespaces too.
<xsd:complexType name="SecurityType">
<xsd:sequence>
<xsd:element name="UsernameToken" type="wsns:UsernameTokenType"/>
</xsd:sequence>
<xsd:anyAttribute namespace="##other" processContents="lax"/>
</xsd:complexType>
will only work with the WSDL.exe tool if the "wsns" is stripped from the type.
My question to the group is:
- Has anyone encountered this before using .NET wsdl.exe?
- Is it possible we're not adhering to the rules of creating truly interoperable design contracts, even though AXIS2 WSDL2JAVA let our WSDL fly?
Thanks
\Sarwar