Thanks. I tried something in the lines of what you suggest. I think it would 'understandable' if the code notified the faultlisteners in case of deserialisation exceptions too :-), so I thought I would submit as an extension suggestion via bugzilla, but it seems you can't report to Apache SOAP (not in list)?
The thing is I don't really have the opportunity to deploy a modified version of Apache SOAP so I look forward to seeing this in the next release, which is really soon off course... Just kidding, no pressure - great product anyway. /Chr ----- Original Message ----- From: "Scott Nichol" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, March 15, 2004 3:00 PM Subject: Re: Deserializer and faultListener > I believe you are correct. I find it understandable that the code works this way, > although it does not really have to. > > In order to determine the correct deployment descriptor, Apache SOAP must parse the > namespace from the XML element specifying the method. It does this within RPCRouter#extractCallFromEnvelope. Interestingly, within that method, after getting the namespace, Apache SOAP gets the deployment descriptor to verify that the namespace is supported. When the method returns, RPCRouterServlet#doPost gets its own copy of the deployment descriptor. So, if the RPCRouterServlet could have RPCRouter set its deployment descriptor reference, it would give you the desired behavior. > > Scott Nichol > > Do not send e-mail directly to this e-mail address, > because it is filtered to accept only mail from > specific mail lists. > ----- Original Message ----- > From: "Christian Landbo (Presys A/S)" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, March 15, 2004 5:13 AM > Subject: Deserializer and faultListener > > > It seems to me that any exceptions thrown from a deserializer won't get sent to a > custom faultListener since the > 'DeploymentDescriptor dd' is null at that point in the RPCRouterServlet. > > Is this on purpose or am I getting it all wrong? > > /Chr > >
