You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by glopezm <gm...@gmail.com> on 2010/02/16 03:31:49 UTC
Axis2-1.5.1 and user exceptions
Hi,
I'm using axis2 v1.5.1 as it is stated in the subject of this message and
I've found that user exceptions are not being reported as they used to be
with axis1. If one declare an operation throwing an exception, whenever the
exception is thrown the detail part of the soap fault element used to be
populated by axis1 with all exception data. However it is not working (at
least in this way) anymore. The <soapenv:Detail /> tag is empty. There is a
bug that was filed almost two years ago
(https://issues.apache.org/jira/browse/AXIS2-3443) which explains the
situation very clearly but it has not even been assigned yet!
Now I'm wondering whether someone is aware of a workaround to overcome this
issue since it does not happen that the bug will be corrected anytime soon
:-(.
Thanks in advance for your help!
--
View this message in context: http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27602949.html
Sent from the Axis - User mailing list archive at Nabble.com.
Re: Axis2-1.5.1 and user exceptions
Posted by glopezm <gm...@gmail.com>.
Thanks for your reply!
Just as an update I wanted to state that I've resolved this issue by moving
on to the axis2 jaxws implementation which works pretty good so far and
exceptions work like it is expected. Using this approach you can develop
contract last web services without spending too much time.
Regarding the contract first approach, I think it is a good practice but
almost just for the books. This is for me (saying that with all my respect
for other opinions) almost impossible to do in the real world since you
always have a tight schedule to develop an application and web services are
just a small part of it (the interface). It is not possible/reasonable to
dedicate such a long time while you have more important things to resolve
like the the core business internal implementation. I'm not saying that one
do not have to pay attention to web services and compatibility issues that
may come with contract last, but it is not a fact that you'll have problems
if you do it and even though all issues can be resolved. This is just my
opinion :-).
Regardless of what I stated, I recognize that under certain conditions
contract first might be a better approach.
Thanks again for the help!!!
Mauro Molinari wrote:
>
> Il 17/02/2010 3.53, glopezm ha scritto:
>> Any thoughts/experiences with a similar issues with axis2?
>
> I use contract-first approach. My user exceptions extend Exception and
> have a field called faultMessage with getter getFaultMessage and setter
> setFaultMessage. The constructor prepares the faultMessage and sets it
> via setFaultMessage. The faultMessage is an object of a class generated
> by WSDL2Code from an XMLSchema type that describes my fault message, so
> that it implements ADBBean.
>
> In this way, when my code raises my user defined exception, Axis2
> recognizes the existence of the fault message and attaches it correctly
> to the fault returned to the client code.
>
> This is the result of my trial-and-errors researches of some years ago
> with Axis2 1.3 and it is working with Axis2 1.5 too. I think that you
> may find something else in this mailing list archive by me on this
> subject.
>
> --
> Mauro Molinari
> Software Designer & Developer
> E-mail: mauro.molinari@cardinis.com
>
>
--
View this message in context: http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p28276660.html
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@axis.apache.org
For additional commands, e-mail: java-user-help@axis.apache.org
Axis2-1.5.1 and CallbackHandler
Posted by TomazM <to...@arnes.si>.
What is the best practices to retrieve identifier in service operation method?
Is identifier from CallbackHandler stored in local thread?
Regards, Tomaz
Re: Axis2-1.5.1 and user exceptions
Posted by Mauro Molinari <ma...@cardinis.com>.
Il 19/02/2010 16.14, Martin Gainty ha scritto:
> when you state ..it definitely worked under axis1 ..are you stating you
> must specify RPC over doc-literal?
> Is the use of RPC a stated business requirement?
Hi Martin,
I think RPC doesn't matter at all here. Li Ma was saying that "Axis1
definitely worked" regarding the handling of user exceptions in
code-first approach.
--
Mauro Molinari
Software Designer & Developer
E-mail: mauro.molinari@cardinis.com
RE: Axis2-1.5.1 and user exceptions
Posted by Martin Gainty <mg...@hotmail.com>.
Hello Li
the biggest problem with a contract is you are bound to fixed record
doc-literal-encoded has been around for 7 years and has been deployed numerous times on numerous production sites
Here is a good whitepaper to read on the advantages of doc-literal over RPC
http://www.ibm.com/developerworks/webservices/library/ws-whichwsdl/
also DOC-LITERAL (with encoding) is clearly the best choice for complex structures over any RPC based implementation
ALSO rpc is using a remote procedure call to call the function with the parameters leaving a HUGE security hole
in your webservice with the open port you are using to the RPC method
AXIS2 is heavily favoring doc-literal over RPC for above stated reasons
when you state ..it definitely worked under axis1 ..are you stating you must specify RPC over doc-literal?
Is the use of RPC a stated business requirement?
Martin Gainty
______________________________________________
please do not modify or disrupt this transmission. Thank You
Date: Fri, 19 Feb 2010 09:15:03 -0500
Subject: Re: Axis2-1.5.1 and user exceptions
From: lima01@gmail.com
To: axis-user@ws.apache.org
I have been puzzled by this issue for long time. Seams like at this point, using contract-first approach is the only solution for now.
But it will still be very very helpful if something can be done so code-first approach can work too. Axis1 definitely worked. I can imagine lots of people are using code-first approach because of its simplicity.
Thanks!
Li
On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari <ma...@cardinis.com> wrote:
Il 17/02/2010 3.53, glopezm ha scritto:
Any thoughts/experiences with a similar issues with axis2?
I use contract-first approach. My user exceptions extend Exception and have a field called faultMessage with getter getFaultMessage and setter setFaultMessage. The constructor prepares the faultMessage and sets it via setFaultMessage. The faultMessage is an object of a class generated by WSDL2Code from an XMLSchema type that describes my fault message, so that it implements ADBBean.
In this way, when my code raises my user defined exception, Axis2 recognizes the existence of the fault message and attaches it correctly to the fault returned to the client code.
This is the result of my trial-and-errors researches of some years ago with Axis2 1.3 and it is working with Axis2 1.5 too. I think that you may find something else in this mailing list archive by me on this subject.
--
Mauro Molinari
Software Designer & Developer
E-mail: mauro.molinari@cardinis.com
--
Li Ma
lima01@gmail.com
_________________________________________________________________
Your E-mail and More On-the-Go. Get Windows Live Hotmail Free.
http://clk.atdmt.com/GBL/go/201469229/direct/01/
Re: Axis2-1.5.1 and user exceptions
Posted by Dennis Sosnoski <dm...@sosnoski.com>.
The Jibx2Wsdl tool can be used to easily convert most existing code to
an Axis2 (or JiBX/WS) web service. The output of Jibx2Wsdl includes
WSDL, schema, and JiBX binding definitions you can use to deploy your
service code on Axis2. The documentation page at
http://jibx.sourceforge.net/fromcode/jibx2wsdl.html gives an
introduction to using it, and the JiBX distribution comes with a set of
five examples
(http://jibx.sourceforge.net/fromcode/jibx2wsdl-examples.html) showing
some usage variations.
Jibx2Wsdl generates clean WSDL and schema definitions for most existing
code directly, but is also fully customizable, both at the service
definition and schema levels. The article at
http://www.ibm.com/developerworks/java/tutorials/j-jibx1/ discusses the
schema (and JiBX binding) generation from code part, including
customizations.
And yes, it includes handling of user exceptions - see the example code
for some details. General information on using JiBX in Axis2, including
information about the jibx-axis2 distribution package for updating older
versions of Axis2 to work with newer versions of JiBX (and to take
advantage of fixes to the Axis2/JiBX linkage code), is at
http://jibx.sourceforge.net/axis2/index.html
- Dennis
Dennis M. Sosnoski
XML and Web Services in Java
Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Pär Malmqvist wrote:
> Hello!
>
> I have been waiting for code-first approach to handle custom
> exceptions for about three years now...
>
> So I always have to use contract-first approach to get it to work.
> Its really time consuming but not much to do.
>
> Regards
> Pär Malmqvist
>
>
> ------------------------------------------------------------------------
> Date: Fri, 19 Feb 2010 09:15:03 -0500
> Subject: Re: Axis2-1.5.1 and user exceptions
> From: lima01@gmail.com
> To: axis-user@ws.apache.org
>
> I have been puzzled by this issue for long time. Seams like at this
> point, using contract-first approach is the only solution for now.
>
> But it will still be very very helpful if something can be done so
> code-first approach can work too. Axis1 definitely worked. I can
> imagine lots of people are using code-first approach because of its
> simplicity.
>
> Thanks!
>
> Li
>
> On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari
> <ma...@cardinis.com> wrote:
>
> Il 17/02/2010 3.53, glopezm ha scritto:
>
> Any thoughts/experiences with a similar issues with axis2?
>
>
> I use contract-first approach. My user exceptions extend Exception
> and have a field called faultMessage with getter getFaultMessage
> and setter setFaultMessage. The constructor prepares the
> faultMessage and sets it via setFaultMessage. The faultMessage is
> an object of a class generated by WSDL2Code from an XMLSchema type
> that describes my fault message, so that it implements ADBBean.
>
> In this way, when my code raises my user defined exception, Axis2
> recognizes the existence of the fault message and attaches it
> correctly to the fault returned to the client code.
>
> This is the result of my trial-and-errors researches of some years
> ago with Axis2 1.3 and it is working with Axis2 1.5 too. I think
> that you may find something else in this mailing list archive by
> me on this subject.
>
> --
> Mauro Molinari
> Software Designer & Developer
> E-mail: mauro.molinari@cardinis.com
>
>
>
>
> --
> Li Ma
> lima01@gmail.com
>
>
> ------------------------------------------------------------------------
> Hotmail: Powerful Free email with security by Microsoft. Get it now.
> <https://signup.live.com/signup.aspx?id=60969>
RE: Axis2-1.5.1 and user exceptions
Posted by Pär Malmqvist <pa...@hotmail.com>.
Hello!
I have been waiting for code-first approach to handle custom exceptions for about three years now...
So I always have to use contract-first approach to get it to work.
Its really time consuming but not much to do.
Regards
Pär Malmqvist
Date: Fri, 19 Feb 2010 09:15:03 -0500
Subject: Re: Axis2-1.5.1 and user exceptions
From: lima01@gmail.com
To: axis-user@ws.apache.org
I have been puzzled by this issue for long time. Seams like at this point, using contract-first approach is the only solution for now.
But it will still be very very helpful if something can be done so code-first approach can work too. Axis1 definitely worked. I can imagine lots of people are using code-first approach because of its simplicity.
Thanks!
Li
On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari <ma...@cardinis.com> wrote:
Il 17/02/2010 3.53, glopezm ha scritto:
Any thoughts/experiences with a similar issues with axis2?
I use contract-first approach. My user exceptions extend Exception and have a field called faultMessage with getter getFaultMessage and setter setFaultMessage. The constructor prepares the faultMessage and sets it via setFaultMessage. The faultMessage is an object of a class generated by WSDL2Code from an XMLSchema type that describes my fault message, so that it implements ADBBean.
In this way, when my code raises my user defined exception, Axis2 recognizes the existence of the fault message and attaches it correctly to the fault returned to the client code.
This is the result of my trial-and-errors researches of some years ago with Axis2 1.3 and it is working with Axis2 1.5 too. I think that you may find something else in this mailing list archive by me on this subject.
--
Mauro Molinari
Software Designer & Developer
E-mail: mauro.molinari@cardinis.com
--
Li Ma
lima01@gmail.com
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
https://signup.live.com/signup.aspx?id=60969
Re: Axis2-1.5.1 and user exceptions
Posted by Li Ma <li...@gmail.com>.
I have been puzzled by this issue for long time. Seams like at this point,
using contract-first approach is the only solution for now.
But it will still be very very helpful if something can be done so
code-first approach can work too. Axis1 definitely worked. I can imagine
lots of people are using code-first approach because of its simplicity.
Thanks!
Li
On Fri, Feb 19, 2010 at 6:42 AM, Mauro Molinari <mauro.molinari@cardinis.com
> wrote:
> Il 17/02/2010 3.53, glopezm ha scritto:
>
> Any thoughts/experiences with a similar issues with axis2?
>>
>
> I use contract-first approach. My user exceptions extend Exception and have
> a field called faultMessage with getter getFaultMessage and setter
> setFaultMessage. The constructor prepares the faultMessage and sets it via
> setFaultMessage. The faultMessage is an object of a class generated by
> WSDL2Code from an XMLSchema type that describes my fault message, so that it
> implements ADBBean.
>
> In this way, when my code raises my user defined exception, Axis2
> recognizes the existence of the fault message and attaches it correctly to
> the fault returned to the client code.
>
> This is the result of my trial-and-errors researches of some years ago with
> Axis2 1.3 and it is working with Axis2 1.5 too. I think that you may find
> something else in this mailing list archive by me on this subject.
>
> --
> Mauro Molinari
> Software Designer & Developer
> E-mail: mauro.molinari@cardinis.com
>
--
Li Ma
lima01@gmail.com
Re: Axis2-1.5.1 and user exceptions
Posted by Mauro Molinari <ma...@cardinis.com>.
Il 17/02/2010 3.53, glopezm ha scritto:
> Any thoughts/experiences with a similar issues with axis2?
I use contract-first approach. My user exceptions extend Exception and
have a field called faultMessage with getter getFaultMessage and setter
setFaultMessage. The constructor prepares the faultMessage and sets it
via setFaultMessage. The faultMessage is an object of a class generated
by WSDL2Code from an XMLSchema type that describes my fault message, so
that it implements ADBBean.
In this way, when my code raises my user defined exception, Axis2
recognizes the existence of the fault message and attaches it correctly
to the fault returned to the client code.
This is the result of my trial-and-errors researches of some years ago
with Axis2 1.3 and it is working with Axis2 1.5 too. I think that you
may find something else in this mailing list archive by me on this subject.
--
Mauro Molinari
Software Designer & Developer
E-mail: mauro.molinari@cardinis.com
RE: Axis2-1.5.1 and user exceptions
Posted by glopezm <gm...@gmail.com>.
I've continued doing some research about these issues and I've also found out
that there's another related issue in
http://issues.apache.org/jira/browse/AXIS2-3412. It is now clear for me that
custom exceptions are not working the way it should (at least for those like
me using the code first approach) and that throwing an AxisFault is the
solution/workaround to get the chance to generate the detail part manually
as I shown in my previous message. Even though in order to get the generated
client side code to work or handle the exceptions appropriately I had to do
some subtle changes regarding namespace uri within the stub while parsing
the response...
Any thoughts/experiences with a similar issues with axis2?
glopezm wrote:
>
> Thanks for your response Michael!!!
>
> That may be useful and I was not aware of that setting however I was
> trying to get axis2 to work pretty much the same way it was doing it in
> previous versions. Let me explain. Axis1 whenever you expose an operation
> as a web service (bottom up) it generates the wsdl:fault within the wsdl
> and also places the information within the "detail" tag so it could be
> mapped to whatever language you are working with in the other end. Now
> this is not working this way. If you expose the same operation through
> axis2 the exception would be present within the generated wsdl but no
> information regarding the exception is placed within the soap fault's
> detail tag so nobody will be able to deserialize anything.
>
> The good news is that while I was waiting for someone to come up with an
> idea/clue about this issue I found out a way to create and set the tag by
> declaring those methods/operations throwing AxisFault.
>
> This is not exactly what I was expecting and it is not my idea of a good
> solution however I can get it to work.
>
> The code for the operation in case anyone else raise the same issue is the
> following:
>
> public void sayHello(String str) throws AxisFault {
> //First get the message context
> MessageContext messageContext =
> MessageContext.getCurrentMessageContext();
>
> //Create the soap factory
> SOAPFactory soapFactory = null;
> if (messageContext.isSOAP11()) {
> soapFactory = OMAbstractFactory.getSOAP11Factory();
> } else {
> soapFactory = OMAbstractFactory.getSOAP12Factory();
> }
>
> //Create the detail with an error code and message
> SOAPFaultDetail soapFaultDetail = soapFactory.createSOAPFaultDetail();
> QName qName = new QName("http://test", "fault", "ns");
> OMElement detail = soapFactory.createOMElement(qName, soapFaultDetail);
>
> qName = new QName(null, "code", "ns");
> OMElement code = soapFactory.createOMElement(qName, null);
> code.setText("ERR-1234");
> detail.addChild(code);
>
> qName = new QName(null, "message", "ns");
> OMElement message = soapFactory.createOMElement(qName, null);
> message.setText("A readable message");
> detail.addChild(message);
>
> //Finally create the axis fault and populate it
> AxisFault af = new AxisFault("CustomException: The message");
> af.setDetail(detail);
> af.setFaultCode(new QName(null, "Receiver.userException", "soapenv"));
>
> throw af;
> }
>
> I'd say that all this stuff should be done by axis2 itself whenever a
> service operation throws a (checked) exception and this was the way it was
> working and it is currently working axis1.
>
> Please send me your comments if you have a better solution/idea.
>
> Thanks again for your response!
>
>
>
> Doughty, Michael wrote:
>>
>> In the axis2.xml file on the server/service side, you should see this
>> line:
>>
>> <parameter name="sendStacktraceDetailsWithFaults">false</parameter>
>>
>> Set that parameter to "true".
>>
>> Additionally, you might want to change this parameter as well:
>>
>> <parameter name="DrillDownToRootCauseForFaultReason">false</parameter>
>>
>> Setting that to "true" should force more stack trace detail to be sent
>> along with it, including the details of the root cause exception.
>>
>> -----Original Message-----
>> From: glopezm [mailto:gmlopez.mackinnon@gmail.com]
>> Sent: Monday, February 15, 2010 8:32 PM
>> To: axis-user@ws.apache.org
>> Subject: Axis2-1.5.1 and user exceptions
>>
>>
>> Hi,
>> I'm using axis2 v1.5.1 as it is stated in the subject of this message and
>> I've found that user exceptions are not being reported as they used to be
>> with axis1. If one declare an operation throwing an exception, whenever
>> the
>> exception is thrown the detail part of the soap fault element used to be
>> populated by axis1 with all exception data. However it is not working (at
>> least in this way) anymore. The <soapenv:Detail /> tag is empty. There is
>> a
>> bug that was filed almost two years ago
>> (https://issues.apache.org/jira/browse/AXIS2-3443) which explains the
>> situation very clearly but it has not even been assigned yet!
>>
>> Now I'm wondering whether someone is aware of a workaround to overcome
>> this
>> issue since it does not happen that the bug will be corrected anytime
>> soon
>> :-(.
>>
>> Thanks in advance for your help!
>> --
>> View this message in context:
>> http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27602949.html
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>>
>
>
--
View this message in context: http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27618457.html
Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2-1.5.1 and user exceptions
Posted by glopezm <gm...@gmail.com>.
Thanks for your response Michael!!!
That may be useful and I was not aware of that setting however I was trying
to get axis2 to work pretty much the same way it was doing it in previous
versions. Let me explain. Axis1 whenever you expose an operation as a web
service (bottom up) it generates the wsdl:fault within the wsdl and also
places the information within the "detail" tag so it could be mapped to
whatever language you are working with in the other end. Now this is not
working this way. If you expose the same operation through axis2 the
exception would be present within the generated wsdl but no information
regarding the exception is placed within the soap fault's detail tag so
nobody will be able to deserialize anything.
The good news is that while I was waiting for someone to come up with an
idea/clue about this issue I found out a way to create and set the tag by
declaring those methods/operations throwing AxisFault.
This is not exactly what I was expecting and it is not my idea of a good
solution however I can get it to work.
The code for the operation in case anyone else raise the same issue is the
following:
public void sayHello(String str) throws AxisFault {
//First get the message context
MessageContext messageContext =
MessageContext.getCurrentMessageContext();
//Create the soap factory
SOAPFactory soapFactory = null;
if (messageContext.isSOAP11()) {
soapFactory = OMAbstractFactory.getSOAP11Factory();
} else {
soapFactory = OMAbstractFactory.getSOAP12Factory();
}
//Create the detail with an error code and message
SOAPFaultDetail soapFaultDetail = soapFactory.createSOAPFaultDetail();
QName qName = new QName("http://test", "fault", "ns");
OMElement detail = soapFactory.createOMElement(qName, soapFaultDetail);
qName = new QName(null, "code", "ns");
OMElement code = soapFactory.createOMElement(qName, null);
code.setText("ERR-1234");
detail.addChild(code);
qName = new QName(null, "message", "ns");
OMElement message = soapFactory.createOMElement(qName, null);
message.setText("A readable message");
detail.addChild(message);
//Finally create the axis fault and populate it
AxisFault af = new AxisFault("CustomException: The message");
af.setDetail(detail);
af.setFaultCode(new QName(null, "Receiver.userException", "soapenv"));
throw af;
}
I'd say that all this stuff should be done by axis2 itself whenever a
service operation throws a (checked) exception and this was the way it was
working and it is currently working axis1.
Please send me your comments if you have a better solution/idea.
Thanks again for your response!
Doughty, Michael wrote:
>
> In the axis2.xml file on the server/service side, you should see this
> line:
>
> <parameter name="sendStacktraceDetailsWithFaults">false</parameter>
>
> Set that parameter to "true".
>
> Additionally, you might want to change this parameter as well:
>
> <parameter name="DrillDownToRootCauseForFaultReason">false</parameter>
>
> Setting that to "true" should force more stack trace detail to be sent
> along with it, including the details of the root cause exception.
>
> -----Original Message-----
> From: glopezm [mailto:gmlopez.mackinnon@gmail.com]
> Sent: Monday, February 15, 2010 8:32 PM
> To: axis-user@ws.apache.org
> Subject: Axis2-1.5.1 and user exceptions
>
>
> Hi,
> I'm using axis2 v1.5.1 as it is stated in the subject of this message and
> I've found that user exceptions are not being reported as they used to be
> with axis1. If one declare an operation throwing an exception, whenever
> the
> exception is thrown the detail part of the soap fault element used to be
> populated by axis1 with all exception data. However it is not working (at
> least in this way) anymore. The <soapenv:Detail /> tag is empty. There is
> a
> bug that was filed almost two years ago
> (https://issues.apache.org/jira/browse/AXIS2-3443) which explains the
> situation very clearly but it has not even been assigned yet!
>
> Now I'm wondering whether someone is aware of a workaround to overcome
> this
> issue since it does not happen that the bug will be corrected anytime soon
> :-(.
>
> Thanks in advance for your help!
> --
> View this message in context:
> http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27602949.html
> Sent from the Axis - User mailing list archive at Nabble.com.
>
>
>
--
View this message in context: http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27603868.html
Sent from the Axis - User mailing list archive at Nabble.com.
RE: Axis2-1.5.1 and user exceptions
Posted by "Doughty, Michael" <Mi...@bmc.com>.
In the axis2.xml file on the server/service side, you should see this line:
<parameter name="sendStacktraceDetailsWithFaults">false</parameter>
Set that parameter to "true".
Additionally, you might want to change this parameter as well:
<parameter name="DrillDownToRootCauseForFaultReason">false</parameter>
Setting that to "true" should force more stack trace detail to be sent along with it, including the details of the root cause exception.
-----Original Message-----
From: glopezm [mailto:gmlopez.mackinnon@gmail.com]
Sent: Monday, February 15, 2010 8:32 PM
To: axis-user@ws.apache.org
Subject: Axis2-1.5.1 and user exceptions
Hi,
I'm using axis2 v1.5.1 as it is stated in the subject of this message and
I've found that user exceptions are not being reported as they used to be
with axis1. If one declare an operation throwing an exception, whenever the
exception is thrown the detail part of the soap fault element used to be
populated by axis1 with all exception data. However it is not working (at
least in this way) anymore. The <soapenv:Detail /> tag is empty. There is a
bug that was filed almost two years ago
(https://issues.apache.org/jira/browse/AXIS2-3443) which explains the
situation very clearly but it has not even been assigned yet!
Now I'm wondering whether someone is aware of a workaround to overcome this
issue since it does not happen that the bug will be corrected anytime soon
:-(.
Thanks in advance for your help!
--
View this message in context: http://old.nabble.com/Axis2-1.5.1-and-user-exceptions-tp27602949p27602949.html
Sent from the Axis - User mailing list archive at Nabble.com.