Thanks Martin,
The only application containing that line was example2. I think I
somehow got that application's .aar file installed under axis2 in
the tomcat webapps folder. The service was not showing on the
axis2 admin console as active, but something was there. Anyway, I
rebuilt a clean axis2.war and redeployed it. Now the problem is
gone. User error, I guess. Thanks.
Duncan
Martin Gainty wrote:
Good Morning Duncan
These are great suggestions
what would happen if you replaced this line from services.xml
<module ref="logging"/>
with a blank line?
Again these are great suggestions as they step you thru the process in a
chronological fashion
Thanks,
Martin--
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message ----- From: "Duncan Thomson" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, April 16, 2007 9:17 AM
Subject: Logging module error with userguide examples
I'm slogging my way through the axis2 userguide introduction
section, and I have some questions. Hopefully there is someone on the
list familiar with how the userguide examples were put together who
can tackle these...
I've deployed axis2 (1.1.1) into apache tomcat (6). I created and
deployed the server example as described in the "Apache Axis2 User's
Guide -Building Services" section. I created and deployed the client
as described in the "Creating Clients" section. The client and server
are both based on the wsdl file in code listing 5 in the userguide.
The client and server seem to work, however when I run the client
under axis2 I get a bunch of error messages related to undeployed
logging modules (messages duplicated below).
I did some searching of the archives, and found some information about
configuration things that have to be done to enable logging modules.
But...
1) At this point in the user guide logging modules have not even
been mentioned, and I don't think the example in question uses
them. So... what is trying to load them? Is this perhaps the way
the way axis2.war comes set up by default? Did I inadvertently
turn logging on (or miss a step in which I was supposed to turn it
off)?
2) How do I either turn logging off or properly deploy it?
3) In general, what's with all the "Deploying module" stuff I'm
getting when I run the client? I'm just trying to figure this
stuff out, but I exepected the client to simply send SOAP messages
to the service, which has already been deployed, hasn't it? So what's
with all these messages about "doDeploy" when I run the client? (Note
- at this point I still don't really understand
exactly what this client is doing - I'm just working through the
examples in the userguide.)
Any help would be appreciated!
Duncan
p.s. A comment to the userguide authors - suggest we move the
example of building a service BEFORE the example of building the
client, because obviously the client won't work until the service
is built and deployed.
p.s. Another comment for userguide authors - suggest the example
commands be given for both Windows and unix environments, rather than
just Windows.
Here are the error messages I get when I try to run the client...
seafox:~/myservice> axis2.sh org.apache.axis2.axis2userguide.Client
Using AXIS2_HOME: /home/duncant/axis2
Using JAVA_HOME: /usr/local/java
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : addressing-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying module : soapmonitor-1.1.1
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service version.aar
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service sample-MyService.aar
org.apache.axis2.deployment.DeploymentException: Processing
Operations Modules logging module is invalid or has not been
deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:139)
at
<snip>
Caused by: org.apache.axis2.deployment.DeploymentException:
Processing Operations Modules logging module is invalid or has not
been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
org.apache.axis2.deployment.DeploymentException: logging
module is invalid or has not been deployed; nested exception is:
<etc...>
Apr 15, 2007 11:26:28 AM
org.apache.axis2.deployment.DeploymentEngine doDeploy
INFO: Deploying Web service sample-WsaMappingService.aar
done
echo! ... echo!
[EMAIL PROTECTED]
true
23872983
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Duncan Thomson
Tel: 703-983-7337
Mobile: 703-463-0536
Text Msg: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
