Re: how to specify encodingStyle ?
Thank you for responding. I did read something about this: http://www-128.ibm.com/developerworks/webservices/library/ws-tip-j2eenet1/ But I couldn't confirm it by reading the specs on ws.apache.org/axis any references to specs related to this would be appreciated. best regards, raymond On Mon, 1 May 2006 20:25:20 -0500, Anne Thomas Manes wrote > "literal" means there is no encoding style. It is inappropriate to specify > one. > > Anne > > On 5/1/06, Raymond Domingo <[EMAIL PROTECTED]> wrote: > > > > Hello, > > > > Is there really no way to enable encodingStyle when using rpc literal ? > > > > In the request I recieve from some (soap) client there is an > > encodingStyle, > > but the response from my axis server has no encodintStyle. I suspect this > > is > > the cause why my clients to throw an exception. > > > > client request: > > > > http://schemas.xmlsoap.org/soap/envelope/"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > > xmlns:xsd="http://www.w3.org/2001/XMLSchema";> > > > > > SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml";> > > > > > > > > > > server response: > > http://schemas.xmlsoap.org/soap/envelope/ > > " > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"; > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> > > > > > > > > > > Any hints please ? > > > > thnx > > raymond domingo > >
Re: [Axis2] cannot create war with axis2-std-1.0-RC3-src.zip
Hi Robert,
Thanks! After running "maven release" ran into 2 issues: 1st one was maven asking for a username. After specifying the user name on the cmd line, the build failed trying to create a process that would secure shell. Any tips here? The output from "maven release" and "maven -
Dmaven.username=xyz" is below
If there is any documentation for all of this, please guide me to it
Thanks,
Al
C:\axis2-std-1.0-RC3-src> maven release
build:start:
release:validate-pom-for-release:
pom:deploy: [echo] maven.repo.list is not set - using legacy deploy mode [echo] DEPRECATED: use of deploy:artifact tag and the legacy deploy method are deprecated
BUILD FAILEDFile.. C:\Documents and Settings\c_aveita\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jellyElement... maven:user-checkLine.. 258Column 45+--
| ERROR!|| You must specify a maven username in order to deploy the site!| You can either set this property in your ~/build.properties| or specify one on the command line:|| maven -Dmaven.username=${user.name}
[goal]+--Total time: 1 secondsFinished at: Sun Apr 30 13:23:07 PDT 2006
BELOW is OUTPUT AFTER specifying maven.username
C:\axis2-std-1.0-RC3-src> maven -Dmaven.username=xyz release
build:start:
release:validate-pom-for-release:
pom:deploy: [echo] maven.repo.list is not set - using legacy deploy mode [echo] DEPRECATED: use of deploy:artifact tag and the legacy deploy method are deprecated [echo] Copying project.xml
to the /axis2/poms on
BUILD FAILEDFile.. C:\Documents and Settings\c_aveita\.maven\cache\maven-artifact-plugin-1.4.1\plugin.jellyElement... ant:execLine.. 313Column 72Execute failed: java.io.IOException
: CreateProcess: ssh -l xyz"mkdir -p /axis2/poms" error=2Total time: 1 secondsFinished at: Sun Apr 30 13:23:35 PDT 2006
On 4/30/06, robert lazarski <[EMAIL PROTECTED]
> wrote:
'maven release' will create a war. HTH,Roberthttp://www.braziloutsource.com/
On 4/30/06, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
Hi Folks,Need some guidance w.r.t. axis2-std-1.0-RC3-src.zip. Am trying to create the
axis2.war from this distribution but it does not look as if there are anytargets to perform this?The comments in the maven.xml state that the main goals are "default" , "clean"and "clean-repo".
In the .95 release, there was an explicit "war" target in the maven.xml.Thanks,Al
Re: Is AXIS compliant with WSDL 2.0
Axis does not support WSDL 2.0 (which isn't final yet).On 5/1/06, Jim Collins <[EMAIL PROTECTED] > wrote:Hi all,Does anyone know if AXIS is compliant with WSDL 2.0. I tried using the WSDL to Java Ant task on a WSDL 2.0 file and got exceptions. It did not recognisethe tag.RegardsJim
Re: how to specify encodingStyle ?
"literal" means there is no encoding style. It is inappropriate to specify one.AnneOn 5/1/06, Raymond Domingo < [EMAIL PROTECTED]> wrote:Hello,Is there really no way to enable encodingStyle when using rpc literal ? In the request I recieve from some (soap) client there is an encodingStyle,but the response from my axis server has no encodintStyle. I suspect this isthe cause why my clients to throw an exception. client request:http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"xmlns:xsd="http://www.w3.org/2001/XMLSchema"> SOAP-ENV:encodingStyle="http://xml.apache.org/xml-soap/literalxml"> server response:http://schemas.xmlsoap.org/soap/envelope/"xmlns:xsd=" http://www.w3.org/2001/XMLSchema"xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">Any hints please ?thnxraymond domingo
Re: [Axis2]Error Using WSDL2Java
Perhaps you can check this comand Try this, WSDL2Java -uri file.wsdl -ss -sd -p com.maryam.grid -d xmlbeans -g if you are using namespaces in your wsdl, can use without specifiying -p option. Further you can send your wsdl for reference. Kensky On 5/1/06, Maryam Moazeni <[EMAIL PROTECTED]> wrote: Hi all, I'm using WSDL2Java but I got the following error when I run this command: WSDL2Java -uri file.wsdl -ss -sd -p com.maryam.grid Can anyone please help me figure out the problem. Shall I add anything to my CLASSPATH? Error: Exception in thread "main" java.lang.NullPointerException at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.createSchemaForPorttype (WSDLPump.java:732) at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.generateWrapperSchema (W SDLPump.java:662) at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.populateDefinition(WSDL Pump.java:187) at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.pump(WSDLPump.java:135) at org.apache.axis2.wsdl.builder.wsdl4j.WSDL1ToWOMBuilder.build(WSDL1ToW OMBuilder.java:124) at org.apache.axis2.wsdl.builder.wsdl4j.WSDL1ToWOMBuilder.build(WSDL1ToW OMBuilder.java:93) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.getWOM(CodeGenerat ionEngine.java:162) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerat ionEngine.java:70) at org.apache.axis2.wsdl.WSDL2Code.main (WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Thanks in advance --Maryam
[Axis2]Error Using WSDL2Java
Hi all, I'm using WSDL2Java but I got the following error when I run this command: WSDL2Java -uri file.wsdl -ss -sd -p com.maryam.grid Can anyone please help me figure out the problem. Shall I add anything to my CLASSPATH? Error: Exception in thread "main" java.lang.NullPointerException at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.createSchemaForPorttype(WSDLPump.java:732) at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.generateWrapperSchema (WSDLPump.java:662) at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.populateDefinition(WSDLPump.java:187) at org.apache.axis2.wsdl.builder.wsdl4j.WSDLPump.pump(WSDLPump.java:135) at org.apache.axis2.wsdl.builder.wsdl4j.WSDL1ToWOMBuilder.build(WSDL1ToWOMBuilder.java:124) at org.apache.axis2.wsdl.builder.wsdl4j.WSDL1ToWOMBuilder.build(WSDL1ToWOMBuilder.java:93) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.getWOM(CodeGenerationEngine.java:162) at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.(CodeGenerationEngine.java:70) at org.apache.axis2.wsdl.WSDL2Code.main (WSDL2Code.java:32) at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:21) Thanks in advance --Maryam
Axis Client - Connection Timeout
Hello,
I'm trying to get a axis client to work with my web service (located on
a remote machine) over HTTPS. The call of the web service succeeds with
the browser. I accept the server certificate (self-signed), then I am
able to access and call the methods.
But with the java client I got the following Exception:
java.net.ConnectException: Connection timed
out: connect
(the whole stacktrace is included lower)
>From the view of the amount of time passed, no connection timeout
should occur. I though it maybe be an SSL cert thing, so I used the
"SunFakeTrustSocketFactory" from the Axis Wiki, but the result was the
same as before.
Maybe I am doing something in the basics?
The stub code looks like this:
MeasuringDeviceMonitorService loc = new
MeasuringDeviceMonitorServiceLocator();
MeasuringDeviceMonitorIF service = loc.getmdmonitor();
Header header = service.getDevice("11/100");
Currently I have no way of disabling SSL from the web service, so any
help is much appreciated.
kind regards,
Artur Kraft
Exception Stacktrace:
trigger seeding of SecureRandom
done seeding SecureRandom
AxisFault
faultCode:
{http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out: connect
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException:
Connection timed out: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:507)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:546)
at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.(SSLSocketImpl.java:349)
at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:69)
at
org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:92)
at
org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
at
org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
at
org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
de.qsgrimm.wsclient.mdm.gen.MdmonitorSoapBindingStub.getMeasuringDevice(MdmonitorSoapBindingStub.java:752)
at
de.qsgrimm.wsclient.mdm.MainFrame$1.actionPerformed(MainFrame.java:164)
at
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849)
at
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2169)
at
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:420)
at
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:258)
at
javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:234)
at java.awt.Component.processMouseEvent(Component.java:5488)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
at java.awt.Component.processEvent(Component.java:5253)
at java.awt.Container.processEvent(Container.java:1966)
at java.awt.Component.dispatchEventImpl(Component.java:3955)
at java.awt.Container.dispatchEventImpl(Container.java:2024)
at java.awt.Component.dispatchEvent(Component.java:3803)
at
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4212)
at
java.awt.LightweightDispatcher.processMouseEvent(Container.java:3892)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
at java.awt.Container.dispatchEventImpl(Container.java:2010)
at java.awt.Window.dispatchEventImpl(Window.java:1774)
at java.awt.Component.dispatchEvent(Component.java:3803)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
how to specify encodingStyle ?
Hello, Is there really no way to enable encodingStyle when using rpc literal ? In the request I recieve from some (soap) client there is an encodingStyle, but the response from my axis server has no encodintStyle. I suspect this is the cause why my clients to throw an exception. client request: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://xml.apache.org/xml-soap/literalxml";> server response: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> Any hints please ? thnx raymond domingo
how to specify encodingStyle ?
Hello, Is there really no way to enable encodingStyle when using rpc literal ? In the request I recieve from some (soap) client there is an encodingStyle, but the response from my axis server has no encodintStyle. I suspect this is the cause why my clients to throw an exception. client request: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://xml.apache.org/xml-soap/literalxml";> server response: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> Any hints please ? thnx raymond domingo
[Axis2][1.0RC5] Asynchrony at the server side (EchoNonBlockingDualClient for long running MyService)
Hi all, As you know, EchoNonBlockingDualClient calls MyService and waits the response by launching SimpleHTTPServer on port 6060. Could someone check the correctness of the following flow, please? C: client S: server [C->S] open connection to the server's endpoint [C->S] send request SOAP with the ReplyTo declaring port 6060 [C<-S] send HTTP 200 OK [C->S] close connection [C] open a thread and listen to port 6060. ... (time passes) [C<-S] open connection to the client's port 6060 [C<-S] send the result SOAP [C->S] send HTTP 200 OK [C->S] close connection According to the sample, MyService completes quickly and the result is returned immediately. Thus, there is no asynchrony at the server side. How can I do the followings: - Open a new thread that will do the actual work, when the echo operation of MyService is called. - Complete the rest of the echo operation WITHOUT sending any response to the client which would cause SimpleHTTPServer to be closed. - After the actual work has done in the thread, send the result to the client's SimpleHTTPServer. Any help would be great! Ali Sadik Kumlali __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [Axis2] Obtaining WS-Addressing ReferenceParameters
You have to engage addressing in client side as well. There should be
AddressingOutHandler in the client side to serialize the reference
parameters you have put.
I updated the documentation on this, and waiting for the Chatra to
update the site. In the mean while you can check it here :
http://svn.apache.org/viewcvs.cgi/webservices/axis2/trunk/java/xdocs/latest/userguide3.html?view=markup.
Check in the EchoNonBlockingDualClient section.
-- Chinthaka
Tung Tran wrote:
> Hello,
>
> I'm trying to include some service-unique information as a
> referenceParameter of the To's EndpointReference. However I can't
> extract that piece of info with a handler deployed on the server side.
>
> Basically, on the client side, I do something like this:
>
> referenceParameters.put("param", "xyz");
> targetEPR.setReferenceParameters(referenceParameters);
> options.setTo(targetEPR);
>
> sender = new ServiceClient();
> sender.setOptions(options);
> sender.sendReceiveNonBlocking(payload, callback);
>
> On the server side, I deploy a handler and and try to get the
> SOAPHeader (from inside the handler's invoke method) with:
>
> msgContext.getEnvelope().getHeader()
>
> This header, however, is empty. I've expected that the
> referenceParameter above should be here.
>
> The addressing module is engaged on server. I'm not sure if I have to
> do anything on the client side.
>
> Any pointers to the right direction would be greatly appreciated.
> Thanks all in advance.
>
> Tung Tran
>
signature.asc
Description: OpenPGP digital signature
No Deserializer found to deserialize a ':parameters' using encoding style 'null'
Hello everyone, We are STRUGGELING to connect our soap client to our axis server for some time now, PLEASE HELP ! We suspect there is a problem with the encodingStyle. We created a test client (using axis) and it works ok. After comparing the soap message (obtained using sniffer) from our Testclient and the soap client we discovered the soap client is using an encodingStyle, and our working test client is not. There is also some difference in the namespace, but we assume this difference isnt the cause. Because it should do exactly the same. See snapshot of xml below: The Exception from soap client: 2006-05-01 09:53:57,503 - ERROR - (nl.foo .) - Invoking 'adHocVragen' failed! [SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to deserialize a ':parameters' using encoding style 'null'.; targetException=java.lang.IllegalArgumentException: No Deserializer found to deserialize a ':parameters' using encoding style 'null'.] at org.apache.soap.rpc.Call.invoke(Call.java:294) Our testclient xml: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> Our soap client xml http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:xsd="http://www.w3.org/2001/XMLSchema";> http://xml.apache.org/xml-soap/literalxml";> We cant change our client code, because it is already used by many customers. Currently we are building a new webservice using axis. We are using axis 1.3 and soap 2.3. Can anyone please explain to me why my soap client cant connect to the axis server ? Best regards, Raymond domingo
Re: [axis2] Strange xmlbeans problem
Can u please log a bug report? i almost missed this one.
thanks,
dims
On 4/30/06, robert lazarski <[EMAIL PROTECTED]> wrote:
Hi all,
I'm using RC4 for this example. I'm written a very simple example to
explain my problem. Can somebody please give a quick look - it must be
something simple but I'm having a hard time tracking it down.
The wsdl is attached and validates fine.
The response envelope is:
http://schemas.xmlsoap.org/soap/envelope/";>http://simpleNS/types";>my random
stringhttp://www.w3.org/2001/XMLSchema-instance";
xsi:nil="true"
/>
I'm setting 'web_user_name' in the service, but it's not showing up.
On the client side, simpleLoginResponseDocument.toString()
gives me:
http://simpleNS/types";>
my random string
http://www.w3.org/2001/XMLSchema-instance"/>
I'm getting the 'soap_user_session' in the soap message, but I'm getting
null when trying to call
simpleLoginResponse.getSoapSessionId() . The reason is here
in
simplens/types/impl/SimpleLoginResponseDocumentImpl.java -
I've put in a few println() :
public static class SimpleLoginResponseImpl extends
org.apache.xmlbeans.impl.values.XmlComplexContentImpl
implements
simplens.types.SimpleLoginResponseDocument.SimpleLoginResponse
{
public SimpleLoginResponseImpl(org.apache.xmlbeans.SchemaType
sType)
{
super(sType);
}
private static final javax.xml.namespace.QName SOAPSESSIONID$0 =
new javax.xml.namespace.QName("", "soap_session_id");
private static final javax.xml.namespace.QName WEBUSERNAME$2 =
new javax.xml.namespace.QName("", "web_user_name");
/**
* Gets the "soap_session_id" element
*/
public java.lang.String getSoapSessionId()
{
synchronized (monitor())
{
check_orphaned();
org.apache.xmlbeans.SimpleValue target = null;
target =
(org.apache.xmlbeans.SimpleValue)get_store().find_element_user(SOAPSESSIONID$0,
0);
if (target == null)
{
System.out.println("target is null");
return null;
}
System.out.println("target is ok? " + target);
return target.getStringValue();
}
}
The target is null, but the value is showing in the soap message.
Any ideas?
Robert
--
Davanum Srinivas : http://wso2.com/blogs/
Re: [Axis2] SimpleHTTPServer port conflict for multiple EchoNonBlockingDualClient threads
Hi Deepal,
I'm currently running 1.0RC5 and still have the same problem.
May be, as you said, I need somehow to use ListenerManager. Could you
please tell me what to do?
Thanks,
Ali Sadik Kumlali
--- Deepal Jayasinghe <[EMAIL PROTECTED]> wrote:
> Hi Sadik;
>
> In the current code base we done a major improvements in our
> transport
> freamwork with the introduction of ListenerManager. So in the next
> release onword you wont have such a problem.
>
> Ali Sadik Kumlali wrote:
>
> > Dear all,
> >
> > I simply changed EchoNonBlockingDualClient sample to make it run as
> > threads and created two threads. First one successfully starts
> > SimpleHTTPServer on port 6060 and the second one gets an
> > "java.net.BindException: Address already in use: JVM_Bind" while
> > trying to start the server.
> >
> > Doesn't I have an option to listen all the responses for its
> dedicated
> > port? For example 6060 for first request, 6061 for the second, and
> so
> > on. Or, should i assume Axis2 to use the same port for the
> responses
> > of all the long running transactions?
> >
> > Thanks a lot for any help.
> >
> > Ali Sadik Kumlali
> >
> >
>
--
> > Error Message I Get
> >
>
--
> > testEchoNonBlockingDualClient:
> > [java] [CLIENT1] Outgoing message
> > [java] > xmlns:example1="http://example1.org/example1";> > e1:Text>Axis2 Echo String
> > [java] - Deploying module : addressing
> > [java] [CLIENT2] Outgoing message
> > [java] > xmlns:example1="http://example1.org/example1";> > e1:Text>Axis2 Echo String
> > [java] - Deploying module : addressing
> > [java] - java.net.BindException: Address already in use:
> JVM_Bind
> > [java] org.apache.axis2.AxisFault: Address already in use:
> > JVM_Bind; nested
> > exception is:
> > [java] java.net.BindException: Address already in use:
> JVM_Bind
> > [java] at
> > org.apache.axis2.transport.http.SimpleHTTPServer.start(Simple
> > HTTPServer.java:220)
> > [java] at
> > org.apache.axis2.client.ListenerManager.makeSureStarted(Liste
> > nerManager.java:73)
> >
> >
> >
>
--
> > Modified EchoNonBlockingDualClient.java
> >
>
--
> > public class EchoNonBlockingDualClient implements Runnable {
> > private static EndpointReference targetEPR = new
> EndpointReference(
> > "http://127.0.0.1:8080/axis2/services/MyService";);
> >
> > private String name;
> >
> > public EchoNonBlockingDualClient(String name) {
> > this.name = name;
> > }
> >
> > publ ic OMElement getPayload() throws XMLStreamException,
> > FactoryConfigurationError {
> > OMElement payload = ClientUtil.getEchoOMElement();
> >
> > // Log the outgoing payload
> > StringWriter writer = new StringWriter();
> >
> >
>
payload.serialize(XMLOutputFactory.newInstance().createXMLStreamWriter(
> > writer));
> > writer.flush();
> > System.out.println("[" + name + "] Outgoing message\n"
> > + writer.toString());
> > return payload;
> > }
> >
> > public Options getOptions() {
> > & nbsp; Options options = new Options();
> > options.setTo(targetEPR);
> > options.setTransportInProtocol(Constants.TRANSPORT_HTTP);
> > options.setUseSeparateListener(true);
> > return options;
> > }
> >
> > public void makeRequest() {
> > try {
> > OMElement payload = getPayload();
> > Options options = getOptions();
> >
> > // Callback to handle the response
> > Callback callback = new Callback() {
> > public void onComplete(AsyncResult result) {
> > try {
> > StringWriter writer = new StringWriter();
> > result.getResponseEnvelope().serialize(
> > XMLOutputFactory.newInstance()
> >
> .createXMLStreamWriter(writer));
> > writer.flush();
> > System.out.println("[" + name + "] Incoming
> > message\n"
> > + writer.toString());
> > try {
> > Thread.sleep(1000);
> > } catch (InterruptedException e) {
> > // TODO Auto-generated catch block
> > e.printStackTrace();
> > }
> >
> > } catch (XMLStreamException e) {
> > onError(e);
> >
Is AXIS compliant with WSDL 2.0
Hi all, Does anyone know if AXIS is compliant with WSDL 2.0. I tried using the WSDL to Java Ant task on a WSDL 2.0 file and got exceptions. It did not recognise the tag. Regards Jim
