I create my ServiceClient like this:
ConfigurationContext configContext =
ConfigurationContextFactory.createConfigurationContextFromFileSystem("C:/Program
Files/Apache Software Foundation/Tomcat 5.5/webapps/axis2/WEB-INF", null);
//Non-Blocking Invocation
sender = new ServiceClient(configContext, null);
sender.engageModule(new QName(Constants.MODULE_ADDRESSING));
sender.engageModule(new QName("logging"));
Actually, the module WS-Addressing is well-engaged and works properly.
The client has access to the module "logging" in ./module/
Is it necessary to specify the location of the file axis2.xml or could it
work like that?
Actually I think, the client has access to my axis2.xml file but the
exception tells me that the phase isn't specify whereas it is.
I don't understand...
Fabien
----- Original Message -----
From: "Susanne Kaiser" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, July 06, 2006 11:03 AM
Subject: Re: org.apache.axis2.phaseresolver.PhaseException
How do you create your ServiceClient?
If you use the default constructor, then the
org/apache/axis2/deployment/axis2_default.xml configuration file from the
axis2-kernel jar is going to be used instead of your adjusted axis2.xml.
To use my axis2.xml file, I created a ConfigurationContext first and then
the ServiceClient with the context as parameter:
final URL axis2Url = ClassLoader.getSystemClassLoader().getResource(
"conf/axis2.xml" );
final ConfigurationContext context =
ConfigurationContextFactory.createConfigurationContextFromFileSystem(
null, axis2Url.getPath() );
final ServiceClient serviceClient = new ServiceClient( context, null );
serviceClient.engageModule( new QName( "logging" ) );
Make sure, that your axis2.xml is residing in your classpath.
--
Susanne Kaiser
On Thursday 06 July 2006 10:29, Fabien Couble wrote:
Actually, I have already added this entry as you can see on the file.
Or maybe I did it wrong!!?
But I added the phase logging in every phase order type without any
success...
Fabien
----- Original Message -----
From: "Deepal Jayasinghe" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, July 06, 2006 10:01 AM
Subject: Re: org.apache.axis2.phaseresolver.PhaseException
> You need to add following entry into axis2.xml
>
> <phaseOrder type="inflow">
> <phase name="Logging"/>
> </phaseOrder>
>
> Fabien Couble wrote:
>
>> Hi,
>> I'm trying to engage a module at the client side but I have the
>> following exception
>>
>> org.apache.axis2.phaseresolver.PhaseException: Invalid phases please
>> recheck axis2.xml logging for the handler InFlowLogHandler
>>
>> at
>> org.apache.axis2.phaseresolver.PhaseHolder.addHandler(PhaseHolder.java:66)
>>
>> at
>>
org.apache.axis2.phaseresolver.PhaseResolver.engageModuleToOperation(PhaseResolver.java:191)
>>
>> at
>>
org.apache.axis2.description.AxisOperation.engageModule(AxisOperation.java:128)
>>
>> at
>> org.apache.axis2.description.AxisService.engageModule(AxisService.java:426)
>>
>> at
>> org.apache.axis2.client.ServiceClient.engageModule(ServiceClient.java:279)
>>
>> at
>>
userguide.clients.EchoNonBlockingDualClient.main(EchoNonBlockingDualClient.java:68)
>>
>> As you can see, Axis finds the module without any problems but I think
>> there is a problem with my configuration files and more precisely
>> axis2.xml. (as it is written)
>>
>> I don't understand because I include the phase name logging into the
>> axis2.xml like in the module.xml.
>>
>> You can find enclosed my configuation files if you can have a look it
>> could ce very nice...
>>
>> Thanks for your help...
>>
>> Fabien
>>
>> This message contains information that may be privileged or
>> confidential and is the property of the Capgemini Group. It is
>> intended only for the person to whom it is addressed. If you are not
>> the intended recipient, you are not authorized to read, print, retain,
>> copy, disseminate, distribute, or use this message or any part
>> thereof. If you receive this message in error, please notify the
>> sender immediately and delete all copies of this message.
>>
>>------------------------------------------------------------------------
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>
> --
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
This message contains information that may be privileged or confidential
and is the property of the Capgemini Group. It is intended only for the
person to whom it is addressed. If you are not the intended recipient,
you are not authorized to read, print, retain, copy, disseminate,
distribute, or use this message or any part thereof. If you receive this
message in error, please notify the sender immediately and delete all
copies of this message.
---------------------------------------------------------------------
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]
This message contains information that may be privileged or confidential and is
the property of the Capgemini Group. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not authorized
to read, print, retain, copy, disseminate, distribute, or use this message or
any part thereof. If you receive this message in error, please notify the
sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
