On Fri, Feb 2, 2018 at 6:23 AM, robertlazarski . <robertlazar...@gmail.com> wrote:
> > > On Thu, Feb 1, 2018 at 9:16 PM, fateh.singh <fateh.si...@newgen.co.in> > wrote: > >> Hi Robertlazarski, >> >> >> >> Thank you for response and support provided. >> >> The configuration you shared is for wildfly and JBoss 7 onwards. JBoss >> 6.X does not support this feature. Please let me know is there any other >> way we can configure in following server. >> >> 1) JBoss eap 6.X >> >> 2) Weblogic 12c >> >> 3) Websphere 7, 8.5 >> >> >> >> Regards, >> >> Fateh Singh, >> >> > Best I can tell JBoss EAP 6 supports display-source-fragment=false. That > may help. Your version of JBoss is before stack-trace-on-error="none" was > added, to JBoss 7 over 6 years ago. > > If you still have problems, you'll have to patch a code fix on your side > and optionally submit a patch via Jira to axis2. > > Weblogic and WebSphere are commercial products with official support, I > suggest you ask them as I have no recent experience with their products. > > - R > > > > > > > > > Since this is an issue brought up by an external tool ... Try setting "content-type: text/xml" to the http header. wget --post-file=soaprequest.xml --header="Content-Type: text/xml" --header="SOAPAction: \"soapaction\"" * myserver.com/axis2/services/ibps07jan_11_ <http://myserver.com/axis2/services/ibps07jan_11_>1_service.ibps07jan_11_1_serviceHttpEndpoint* -O response.xml You may need to also define a payload i.e an xml "envelope" for that to work. Looks like the root cause of the issue, is that you cannot just do "wget myendpoint" or use any type of automated tool to go directly to an axis2 endpoint, without the right http headers and payload defined. - R
