File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services and the fly likes Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark ""Bad types" error from BPEL invoke" Watch ""Bad types" error from BPEL invoke" New topic

"Bad types" error from BPEL invoke

nj toto

Joined: May 24, 2006
Posts: 4
I made a simple bpel procedure based on web service.
when I finished the bpel procedure, I release the bpel process on the tomcat.then I start tomcat engine, use the bpel address while give the operation name and parameters & values, the screen show the right result.
But when I use another method to invoke the bpel procedure ,there exist an error, I do not how to do with .
client invoke src code is as below:
import java.util.*;
import org.apache.axis.client.Call;
import org.apache.axis.client.Service;
import javax.xml.namespace.QName;
import org.apache.axis.server.AxisServer;
import org.apache.axis.MessageContext;
import org.apache.axis.description.OperationDesc;
import org.apache.axis.Message;
import org.apache.axis.encoding.XMLType;
import org.xml.sax.*;
import javax.xml.rpc.ParameterMode;

public class Customer

public static void main(String[] args) throws Exception
boolean tt=true;
String endpoint = "";
String operationName = "projectmanage";
Service service = new Service();
Call call = (Call) service.createCall();
call.addParameter( "invoke", XMLType.XSD_BOOLEAN, ParameterMode.IN );
call.invoke( new Object[] {new Boolean(tt)} );
the error exist is:
org.xml.sax.SAXException: Bad types (class java.lang.String -> class java.math.B:igInteger),

do you have the same question as me? If you have solved this problem ,please tell me the answer.thank you.
Ulf Dittmer

Joined: Mar 22, 2005
Posts: 42965
Are you sure that the error is caused by the client code? No String or BigInteger is sent by it, so it seems more likely that is is caused by another call which the BPEL process makes in turn.

You could use a tool like TCPMon to observe the SOAP that is sent over the wire, just to make that the calls generated are OK.
nj toto

Joined: May 24, 2006
Posts: 4
I think there exist error in the client invoke code,because if I use another method ,the screen will show the true result.The another method is through entering the bpel procedure address at the IE url.The bpel procedure address is "".
I think my code is not some error,so I do not use the tcpmonitor to watch the soap request.Tonight I will use tcpmonitor to watch the detail soap request to see if there are some strange.
I agree. Here's the link:
subject: "Bad types" error from BPEL invoke
It's not a secret anymore!