Copied the addressing-0.95.mar into Axis2-home lib (where all libs
reside) solves the moudle not found problem
BUT
executing a client with NonBlockingDual functionality prints that at the
web service side:
- I/O exception (java.net.ConnectException)
caught when processing request: Connection refused: connect
- Retrying request
- Connection refused: connect; nested exception is:
java.net.ConnectException: Connection refused: connect;
nested exception is:
org.apache.axis2.AxisFault: Connection refused: connect;
nested exception is:
java.net.ConnectException: Connection refused: connect
At the same time the output of the client shows due to
while (!callback.isComplete()) {
System.out.print(".");
Thread.sleep(100);
}
this:
[SimpleHTTPServer] Stop called
............ infinite .........
Setting this on client-side
options.setUseSeparateListener(false);
the invoke success!
It seems the NonBlockingDual invocation doesn't work...
Finian O'Boyle wrote:
Thank you Michele - I thought that was an ingenious idea - I hadn't thought
of using Ant to execute the class. I did what you said and added
addressing-0.95.mar to the classpath, but sadly it still gives me the same
error, as detailed below.
Finian
[java] org.apache.axis2.AxisFault: Module not found
[java] at
org.apache.axis2.description.AxisService.engageModule(AxisService.java:311)
[java] at
org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:273)
[java] at userguide.clients.EchoBlockingDualClient.main(Unknown Source)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
Source)
[java] at java.lang.reflect.Method.invoke(Unknown Source)
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.run(ExecuteJava.java:202)
[java] at
org.apache.tools.ant.taskdefs.ExecuteJava.execute(ExecuteJava.java:134)
[java] at org.apache.tools.ant.taskdefs.Java.run(Java.java:710)
[java] at org.apache.tools.ant.taskdefs.Java.executeJava(Java.java:178)
[java] at org.apache.tools.ant.taskdefs.Java.execute(Java.java:84)
[java] at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[java] at org.apache.tools.ant.Task.perform(Task.java:364)
[java] at org.apache.tools.ant.Target.execute(Target.java:341)
[java] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[java] at
org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[java] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[java] at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.j
ava:40)
[java] at
org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets
(EclipseDefaultExecutor.java:32)
[java] at
org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[java] at
org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunn
er.java:423)
[java] at
org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRun
ner.java:137)
-----Original Message-----
From: Michele Mazzucco [mailto:[EMAIL PROTECTED]
Sent: 07 April 2006 12:51
To: [email protected]
Subject: Re: [Axis2] 0.95 WS-Addressing client-side: module not found
Finian,
actually Eclipse doesn't need it (at least not during compilation). It
is enough that you add the .mar file into your classpath in build.xml
and then you can run your client from ant.
Michele
Finian O'Boyle wrote:
Hi, I'm new to this list - I'm an Axis 1.3 user and am currently
converting
to Axis 2 0.95. I run using Eclipse 3.1.1/Ant 1.6.5/Tomcat 5.5 and I'm
also
developing .Net interoperable systems with .Net 1.1.
I, too, have been struggling with the "module not found" problem that
Roman
has encountered. Whenever ServiceClient tries to engage "addressing", I
get
"module not found". If, as Deepal says, "addressing-0.95.mar" has to be in
the Eclipse classpath, then it's going to be a problem, because Eclipse
doesn't seem to recognize that as a valid entry in the buildpath. You
can't
add it within Eclipse, because it only allows .jar and .zip files when you
try to "Add External Jar" to the buildpath. Even if you modify the
.classpath file outside Eclipse it doesn't recognize "addressing-0.95.mar"
as a valid entry.
Finian
-----Original Message-----
From: Roman Weidlich [mailto:[EMAIL PROTECTED]
Sent: 06 April 2006 19:59
To: [email protected]
Subject: Re: [Axis2] 0.95 WS-Addressing client-side: module not found
every try of this:
serviceClient.engageModule(new QName(Constants.MODULE_ADDRESSING));
results in this:
org.apache.axis2.AxisFault: Module not found
but in the administration for the webservice is displayed:
Service Status : Active Engaged modules for the service
* addressing-0.95
Roman Weidlich wrote:
trying "addressing-0.95.mar" in the classpath doesn't change anything...
Deepal Jayasinghe wrote:
ohhh , that is not going to be work !
you have to have the .mar extension otherwise system will not figure
that out as an AxisModule.
Roman Weidlich wrote:
I renamed addressing-0.95.mar to addressing-0.95.jar and add it to the
project libraires in Eclipse.
EchoNonBlockingDualClient arises this:
org.apache.axis2.AxisFault: Module not found
at
org.apache.axis2.description.AxisService.engageModule(AxisService.java:311)
at
org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:273)
at client.Client.invoke(Client.java:66)
at client.Client.<init>(Client.java:28)
at client.Client.main(Client.java:109)
Chinthaka wrote:
Michele Mazzucco wrote:
Hi Eran,
I'm sorry, but I cannot find the options.engageModule() call. Do you
mean options.setAction() (I'm just trying to guess since the APIs
don't
explain what that method actually do)?
I'm sorry its ServiceClient.engageModule("addressing").
