Unhandled exception at 0x7c901230 : User breakpoint

2006-02-26 Thread Yaron Cohen 








Hi, 

I have the same problem as described at: http://www.nabble.com/Using-generated-CPP-files-in-visual-studio-2003-t841990.html#a2181671.




Can you please explain to me: 

How should I configure the conf file? It looks like what ever I do in order to configure
it, I get the same error.

 

Please note that I did what ever you explain under “Client
Installation and Configuration” and it does not work.

Thanks 
Yaron 

 

 

Yaron Cohen

VoIP
Integrations Software Engineer EIS, R&D

NICE Systems. Israel

 

(T) +972 (9) 7752338

(M) +972 (54) 5442488
(F) +972 (9) 7753600 

[EMAIL PROTECTED]


www.nice.com

 

---

NICE - Insight from Interactions

 

Serialize/DeSerialize SoapFault

2006-02-26 Thread [EMAIL PROTECTED] 
Hi,

The problem I am having is related to the fix for JIRA Issue AXISCPP-706. 

In the currently nightly build, the code for serialize SoapFault (in
SoapFault.cpp) seems to add  tags around fault details for
complex fault detail (eg user defined exception type) but not for simple
fault detail like string. 

My understanding of AXISCPP-706 is that  tag should be added to
simple fault detail instead of complex fault detail as the simple fault
details don't have sub-elements (which apparently will crash Java clients),
where as the complex fault details already have. This extra wrapping cause
user-define exceptions to not be correctly deserialized on client side.

If the  tag is suppose to be only for simple fault detail like
string then there is further requirement that the tag be skipped when
deserializing on the client side.

I just want to make sure this is correct.


Kind Regards,
Yuan

[Axis2] Problem in om element?

2006-02-26 Thread Samisa Abeysinghe 

We have the floowing on line 439 of modules/xml/om/om_element.c:
return axis2_om_element_find_namespace (
   
(axis2_om_element_t*)AXIS2_OM_NODE_GET_DATA_ELEMENT(node, env),

   env, parent, uri, prefix);

I think we are doing something wrong here, mixing up the element with 
the parent node.


Should we not have the following instead?:
return axis2_om_element_find_namespace (
   
(axis2_om_element_t*)AXIS2_OM_NODE_GET_DATA_ELEMENT(parent, env),

   env, parent, uri, prefix);

Or have I missed something here?

NOTE: I get a seg fault in axis2_om_element_find_namespace for some of 
the responses from WCF test endpoints.


Thanks,
Samisa...