[Axis2] Deploying module problem? addressing

["Villalba, Gregorio, VF-ES (gvillal2) EXT" <gv...@corp.vodafone.es>]

Hello,
 
I still have the same problem. I am getting crazy with it because the
same code works fine in Windows. And what is worst, for a Linux machine,
the same code works fine in a directory and does not work in other
directory which is exactly in the same path! I think it is related with
the way that Axis2 deploys the addressing module (see the log). 
 
I welcome any idea, thanks.

	-----Mensaje original-----
	De: Villalba, Gregorio, VF-ES (gvillal2) EXT 
	Enviado el: viernes, 20 de enero de 2006 9:51
	Para: axis-dev@ws.apache.org
	Asunto: [Axis2] Deploying module problem? addressing
	
	
	Hi everybody,
	 
	I am developing an application to run in a Linux OS, this
service uses a WS with Addressing. I developed the WS "client" with
Axis2 v0.92, I have done several versions of my service and a very
strange thing happens. In some versions when I try to create the
Subscribedocument to make the subscription I get this:
	 
	2006-01-20 08:59:43.278  INFO
[org.apache.axis2.deployment.DeploymentEngine]  adding new module
	2006-01-20 08:59:43.279  INFO
[org.apache.axis2.deployment.DeploymentEngine]  Deploying module :
addressing
	null
	java.lang.ClassCastException
	        at
com.vodafone.jaw.ws.evsubsc.databinding.org.xmlsoap.schemas.SubscribeDoc
ument$Factory.newInstance(SubscribeDocument.java:166)
	        at
com.vodafone.jaw.ws.StubHelper.SubscribeRequestSinc(StubHelper.java:121)
	        at
com.opencloud.slee.services.sip.proxy.ProxySbb.onInviteRequest(ProxySbb.
java:161)
	        at
com.opencloud.rhino.deployed.sbb.Open_Cloud.ProxySbb_1_5_1.SbbEJBBean.sb
bDeliverEvent(SbbEJBBean.java:328)
	        at
com.opencloud.deployed.Service_SIP_Proxy_Service_1_5_1__Open_Cloud.SBB_P
roxySbb_Open_Cloud_1_5_1EJB_Container.invoke_sbbDeliverEvent(SBB_ProxySb
b_Open_Cloud_1_5_1EJB_Container.java:187)
	        at
com.opencloud.deployed.Service_SIP_Proxy_Service_1_5_1__Open_Cloud.SBB_P
roxySbb_Open_Cloud_1_5_1EJB_Container.local_sbbDeliverEvent(SBB_ProxySbb
_Open_Cloud_1_5_1EJB_Container.java:1910)
	        at
com.opencloud.deployed.Service_SIP_Proxy_Service_1_5_1__Open_Cloud.SBB_P
roxySbb_Open_Cloud_1_5_1EJB_Local.sbbDeliverEvent(SBB_ProxySbb_Open_Clou
d_1_5_1EJB_Local.java:109)
	        at com.opencloud.ob.rhinosdk.yw.a(DashOB8895)
	        at com.opencloud.ob.rhinosdk.yw.a(DashOB8895)
	        at com.opencloud.ob.rhinosdk.yw.a(DashOB8895)
	        at com.opencloud.ob.rhinosdk.yq.c(DashOB8895)
	        at com.opencloud.ob.rhinosdk.yq.a(DashOB8895)
	        at com.opencloud.ob.rhinosdk.wg.a(DashOB8895)
	        at com.opencloud.ob.rhinosdk.wf.a(DashOB8895)
	        at com.opencloud.ob.rhinosdk.hw.e(DashOB8895)
	        at com.opencloud.ob.rhinosdk.hw.run(DashOB8895)
	        at java.lang.Thread.run(Thread.java:534)
	 
	The WS "client" code is right, because It works in my Windows PC
and because It has eventually worked for some versions, so I suppose It
is a problem of the Addressing module deployment. 
	Anyone can help, please? 
	Where is it supposed to be placed the module "addressing.mar"?
	 
	Thanks in advance for your time.
	 

Confidencialidad 
Este correo electr�nico y, en su caso, cualquier fichero anexo al mismo, contiene informaci�n de car�cter confidencial exclusivamente dirigida a su destinatario o destinatarios y propiedad de Vodafone Espa�a. Queda prohibida su divulgaci�n, copia o distribuci�n a terceros sin la previa autorizaci�n escrita de Vodafone Espa�a, en virtud de la legislaci�n vigente. En el caso de haber recibido este correo electr�nico por error, se ruega notificar inmediatamente esta circunstancia mediante reenv�o a la direcci�n electr�nica del remitente y la destrucci�n del mismo.

Confidentiality 
The information in this e-mail and in any attachments is classified as Vodafone Espa�a Confidential and Proprietary Information and solely for the attention and use of the named addressee(s). You are hereby notified that any dissemination, distribution or copy of this communication is prohibited without the prior written consent of Vodafone Espa�a and is s strictly prohibited by law. If you have received this communication in error, please, notify the sender by reply e-mail.