I've been working with axis2 now for a few weeks and overall, I've found the experience enjoyable, but quite frustrating at times.

One of the frustrating times came today with trying to implement the logging of the raw SOAP XML messages that are received and sent by the server.

There are errors on the following web page: http://ws.apache.org/axis2/1_2/modules.html

If you look under Step3 : module.xml you'll see the example given for the logging module's config file.

There are 5 errors (at least for my setup) for that example config.

1.) the class="..." entry has a space at the end of the class name. This causes a ClassNotFoundException but only if logging is turned on for org.apache.axis2. 2.) The element inflow needs to be InFlow. (The elements are case sensitive.) 3.) The element outflow needs to be OutFlow. (The elements are case sensitive.) 4.) The element Outfaultflow needs to be OutFaultFlow. (The elements are case sensitive.) 5.) The element InFaultFlow needs to be InFaultFlow. (The elements are case sensitive.)


Documentation Clarification... I don't think this is mentioned anywhere in the documentation, but from what I've read it SEEMS as though the *.aar and *.mar files are required for deploying services and modules.

However, the *.aar and *.mar files are not required. (As I'm sure many people know but, isn't mentioned in the online documentation very well.

A directory structure can be used in place of using either the *.aar or *.mar files. Here is an example.

WEB-INF
 services
   <service name>
     META-INF
       service.xml
     <package structure - optional read below>
<the actual class files DO NOT need to be present here if they are somewhere>
       <else in your classpath.>
 moduels
   <module name>
     META-INF
       module.xml
     <package structure - optional read below>
<the actual class files DO NOT need to be present here if they are somewhere>
       <else in your classpath.>


Finally a question about logging. Why is the logging of the raw SOAP XML so difficult? I would hope that there would be a simple entry into a log4j.properties file and the request and response would be outputted. Or having a service reference a logging module. Why force people to go through the rigmarole of adding a new module and runner? Isn't there lots of people that want to log the raw SOAP XML?


I know this email must seem critical, but i do like Axis2. I just wish it was easier to work with and was configured to be added to a current system better.

Thank you for your time.

_________________________________________________________________
Catch suspicious messages before you open them—with Windows Live Hotmail. http://imagine-windowslive.com/hotmail/?locale=en-us&ocid=TXT_TAGHM_migration_HM_mini_protection_0507


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to