RE: AxisFault and CustomException

2007-10-05 Thread Jay Zawar
Hi Pär,
 
I am also quite dazzled. At least in Axis2 1.2, the exception class generated 
for the service implements serialization methods, and in fact there are 
Hundreds () of lines of code for just a simple service. 
 
I do not know if this is the way to go. For a simple service just doing an 
addition of two numbers, and having 3 kinds of exceptions thrown, this is 
somewhat absurd (I pasted the code to a word document - 157 pages...). 
 
I don't think that component-code (business logic) should be mixed with code 
specfici to the Axis2 framework. I think that what WSDL2JAVA does should in 
fact for the most be generated and handled at runtime, or when the service is 
deployed - but all of this should be kept hidden to the developer. Also, when 
looking at the client code, it is just overbloated with 
service-/xml-/axis-specific code. 
 
I am now investigating methods to call webservices through EJB/JBoss via a 
stateless session facade. I hope to see a cleaner separation of business logic 
and "technical" code there. 
 
Keep me updated with your results, thanks in advance,
 
Jay

-Original Message-
From: Pär Malmqvist [mailto:[EMAIL PROTECTED]
Sent: jeudi 4 octobre 2007 15:20
To: axis-user@ws.apache.org
Subject: AxisFault and CustomException



Hello!
 
I have created a simple Axis2 service called MyService, se code below. It has 
one method: addOneToPositiveValue. If it is called with a negative value it 
throws a CustomException.
I have created a MyService.aar and deployed it on Axis2 1.3 and Tomcat 5.5.23
 
Then I created a simple client with wsdl2java and xmlbeans style.
 
Its really hard to get the CustomException in an easy way at the client side.
The AxisFault.getDetail() displays the name of the exception deep down in some 
kind of stacktrace. Thats all.
 
Can you Axis2 gurus have a look at it please?
If I haven't missed anything I think something has to be done to make this 
easier.
 
Thanks.
 
/Pär
 

package axis2test;
public class MyService {
public MyService() {
}
public int addOneToPositiveValue(int value) throws CustomException {
if(value < 1) {
throw(new CustomException());
}

return(value + 1);
}
}
 
package axis2test;
public class CustomException extends Exception {   
private static final long serialVersionUID = 9;
public CustomException() {
super();
}
public String toString() {
return(super.toString() + ' axis2test.CustomException');
}
}
 


This is a webservice for MyService




axis2test.MyService



  _  

Get news, entertainment and everything you care about at Live.com. Check it 
out!   



RE: AxisFault and CustomException

2007-10-04 Thread ROSSILLE Samuel
Hi

 

I'm not yet Axis2 guru, but i think i understand your problem :-)

 

When the java method of your service throws a method, axis translates the java 
exception into a soap fault. Soap fault is less structured than a java 
exception. It has only a soap:code and a soap:reason. Both are text elements. 
By default, axis sets this text to the value of the stack trace of the java 
exception (look at comments at the beginning of axis2.xml).

 

Then, when your client catches the soap fault, it raises an AxisFault, which is 
a java exception, but you have lost the structure, because of the fact that 
there is no equivalent in soap to the very structured java exception.

 

getDetail() just gives you soap element  which contains the code and the reason.

 

For myself, I would not use a soap fault, but encapsulate the result type of my 
method in a wrapper which contains an error code (one of the codes means that 
result ok). If the method fails, the error code gives you the exception and the 
wrapper object would be null:

 

package axis2test;
public class MyService {
public MyService() {
}
public MyDataType addOneToPositiveValue(int value) throws CustomException {



MyDataType result = new MyDataType();

if(value < 1) {
result.setErrorCode(1);

return 0;
}
else {

 result.setErrorCode(0)

 return(value + 1);
}  
}
}



package axis2test;
public class MyDataType {
private int data;

private int errorCode;

 

public getters, setters,...

 



}



Samuel Rossilel



De : Pär Malmqvist [mailto:[EMAIL PROTECTED] 
Envoyé : jeudi 4 octobre 2007 15:20
À : axis-user@ws.apache.org
Objet : AxisFault and CustomException

 


Hello!
 
I have created a simple Axis2 service called MyService, se code below. It has 
one method: addOneToPositiveValue. If it is called with a negative value it 
throws a CustomException.
I have created a MyService.aar and deployed it on Axis2 1.3 and Tomcat 5.5.23
 
Then I created a simple client with wsdl2java and xmlbeans style.
 
Its really hard to get the CustomException in an easy way at the client side.
The AxisFault.getDetail() displays the name of the exception deep down in some 
kind of stacktrace. Thats all.
 
Can you Axis2 gurus have a look at it please?
If I haven't missed anything I think something has to be done to make this 
easier.
 
Thanks.
 
/Pär
 

package axis2test;
public class MyService {
public MyService() {
}
public int addOneToPositiveValue(int value) throws CustomException {
if(value < 1) {
throw(new CustomException());
}

return(value + 1);
}
}
 
package axis2test;
public class CustomException extends Exception {   
private static final long serialVersionUID = 9;
public CustomException() {
super();
}
public String toString() {
return(super.toString() + ' axis2test.CustomException');
}
}
 


This is a webservice for MyService




axis2test.MyService




Get news, entertainment and everything you care about at Live.com. Check it 
out!