> Is it necessary to have a module tag in the axis2.xml configuration file
> when the file is only being referenced by a client application? (Server is
> on another machine altogether)
AFAIK it's not necessary unless you need to globally engage that
module, aka engage that module to all the outgoing messages... Usually
in the client side an Axis2 repository, with the modules directory
containing the necessary axis2 modules (eg: rampart, sandesha,
addressing), is used. Then the client creates the AxisConfiguration
pointing to that repository and to an axis2.xml file. With these
setup, you can call serviceclient.engageModule("module name") from
your client program to engage the module..
>
> I am running a test as a stand alone java app, attempting to use rampart to
> encrypt the message body. When running the code I get an error stating that
> the rampart module could not be loaded. I am running this out of eclipse, I
> have the AXIS2_HOME environment variable set to the correct path in the
> operating system, eclipse: run->environment and as a –D argument to the jvm
> just in case. Also the –Daxis2.xml argument set to the correct location and
> I know this is working.
Do you have the rampart module in the repository/modules directory of
the the AXIS2_HOME..
thanks,
Thilina
>
>
>
> Also the axis2.xml files that come with rampart issue a number of warnings
> stating that the Dispatchers are deprecated. (v1.3 on both) What is the
> latest methods of defining the dispatchers?
>
>
>
> Thanks!
>
> -P
--
Thilina Gunarathne - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
